On 11/06/2010 09:39 PM, Michał Rudolf wrote: Hi!
> Dnia 2010-11-06, sob o godzinie 20:46 +0100, Milan Zamazal pisze: >> The Czech translation file is encoded in ISO 8859-2 which means that all >> Scid translated texts are displayed incorrectly in standard UTF-8 >> environment. When I convert the file to UTF-8, translated texts in Scid >> are fine. >> >> Is there any reason to keep czech.tcl in ISO 8859-2 > Yes, Windows. > >> or can it be >> converted to UTF-8 to make Scid work correctly in common UTF-8 >> environment? > I tried to convince one of Scid maintainer (don't remember who it was > then) but it turned out that UTF-8 works well in Linux but is broken in > Windows. CP1250 works OK in Windows but of course is broken in Linux. Well, an apparently easy solution is to set the LOCAL for the scid startup environment. THIS is easy on Unix and AFAIK(! I don't do DOS for a very long time now) impossible on Windows. How about something like export LANG=cs_CZ.ISO8859-2 before starting Scid? A simple startup wrapper might do: #!/bin/bash export LANG=cs_CZ.ISO8859-2 exec scid > Therefore the maintainer decided to go for multiplatform solution, > choosing ISO8859-2 which is broken on both platforms... Well it is broken on Unix if you set the LOCAL to UTF8. It should of course work if you set the correct locale. It will probably take some time till Windows knows to handle UTF-8. Probably in Win 7? (Up to XP at least it is broken.) cu Alexander ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
