Localization - Revision history

Notklaatu: /* Concepts */ fixed spelling error

2012-11-02T16:04:11Z

‎Concepts: fixed spelling error

2012-07-15T09:57:23Z

2011-11-26T12:35:57Z

Modified description of Pology.

2010-02-16T20:31:57Z

‎Tools

2010-02-16T20:31:23Z

‎Tools

2010-01-01T13:09:42Z

Summary of the imminent article on the ascription system.

2009-02-13T00:31:12Z

2008-12-30T10:01:58Z

‎Tools

2008-11-23T12:27:07Z

Added article about translation in summit.

2008-09-06T11:36:01Z

Change link to PO format article.

@@ Line 36: / Line 36: @@
 ; [[Localization/Concepts/PO_Odyssey|The PO Format]]
-: ''The PO format is the mainstay of free software translation. Ragardless of the actual workflows and tools used, translators should maintain a good measure of familiarity with the underlying PO format. This article thoroughly describes the elements of the PO format and various uses of PO catalog files which embody it.''
+: ''The PO format is the mainstay of free software translation. Regardless of the actual workflows and tools used, translators should maintain a good measure of familiarity with the underlying PO format. This article thoroughly describes the elements of the PO format and various uses of PO catalog files which embody it.''
 <!-- write about: dynamic, static, detailed story -->

← Older revision		Revision as of 09:57, 15 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Localization}}~~	+

	''Welcome, adventurer, to the universe of KDE localization! Brought along a generous reserve of breathing air?''		''Welcome, adventurer, to the universe of KDE localization! Brought along a generous reserve of breathing air?''

@@ Line 102: / Line 102: @@
 ; [[Localization/Tools/Pology|Pology]]
-: ''Pology is a Python-based framework for quick and robust assembly of "field" scripts for processing PO files, to operate in a version-controlled environment with numerous catalogs. As of yet it is experimental, living in KDE repository only, but with an array of already applicable tools.''
+: ''Pology is a Python library and a set of command-line tools for processing PO files. The tools perform various specialized operations on PO files, some of which have explicit support for PO files within the KDE Translation Project. The library is geared towards quick and robust assembly of "field" scripts for processing PO files, in a version-controlled environment.''
 ; [[Localization/Tools/Lbundle_Check|Lbundle Checker]]

@@ Line 89: / Line 89: @@
 : ''GNU Gettext is the de-facto referent implementation of the PO format. It is used to extract templates from the code and update PO catalogs, and has many tools for processing PO files. Its compiler of PO format into binary format for application use, is the final arbiter of validity of a PO file.''
-; [[http://userbase.kde.org/Lokalize Lokalize]]
+; [http://userbase.kde.org/Lokalize Lokalize]
 : ''[http://userbase.kde.org/Lokalize Lokalize] is a computer-aided translation (CAT) tool, a full-featured GUI application for translators, written from scratch using KDE4 framework. Aside from basic editing of PO files with nifty auxiliary details, it integrates support for glossary, translation memory, diff-modes for QA, project managing, etc.''

@@ Line 89: / Line 89: @@
 : ''GNU Gettext is the de-facto referent implementation of the PO format. It is used to extract templates from the code and update PO catalogs, and has many tools for processing PO files. Its compiler of PO format into binary format for application use, is the final arbiter of validity of a PO file.''
-; [[Localization/Tools/Lokalize|Lokalize]]
+; [[http://userbase.kde.org/Lokalize Lokalize]]
 : ''[http://userbase.kde.org/Lokalize Lokalize] is a computer-aided translation (CAT) tool, a full-featured GUI application for translators, written from scratch using KDE4 framework. Aside from basic editing of PO files with nifty auxiliary details, it integrates support for glossary, translation memory, diff-modes for QA, project managing, etc.''

@@ Line 140: / Line 140: @@
 ; [[Localization/Workflows/PO_Summit|Translating in Summit]]
 : ''Handling two branches for translation, stable and trunk, can be tedious. Porting fixes from one to another branch, making sure team members work on correct branch, etc. Especially so when non-core modules are considered, like extragear. Read about one possibility to curb this overhead.''
 [[Category:Localization]]

← Older revision		Revision as of 00:31, 13 February 2009
Line 1:		Line 1:
−	~~<!--~~{{Template:I18n/Language Navigation Bar\|Localization}}~~//-->~~	+	{{Template:I18n/Language Navigation Bar\|Localization}}

	''Welcome, adventurer, to the universe of KDE localization! Brought along a generous reserve of breathing air?''		''Welcome, adventurer, to the universe of KDE localization! Brought along a generous reserve of breathing air?''

@@ Line 90: / Line 90: @@
 ; [[Localization/Tools/Lokalize|Lokalize]]
-: ''Lokalize is a computer-aided translation (CAT) tool, a full-featured GUI application for translators, written from scratch using KDE4 framework. Aside from basic editing of PO files with nifty auxiliary details, it integrates support for glossary, translation memory, diff-modes for QA, project managing, etc.''
+: ''[http://userbase.kde.org/Lokalize Lokalize] is a computer-aided translation (CAT) tool, a full-featured GUI application for translators, written from scratch using KDE4 framework. Aside from basic editing of PO files with nifty auxiliary details, it integrates support for glossary, translation memory, diff-modes for QA, project managing, etc.''
 ; [[Localization/Tools/Emacs_and_Vim|Emacs & Vim]]

@@ Line 137: / Line 137: @@
 : ''Daily in the KDE repository, the lumbering machinery scrutinizes code, updates translations to reflect changes, performs checks, serving the results to translators. Learn to follow its hum, and know where to grease when the gears clog.''
 <!-- write about: Scripty the Beast from start to end, script by script; template extraction, desktop files, doc -> POT, logs, i18n code checks -->
 [[Category:Localization]]