Re: el.po for ldm

As a translator, I find debug messages hard to translate; I sometimes
need to look at the source code to help me in the translation. That
means that the debug messages translations don't have the same quality
as the UI messages translations.

More importantly, as a user, I don't like translated debug messages
because they don't show up in google as often as the original ones. I
know a lot of Greek people that prefer to have an English UI in their OS
only because of this. And debug messages are the ones that people will
mostly google for, trying to pinpoint the problem.
Moreover, it isn't easy to do `LANG=en ldm` and reproduce the problem to
get the original English message...

If you'll be changing the _()'s, may I also suggest that you leave out
as much styling information or punctuation as you can, e.g.
'<b>Verifying password.  Please wait.</b>' => leave out the '<b>' or
'\n' and join them with g_strconcat in the code. It'll be both easier
for translators and more reusable.

Kind regards,
Alkis


Στις 25-01-2009, ημέρα Κυρ, και ώρα 18:30 -0500, ο/η Stéphane Graber
έγραψε:
> I don't know what's the feeling among our users but I always find it
> disturbing when the softwares I use report translated debug output.
> It also makes it more difficult for us developers to debug a user's
> problem.
> 
> Opinions about that ? Should we just drop all our debug output from the
> translation template ? (basically just strop using _() for them)



------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net