Author: Michael Yee
Date: 04:48:41 03/19/05
Go up one level in this thread
On March 19, 2005 at 07:01:43, Peter Schäfer wrote: >On March 18, 2005 at 20:32:08, Michael Yee wrote: > > >>(6) translation/localization mechanism: >>- options are stored in options.xci file (with ids, no translations) >>- translations are stored in options.en, options.de, etc. > >That's quite flexible, but there need to be a convention where these files are >stored. >What if GUI and engine connect over a network ? >Or GUI has no access rights to the engine's directory ? > >There should be a way to transmit the options and translation through the >protocol. > >-- Peter Very good point... The main reason for having the files was so that other people could provide translations by just adding a new file. However, it should be up to the engine programmer if they want to use such a procedure for managing translations. Maybe the new translation mechanism can be something like: ----- xci option ... option ... option XCI_Language type language default en var en var de ... translation language en name king-safety value "King Safety" name ... value ... translation language de name king-safety value "..." name ... readyok ----- And the engine itself can choose to look in its local directory (or wherever) for translations. The XCI spec can suggest this, but it won't be mandatory. Michael
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.