Some days ago I've had a look into this. The basic problem is, that the file names in zip-files have no defined encoding. We could use chardet, but it is not relyable for such short strings (even though wrong detection does not need to cause problems).
My approach would be to ignore the filenames and derive new filenames from the string stored in the theme XML. This would works fine for now. As soon we want to store multiple files of the one type in the same theme it is not trivial anymore to assign the data to the generated filenames. To be future proove we either have to restrict the filenames of additional files inside a theme or use the proposed solution only for 1.x themes while expecting filenames in 2.x themes being utf8 encoded. Which one of these options should we prefere? -- You received this bug notification because you are a member of OpenLP Core, which is subscribed to OpenLP. https://bugs.launchpad.net/bugs/882819 Title: Problem with v1 theme with non-english characters in the name Status in OpenLP - Worship Presentation Software: Confirmed Bug description: Windows 7, 64 bit, Home Premium and Vista Home Premium OpenLP 1.9.7 Importing a v1 theme with non-english characters in the name results in three times of this dialog: Error File is not a valid theme The content encoding is not UTF-8 and one time of this dialog: Validation Error: File is not a valid theme This defect is related to Windows only since non-english characters in filenames are allowed from Win95 and onwards. Attached example theme To manage notifications about this bug go to: https://bugs.launchpad.net/openlp/+bug/882819/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openlp-core Post to : [email protected] Unsubscribe : https://launchpad.net/~openlp-core More help : https://help.launchpad.net/ListHelp
