At long last and after much beating about the head, I've implemented an
infrastructure such that users can create "Locale" files. Locale files can
change *all* Sailwave User Interface elements into the language of your
choice (menus, entry prompts, status bar test, button text etc etc). This
also means you can have alternative English locales. Locale strings specify
the hot keys, so the standard hot keys can also be fiddled with.
Locale files are .ini files that reside in Sailwave/Locales. Sailwave will
ship with just one: UKEnglish.ini. Others will be downloadable from the web
site if there are volunteers to create *AND* maintain them. We can probably
do a deal about unlimited registration or something for volunteers; regional
variations welcome etc.
To test the infrastructure I've just created the UKEngligh locale file with
the entry prompts for Edit+Competitor - this is the only window that will
respond - and it's only the prompts that respond. The file is attached. To
create your own Locale file, copy the attached and edit it appropriately and
then when 1.44beta4 is available, plonk it in Sailwave/Locales. It'll then
be selectable from the Locate Tab in Edit+GlobalOptions. I would be
grateful for some tests in other languages before I enable the rest of the
app...
Tested tonight, seems to work. Will upload later or tomorrow...
Regards,
Colin
···
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
Hi Colin Jenkins,
At long last and after much beating about the head, I've implemented an
infrastructure such that users can create "Locale" files. Locale files can
change *all* Sailwave User Interface elements into the language of your
choice (menus, entry prompts, status bar test, button text etc etc). This
also means you can have alternative English locales. Locale strings specify
the hot keys, so the standard hot keys can also be fiddled with.
That's great!
Locale files are .ini files that reside in Sailwave/Locales. Sailwave will
ship with just one: UKEnglish.ini. Others will be downloadable from the web
site if there are volunteers to create *AND* maintain them. We can probably
do a deal about unlimited registration or something for volunteers; regional
variations welcome etc.
To test the infrastructure I've just created the UKEngligh locale file with
the entry prompts for Edit+Competitor - this is the only window that will
respond - and it's only the prompts that respond. The file is attached. To
create your own Locale file, copy the attached and edit it appropriately and
then when 1.44beta4 is available, plonk it in Sailwave/Locales. It'll then
be selectable from the Locate Tab in Edit+GlobalOptions. I would be
grateful for some tests in other languages before I enable the rest of the
app...
I've translated a part of the .ini into the german language. The
de_DE.ini file is attached.
Tested tonight, seems to work. Will upload later or tomorrow...
The test was ok.
···
On Thursday, August 08, 2002, 11:47:14 PM you wrote:
Regards,
Colin
--
Regards
Andreas Kaiser mailto:akaiser@ssvep.de
Segelverein Einheit Plauen (SSVEP)
Hi Andreas,
Thanks for that. One thing that we're going to come across is the screen
size allocated to the entry prompts etc, especially for something like
German; many of your strings will possibly not fit as it stands. I'll need
to reengineer each window as I move it over to be locale based... I'll try
and get some other screens locale-ised ASAP. Let me know if you have any
ideas for improvements etc.
Regards,
Colin
···
-----Original Message-----
From: Andreas Kaiser [mailto:listen@vocote.de]
Sent: 09 August 2002 09:13
To: sailwave@yahoogroups.com
Subject: Re: [sailwave] Locales/Internationalisation
Hi Colin Jenkins,
On Thursday, August 08, 2002, 11:47:14 PM you wrote:
At long last and after much beating about the head, I've implemented an
infrastructure such that users can create "Locale" files. Locale files
can
change *all* Sailwave User Interface elements into the language of your
choice (menus, entry prompts, status bar test, button text etc etc). This
also means you can have alternative English locales. Locale strings
specify
the hot keys, so the standard hot keys can also be fiddled with.
That's great!
Locale files are .ini files that reside in Sailwave/Locales. Sailwave
will
ship with just one: UKEnglish.ini. Others will be downloadable from the
web
site if there are volunteers to create *AND* maintain them. We can
probably
do a deal about unlimited registration or something for volunteers;
regional
variations welcome etc.
To test the infrastructure I've just created the UKEngligh locale file
with
the entry prompts for Edit+Competitor - this is the only window that will
respond - and it's only the prompts that respond. The file is attached.
To
create your own Locale file, copy the attached and edit it appropriately
and
then when 1.44beta4 is available, plonk it in Sailwave/Locales. It'll
then
be selectable from the Locate Tab in Edit+GlobalOptions. I would be
grateful for some tests in other languages before I enable the rest of the
app...
I've translated a part of the .ini into the german language. The
de_DE.ini file is attached.
Tested tonight, seems to work. Will upload later or tomorrow...
The test was ok.
Regards,
Colin
--
Regards
Andreas Kaiser mailto:akaiser@ssvep.de
Segelverein Einheit Plauen (SSVEP)
http://groups.yahoo.com/group/sailwave
http://www.sailwave.com/
Convert to daily digest of emails send blank email to:
sailwave-digest@yahoogroups.com
To unsubscribe from this group, send an email to:
sailwave-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
Hi Colin,
Hi Andreas,
Thanks for that. One thing that we're going to come across is the screen
size allocated to the entry prompts etc, especially for something like
German; many of your strings will possibly not fit as it stands. I'll need
to reengineer each window as I move it over to be locale based... I'll try
and get some other screens locale-ised ASAP. Let me know if you have any
ideas for improvements etc.
Problems with string lengths are possible. One way to solve this is
the abbreviation of this long word. But the dynamic change of window
size is the better solution (however more time consuming for you).
Another point is the "key-char" (&). The translator must be carefull,
because a double assignment of a "key-char" doesn't work well. (This
problem is not so important).
It would be nice if I could be the maintainer for the german
translation. So I can give something back for this great piece of
software!
One wish from my list is a new field in the competitor dialog for the
Club of the crew. Sometimes the crew and the helm are from different
clubs.
On our last regatta I've tested sailwave and is was a great experience
how easy it was. Now, where localisation is supported, sailwave is the
regatta scoring software #1 for our club!
Thanks!
PS: Have you ever thought about a XML file format instead the .blw
file format? I think that you must parse the .blw file too. With a XML
file you have more flexibility. XML as standard file format were a
"nice-to-have"
···
On Friday, August 09, 2002, 10:50:04 AM you wrote:
Regards,
Colin
--
Regards
Andreas Kaiser mailto:akaiser@ssvep.de
Segelverein Einheit Plauen (SSVEP)
Hi Andreas,
I'll publish a new web page soon identifying who is allocated to and
maintaining the locale files for each Language; and of course will put you
down for German. As the English locale file grows, you'll need to update
the German one. To aid this I'll add a merge facility to merge in new
locale keys from one locate to another - this way you can just do the merge
form EN to DE every now and again and scan for those keys still in English.
It would be a nightmare doing it by hand.
Regards,
Colin
···
-----Original Message-----
From: Andreas Kaiser [mailto:listen@vocote.de]
Sent: 09 August 2002 10:39
To: sailwave@yahoogroups.com
Subject: Re: [sailwave] Locales/Internationalisation
Hi Colin,
On Friday, August 09, 2002, 10:50:04 AM you wrote:
Hi Andreas,
Thanks for that. One thing that we're going to come across is the screen
size allocated to the entry prompts etc, especially for something like
German; many of your strings will possibly not fit as it stands. I'll
need
to reengineer each window as I move it over to be locale based... I'll
try
and get some other screens locale-ised ASAP. Let me know if you have any
ideas for improvements etc.
Problems with string lengths are possible. One way to solve this is
the abbreviation of this long word. But the dynamic change of window
size is the better solution (however more time consuming for you).
Another point is the "key-char" (&). The translator must be carefull,
because a double assignment of a "key-char" doesn't work well. (This
problem is not so important).
It would be nice if I could be the maintainer for the german
translation. So I can give something back for this great piece of
software!
One wish from my list is a new field in the competitor dialog for the
Club of the crew. Sometimes the crew and the helm are from different
clubs.
On our last regatta I've tested sailwave and is was a great experience
how easy it was. Now, where localisation is supported, sailwave is the
regatta scoring software #1 for our club!
Thanks!
PS: Have you ever thought about a XML file format instead the .blw
file format? I think that you must parse the .blw file too. With a XML
file you have more flexibility. XML as standard file format were a
"nice-to-have"
Regards,
Colin
--
Regards
Andreas Kaiser mailto:akaiser@ssvep.de
Segelverein Einheit Plauen (SSVEP)
http://groups.yahoo.com/group/sailwave
http://www.sailwave.com/
Convert to daily digest of emails send blank email to:
sailwave-digest@yahoogroups.com
To unsubscribe from this group, send an email to:
sailwave-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
Andreas,
It would be nice if I could be the maintainer for the german
translation. So I can give something back for this great piece of
software!<
I'm going to have to generalise things; the current internationalisation
implementation is too hard to maintain my end. It'll be a similar system
WRT the locale files except that the string will take the form
English text = my text
e.g.
butterfly=sc&hmetterling (sp?)
I am going=Ich &gehe
Case insensitive matches.
For now it'll be window *in*dependent and we may well end up with
ambiguities but we can sort that out later with contexts of window names
somehow. The advantage to you is that the *whole* of Sailwave (menus,
status text, buttons, prompts etc) becomes available for translation *now*;
it's a completely generic solution. When each window is opened in Sailwave
it'll scan (cached for speed) the file for translation strings and apply
them to menus, prompts and buttons etc appropriately. The downside is that
if I change some UI text - your UI will jump back to English for tat element
until you update your file. I can arrange things such that Sailwave will
ask you translation strings as you use it, if they are missing...
Sorry to mess you around, it just seems a more practical, if less exact way
forward; limited time and all that; is this OK with you...?
Regards,
Colin
www.sailwave.com
···
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
Hi Colin,
Andreas,
I'm going to have to generalise things; the current internationalisation
implementation is too hard to maintain my end. It'll be a similar system
WRT the locale files except that the string will take the form
English text = my text
e.g.
butterfly=sc&hmetterling (sp?)
I am going=Ich &gehe
Correct 
Case insensitive matches.
For now it'll be window *in*dependent and we may well end up with
ambiguities but we can sort that out later with contexts of window names
somehow. The advantage to you is that the *whole* of Sailwave (menus,
status text, buttons, prompts etc) becomes available for translation *now*;
it's a completely generic solution. When each window is opened in Sailwave
it'll scan (cached for speed) the file for translation strings and apply
them to menus, prompts and buttons etc appropriately. The downside is that
if I change some UI text - your UI will jump back to English for tat element
until you update your file.
This way is ok. The downside is not a problem, it's a hint for the
translator.
I can arrange things such that Sailwave will
ask you translation strings as you use it, if they are missing...
This is not necessary, I think. If you use an source code versioning
system then you can send a message for all language maintainers.
Sorry to mess you around, it just seems a more practical, if less exact way
forward; limited time and all that; is this OK with you...?
It's no problem for me, because I'll use SW again in the next year.
···
On Tuesday, August 13, 2002, 2:14:26 PM you wrote:
Regards,
Colin
www.sailwave.com
--
Regards
Andreas Kaiser mailto:akaiser@ssvep.de
Segelverein Einheit Plauen (SSVEP)
Andreas,
This way is ok. The downside is not a problem, it's a hint for the
translator.<
OK, I'll tweak it tonight if I get the chance...
Regards,
Colin
···
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002