On Sat, Jun 20, 2009 at 12:45 PM, Peer
Sommerlund<[email protected]> wrote:
> What is the general opinion with respect to translation of exception
> messages?
> From a developer point of view I would prefer to have untranslated messages,
> otherwise I cannot help a user with a language that I don't know. Even if I
> know the language, it is harder to locate the point in the source code where
> the error originated.
> From a user point of view some (not me) might prefer a translated message. I
> would say that this is only relevant for error messages, not for exception
> messages.
> Right now I'm looking at the string "unhandled transition: %s -> %s"
> i hggtk\hgshelve.py:294 -- where the strings used in %s are not translated.

The policy has grown somewhat organically, but we seem to be moving
towards keeping true bug messages in English and translating user
errors.  So, for instance in the bug report dialog we translate the
text that tells the user a bug has been found and how to report it,
but the rest of the text is left in English.

So, if the message indicates a bug, it should probably throw up to the
bug report dialog.  Otherwise it needs to be translated.

That particular line came from the record extension, before there was
a concerted effort to translate Mercurial.  It's tough to classify
that as a bug or user error, as it looks like it could be caused by a
malformed patch.

--
Steve Borho

------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop

Reply via email to