Hi Terje,
cross-posting to x2go-dev as not so many people are listening to
x2go-i18n, yet.
On Mi 15 Feb 2012 20:10:32 CET Terje Andersen wrote:
I've been thinking here (I know, that's dangerous :p) and I've got
two suggestions:
- I've been thinking about the translation of X2Go into languages with
less widespread usage (like Norwegian is because of the small
population). When someone gets an error message and he/she wants to search for
more information on that error, they got less chance on finding any
help/information because the text they search on is in a "small"
(less used) language. Knowing what the text is in the original
(English) language isn't possible/easy as the translation isn't done
word-for-word, so the user can't search in English. What I propose is to add an error-code/number which is the same
regardless of the language used. If this could be something more
than just a number, like "[x2go-1234568]" it would be real easy to
find information with search engines. This would greatly improve the
success rate in resolving any errors, and reduce the potential for
frustration. A list, with the potential for translated versions, on
the wiki could be kept updated with the error-code and a short
helpful explanation/help text.I really hope this can be considered for X2Go.
From my point of view, I would rather make it easy to run the
application in English for debugging and recommend this as the way to
go. On Linux, this is easy:
LANG=C x2goclient LANG=C pyhoca-gui
On Windows, pyhoca-gui has a --lang <LANG> option. About x2goclient, I
do not have a clue.
Doing error number bookkeeping, I guess I won't become a fan of... Hmmm...
- In the original text (English) in the X2Go client the words
"suspend" and "resume" gives the impression (at least for me) that
the session is paused when suspended. I remember the early version
of the NX libraries which actually paused the session when
suspended, but that's a long time ago, and no longer the case. I
therefore propose to use the words "disconnect" and "reconnect"
instead, as this would more correct indicate the functionality that
actually takes place.
I guess we should not change anything here, unless we find a way to
offer both possibilities:
suspend+resume -> freeze a session state and unfreeze it later disconnect+reconnect -> leave a session running, come back to it later
I am wondering if the freeze/unfreeze couple is still available with
NX!!! If so, that would be an interesting feature.
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
What I propose is to add an error-code/number which is the same regardless of the language used. If this could be something more than just a number, like "[x2go-1234568]" it would be real easy to find information with search engines. This would greatly improve the success rate in resolving any errors, and reduce the potential for frustration. A list, with the potential for translated versions, on the wiki could be kept updated with the error-code and a short helpful explanation/help text.
I really hope this can be considered for X2Go.
From my point of view, I would rather make it easy to run the application in English for debugging and recommend this as the way to go. On Linux, this is easy:
LANG=C x2goclient LANG=C pyhoca-gui
On Windows, pyhoca-gui has a --lang <LANG> option. About x2goclient, I do not have a clue.
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.
Cheers, Daniel
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'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. 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.
-Stefan
2012/2/16 newsgroups.mail2@stefanbaur.de <newsgroups.mail2@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
As Terje is proposing, the error code wouldn't *just* be a number, it would also contain an identification string of some sort.
One example is STOP-codes in Windows, it's easy to find troubleshooting info about "STOP 0x0000007B", a localized error message - something like "Åtkomst till startenhet misslyckades" - wouldn't return much when Googling for support.
Cheers, Daniel
-
Daniel Lindgren -
Mike Gabriel -
newsgroups.mail2＠stefanbaur.de -
Terje Andersen