Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
worlddomination [2007/01/18 10:04] manniworlddomination [2008/02/08 19:49] (current) – external edit 127.0.0.1
Line 10: Line 10:
  
 This page provides full details of how POPFile localization is done. This page provides full details of how POPFile localization is done.
 +
  
 ===== The L10N Scheme ===== ===== The L10N Scheme =====
Line 16: Line 17:
  
 <code> <code>
-  - Identify the language and character set used for the interface+Identify the language and character set used for the interface
 LanguageCode                            en LanguageCode                            en
 LanguageCharset                         ISO-8859-1 LanguageCharset                         ISO-8859-1
 LanguageDirection                       ltr LanguageDirection                       ltr
  
-  - This is used to get the appropriate subdirectory for the manual+This is used to get the appropriate subdirectory for the manual
 ManualLanguage                          en ManualLanguage                          en
 </code> </code>
  
-A line that begins with //#// is a comment and ignored by POPFile.  Lines that contains text consist of an identifier (e.g. //<nowiki>LanguageCode</nowiki>//) that contains no whitespace, then some whitespace, and finally the string associated with the identifier.+A line that begins with //#// is a comment and ignored by POPFile.  Lines that contains text consist of an identifier (e.g. //LanguageCode//) that contains no whitespace, then some whitespace, and finally the string associated with the identifier.
  
 There are five special identifiers.  The special identifiers are: There are five special identifiers.  The special identifiers are:
  
 ||Identifier                || Meaning || Values || ||Identifier                || Meaning || Values ||
-||//<nowiki>LanguageCode</nowiki>//     || The base language for the user interface in HTML terms; used to set the //lang// attribute on the //&lt;html&gt;// tag of the UI.||See http://www.w3.org/TR/html401/struct/dirlang.html#adef-lang for details.|| +||//%%LanguageCode%%//     || The base language for the user interface in HTML terms; used to set the //lang// attribute on the //&lt;html&gt;// tag of the UI.||See http://www.w3.org/TR/html401/struct/dirlang.html#adef-lang for details.|| 
-||//<nowiki>LanguageCharset</nowiki>//  || Sets the character set for the UI; used in a //&lt;meta&gt;// tag that sets the //Content-Type// of the UI.||See http://www.w3.org/TR/html401/charset.html#h-5.2 for details.|| +||//%%LanguageCharset%%//  || Sets the character set for the UI; used in a //&lt;meta&gt;// tag that sets the //Content-Type// of the UI.||See http://www.w3.org/TR/html401/charset.html#h-5.2 for details.|| 
-||//<nowiki>LanguageDirection</nowiki>//|| The direction in which the language is read.  e.g. English is left to right, Arabic is right to left; used to set the //dir// attribute on the //&lt;html&gt;// tag of the UI. ||//ltr//, //rtl//; see http://www.w3.org/TR/html401/struct/dirlang.html#bidirection for details.|| +||//%%LanguageDirection%%//|| The direction in which the language is read.  e.g. English is left to right, Arabic is right to left; used to set the //dir// attribute on the //&lt;html&gt;// tag of the UI. ||//ltr//, //rtl//; see http://www.w3.org/TR/html401/struct/dirlang.html#bidirection for details.|| 
-||//<nowiki>ManualLanguage</nowiki>//   || The subdirectory of //manual/// that contains the manual for this language.  If no translation use //en// English.  Note that non-English manuals are not served locally, but come from //http://popfile.sourceforge.net/manual///. || Subject to change, check //http://popfile.sourceforge.net/manual/// || +||//%%ManualLanguage%%//   || The subdirectory of //manual// that contains the manual for this language.  If no translation use //en// English.  Note that non-English manuals are not served locally, but come from http://popfile.sourceforge.net/manual/. || Subject to change, check http://popfile.sourceforge.net/manual/ || 
-||//<nowiki>Locale_Date</nowiki>//|| Two format strings that determine how the message dates will be formatted on the POPFile History screen. The first one determines the format used for messages that are less than 7 days old, the second one for older messages. Both format strings are devided by the '|' sign. ||The format specifiers you can use here are described on the DateFormat page.||+||//Locale_Date//|| Two format strings that determine how the message dates will be formatted on the POPFile History screen. The first one determines the format used for messages that are less than 7 days old, the second one for older messages. Both format strings are devided by the '%%|%%' sign. ||The format specifiers you can use here are described on the DateFormat page.||
  
 Some of the strings contain the character sequence %s. These are also format strings and the %s will be replaced by another string at run-time. For example, the string named 'Bucket_Error2' is set to "Bucket named %s already exists" in the Engish version. The %s symbol will be replaced by whatever bucket name the user entered on the Buckets page when this bucket name already exists to come up with a nice error string. Some of the strings contain the character sequence %s. These are also format strings and the %s will be replaced by another string at run-time. For example, the string named 'Bucket_Error2' is set to "Bucket named %s already exists" in the Engish version. The %s symbol will be replaced by whatever bucket name the user entered on the Buckets page when this bucket name already exists to come up with a nice error string.
Line 40: Line 41:
 ===== Tools and helpers for translators ===== ===== Tools and helpers for translators =====
  
-To make it easier for you to translate the POPFile UI, you can change the <code>html_test_language</code> variable and use the script <code>check.pl</code>.+To make it easier for you to translate the POPFile UI, you can change the ''html_test_language'' variable and use the script ''check.pl''.
  
-==== //html_test_language// ====+==== html_test_language ====
  
 The POPFile option //html_test_language// (see OptionReference) can be set to 1 to make POPFile's UI show the identifiers used for each string instead of strings in a particular language. This can prove helpful if someone doing localization wants to discover the relationship between specific strings in an MSG file and the UI. The POPFile option //html_test_language// (see OptionReference) can be set to 1 to make POPFile's UI show the identifiers used for each string instead of strings in a particular language. This can prove helpful if someone doing localization wants to discover the relationship between specific strings in an MSG file and the UI.
Line 48: Line 49:
 Example: With the parameter set to 1 the text "POPFile Control Center" changes to "Header_Title" which is an identifier that can be found in the MSG files. Example: With the parameter set to 1 the text "POPFile Control Center" changes to "Header_Title" which is an identifier that can be found in the MSG files.
  
-==== //check.pl// ====+==== check.pl ====
  
 The languages directory also contains a little script which you can used to easily find out which strings still need to be translated, which strings are no longer used, etc. The script is named "check.pl" and can be used like this: The languages directory also contains a little script which you can used to easily find out which strings still need to be translated, which strings are no longer used, etc. The script is named "check.pl" and can be used like this:
 
worlddomination.1169114686.txt.gz · Last modified: 2008/02/08 19:49 (external edit)
Old revisions

Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.

Recent changes RSS feed Donate Driven by DokuWiki
The content of this wiki is protected by the GNU Fee Documentation License