[FFmpeg-trac] #3718(avformat:reopened): ffmpeg does not correctly read input text file.

[FFmpeg]

#3718: ffmpeg does not correctly read input text file.
-------------------------------------+------------------------------------
             Reporter:  Maxwell175   |                    Owner:
                 Type:  enhancement  |                   Status:  reopened
             Priority:  wish         |                Component:  avformat
              Version:  git-master   |               Resolution:
             Keywords:  concat       |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+------------------------------------

Comment (by Maxwell175):

 Replying to [comment:4 Cigaes]:
 > A byte order mark is an invisible neutral character as human-readable
 text goes, but it is nonetheless a character, and therefore included in a
 computer-readable text. Supporting it wold be possible, but verly low in
 my priority list, and only if it can be done in a generic way that does
 not require changing all parts of the code that read text files.

 Since I am also a programmer, though not a C programmer, I looked around a
 bit and found some code samples:
 https://workspaces.codeproject.com/user-8645021/reading-
 utf-8-with-c-streams. Since to download from there you need to register, I
 have also uploaded it to another place so you may download it
 http://www.mediafire.com/download/5hsc5h2j71avw1g/utf8code.zip.
 Also, shouldn't there be a separate function that gets called from all the
 places to read text files, so you would not have the same code repeated
 many times.
 [[BR]]
 [[BR]]
 [[BR]]
 > As a side note, you will get the same problem from a lot of other
 program, so you should definitely try to learn how to produce files with
 just what you want in them and not what any random API decides to add.

 This is NOT some "random" API. Many people use this method, especially
 beginners. Since I know other methods, I can use them, but still...

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