[FFmpeg-trac] #11240(ffmpeg:new): non-ASCII characters in report filename create wrong log filename on Windows (was: [Windows] Non-ASCII characters in command incorrectly reflected in "-report")

FFmpeg trac at avcodec.org
Fri Oct 25 21:01:18 EEST 2024


#11240: non-ASCII characters in report filename create wrong log filename on
Windows
-------------------------------------+----------------------------------
             Reporter:  m.feriati    |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  ffmpeg
              Version:  unspecified  |               Resolution:
             Keywords:  FFREPORT     |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+----------------------------------
Changes (by Marton Balint):

 * type:  enhancement => defect
 * component:  avutil => ffmpeg
 * summary:
     [Windows] Non-ASCII characters in command incorrectly reflected in
     "-report"
     =>
     non-ASCII characters in report filename create wrong log filename on
     Windows

Comment:

 Replying to [comment:2 MasterQuestionable]:
 > ͏    Likely Windows problem.
 > ͏    See also: https://trac.ffmpeg.org/ticket/11241#comment:5
 >
 > ͏    Windows is known to be buggy with Unicode support.
 > ͏    I guess this one is probably caused by the shell and OS's handling.
 > ͏    Likely not addressable from FFmpeg.

 No, ffmpeg has full unicode filename support even on windows. The problem
 is likely that the ffreport file is opened using fopen() instead
 fopen_utf8().
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11240#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list