Internationalization/file format - Revision history

Leo at 08:15, 4 September 2006

2006-09-04T08:15:10Z

Etienner: /* Format of PO files */

2006-09-02T15:45:39Z

‎Format of PO files

Etienner: xliff...

2006-09-02T15:44:53Z

xliff...

Etienner: /* Negative aspects */

2006-09-02T14:56:02Z

‎Negative aspects

Etienner: /* Normal entry */

2006-09-02T14:54:59Z

‎Normal entry

Etienner: /* ts Files */ -> Negative aspects

2006-09-02T09:01:47Z

‎ts Files: -> Negative aspects

Etienner: /* XML */

2006-09-02T08:39:22Z

‎XML

Leo at 17:31, 15 August 2006

2006-08-15T17:31:37Z

Leo at 17:31, 15 August 2006

2006-08-15T17:31:14Z

Etienner at 06:13, 3 June 2006

2006-06-03T06:13:44Z

@@ Line 3: / Line 3: @@
 ==Summary==
-A bref description of the most importat file formats used for the translation of programs.
+A bref description of the most important file formats used for the translation of programs.
 ==PO Files==
@@ Line 68: / Line 68: @@
 ===Format of ts files===
-The .ts file format is used Trolltech for the QT applications. They are XML conforming files. Here an example of a .ts file, generated my lupdate (a tool made by Trolltech that extracts translatable text from the C++ source code of the Qt application, see [[Internationalization/tool evaluation|here]] for further information):
+The .ts file format is used Trolltech for the QT applications. They are XML conforming files. Here an example of a .ts file, generated by lupdate (a tool made by Trolltech that extracts translatable text from the C++ source code of the Qt application, see [[Internationalization/tool evaluation|here]] for further information):
   <!DOCTYPE TS><TS>

@@ Line 112: / Line 112: @@
 == xliff Files ==
-===Format of PO files===
+===Format of XLIFF files===
 XLIFF is the XML Localization Interchange File Format. It is intended to give any software provider a single interchange file format that can be understood by any localization provider.

@@ Line 3: / Line 3: @@
 ==Summary==
-Here [[Internationalization|we]] evaluate various file formats used for the translation of programs. For the moment we are considering:
+A bref description of the most importat file formats used for the translation of programs.
-−
-* XML
-* po
-* [http://transolution.python-hosting.com xliff] (good description in this homepage)
-* create an own format
 ==PO Files==
@@ Line 49: / Line 44: @@
 character encodings that can be used are limited to those supported by both GNU libc and GNU libiconv. These are: ASCII, ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9, ISO-8859-13, ISO-8859-15, KOI8-R, KOI8-U, CP850, CP866, CP874, CP932, CP949, CP950, CP1250, CP1251, CP1252, CP1253, CP1254, CP1255, CP1256, CP1257, GB2312, EUC-JP, EUC-KR, EUC-TW, BIG5, BIG5-HKSCS, GBK, GB18030, SHIFT_JIS, JOHAB, TIS-620, VISCII, UTF-8.
 ===Po Editors===
@@ Line 102: / Line 95: @@
 The creation of .qm files can also be done with the GNU gettext tools: with "xgettext --qt" as string extractor for producing the .pot file. And then convert the translated file (.po) with the "msgfmt --qt" command for creating the .qm files.
 ===Positive aspects===
-* full support for unicode character encodings
+* "full" support for unicode character encodings
 * In trolltech's opinion it's a human readable text
@@ Line 113: / Line 110: @@
 * Qt message catalog format supports Unicode only in the translated strings, not in the untranslated strings
-==New Format==
+== xliff Files ==
-===Format of our Format===
+===Format of PO files===
-* It doesn't exist yet, so we don't know how it looks like.
+XLIFF is the XML Localization Interchange File Format. It is intended to give any software provider a single interchange file format that can be understood by any localization provider.
-* We could give our own extension to the file format for example .et (eiffel translation) or .babe (babylon eiffel) or .eint (eiffel i18n) ... (''huge'' advantage)
-===Positive aspects===
+You can find a XLIFF Tree Structure [http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm#AppTree here]
-* Free to do what we want
+=== ts Editors ===
-* We don't have to care about licenses
-* Possibility to make it the best human readable format
-* So that we can say that we invented a new file format
-* Better integrated and consistent with eiffel syntax
-===Negative aspects===
+*[http://www.heartsome.net/EN/xlfedit.html heartsome]
-* A new format? Why should we be different?
+===Positive aspects===
-* Do more work as needed (there are already good formats)
-* Long time until it becomes famous
-==Conclusions==
+* OASIS standard
-Our decision is to use the po file format.
+* complicated plural form handling
 ==References==

@@ Line 69: / Line 69: @@
 ===Negative aspects===
-* We have to write a PO parser
+* The PO file format does not provide a way of identifying the source and target language within a file. By GNU standards, GNU software is written in American English (en-US), and this is reflected in Gettext by only having support for Germanic plural forms in the source language. It is therefore recommended to set the source-language attribute to en-US by default.
 ==ts Files==

@@ Line 22: / Line 22: @@
   white-space
   #  translator-comments
-  #. automatic-comments
+  #. extracted-comments
-  #: reference...
+  #: references...
   #, flag...
   msgid untranslated-string
@@ Line 29: / Line 29: @@
 Where the ''translator-comments'' are created and maintained exclusively by the translator, this comments have some white space immediately following the #. The other comments are created by the program that created the PO file.
 After the special comment "#," there can be some ''flags'', as ''fuzzy'' shows that the msgstr string might not be a correct translation, i.e. the translator is not sure of his work.
 The 'untranslated-string' is the untranslated string as it appears in the original program source. The ''translated-string'' is (as the name suggests) the translated string, if there is no translation it is an empty string.

@@ Line 70: / Line 70: @@
 * We have to write a PO parser
-==XML==
+==ts Files==
-===Format of XML===
+===Format of ts files===
-XML is used for example by Trolltech for their .ts files. Here an example of .ts file, generated my lupdate (a tool made by trolltech that extracts translatable text from the C++ source code of the Qt application, see [[Internationalization/tool evaluation|here]] for further information):
+The .ts file format is used Trolltech for the QT applications. They are XML conforming files. Here an example of a .ts file, generated my lupdate (a tool made by Trolltech that extracts translatable text from the C++ source code of the Qt application, see [[Internationalization/tool evaluation|here]] for further information):
   <!DOCTYPE TS><TS>
@@ Line 97: / Line 97: @@
       </context>
   </TS>
 ===Positive aspects===
 * full support for unicode character encodings
 * In trolltech's opinion it's a human readable text
@@ Line 107: / Line 110: @@
 * Not everybody knows it
-* Microsoft seeks XML-related patents that could restrict the use of XML (there should be a "Very negative aspect" section)
+* QT's translation framework does not support plurals
-:Thank you for that link, but the Microsoft Patents apply only on the Office dialect of XML, which it uses to save its own documents... they DON'T apply to the XML standard and general use (as we would create our format). [[User:Trosim|Trosim]]
-* In my opinion it's not a human readable text (Fortunately not all human beings are Computer scientists)
 ==New Format==

← Older revision		Revision as of 17:31, 15 August 2006
Line 1:		Line 1:
	[[Category:Internationalization]]		[[Category:Internationalization]]
−	~~[[Category:Internationalization SA project]]~~

	==Summary==		==Summary==

← Older revision		Revision as of 06:13, 3 June 2006
Line 1:		Line 1:
−	~~[[Category:Projects]]~~
	[[Category:Internationalization]]		[[Category:Internationalization]]