A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | AE | AF | AG | AH | AI | AJ | AK | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Feature or something | Pootle | Translatewiki.net | Transifex | Weblate | Launchpad (formerly Rosetta) | GlotPress | Zanata | Pontoon (Mozilla) | B-Translator | Steam | Twitter - discontinued | Adobe | aNobii | App Translator | Crowdin | GNOME: Damned Lies | Drupal Translations | Narro [3] | Skype | Google and Android | GlobalSight | Gengo | Mylingual / Japanize | wordbee | BabelZilla | GetLocalization | LocaleApp | OneSky | Acoveo [3] | ICanLocalize [3] | Unbabel | Loco | Wordapp | Solas | Kató | ||
2 | URL to instance | http://pootle.locamotion.org/ | https://translatewiki.net | https://www.transifex.com | http://hosted.weblate.org/ | https://translations.launchpad.net/ | http://translate.wordpress.org/ | https://translate.zanata.org/zanata/ | https://developer.mozilla.org/en-US/docs/Mozilla/Implementing_Pontoon_in_a_Mozilla_website | https://l10n.org.al/ | http://translation.steampowered.com/ | http://translate.twitter.com/ | https://translate.adobe.com/adobe | https://www.facebook.com/?sk=translations | http://www.apptranslator.org/ | http://crowdin.net/projects/ | l10n.gnome.org | http://localize.drupal.org/ | None public? | http://gengo.com/ | http://mylingual.net/ | http://www.wordbee.com/ | http://www.babelzilla.org/ | getlocalization.com | http://www.localeapp.com/ | oneskyapp.com | translate-software.com | https://localise.biz/ | http://www.wordapp.io/ | https://trommons.org/ | https://translatorswithoutborders.org/our-work/kato-translation-platform/ | |||||||
3 | URL to code | https://github.com/translate/pootle / http://pootle.translatehouse.org/ / https://launchpad.net/~translate.org.za/+archive/ppa / translate.org.za (offline as of October 2013) | https://github.com/wikimedia/translatewiki https://github.com/wikimedia/mediawiki-extensions-Translate | https://github.com/transifex | http://weblate.org / https://github.com/nijel/weblate | https://glotpress.trac.wordpress.org/browser/trunk | https://github.com/zanata/ | https://github.com/mozilla/pontoon | https://github.com/dashohoxha/B-Translator | – | – | https://translate.adobe.com/adobe | – | https://github.com/kjk/apptranslator | code.google.com/p/narro | http://sourceforge.net/projects/globalsight/ | Example: http://gengo.com/string/p/aloha-editor-1/ | https://github.com/BabelZilla/WTS | https://github.com/Locale/localeapp | – | https://github.com/TheRosettaFoundation/SOLAS-Match | |||||||||||||||||
4 | License | GPLv3 | GPL2+ | Formerly GPL, nowadays proprietary https://identi.ca/cwebber/note/qD48JOcbShyKiRQvH6h7yg | GPL | AGPL 3.0 | GPL | LGPL | Unknown | – | – | Commercial | – | No | BSD | Commercial only (very expensive?) | Google Internal Translation Service (proprietary, and not only for Android, but for all Google Apps) | Apache License 2.0 | ? | Proprietary, gratis for FLOSS projects | Proprietary, gratis for "public" projects | AGPL? | Proprietary | |||||||||||||||
5 | Number of supported languages | >400 MediaWiki supports 350+ languages | 200+ (plus 200+ sublocales), only 12 for its interface | Albanian and? | 25 | 53 (incl. Lolcat) | Varies by product. | 50 to 111, depending on where you look | Added manually on request | ? + Pseudolocalization | 107 | Various. Example: Aloha Editor project has 50. | 12 | various | ||||||||||||||||||||||||
6 | Notes | "just another po manager which adds more problems than it solves" – someone, 2012. Translate.org.za packages it with Virtaal, which is like an updated version of Poedit. Also asked User:El libre: It's good to merge and upload translations with Poedit | Usually a pain to get a new project added. See VuFind, OJS, Sharelatex... | Based on Django and Python. Upcoming version 1.0, with things TWN already has plus "native support for Qt files". TWN is already the Transifex that is not yet, we could say. Column expanded with help by User:Keunes. | Born as another PO/translator toolkit web GUI à la Pootle, it's gradually implementing features that the other platforms have had for many years (hence some cells below are not up to date; cf. https://blog.cihar.com/archives/2016/11/04/weblate-29/ ). Instructions at weblate.org/hosting/ | Also some WordPress and Debian teams; OpenShot Video Editor; OpenERP Server, Web and Add-Ons; Blender Animation Design software; Linux Mint Distribution; Astronomer’s program Stellarium. Used even by GNU that hates web translation, but only 4 languages for few small projects. https://translations.launchpad.net/+groups/gnu-translators "Launchpad used to be insecure and of low quality, but that was a while back. I hear they've improved." "Launchpad builds Debian-format packages only". Also asked User:El libre | Asked User:Martin, User:Moorshidi and User:KaidoKikkas. Seems slightly active and their issue tracker is tidy, but feature set quite basic. https://www.ohloh.net/p/glotpress | RedHat project created by unhappy Fedora users not agreeing with https://fedoraproject.org/wiki/FAQ_on_migration_to_transifex.net , hosting only few fedora projects now. Based on Java. Real-time collaboration on string level, but hacky. | PHP, Drupal module | Asked User:Ryo567 | Claim to have 350k participants. Translations are approved by the moderator's dogma not by majority voting. "Translation Feedback" feature: If the translator's translation is not approved, the unapproved translations appear as threefold choices. | Originally developed by team in Romania. Integrates with Adobe translation infrastructure. | Votes seem to play a major role, however it is unclear, on what basis translations are approved. Facebook encourages "translator communities" and shows translators whom of their friends they "help" by translating, i.e. it's "such an honor to do it". :) "several steps, but only two of them involve professional translators" https://books.google.it/books?hl=it&lr=&id=9fEjCQAAQBAJ | Link from each word in the interface when enabled, you can only propose and vote translations then they get locked. | Used for SumatraPDF. He thinks TWN very ugly and hard to use and doesn't care about its features, may like it with TUX. | Actually just a code browser, to download po files, see statistics, etc. All the work is still manual. https://wiki.gnome.org/TranslationProject/LocalisationGuide Can mark tasks as ongoing (https://wiki.gnome.org/TranslationProject/ContributeTranslations#Reserve_a_translation https://l10n.gnome.org/help/vertimus_workflow/) pot files generated with https://wiki.gnome.org/TranslationProject/LocalisationGuide#po_files Maybe GNOME is not using it at full potential though. | Based on PHP and MySQL. Simple web interface. | Asked User:Chaduvari | Asked User:Chaduvari. Not so good if I see "Play [the screeshot]" translated as "Play [the game]" on G+. | Java, MySQL | "Mylingual" enables to translate the various web-services into your language unofficially. Can translate the various web services. | Forum registration broken as of October 2015. | Translate is "not quite as smooth" https://github.com/gittip/www.gittip.com/issues/957#issuecomment-40908124 | They make screenshots and "tag" (document) messages semi-automatically for you | Maven+Jenkins plugin which extracts strings from a software and sends them to their website for paid translation | Website translation for Drupal and Wordpress | Yet another online PO editor | |||||||||||
7 | Who is using it? | Lot (LibreOffice, BOINC, YoWindow, Evernote, ...) | MediaWiki, iHRIS, FreeCol... 500 active translators per month of total of 4700. Plus self-hosted instances like f-droid.org/translate | Lot (5000+ devs; Fedora, MeeGo, Mozilla, Mercurial, Creative Commons, VirusTotal, Django, FreedomBox, DoudouLinux, OpenTranslators, OwnCloud, Zotero). «customers in over 30 countries representing over 17,000 projects with 170,000 users» | phpMyAdmin (dozen projects, 2k strings) | Lot, but "Launchpad Rosetta module is unmaintained (see the constant "Timed out" errors that appears everywhere)". Almost all Ubuntu translations live here, but translators appear to be dissatisfied and Canonical doesn't invest on it. | ? (Wordpress and Automattic stuff, LimeSurvey) | Nobody | Nobody | – | – | Only Adobe products. | Used by Facebook to receive translations from the people who have to know it best. Number of translators unknown, many inactive. | – | Nobody (300 strings, some languages) | ? | GNOME | Mozilla Projects, Romanian FLOSS translators website | – | – | AOL | various projects such as Aloha Editor | Various extensions (add-ons) for Firefox and Thunderbird. Says over 1000 portuguese something (translators? fully translated extensions? extensions with a portuguese translator?) | Rails apps only | A handful small companies | Decathlon and other e-commerce websites, to freelance product description creation (not necessarily translation) | TheRosettaFoundation.org | TranslatorsWithoutBorders | ||||||||||
8 | Can buy translations via it? | No | No | Yes | No | No | – | No | No | – | – | – | No | – | – | Probably, via parent company Welocalize "able to deliver on-demand translation in over 100 languages", "over 400 employees worldwide" | They have professional translators. Probably everyone can also ask them to translate, for a fee. | – | – | Yes | Yes, including testing on-device | Yes | Yes | |||||||||||||||
9 | Search | "Extract messages using simple text or a regular expression". Search via pogrep or Lucene, can distinguish among files but not languages (source and target searched together?). | ReplaceText with regular expressions by admins directly on wiki; Special:SearchTranslations for everyone (no regex): each language (including message documentation) can be filtered. Each string is a wiki page: everything is crawled by search engines and it's immediate to go from a language to another of it (compare https://bugzilla.mozilla.org/show_bug.cgi?id=868326). | No? | Fulltext search based on Whoosh (?) | You can search in english or your language string | Searches everything together, allows to filter out some words. | Can search for string keys and content. Can limit search to particular file (no facets) and filter with status (untranslated, outdated tokens (fuzzy?)) and sort by state | Can search for content (source and translations). Search is limited to particular message-group, and filter with status ("untranslated (by me)", "translated/voted (by me)", "live"). Search results can be sorted by 6 ways (incompleted/completed, easy/difficult, old/new). | Yes. By product. By language. By string. | Search (Original/Translations) is available but may not always show all matching strings. Strings can be edited directly on the results page. No additional filtering. | Search by string is only way to find messages to translate/vote. | No | ? | Can search in the project. | None | Can search in the project. | |||||||||||||||||||||
10 | Cross-language search | Yes, with web interface Special:SearchTranslations, powered by ElasticSearch + web API. | No | Advanced users may manage to use pology's posieve command-line tool for this purpose? http://pology.nedohodnik.net/doc/user/en_US/ch-sieve.html | ||||||||||||||||||||||||||||||||||
11 | Translation aids and contextualization [1] / message documentation | Assistant languages ("alternative source language"), by string content rather than key; no diff for fuzzy. | TM, IOL/"in other languages" [i.e. assistant languages], docs, checks [partly documented], Ask question, insertables | Docs (but "only comments in the headers of the source file" from PO), but «they only accept really short context/description text fields»; no diff for fuzzy; recently added side by side, diff and assistant language (http://blog.transifex.com/post/81393514388/improved-translator-experience-in-web-editor). | Standard pofilter checks (90 % for format or editor limitations, can be customised). "you can also let Weblate automatically recognize texts on the screenshots using OCR and suggest strings to assign" https://blog.cihar.com/archives/2017/02/17/whats-coming-weblate-212/ | There are Translation Memory suggestions of some sort. Some users maintain glossaries for themselves. | Fuzzying is unconditional. https://glotpress.trac.wordpress.org/ticket/263 | word-by-word comparison for fuzzies | Cross-language discussion | There are discussions, but inactive. | Translation memory, string leveraging support | Facebook Group for each language. Assistant languages introduced only in 2015. https://www.facebook.com/FacebookTranslationsTeam/posts/943507839029348 | None | None. (Has a check "that order of printf-formating directives (%s, %d etc.) is the same in the translation as in original string".) | context information, ask | – | None | None | "Great QA features": "Write notes", "Automatic validation", "Placeholder highlighting" | |||||||||||||||||||
12 | Translation memory or other? | No TM; glossary i.e. terminologies where suggestion/definition for a word is shown to translators every time that word is used, with poterminology suggesting common words to standardise. They're trying to set up TM services at http://amagama.translatehouse.org/ now (still just a prototype). | Own TM, ElasticSearch (also Solr option). Can be federated and can access TM of other instances over the web if public. | Transifex incorporates a Translation Memory (TM) system to provide automatic suggestions based on similarities between source strings, allowing translators to leverage previous translations. See http://help.transifex.com/features/tm.html. As of 2015, it was missing some features offered by translatewiki.net: https://www.transifex.com/blog/2015/translation-memory-3-0/ | MyMemory? Some dictionary feature, since 2.4 editable while translating | Yes, about all the projects inside Launchpad | No TM. https://glotpress.trac.wordpress.org/ticket/288 | 2.0 will have some sort of glossary feature https://github.com/zanata/zanata/wiki/Glossary-management | No; but glossary (a list of existing translations for words are searched from the database) | Similar translations are shown in Translation view. Pop-up glossary. | Yes. | No memory, but a glossary for terms that have a fixed translation. Many strings have an explanation attached to them (not always helpful). | No | TM, glossary | – | No | Translation suggestions are shared among the projects and users can vote their preferred suggestion. | Yes, TM (one or multiple) | No | No | No | Glossary suggestions, also from translation memory | ||||||||||||||||
13 | Machine translation? | Yes: Google (if you pay and get key), Apertium, others | Yes: Microsoft (with old free key), Apertium, Yandex, others (Google removed, no key) | Yes (elaborate!) | Microsoft, Apertium | No | Only Google Translate plugin. https://glotpress.trac.wordpress.org/ticket/103 https://glotpress.trac.wordpress.org/browser/trunk/plugins | No | Yes. | No | – | No | Yes (Asia Online, other?) | No | No | No | "Variable checking between original & translated text" | |||||||||||||||||||||
14 | How is MT/TM/other shown to translator? | Immediately shown on top next to definition and docs, but can require scrolling to see everything (and usually does for lower things like assistant languages); was all shown, on top, with old interface | Immediately shown below translate text box. | first there is the original string, then the target language string or suggestion and then you write the new string or suggestion. | "translation" textarea is followed by a list of similar sources/translations. | Flagged. | Description, if available, underneath every string. Glossary entries shown underneath textfield. | – | N/A | – | – | – | ||||||||||||||||||||||||||
15 | Translator experience for outdated translations [1] | Changes in source automatically mark translations as outdated; translators can list them; a diff for both the source and the translation is available to them within the editor | When the source string is changed, the current translations are unconditionally removed? But they stay in the translation memory. | – | ||||||||||||||||||||||||||||||||||
16 | Validation features | Rudimentary TM; checkers to be written by admins, but 47 error checks for admins from pofilter, mostly specific to formats or compensating shortcomings in the translation editor and other requirements for valid target file export (like missing credits, blank translations). Actual benefit to translators and in preventing errors: dubious. But TWN doesn't check all variables even for MediaWiki (e.g. nonexisting magic words). http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/pofilter_tests.html Didn't find anything like http://pology.nedohodnik.net//doc/user/en_US/index-mono.html#sv-check-tp-kde though | Reviewing; fuzzy messages (e.g. PO), converted to suggestions; votes for suggestions (not sure if the latter belongs into this box) | None | No | All translations need to be approved by a team of 2-3 validators per language. Discussion with(in) the teams and feedback on a separate forum. However this is a hack, not yet a GlotPress feature: https://glotpress.trac.wordpress.org/ticket/123 | Votes and suggestions that can be exported and used for offline translation https://github.com/dashohoxha/B-Translator/blob/master/docs/README.org#the-processwork | Voting and karma | «At RailsConf 2012, Dutro [12] reported on Twitter’s highly successful approach to collaborative translation involving 550,000 volunteers, 16,000 active source language phrases, and 1,450,000 translations. Twitter’s approach involves the moderation of strings by translators with elevated moderator privileges and a reputation system that not only takes into account the amount of words translated by a particular translator, but also keeps track of their ‘karma’ and ‘phrase maturity’; as an additional mechanism, the Translation Center uses a community voting system to support the identification or the most suitable translation.» https://dx.doi.org/10.1007/978-3-642-35085-6_3 | Votes | Votes | None | ?; TM match stats, votes | – | None | "Concordance search"? | None | None | RVoting; reviewers and moderators to approve/change translations | |||||||||||||||||||
17 | Registration and unified login | "When I last used it, (free-software localization interface) Pootle didn't have email integration". They have some RSS notifications for events like sync with VCS. http://docs.translatehouse.org/projects/pootle/en/latest/features/notifications.html | Free to all. | Gratis registration for all translators; gratis registration of open source projects. No unified login. | Form, confirm email; email notifications for events | Launchpad | wordpress.org forum account | Via FAS (Fedora Account System) account for fedora.zanata.org; otherwise OpenID or local registration | With Steam account | Login via Twitter | Yes. Adobe Id? | Login via Facebook | Same as site | Google, Twitter, FB | – | drupal.org user account | Drupal/Wordpress? | Gengo user account. Can also login with Facebook or Google | Twitter authorization | BrowserID (Persona) | Via GitHub | |||||||||||||||||
18 | Activity notification, incentives etc. | Community building: translation rallies, aperiodic newsletters. RSS for edits but not for translation project events; email notifications only for edits/reviews/comments on watchlist | Updates from project managers and various other kinds of notifications. | "Zanata does not support notifications", 2015 | They give letter of recommendation to translators. A badge might be shown on your twitter profile if you're very active. They give achievement badges. http://translate.twitter.com/assets/achievements-ee10ae7f483e324eaffbad4fb6ecef82.png There's a list of top translators. | Gamification. Badges. Moderation. | Facebook Notification on translation approval, leaderboard (weekly, monthly, all time, total impact), awards (based on translation quality and quantity), "By translating, you help these friends who use Facebook in [lang]". | No | Translations ranking | None | None There is a list of websites with last modified times and translators' usernames | None | ||||||||||||||||||||||||||
19 | Prioritisation and the like [1] | Messages can be placed in "virtual folders" | Messages can be placed in different "message groups" depending on the VCS file they come from, or other methods (list of messages by key). | None, but project managers can make different 'resources' (with attached priority) | None? But translation groups organise themselves, e.g. Ubuntu translators don't bother translating components of the OS which "arrive from elsewhere" (like GNOME). | Allow setting originals’ priority on import (a recurring topic in their blog, they seem to care a lot) | No. | No | ||||||||||||||||||||||||||||||
20 | Other interface features | Rudimentary special characters insertor per language | Full-pledged input methods and web fonts (ULS) | "Most other tools have similar hotkeys, a reasonable amount doesn't or didn't work in weblate. It's UI has different margins everywhere and in very bright." https://ieji.de/@martijn/109224236363877483 | "Launchpad does not allow direct downloading/uploading translation. You have to wait for several hours just to download/upload a translated file." | "Zanata has monstrous and slow CLI client", 2015 | You have to choose a category like Twitter for Android or Twitter.com, so no translating "All strings" | Moderation interface. | All strings are basicly listed on one page, no categories, you edit/vote on individual strings that appear randomly or via search. SPECIAL feature: If you use Facebook in the language you translate into, you can translate inline anywhere on the site via underlined phrases. | – | None | "Setting the tone and background information", length limits | Sidebar dictionary (translations from standard bilingual dictionaries) | |||||||||||||||||||||||||
21 | Permissions needed | Only admin and reviewers can see error checks and act on them. Some users can only give suggestions for the translators to approve, not all users have "overwrite" permission. | Translation: fill a form, manual approval. All translators are equal, no suggestions. All translators see the checks and can review; for this reason, checks are not spammy and have few false positives. | Can ask a License agreement to be subscribed. Without logging in, users can't even see l10n: no discoverability for people wishing to fix specific things. | None | None to suggest translations. | Request via email to get new project added; just click to join a translation team? | Difficult test translation, 2 hours to complete. | Have to sign a very nasty Translation Agreement and to follow up to ten "lessons" (lenghty walkthroughs/quizzes) before tasks activate ||| juthilo: I actually don't remember any nasty signup process, so if there was one, it was endurable for me. ||| Nemo: I meant nasty as in legal conditions; what about the lessons? Didn't try those- | Not for translation. Yes for moderation. | None as far as I remember. | Request button but they seem to accept everyone in a while | None | – | None | No | Maximum 3 official translators [per language]? http://www.babelzilla.org/index.php?option=com_content&task=view&id=43&Itemid=25 | |||||||||||||||||||||
22 | Supported file formats | OpenOffice.org SDF/GSI; Mozilla: .properties, DTD, XHTML, .inc, .ini, etc.; Comma Separated Value, TMX, XLIFF, TBX, PHP, WordFast TXT, Qt .ts, txt, .ini, Windows .rc, ical, subtitles, Mac OS X strings | AndroidXml, Dtd, PHP, Gettext, Ini, Java, JavaScript, Json, MediaWiki, PythonSingle, RubyYaml, Wiki, Yaml, AMD i18n bundle | Android Resources, Apple strings, Desktop, Gettext, Java property, Joomla INI, Magento CSV, Maker Interchange Format (MIF), Mozilla DTD, Mozilla Property, PHP, Plain text, .plist, Qt Linguist (TS), Subtitle formats (3), Wiki markup, Windows resource (.resx), HTML/XHTML, XLIFF, YAML (1.1 only) | Originally those of Translate-toolkit, but only PO (Gettext) used/tested. Various other formats added in later versions with various levels of support (checked up to 4.14): XLIFF, Qt .ts, AndroidXml, ARB, Fluent (.ftl) and others https://docs.weblate.org/en/latest/formats.html#translation-types-capabilities | Only PO according to http://help.transifex.com/intro/faq.html#how-is-transifex-different-from-launchpad-s-rosetta . Translators however, at least in Ubuntu, never see the PO files and only interact with the web interface. | .po, .android and .rrc | Gettext/PO, Java Properties and XLIFF (partial) | – | N/A | Web interface. Database based. No file export. Sent via API to central infrastructure. | N/A | None | Custom (gettext-like) | "All" | Gettext | gettext .po | It supports several format files as gettext, open office sdf files, mozilla dtd files and more. | – | – | "Filters for dozens of filetypes, including Word, RTF, PowerPoint, Excel, XML, HTML, Javascript, PHP, ASP, JSP, Java Properties, Frame, InDesign, etc." | JSON | Can process xpi (zip) file. | No PHP; YAML, ... | YAML | App l10n and markets (.strings, .xml, .resx, .resjson, .rrc), YAML, .properties, Gettext, documents (.doc .pdf etc.) | ||||||||||||
23 | RTL support | Comprehensive for the web UI and for the translation editor. | Comprehensive for the web UI (uses MediaWiki) and for the translation editor. | Comprehensive for the translations. | Comprehensive for the translations. | Comprehensive for the web UI and for the translation editor. | Comprehensive for the translation editor. | Comprehensive for the translation editor. | ||||||||||||||||||||||||||||||
24 | Mobile support | Pretty OK. The website is adapted for mobile phones. The current source sentence is shown at the top of the mobile screen, and the translation is typed in the middle. There are buttons to submit the translation and for going back and forth. The whole list of source sentences can be seen by swiping the screen left to right. | ||||||||||||||||||||||||||||||||||||
25 | Translation templates | Bilingual file formats PO, XLIFF, Qt TS, TBX, TMX can be used for offline translation (Virtaal recommended). POT used for PO files; can import Java properties, Mac OSX strings, PHP arrays, Subtitles in many formats | PO; gettext strings converted to "MediaWiki-keys" format used by Translate, templates never needed (yet?). | Can use POT (but also PO) as the source file for creating a resource | Yes | templates? | No. | – | – | No | – | No | None | None | ||||||||||||||||||||||||
26 | Plural, grammar, gender and whatnot | Case on next column: imported but not exported. | In PO, "If a plural string doesn’t have all the plural form fields filled in or the number of plural forms is different than the number we have in our database for this language, the translations will not be imported" | You have the po option for plural | Something for plural | Plural tags appears. e.g. {{#targets_count_one}} for singular, {{#targets_count_other}} for plural. {{}}s are for {{ mustache }} library: http://mustache.github.com/ ||| juthilo: Often, they use multiple strings where one with a variable might have been enough. | Depends on product. | There are variables but strings are just newly created for each applicable case. Gender is a problem because there is no popular equivalent in many languages to the English "they" for unknown and many strings become inflexible because of the variables/their position. | No | – | Can use regular expression to translate the various DOM nodes. | No | "Pluralization string grouping" O_o | |||||||||||||||||||||||||
27 | Export | All the supported formats via API + .qph, .qm, .mo. Can be integrated with VCS (CVS, SVN, Git, Darcs, Bazaar, Mercurial) on own Pootle server: only via PO, doesn't handle conflicts (VCS wins and Pootle marks own translations for review), can be triggered via GUI but needs passwordless keys. | Directly to VCS by shell users, with no problems of format validation in export phase or other errors, that are not the committer's responsibility; .po export via GUI (url); export in native format via GUI (url). Plans for a fully automated export to the VCS in the future. | "They constantly forget to do tx pull/tx push in Fedora which leads to untranslated apps" https://www.mageia.org/pipermail/mageia-i18n/2013-April/004170.html ; "translators can accidentally break your package build", "developer gave Transifex write access to his VCS repository, and translations were automatically committed by Transifex" (before 1.0); in 1.0 export is triggered by project admin via CLI | Git, Mercurial, no SVN; no conflict resolution | Only to bzr repo directly; or PO download. The web transltor adds some legal headers automatically. | Doesn't export message documentation. https://glotpress.trac.wordpress.org/ticket/294 | N/A | No. | N/A | – | Manual/custom | "Note that you can obtain .po files from your language's status pages on the GNOME Translation Project website. (See below). Sometimes special characters (non-ASCII) can be garbled doing this" | gettext .po | – | – | PHP single quoted array (zipped) | simple text format and JSON | Single file or xpi (zip) archive. Developers get an email when the "official translator" marks a l10n as released. http://www.babelzilla.org/index.php?option=com_content&task=view&id=42&Itemid=25 | Automatic sync | ||||||||||||||||||
28 | Import | "Merge snippets of PO files into your existing translations", but can only bulk-select them as approved/discarded/suggestions. New files (and projects) added by privileged users (admins) via GUI, also mass-upload of ZIPs; maybe also automatically if VCS integration and file pattern configured. | Full offline-online translation integration via .po import/export by translators on GUI; new strings automatically from CVS, but new projects/files added by shell users. As of 2015, experimental feature to have group configuration on-wiki, with fully automated import. | New projects created with a form on the site; management (only?) via your command line. From 1.0, will require POT: "intltool-based projects which do not have a POT file are not supported". | "To enable automated workflow on GitHub, you need to enable Weblate service hook in settings with hosted.weblate.org as URL. If you want Weblate to automatically push changes as well, add Weblate user to collaborators and let us know you want to use this option. " Since 2.4, also bitbucket hooks. | You can upload a po before you have download from Launchpad before (they put something at the headers'file). "Launchpad needs the POTs to be build during general make cycle". | N/A | No. | N/A | – | Manual/custom | – | gettext .po | – | – | simple text format | single file or xpi (zip) archive | |||||||||||||||||||||
29 | Frequent sync AKA continuous translation AKA agile localization [1] | Yes, since September 2009 on Wikimedia | – | |||||||||||||||||||||||||||||||||||
30 | Statistics features | Standard completion stats; "word, string and file counts of your files" with a preference for word counts since sometime in the 2010s. Probably something a bit like KDE's http://pology.nedohodnik.net//doc/user/en_US/index-mono.html#sv-stats | Lots, by number of users or messages involved (including per language, per project or other message group, total; both for translations and reviews). Available for any period and with customisable graphs. | Unclear; "See precise, real-time translation statistics like how many words have been translated, when, and by whom" | Activity; translation completion widget | You have some kind of Karma (about how many translations are approved) | None and not a priority? https://glotpress.trac.wordpress.org/ticket/94 https://glotpress.trac.wordpress.org/ticket/81 | Message-groups: Percentage of translation Translators: Ranking (top %), Number of {translations, approved translations}, Number of {votes, approved votes} the translator gave, Number of votes the translator was given | Multiple. Moderation and translation. | Leaderboard | None | None | Activity, translator stats, other | "Login access should also show translation stats, both software and docs (see GNOME's platform for localization), and you should be able to submit translations there. GNOME have done a lot of work on this, so they're good people to ask." http://mail.python.org/pipermail/mailman-i18n/2012-August/001780.html | percentage of translations | "Cost calculation based on configurable rates for each step of the localization process" | None | completion ratio for each file/language | ||||||||||||||||||||
31 | Exists since | 2004 Pootle v0.8 = Feb 17, 2005 | ~2005 | 2009 | 2012 | After 2005: translation rather recent | 2010? First commit in 2008. | 2011 | October 2011 | Feb 14, 2011 | 2011 | 2012 | 2008 | 2009/2011, "Two online translation editors" (1997 very beginning) | 2007 | August 2005 but launched in March 2006. http://blog.babelzilla.org/2006/03/03/hello-world/ | ||||||||||||||||||||||
32 | Wikipedia | http://en.wikipedia.org/wiki/Pootle | https://en.wikipedia.org/wiki/Translatewiki.net | http://en.wikipedia.org/wiki/Transifex | http://en.wikipedia.org/wiki/Weblate | http://en.wikipedia.org/wiki/Launchpad_(website) | Not for translation | No | No | Not for translation | Not for translation | Not for translation | Not for translation | Not for translation | No | https://en.wikipedia.org/wiki/Crowdin | Not for translation | Not for translation | https://en.wikipedia.org/wiki/GlobalSight | http://ja.wikipedia.org/wiki/Japanize | https://pt.wikipedia.org/wiki/Babelzilla | |||||||||||||||||
33 | Contact | Yours truly | http://blog.glotpress.org | for a bug report and a feature request http://support.twitter.com/forms/translation | ??? | There's a Translations App section in Facebook help with report options. | Krzysztof Kowalczyk <kkowalczyk@gmail.com> | globalsight-dev@googlegroups.com | Kazuho Oku / Cybozu Labs | |||||||||||||||||||||||||||||
34 | License of this document | CC-BY-SA 3.0 (International) | ||||||||||||||||||||||||||||||||||||
35 | Notes on this document | [1] http://personales.upv.es/luileito/web/docs/papers/nimrod-wise2014-preprint.pdf | [2] https://www.zotero.org/groups/foss4trans/items/collectionKey/G4QDQJ78 | [3] Column originally added from Reina, Robles, JGB, http://dx.doi.org/10.1007/978-3-642-38928-3_11 / http://gsyc.urjc.es/~grex/repro/oss2013-translations/ , CC-BY-SA 3.0 | ||||||||||||||||||||||||||||||||||
36 | ||||||||||||||||||||||||||||||||||||||
37 | ||||||||||||||||||||||||||||||||||||||
38 | ||||||||||||||||||||||||||||||||||||||
39 | ||||||||||||||||||||||||||||||||||||||
40 | ||||||||||||||||||||||||||||||||||||||
41 | ||||||||||||||||||||||||||||||||||||||
42 | ||||||||||||||||||||||||||||||||||||||
43 | ||||||||||||||||||||||||||||||||||||||
44 | ||||||||||||||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||||||||||||||
46 | ||||||||||||||||||||||||||||||||||||||
47 | ||||||||||||||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||||||||||||||
52 | ||||||||||||||||||||||||||||||||||||||
53 | ||||||||||||||||||||||||||||||||||||||
54 | ||||||||||||||||||||||||||||||||||||||
55 | ||||||||||||||||||||||||||||||||||||||
56 | ||||||||||||||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||||||||||||||
59 | ||||||||||||||||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||||||||||||||
61 | ||||||||||||||||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||||||||||||||
68 | ||||||||||||||||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||||||||||||||
100 |