Changes between Version 1 and Version 2 of Ticket #6021, comment 5


Ignore:
Timestamp:
Dec 16, 2016, 6:51:18 AM (4 years ago)
Author:
erikbs
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6021, comment 5

    v1 v2  
    1 Thanks, I think I managed to do it, at least I got an email telling me that the list admin had been notified.
     1Thanks, the patch has now been added to the list.
    22
    33Two things remain:
     
    552. UTF-16, as is required by the format specification (only Big Endian UTF-16 is required, UTF-16 is optional)
    66
    7 I will take a look at the first one, but probably not the second, at least not now. According to the specification, UTF-8 is to be assumed unless there is a UTF-16 BOM, and I am afraid I will break something if I even try to solve this. Besides, I have never encountered UTF-16 encoded subtitles and UTF-16 support is broken both with and without my patch (in different ways).
     7I will take a look at the first one, but probably not the second, at least not now. According to the specification, UTF-8 is to be assumed unless there is a UTF-16 BOM, and I am afraid I will break something if I try to solve this without knowing the code. Besides, I have never encountered UTF-16 encoded subtitles and UTF-16 support is broken both with and without my patch (in different ways).
    88
    99PS. Ticket #5429 is about the same problem. I did not realize that my ticket was a duplicate until after I had submitted it.