[x2go-i18n] Suggestions

[Terje Andersen]

2012/2/16 newsgroups.mail2 at stefanbaur.de <newsgroups.mail2 at stefanbaur.de>

> Am 16.02.2012 08:44, schrieb Daniel Lindgren:
>
>  Doing error number bookkeeping, I guess I won't become a fan of... Hmmm...
>>>
>> I'm also a "less used" language user and I've had the exact same idea
>> as Terje. Troubleshooting (i e googling) error messages in Swedish is
>> rarely succesful, you pretty much have to translate them to english -
>> with varying success - to get any hits at all.
>>
>> If all error messages included an error code/number it would simplify
>> things a lot.
>>
>
> I don't think numbering will help that much.  I mean, googling for "42"
> will turn up a lot of answers, but not necessarily the one you're looking
> for. ;-)
>

I didn't propose that, my suggestion was to use a code-scheme like this:

"[x2go-1234568]"

Searching on that specific string would give unique and accurate results. The
concept of error-codes is well know, and is also a part of the error
message at hand.

I'd suggest an option to display the English error message, either by
> hovering the mouse over the translated error message or by clicking a
> button.
>

I'm no developer so I can't tell if that would
require unsubstantial changes to the code, or not, but it sounds to me like
it would, but I see your point.

The easiest way, though, as it wouldn't require changing actual code, would
> be to provide the translation file in a human-readable (and -searchable)
> form on the X2Go homepage or within the x2goclient installation package.
>
>
I understand, then the user would have to use the results found by the
initial search and then translate his/hers error message into another
language and search for the results. It helps somewhat, but in my view it
could be done better with error-codes.

A simple way of achieving this is to use a simple hierarchy of codes -
divide series of codes up and allocate different series to different
code-parts/files and insert the numbers (incrementally) into the error
messages/strings. This way, the translator would keep the error-code in the
translated message. If one sets aside big enough series it would be easy to
add new, and overlooked messages wouldn't present any problem; just pick
the next available number in the allocated series of numbers. Another way
of doing this, would be to just pick a new available series of numbers when
one has been used up.

Example:
[x2go-000000 --> 000099] = X2Goclient
[x2go-000100 --> 000199] = Pyhoca-GUI

and so on.

Regards,
Terje
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x2go.org/pipermail/x2go-i18n/attachments/20120216/87abecd7/attachment.html>