This extension exports articles as text files to pass to external translators. It uses an internal list of pre-configured header translations as well as the table provided by the TranslationManager extension to translate links and headers; this saves on repeat work and helps maintain consistency.
Both TranslationManager and ExportForTranslation are single-language for now, intended for translating Kol-Zchut from Hebrew to Arabic.
The extension adds a user group, translator
, with the user right export-for-translation
.
Users in this group have an additional link in their user tools, which allows exporting an article.
The export results in a download of a plaintext file, where links are replaced with their translation
(if available through language links or TranslationManager). There is also an additional template added,
{{נתוני תרגום}}
, with the following parameters:
- שם (name)
- שם מתורגם (translated name)
- תאריך עדכון מקור (source last updated)
- rev_id
On our system, this template creates and shows a diff link between the exported revision and the current revision; you can adapt it to your needs, and use it to save semantic information, for example.
This template can be found in the wikitemplates
subdirectory.
It is also possible to export pages using Special:ExportForTranslation
, either by selecting a page there,
or passing a page name as a subpage, e.g.: Special:ExportForTranslation/My_Page_Name
.
$wgExportForTranslationNamespaces = [ NS_MAIN ]
Namespaces that show the "export to translation" menu option$wgExportForTranslationDefaultLanguage = 'ar'
ISO 639-1 language code to use by default.
This extension has a hard dependency on TranslationManager.
- Multi-lingual support, matching extension:TranslationManager v0.8.0
- Breaking change: ExportForTranslation:export() now expects a Title.
- ExportForTranslation:export() can now also be passed a revision ID, to export a specific revision.
- The exported text now holds a template of metadata, which was previously encoded as an HTML comment.
- bugfix: the page's own translation was missing because of recent changes
- Do not fall back to title translation for the categories, as it introduces inconsistencies
- Refactor to only pull suggestions and language links for the actual links on page, not every page and suggestion in TranslationManager
- Ignore double spaces inside links, because apparently MediaWiki ignores them
- Handle links that include a fragment
[[Example#Heading2]]
- If a category doesn't have a language link, fall back to title translations (after this refactor, it will only work if the same title is available on page)
- API module