On Friday, August 19, 2011 5:44:02 AM UTC-4, Christiaan Schoenaker wrote: > > Good example. Same goes for many words in discription. I wrote in english > and translated to my native language: dutch. (for i would have a consistent > discription for both languages) but many words were misplaced. They are good > translated but didnt fit. Same for DU and FR. So i dont want to try > something as chinees which i can not read for possible mistakes > On Aug 19, 2011 11:35 AM, "appel" <[email protected]> wrote: > > Adding a bad Google Translation is not always better. >
I think this is generally a good strategy and agree that any translation is better than no translation, especially if your app is relatively intuitive; if only to just describe what it does, and let users then download it and attempt to figure it out. Obviously this will help more if you have a free or lite version, as there's little risk. Some may get pissed that they can't figure it out because it's still in your native language when they install it, but in my experience that seems to be a minority, a few negative comments. Combined with some sanity checks (reverse translations), you can arrive at some relatively effective translations. I noticed that translate does do some wacky things, so it will need some manual correction in some cases, but a little TLC goes a long way. With the Japanese/Korean/Chinese characters, yeah, it's a bit rough. -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-discuss/-/6Oo185_i2E4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
