Re: internationalisation
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Fri, 24 Feb 2006 08:21:37 -0800
I can't argue with that. It amazes me how localization is often left until
the end of the project and then becomes a big nightmare. If people just
programmed with the intention of doing translations (or switching from MBCS
to Unicode which they will likely do at some point) our lives would be
easier. At least Microsoft *has* a paradigm now. It has alot of growing to
do, but it is a process.
Tom
"KMA" <kma@xxxxxxxxxxxxxxx> wrote in message
news:dtmd2f$l34$1@xxxxxxxxxxxxxxxxxxxx
Tom,
This is whay I hinted that the devil is in the detail. There's always
something lurking about ready to pop up.
My point is that if you go down the official route then you end up with a
monumnetal maintenance overhead. You also end up with very well polished
applications.
I doubt if many of us do, or would want to, work on a software project
that has the luxury of enough time to make a really thorough job of
translation.
And so I've tried to develop a workable framework for dealing with
localisation without putting the brakes on new development. It's far from
perfect and I'd love to hear alternatives.
KMA
.
- References:
- internationalisation
- From: David Webber
- Re: internationalisation
- From: KMA
- Re: internationalisation
- From: Tom Serface
- Re: internationalisation
- From: KMA
- internationalisation
- Prev by Date: Re: Why I couldn't use this function?
- Next by Date: Re: Getting child window co-ordinates
- Previous by thread: Re: internationalisation
- Next by thread: Re: internationalisation
- Index(es):
Relevant Pages
|