Difference between revisions of "Translation for developers/en"

Line 34:

Go through the *.xul and *.js files to find hardcoded strings (in English).

If you find one you need to find a string identifier (foobar for example), have a look to the already ~~localised~~ string to see how it should ~~looks~~ like. ~~the~~ most important to know is that in the *.xul files, it should ~~looks~~ like "&foobar;" and in the *.js like "getProperty('foobar')".

If you find one you need to find a string identifier (foobar for example), have a look to the already localized string to see how it should look like. The most important to know is that in the *.xul files, it should look like "&foobar;" and in the *.js like "getProperty('foobar')".

=== Translate it in the master language English ===

Difference between revisions of "Translation for developers/en"

Navigation menu

Search

@@ Line 34: / Line 34: @@
 Go through the *.xul and *.js files to find hardcoded strings (in English).
-If you find one you need to find a string identifier (foobar for example), have a look to the already localised string to see how it should looks like. the most important to know is that in the *.xul files, it should looks like "&foobar;" and in the *.js like "getProperty('foobar')".
+If you find one you need to find a string identifier (foobar for example), have a look to the already localized string to see how it should look like. The most important to know is that in the *.xul files, it should look like "&foobar;" and in the *.js like "getProperty('foobar')".
 === Translate it in the master language English ===