http://bugs.cinelerra.org/show_bug.cgi?id=466
------- Comment #1 from [EMAIL PROTECTED] 2008-02-09 07:37 +2 ------- I think I have a bit better idea of what's happening after experimenting some more (not having looked at the code). The Title video effect dialog lets you select the character encoding, and that's saved in the XML as an attribute of the <TITLE> element, so Cinelerra can interpret it fine. However, it still means that the XML is syntactically invalid if the encoding is other than UTF-8. I see a couple of approaches to solving this: 1) Leave the encoding and Cinelerra internals alone and just add an encoding="ISO-8859-1" to the XML file header. Better than writing a fixed ISO-8859-1 would be to write the encoding actually used by the TITLE tags (and other stored text). However, there could be several encodings used in several titles. In that case, this would produce syntactically valid XML but semantically invalid. Still, that's an improvement since with correct syntax any XML processing program will be able to at least read the files without erring out immediately. 2) Leave the header alone and convert the title text into UTF-8 upon writing the XML and convert it from UTF-8 into the correct encoding upon reading the file. This would be the right way to solve the problem, but considerably more work. Complicating things is that other text can be stored in the XML file, too, such as the track descriptions. That appears to be stored in a format specific to the font, which in my case also appears to be ISO-8859-1. Option 1) would work here too, as would option 2) by converting to/from the encoding used by the font. -- Configure bugmail: http://bugs.cinelerra.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
