The roads I take...
KaiRo's weBlog
| Zeige Beiträge veröffentlicht am 07.04.2007 und auf Englisch an. Zurück zu allen aktuellen Beiträgen |
7. April 2007
A Localizer's Nightmare: Security Backend Error Messages
Today I decided to do some work on the German L10n of nsserrors.properties, which hit the trunk 3 weeks ago and nobody in the German team has dared to localize so far (we have a version in l10n/de trunk that only carries the original English strings).
And there are good reasons why it hasn't been touched for a longer time, as the hardest strings to localize correctly probably fall into three categories: backend messages, technical error messages and security strings. And this files consists of 262 new security backend error messages. Yay!
This means that highly technical terms, often from security areas, like "Certificate Request handshake message" get mixed with hard-to-localize phrases like "experience an error" and untranslatable names like "PKCS#11 token" and/or cryptic (pun intended) abbreviations like OCSP,ASN.1,CA,CKL,SSL,MAC-SHA1,MD5, etc.
Even messages that look innocent like "SSL received a record with bad block padding." can be very challenging for localizers. You might not want to translate that as "SSL hat einen Rekord mit schlechter Klotz-Polsterung empfangen." (thanks to Martin for that suggestion ) or not even someone who actually knows the technology would understand it. Even my current try of "SSL hat einen Eintrag mit falscher Block-Auffüllung erhalten." may not be understood by novices (just like the original) but I hope it will give a clue to most people who read it.
"Unable to digitally sign data required to verify your certificate." is almost a welcome and easy to translate message within a pile of such strings. I hope to find more of those while continuing to dig through that file...
And there are good reasons why it hasn't been touched for a longer time, as the hardest strings to localize correctly probably fall into three categories: backend messages, technical error messages and security strings. And this files consists of 262 new security backend error messages. Yay!
This means that highly technical terms, often from security areas, like "Certificate Request handshake message" get mixed with hard-to-localize phrases like "experience an error" and untranslatable names like "PKCS#11 token" and/or cryptic (pun intended) abbreviations like OCSP,ASN.1,CA,CKL,SSL,MAC-SHA1,MD5, etc.
Even messages that look innocent like "SSL received a record with bad block padding." can be very challenging for localizers. You might not want to translate that as "SSL hat einen Rekord mit schlechter Klotz-Polsterung empfangen." (thanks to Martin for that suggestion ) or not even someone who actually knows the technology would understand it. Even my current try of "SSL hat einen Eintrag mit falscher Block-Auffüllung erhalten." may not be understood by novices (just like the original) but I hope it will give a clue to most people who read it.
"Unable to digitally sign data required to verify your certificate." is almost a welcome and easy to translate message within a pile of such strings. I hope to find more of those while continuing to dig through that file...
Von KaiRo, um 16:07 | Tags: L10n, Mozilla | 7 Kommentare | TrackBack: 0