[kdewebdev-site] kdewebdev.org proposals
Chris Hornbaker
chrishornbaker at earthlink.net
Wed Apr 28 04:33:42 EDT 2004
On Wednesday 28 April 2004 02:17, David Joham wrote:
> On Tuesday 27 April 2004 08:08 pm, David Joham wrote:
> > I'd also like to ask a question of both you and D Reddish. At HP, we have
> > a simple table structure layed out like the following...
> >
> > | Localization ID | English Text | Klingon Text | .....
> >
> > -------------------------------------------------------------------------
> >-- --------------------------
> >
> > | locIDShuttlecraft | Shuttlecraft | lupDujHom | ....
> >
> > *http://www.amazon.com/gp/reader/0671543490/ref=sib_rdr_next1_2/002-00085
> >25 -0958475?%5Fencoding=UTF8&p=S00B&ns=1#reader-page
> >
> > And when we want some text, we (in a nutshell) call something like
> >
> > String locString = locSubsystem.getL10NString(locIDShuttlecraft);
> >
> >
> > I'm not predisposed to this solution, but I do find it simple and fairly
> > easy to work with. I'm curious if either of you considered it and if so,
> > why you decided it was not worth pursuing? Is it a PHP vs. Java thing?
>
> well poo. It never fails, you send out pseudo code and then realize the
> pseudo code had a mental time compile error...
>
> Of course the following line
> String locString = locSubsystem.getL10NString(locIDShuttlecraft);
>
> shoud be
> String locString = locSubsystem.getL10NString(locIDShuttlecraft, <langID>);
>
> so the localization subsystem knows which string to get....
>
Mine does this more or less. Instead of setting the lang code every time a
string is retrieved, I just set it once.
And the problem with IDs, IMO, is that strings changed often.
--
Christopher Hornbaker
Jabber ID: Jilks at jabber.org Email: chrishornbaker at earthlink.net
Join the Free State Project! http://www.freestateproject.org
"Liberty in Our Lifetime"
Was I helpful? Let me know! http://svcs.affero.net/rm.php?r=Jilks
More information about the kdewebdev-site
mailing list