GLOSSARIES
Ability to define a glossary of terms that can be applied across multiple projects. Glossary items should have part of speech and a description that tells the translator how this term should be used. Would be helpful if translator could look up terms in the glossary while translating terms in the main interface. While using poeditor to translate new terms, suggestions would be provided based on Glossary items. Google Translator Toolkit has a custom CSV format that could be used for importing and exporting glossaries http://support.google.com/translate/toolkit/bin/answer.py?hl=en&answer=147854 Pootle has a mechanism to generate a list of frequently appearing terms as a starting point for a person to edit together a glossary. http://translate.sourceforge.net/wiki/pootle/terminology_matching
-
Will Ezell commented
This is crucial to ensure translation quality.
Gengo supports glossaries, and it's necessary to use this feature to ensure any new translations use the same terms as the existing translations.
I suggest that, rather than making glossaries a separate feature, you just allow certain terms in the base language to be marked as glossary terms. The glossary for each language could then be generated from the translations of those terms.
-
Daniel commented
A must have feature.
-
Tomas commented
For us, this is an important feature. Now we need to keep glossary in separate excel sheet and share with all translators which is very ineffective.
-
Florian Simmendinger commented
Amazing idea, this would be really great. For example we translate certain features always the same way (e.g. "Interaction Lock") and it's a hassle to have to manually chase after each word with each translator with each language.