Well, I'd just say 'Buyer beware'. We've had management push to fire developers for doing this. Our Japanese customers were extremely sensitive. Germans as well now that I think about it..
John- On Thu, Jan 28, 2010 at 11:24 AM, Martin Makundi <[email protected]> wrote: > I forgot to mention that it would be half as fun as much as it is > useful ;) Maybe it would be funny for the users too ;) > > BTW: Google itself uses its translation engine to provide localized > UI:s for different languages, and yes, they are funny sometimes. > > ** > Martin > > 2010/1/28 John Armstrong <[email protected]>: >> A default English locale is probably better then gibberish and >> automated calls to Google Translate will get you gibberish. >> >> 1) Online translation engines are terrible. Just yesterday I used >> google translate to tell me how to translate the word 'Bond', it told >> me '007' (true, try it, uppercase B is important). My UI lead is Dutch >> and she says that, while she appreciates the effort, googles >> translations are not making a lot of sense. >> >> 2) Its near impossible to do variable interpolation in any automated way. >> >> We only roll out actually translated languages and getting >> translations is cheap enough these days. We only automate via Google >> Translate for initial QA smoke testing and then pass those files to >> Human Beings who tend to be pretty good at this sort of thing. >> >> I recommend GetText if your looking to 'back localize' an app. We just >> localized a few thousand lines of code using its macro replacement >> method, ran the bundled perl script and generated 10 localization >> files in seconds that are ready for translation. >> >> There is a lib for that : >> http://xnap-commons.sourceforge.net/gettext-commons/ >> >> J >> >> On Thu, Jan 28, 2010 at 10:11 AM, Edward Zarecor >> <[email protected]> wrote: >>> I think Martin's idea is that in the absence of a localized properties >>> file localization via a call to google translate would be attempted. >>> >>> I think there are likely to be more problems the benefits with this >>> design. To wit, http://tinyurl.com/y8nvx2x. >>> >>> Perhaps a shell script to localize your base properties files followed >>> by manual intervention, correction. >>> >>> Ed. >>> >>> On Thu, Jan 28, 2010 at 11:28 AM, Victor Dolirio Ferreira Barbosa >>> <[email protected]> wrote: >>>> There the default properties file for this purpose. Just make a properties >>>> file without locale info in this name, like this example: >>>> >>>> + >>>> |- Application_en_US.properties >>>> |- Application_pt_BR.properties >>>> |- Application.properties >>>> >>>> The last file is used if no other is found for the current locale. >>>> >>>> On Thu, Jan 28, 2010 at 2:15 PM, Martin Makundi < >>>> [email protected]> wrote: >>>> >>>>> Hi! >>>>> >>>>> I wonder, has anybody implemented a wicket stringresource localizer >>>>> that if localized property is not found for the selected language, it >>>>> would attempt to translate it using the default language? >>>>> >>>>> ** >>>>> Martin >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> >>>> -- >>>> []s, >>>> Victor Dolirio >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
