Open main menu


This page is a translated version of the page Help:Extension:Translate/Off-line translation and the translation is 58% complete.
Other languages:
Deutsch • ‎Deutsch (Sie-Form)‎ • ‎English • ‎Kiswahili • ‎Lëtzebuergesch • ‎Nederlands • ‎Zazaki • ‎català • ‎dansk • ‎español • ‎français • ‎italiano • ‎lietuvių • ‎polski • ‎português • ‎português do Brasil • ‎svenska • ‎čeština • ‎Ελληνικά • ‎български • ‎македонски • ‎русский • ‎українська • ‎العربية • ‎मराठी • ‎中文 • ‎日本語 • ‎조선말

本页介绍了如何离线翻译。 如果您对此感兴趣,您可能已经知道Gettext PO文件是什么。出于这个原因,我们将仅讨论如何在带有Translate扩展的wiki中使用它们。否则,您可能对如何在线翻译的教程更感兴趣。



您可以通过选择Special:Translate中的离线翻译导出,将任何消息组下载为Gettext PO文件。但某些站点可能已禁用这个。您应该在开始之前检查本地指南如何处理这些文件。

Although some message groups might have an export option, which exports translations in the native format of that group, and that format could be Gettext, those are not the files that can be used for off-line translation!

The files are standard Gettext PO files with some extra information. The header contains some extra fields shown below; the msgctxt for each message contains an identifier that the Translate extension needs. Some editors are known to strip either the header comments or the msgctxt lines, so start with a small file to make sure that your editor does not remove these – it's not funny to realize the editor was buggy after translating hundreds of messages that you cannot import back into the online system! The message documentation is exported as translation comments.


"X-Language-Code: nl\n"
"X-Message-Group: ext-abc\n"

在此示例中,“ext-abc”是消息组的名称。 For translatable pages, the corresponding message group has the name "page-" + the page name (i.e. for the page "Example", the header would contain the line "X-Message-Group: page-Example\n").

Example entry in a Translate Gettext po file.


#. [Wiki] This text is used on the history tab.
#. [Wiki] 

msgctxt "history_short"
msgid "History"
msgstr "Versionsgeschichte"


There is no need to translate the file completely. Uploading partially translated message groups is perfectly fine. There are two ways to import these files.
The users with correct user rights can use Special:ImportTranslations to upload and import the translations. The special page processes the file, shows the changes and lets the user import them. For large files with lots of changes the importing might take multiple steps, as the processing time is limited.

Importing can also be done using a command line script in Translate/script/poimport.php. It's less flexible but can import everything in one go. It also needs intervention from someone with shell access to the server.

The way how imports of off-line translations are handled (or not) depends on your wiki.



Available for all platforms supporting the wxWidgets toolkit, tested on Unix with GTK+ and Windows.
WARNING: make sure you are using version 1.4.2 or above, otherwise "msgctxt" lines are dropped and your work cannot be processed.
Can be used in the GNOME desktop environment on Unix and Linux platforms.
To be used as plugin in the Eclipse IDE on Linux, Windows and MAC OS X, has various tools integrated.
Uses the KDE 4 Desktop Environment on all platforms supporting it. Has a user wiki and online handbook
Translate Toolkit 
Toolkit written in the python programming language which must be installed as well, usable on all platforms. Supports several other file formats as well.
Multi-format translation tool based on the toolkit above. Currently working in Windows and Linux.
Free tool for professional translators written in Java, requires Java installed; available on all platforms. Supports a variety of other file formats, glosssaries, fuzzy matching, and translation memories.
Eazy PO 
Small program, runs on Windows, no installation required.
Gorm PO file editor 
Small powerful program, runs on Windows, no installation required, version 1.0 fails on msgctxt tags.
Better PO Editor 
Available as source code for Windows, BSD, Unix, Linux, Mac OS X. Includes spell checker and Google Translate suggestions.