Re: Multilanguage support in MFC application
"Mihai N." <email@example.com> wrote in message
I am by default against skin/custom control solutions.
In my opinion:
- they are less intuitive than regular UI
- more trouble to develop
- more troube to localize
- in general they have bad support for accessibility and i18n
- they totaly ignore my preferences of fonts, font sizes, colors
- they use proprietary solutions that are hard to handle in TM tools
(most TM tools undestand RC files, can preview dialogs, giving context
to the translators, ca validate for truncations, double hot-keys and
accelerators, inconsistent use of %s/%d and many other things.)
You throw all this away when you come with a proprietary skin solution.
Your points are valid, but so are the ones who promote skins:
- they are more usable because they represent
a physical object that some people (probably not developers)
can better relate to
- they present relevant info in one glance without the possibility
of scrolling (scrolling can be unusable)
- they are perceived as cooler and thus more of the target audience
actually uses it.
- they look the same regardless of which Windows version is used,
and there is no shortage of opinion that Vista looks "crappy".
Good translators are good translators and that's it. They don't know/want
to do resizing, or such technical work. If they are good translators, they
will refuse a contract if asked to do such work (since they are good at
what they do, they can afford to pick their projects).
The solution is to let the technical work for technical people
OK, I'll rephrase my question. Can you suggest a good outsourcing company
that provides the services of both localization engineers and translators?