0
WELCOME=Willkommen
HOW ARE YOU=Wie geht's?
THANK_YOU=Danke sch?¶n
SEEYOULATER=Bis sp?¤ter
POLITEHELLO=Guten tag %s
The names of the translations, to the left of the equal signs, have no specific naming
convention. This examples use a mixture of different conventions we can use to
name translations. Whatever way we choose to name our translations, we should
always be consistent.
When we translate long pieces of text it is sometimes easier to use abbreviations. For
example the name for an incorrect login is LOGIN_INCORRECT, but the translated text
is far longer.
When we create and edit translation files, it is essential to ensure that the file is UTF-
8 encoded. There are lots of text editors available that support UTF-8 multi-byte
character encoding. One such editor is SciTE, a freely available source-code editor
(http://www.scintilla.org/SciTE.html):
Chapter 9
[ 267 ]
Debugging Translations
It can be useful when creating a new translation to enable language debugging.
When language debugging is enabled, all the text that has passed through a
translation mechanism will be highlighted and some additional information is
displayed at the bottom of the page.
Pages:
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367