>
> There are lots of ways to do this. In my case, I have over a thousand
controls (sounds a lot, but
> when you add up all the labels, group boxes etc!), so maintaining a perl
hash becomes problematic -
> ideally, the translations should be in a separate file or database, so
they can be worked on
Hi,
I was really impressed by your use of French and Spanish - until I read the
google statement:)
There are lots of ways to do this. In my case, I have over a thousand controls
(sounds a lot, but when you add up all the labels, group boxes etc!), so
maintaining a perl hash becomes problematic
Hi,
You can possibly take a look to Locale or i18n package.
http://search.cpan.org/modlist/Internationalization_Locale/Locale
Laurent.
- Original Message -
From: Jez White
To: Win32-GUI
Sent: Tuesday, May 11, 2004 2:15 PM
Subject: [perl-win32-gui-users] Internationaliza
If the text were to always be the same, I would say yes it would be a useful
function. But if the text would usually be customized (which I would
expect), then it might be easier to just use a hash of hashes:
$text{'English'}{'Window'}='My Window';
$text{'Spanish'}{'Window'}='Mi Ventana';
$text{'
Hi,
Has anyone tried to create an application for Win32::GUI that supports various
natural languages?
I've worked on production applications that had to provide this kind of support
in the past, so I've got a rough idea how the whole process should work. Adding
the various windows API internat
5 matches
Mail list logo
