home.KaiRo.at
Bio
weBlog
[arts corner]
[science corner]
Slides
Fotogalerien
Kontakt
Suche
>> www.KaiRo.at
Neuer Kommentar
Name:
E-Mail:
Homepage:
Ort:
JavaScript support is required for this form to work.
Berechne:
10 plus 2 ergibt
Titel:
Beitragstext:
[quote="Björn Graf"]A few general questions (and maybe a disclaimer upfront: this is a more general comment about error messages and l10n than a critique of your work): are these messages visible to average users? If so, could they really do something to fix the problem (esp. in the case of the bad padded SSL record, I am pretty sure my Dad has no clue what to do; heck, even I don't have an idea)? Anyway, considering the visibility of the messages (user vs. log only) do they really need to be localized? I mean, most development related documentations are written in English - I am pretty sure "SSL block padding" is a far better search phrase than "SSL Block-Auffüllung", and to the technical savy user, the latter would not really give a clue about the error (maybe it is my age and the time I started programming - l10n was a rather rare thing in normal applications and unknown in API documentations - but localized error messages are a PITA). The conclusion (of this rather unrelated and misplaced comment) might be to use a more general error message like "Something gone boom [here the one to blame could be named, e.g. the application, the connection or the server failed]. If you studied computer science, click here to view the details. Otherwise, try to reload the page." (not in these exact words but you should get the general idea). Translating for the sake of having a l10n story is not always good. Sorry for having choosen your innocent post about the troubles of a translater for my rant about my error messages and general l10n pet peeves :)[/quote]
Ich akzeptiere und befolge
die Regeln von Home of KaiRo
.
In diesem Eintrag werden
Emoji
,
bbCode
und
manche HTML-Codes
unterstützt.