[FFmpeg-trac] #5721(undetermined:new): bug in AviSynth reader

[FFmpeg]

#5721: bug in AviSynth reader
-------------------------------------+-------------------------------------
             Reporter:  stax76       |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  avisynth     |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by stax76):

 I made a test using a sample file Bär.mkv (German Umlaut) on CP 1252 (West
 Europe) and saved the avs file not as CP 1252 but UTF-8 without BOM,
 VirtualDub2, MPC-BE and ffmpeg are still able to open this, even though
 avs files are supposed to be encoded in the CP of the system, CP 1252
 here.

 I think it can be closed.

 But I also think ffmpeg should use a Unicode manifest to enforce UTF-8,
 there might be some complaints then, it might break some applications etc.

 There is clearly a new trend for enforcing UTF-8, see here:

 https://github.com/staxrip/staxrip/wiki/AviSynth-Unicode-support-on-
 Windows-10-1903

 If it won't be supported I guess I will patch it somehow.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5721#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker