News for hackers. Stuff that matters.
Re:Why you should use English versions of your OS and other ... by rbanffy on Friday January 08, 2010 @10:32AM (#1039695)
Actually you should switch to software that keeps localization in configuration space instead of code, allowing you to switch languages on a per-user, per-program or per-session.

Having user-targeted messages hard coded is a bug.

Re:Why you should use English versions of your OS and other ... by halostatue on Friday January 08, 2010 @10:41AM (#1039719)
Yes, it is. However, if you don't include search keys in the text presented to the user, it isn't going help when you get a dialog that says (FTA):

  Sterownik ekranu przestał działać, ale odzyskał sprawność.
That's missing something at the beginning or end that allows a search engine to say "aha! this is looking for this error message, which in English is this".

This is a hard problem, at the same time; the translated log files[1] from work look something like this:

    2009-12-13 14:21 BACK-E-00234 <text here, with optional parameter values>
The key piece is "BACK-E-00234" (it's from the BACK module, it's an Error, and it's message 00234). When we have messages to display to the user in a dialog, we don't show that key information (or have a way of getting to it) because it's ugly.

It's unlikely that the message mentioned in the article was hard-coded to Polish; instead the author is arguing about users and the searchability of non-English error messages. To increase the searchability, you need to include key details (e.g., "BACK-E-00234") that make the message significantly uglier to read. One possible way around this is to make sure your error dialogs are selectable/copyable (maybe put a button to do this), but on copy silently insert the search key details.

[1] Our untranslated log files look more like:

    <M ID="234" T="2009-12-13T14:21:00.00000" S="E" M="BACK">...parameter tags here...</M>
Re:Why you should use English versions of your OS and other ... by rbanffy on Friday January 08, 2010 @10:47AM (#1039735)
Hmmm... Including a button on dialog boxes for googling (or bing'ing) the error in language-neutral form...

Nice item for a future GUI wishlist.

Re:Why you should use English versions of your OS and other ... by halostatue on Friday January 08, 2010 @11:19AM (#1039808)
I'm not sure that a button for search is the right way to go; it would work, definitely, but at the cost of cluttering your UI. Insertion into copy is probably a better idea, because you may be emailing the error message to a systems administrator instead of searching it.
Re:Why you should use English versions of your OS and other ... by rbanffy on Friday January 08, 2010 @01:42PM (#1040116)
Perhaps a collapsed details or additional actions pane
Re:Why you should use English versions of your OS and other ... by herdrick on Friday January 08, 2010 @03:55PM (#1040409)
Actually this is something the search engines can and should do. Offering this on Bing would be a very smart thing for Microsoft to do. They'd have a nice little competitive advantage from their easy access to the bundles of localization strings. (I doubt if it'd slow Google down much, but even if Bing were the best search engine to use for only a few days after the release of a new MS product that would really help them to get people to try Bing.
Re:Why you should use English versions of your OS and other ... by blasdel on Friday January 08, 2010 @11:33AM (#1039839)
Try hitting Ctrl-C in a standard active Win32 dialog. It already puts something nice on the clipboard automatically :)

You might put the key information in the dialog's window title.

Re:Why you should use English versions of your OS and other ... by henrikschroder on Friday January 08, 2010 @10:58AM (#1039762)
Years ago when I had nVidia graphics cards, their control panel always displayed the language of your computer's country settings, you got absolutely no option of selecting the display language yourself.

Needless to say, the controls for overriding anti-aliasing or fog-table or z-buffer settings, translated to my native language, was completely incomprehensible. I still don't understand why they bothered.

Re:Why you should use English versions of your OS and other ... by rbanffy on Friday January 08, 2010 @11:20AM (#1039812)
English could be considered a neutral language, one to fall back when you can't use the right one.

That does not forbid nVidia from hiring decent translators.

And, BTW, were the software open-source, you could correct the messages for them to make sense..

Re:Why you should use English versions of your OS and other ... by lt on Friday January 08, 2010 @11:33AM (#1039840)
The point is that some technical terms like anti-aliasing usually make little sense even when translated well.
Re:Why you should use English versions of your OS and other ... by xiaoma on Friday January 08, 2010 @01:00PM (#1040029)
How so?

Say 消除鋸齒 to computer geeks in Taiwan and they'll understand it without difficulty. Say it to non-computer people, and they won't get it... just as English-speaking non-computer people won't understand "anti-aliasing".

Assuming you're not talking about languages used by aboriginal groups who don't have computers, how could you translate a term "well" and yet come up with something that makes little sense?

Re:Why you should use English versions of your OS and other ... by lt on Friday January 08, 2010 @01:17PM (#1040068)
I guess some languages are different than others. Some cultures tend to translate pretty much everything (I noticed that in spanish), others accept foreign neologisms.

In portuguese we tend to use the english words for technical terms and jargon, sometimes slightly corrupted to fit the grammar. Terms like delete, debug and commit are conjugated in as if they were regular portuguese verbs and used frequently even with acceptable translations existing. Delete in particular is quite common even among non-technical people.

For many technical terms, specially newer ones, I can't even think of any acceptable translations without it sounding silly. Most of the time they are left as-is and you need to know the jargon to understand the translation.

I much prefer to read technical documents and books in english.

Re:Why you should use English versions of your OS and other ... by rbanffy on Friday January 08, 2010 @01:55PM (#1040143)
Just don't translate the technical terms unless there is a well accepted translation for it. You can translate the rest.
Re:Why you should use English versions of your OS and other ... by kellishaver on Friday January 08, 2010 @12:51PM (#1040010)
I work on a large/popular open source project and the one thing we get requests for more than anything else is multilingual support (which we'll be adding in the next major version). Everyone seems to think it's so easy to add with the inclusion of one language file to translate the system. While it's true that this can be used to translate the core system (and is probably what we'll do) our software is designed to deal with large quantities of user-generated content, so we also need ways to support multiple translations of that content, handling fallbacks if the translations don't exist, switching between them on the fly, search indexing, making our UI fluid enough to accommodate different lengths of text in navigation, etc. The list goes on. None of this is particularly difficult, but there is a lot to consider that, judging from our user base a lot of people (many of which are developers themselves), just don't think of. Proper multilingual support can be quite tedious.
Re:Why you should use English versions of your OS and other ... by Quarrelsome on Friday January 08, 2010 @11:02AM (#1039767)
Typically on a windows box they're in resources (not hard-coded) and the resources pointed to are toggled by the current culture. Unfortunately this usually works on the premise that you change the language for the computer in one go as opposed to being able to do it per application or per session.