Just to let you know: Troy and I talked about it in the chat. We'll go for option 4 for now, so that UTF-8 locales can be added after I verified that UTF-8 will work with Sword internally. Existing locales will remain, and all will get an encoding line. At some point in future we might use only UTF-8.... This way older apps won't break.
I'll give it a try, if somebody wants to help, just speak up. mg Am Dienstag, 13. Januar 2004 16:37 schrieb Martin Gruner: > Hey all, > > now that 1.5.7 is released, I'd like to propose a change to the locale > system. > > It seems that in BibleTime we can only use the locales which are encoded in > the local 8bit encoding of the user. Selecting others won't work, as well > as the windows specific locales (cp*). > > There are different possible approaches to this situation: > > 1. Change nothing. Rremains broken. ;) > 2. Add UTF-8 locales for each language (Encoding= line in config file). > Apps can then select which locale file (local or UTF-8) to use. No overhead > in apps, maintenance overhead in Sword. > 3. Convert everything to UTF-8. Apps then need to convert to local, if > necessary. Small overhead in apps. > 4. Add Encoding= line to all locale files and have apps convert strings to > UTF-8 themselves, if necessary. Larger overhead in apps. > > I'd vote for number 3, but not sure if that is a possibility for Windows > based programs. Any other suggestions/corrections? I'd like to volunteer > for this kind of task (conversion etc.), in case I should be able to do it. > Looking forward to hear what you think. > > Martin > > _______________________________________________ > sword-devel mailing list > [EMAIL PROTECTED] > http://www.crosswire.org/mailman/listinfo/sword-devel _______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel
