Zanata Glossary needs to be upgraded so the entire glossary can be exported, in order, for any language (For Japanese this would mean attaching and ordering via Hiragana metadata of each word). We also need to be able to have context definitions of words (as technical terms may be used differently across business units).
Amazon uses the above mentioned Japanese solution
Now that we have glossary editing in Zanata, we certainly should allow users to export their glossaries. Incidentally, we also need to make the glossary edit feature a lot easier to find - it's currently behind an Info button in the Details column. I assume we want to export PO and CSV (our supported input formats). Isaac, do you have a reference for the information about Amazon's glossary?
Alex, regarding the "context definitions of words" requirement, this is broadly similar to the "part of speech" in Google's CSV format: https://support.google.com/translate/toolkit/answer/147854?hl=en How are we representing the CSV fields (including part of speech) in the Glossary UI?
Hey Sean, I'll see what info I can gather on Amazon's implementation. In the mean time, some further suggestions for implementation have come from some of our translators: - Ability to have multiple entries for each single terminology. As you can see on the attachment, the word "destination" are translated in many different ways, depending on the usage, context or product. - Ability to enter terminology consists of multiple words. For example "hot plug" "embedded database". - Applicable product filed - the same terminology can be translated differently depending on the product. For example, JBoss in Japan might request us to translate a term in a certain way, which might be different from what we are requested to uses for RHEV. If the translation does not vary, we can simply leave that field empty. - Definition / description field: This would be useful when a term has multiple meanings. Translators can read this information to see if the particular translation is adequate for the usage/context in the document he/she is translating. It can also be used to add some extra information that can be useful for translation. (e.g. web link) - Grammatical information (word class / grammatical categories) field - Some word can be used as noun as well as adjective and verb, but the translation should be different. (e.g. "file" can be both noun and verb) When entering multiple translation for single term, this would be very useful.
Created attachment 756121 [details] Example layput of a technical Japanese Glossary
(In reply to Isaac Rooskov from comment #0) > Zanata Glossary needs to be upgraded so the entire glossary can be exported, > in order, for any language (For Japanese this would mean attaching and > ordering via Hiragana metadata of each word). 1. Some languages, like Chinese, have different way to sort words, (Pinyin, Strokes, Radical-Strokes), will the selection of collation be include in this bug? > > We also need to be able to have context definitions of words (as technical > terms may be used differently across business units). 2. As Sean pointed out, it largely depend the export formats: a. For PO, is compendium format (https://www.gnu.org/software/gettext/manual/html_node/Compendium.html#Compendium) Sufficient? b. For CSV, should we also include project name and msgctx?
Reassigned to PM
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-153
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days