diff options
Diffstat (limited to 'doc/wyslij-po.texi')
| -rw-r--r-- | doc/wyslij-po.texi | 37 |
1 files changed, 23 insertions, 14 deletions
diff --git a/doc/wyslij-po.texi b/doc/wyslij-po.texi index 13dcb0a..ee52d38 100644 --- a/doc/wyslij-po.texi +++ b/doc/wyslij-po.texi @@ -160,24 +160,26 @@ A canonical @acronym{PO} name consists of the project name and version, separated by dash, which are followed by a dot, the language code as per @acronym{ISO} 639, and the suffix @samp{.po}. To determine the canonical name, @command{wyslij-po} uses the contents of -@code{Project-Id-Version} and @code{Language-Team} @acronym{PO} +@code{Project-Id-Version} and @code{Language} @acronym{PO} headers. The value of @code{Project-Id-Version} supplies the name and version of the project this file is for, and the value of -@code{Language-Team} gives the full name of the language served by -this @acronym{PO}. This full name is then looked up in a @dfn{language -table} - a special file listing for each language name its @acronym{ISO} 639 -code (@pxref{Langtab}), and the code found is then used. For example, -if the two headers in question were: +@code{Language} gives the @acronym{ISO-639} abbreviation of the +language name@. For example, if the two headers in question were: @example Project-Id-Version: cflow 1.2 -Language-Team: Polish - <translation-team-pl@@lists.sourceforge.net> +Language: pl @end example @noindent then the canonical name for that file is @file{cflow-1.2.pl.po}. +If the @acronym{PO} file lacks the @code{Language} header, +@command{wyslij-po} analyzes the @code{Language-Team} header. The +full language name extracted from this header is looked up in a +@dfn{language table} file to find the corresponding @acronym{ISO-639} +code (@pxref{Langtab}). + @item Verify the consistency of @acronym{PO} file. This step ensures that the file corresponds to the latest version of @@ -701,12 +703,19 @@ sed, GNU sed}) with exactly one parenthesized group. @cindex language code To recreate the canonical @acronym{PO} name (@pxref{canonical-name}) for a given translation, @command{wyslij-po} needs to know the -@dfn{language code} associated with this language. This information cannot -be obtained from @acronym{PO} file directly. Instead, -@command{wyslij-po} obtains the full language name -from the @code{Language-Team} @acronym{PO} header, and then uses this -value as a look-up key in a set of @dfn{language tables}. If the key is -found, its value gives the language code. +@dfn{language code} associated with this language. Normally this +information is kept in the @code{Language} header of the @acronym{PO} +file@footnote{The @code{Language} header is present in @acronym{PO} +files created by @command{gettext} version 0.18 or later.}. If this +header is not present, @command{wyslij-po} will first obtain the full +language name from the @code{Language-Team} @acronym{PO} header, and +then use this value as a look-up key in a set of @dfn{language +tables}. If the key is found, its value gives the language code. + + This language code lookup is retained as a fallback mechanism for +handling old @acronym{PO} files and will be removed in future +releases. This chapter describes the format of language table files +used by @command{wyslij-po}. @cindex language tables, format The language tables are stored in plain text files. Their format is |