Author: Alessandro Scotti
Date: 01:29:21 03/15/05
Go up one level in this thread
On March 15, 2005 at 03:25:00, Dieter Buerssner wrote: >Lance mentioned some internalization issue. I also thought about this, when I >implemented UCI for the first time. But I see no solution - Lance, do you have >any idea in mind? The only thing, I can think of would be to note the >(preferred) language from GUI to engine at the first command. An engine might >want to give options in different languages. I think an engine should not have to deal with such issues. Rather, the translation of option names and values should be put in a separate file that is read by the GUI. This has the advantage of simplifying the engine and also allowing anyone to add a language without having to change the engine itself. BTW this solution could be already applied to existing UCI, just use the current option names and values as identifiers (of themlselves). >Another internationalization issue: May strings contain special chars? My engine >reports my name as "Dieter Buerssner", which is a typical transliteration to the >English alphabet of the proper "Dieter Bürßner". Shredder Classic can display >the proper spelling on my computer, but I always wondered what a user on say a >Russian or Chinese PC would see? Also, such things might be needed to be defined >for each OS seperately? Which would make them rather horrible for an engine >intended to be very portable. If this is an issue, maybe support for Unicode should be designed into the protocol (strings can be streamed using the UTF-8 encoding). Otherwise, special characters are dependent on the current code page and will look different when the engine is run in different countries.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.