View Bug Details

IDProjectCategoryView StatusLast Update
0000686DCP-o-maticBugspublic2021-01-08 00:34
Reportercarl Assigned Tocarl  
PrioritynormalSeveritymajorReproducibilityunable to reproduce
Status closedResolutionfixed 
Platform64 bitOSWindowsOS Version8
Summary0000686: Subtitles rendered with squares
Description

Windows 8. Can't reproduce on Win XP, 7 or 8. Deleting LiberationSans ttf does not trigger it.

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredAverage

Activities

Igor.Voyt

2015-09-19 09:27

reporter  

111.png (723,424 bytes)

Igor.Voyt

2015-09-19 09:30

reporter   ~0000866

Last edited: 2015-09-19 09:31

Confirm. Windows 10x64, DCP-o-matic 2.3.4.
Also in subtitle-view window "subtitle" column is blank. I presume dcpomatic does not recognize non-latin characters

Igor.Voyt

2015-09-19 10:01

reporter   ~0000867

Last edited: 2015-09-19 14:13

I found the reason - if .srt or other subtitle file is created not in UTF-8 encoding, there will be squares. In my case it was windows-1251 (cp-1251)
So the solution is:
1) Creators should check encoding of their subtitle files and, if something wrong, they should convert them to UTF-8;

or

2) Add to DCP-o-matic some more encoding support, or add check of encoding

carl

2015-09-19 19:34

administrator   ~0000869

Igor, can you attach a .srt file that fails for you?

Igor.Voyt

2015-09-19 19:42

reporter  

SubRip.srt (62,709 bytes)

Igor.Voyt

2015-09-19 19:43

reporter   ~0000870

Last edited: 2015-09-19 19:46

Sure.
by mistake uploaded file "SubRip.srt". It is already converted to UTF-8
"SubRip_orig.srt" is original file in win-1251 encoding, that failed for me

Igor.Voyt

2015-09-19 19:45

reporter  

SubRip_orig.srt (46,931 bytes)

carl

2015-09-19 20:06

administrator   ~0000871

OK, thanks. I'm not sure if your problem is the same as the original reporter's... I tried their sub files (which were UTF-8) and they worked for me. I see your problem here though. I'm not sure what we can do except point out invalid UTF-8 in imported .srt files; it's not possible to tell what encoding a file is in just by looking at it...

Igor.Voyt

2015-09-19 20:10

reporter   ~0000872

You mean dcp-o-matic can't recognize encoding? Or user can't just by looking?

carl

2015-09-20 00:16

administrator   ~0000874

You can't be 100% sure what encoding a text file is in; the best you can do is to guess. I don't know whether DCP-o-matic should try, or just insist on UTF-8.

Igor.Voyt

2015-09-20 00:23

reporter   ~0000875

Well, if not open the file, of course we can't know exactly, what encoding it has. But we can see encoding by using lightweight text editors like notepad++ (windows), gedit (ubuntu), textmate (os x).
I think at the moment it is the best solution - check manually.

carl

2015-09-25 22:13

administrator   ~0000886

Encoding problems should be much reduced in 2.3.6; libicu is used to guess the incoming character set and convert it.

carl

2019-11-20 11:48

administrator   ~0003597

I assume this is OK now since we use libicu.

Bug History

Date Modified Username Field Change
2015-09-09 09:09 carl New Bug
2015-09-14 09:15 carl Description Updated
2015-09-19 09:27 Igor.Voyt File Added: 111.png
2015-09-19 09:30 Igor.Voyt Note Added: 0000866
2015-09-19 09:30 Igor.Voyt Note Edited: 0000866
2015-09-19 09:31 Igor.Voyt Note Edited: 0000866
2015-09-19 10:01 Igor.Voyt Note Added: 0000867
2015-09-19 10:02 Igor.Voyt Note Edited: 0000867
2015-09-19 14:13 Igor.Voyt Note Edited: 0000867
2015-09-19 19:34 carl Note Added: 0000869
2015-09-19 19:42 Igor.Voyt File Added: SubRip.srt
2015-09-19 19:43 Igor.Voyt Note Added: 0000870
2015-09-19 19:45 Igor.Voyt File Added: SubRip_orig.srt
2015-09-19 19:46 Igor.Voyt Note Edited: 0000870
2015-09-19 20:06 carl Note Added: 0000871
2015-09-19 20:10 Igor.Voyt Note Added: 0000872
2015-09-20 00:16 carl Note Added: 0000874
2015-09-20 00:23 Igor.Voyt Note Added: 0000875
2015-09-25 22:13 carl Note Added: 0000886
2015-10-30 13:34 carl Assigned To => carl
2015-10-30 13:34 carl Status new => acknowledged
2019-11-20 11:48 carl Status acknowledged => resolved
2019-11-20 11:48 carl Resolution open => fixed
2019-11-20 11:48 carl Note Added: 0003597
2021-01-08 00:34 carl Status resolved => closed