As TAC is going to close in a couple of months and all the teams are moving to Transifex TAC team is going to work only on high priority issues that impact current activity of the remaining TAC users.

Hi!
TRANS-280 TRANS-374 TRANS-600 all the same purpose.

+1 It's very important get more consistency in our translations

Something like this would be lovely.

I think that's correct. Common terms and so on are something that is specific to each locale.

"Mouse" is translated in Polish. Should the glossary be defined per language ?

This feature (term glossary) is important for other translators that use TAC (NZTC already access to this in their tool-set), so they are able to be consistent when translating key concepts of the product in question.

I.E. Whe should not have in JIRA 5 different translations for words like "Issue", "Dashboard", "Worklog" ... This brings me a lot of grief when trying to get quality in the Spanish localisation for example. dbonilla what do you think?

Side note: A term glossary is part of the toolkit that is used by a professional translator.

Thanks for the update.

From what I can tell, implementing this feature will not help NZTC. To help NZTC stay consistent with people who know our products we are implementing TRANS-370.

I think for the moment we will leave this issue unscheduled. As we get more time and as we feel the need for this rise we can come back to it.

Cheers,
Anton

Ah, the request completely just came off the top of my head I was handling the translations for 4.0 a little while ago and was chatting to Adrien Ragot about the French translation, and he pointed out that there was a word (widget, I think) that was translated incorrectly by NZTC. It just made me think that if we can have conflicts between someone who knows our products very well and a professional translation company, we'd get them even more when we ask the general public to translate for us.

If you need any info on how Confluence handled the translations we got from NZTC for TRANS-370, just let me know.

A glossary is a good idea. I believe professional translation tools have a feature which tries to help translators use the same translations for specific terms.

Anna, may I ask where the request for this came from? Is this something you have run into yourself when using TAC to translate Confluence? Or is this coming from a professional translations company?

We are currently working on TRANS-370 such that we can keep professional translation's company "translation memory" up to date for JIRA and Confluence.

I would really like to learn more as to how these requirements came about.

Cheers,
Anton

Do you mean a glossary page in target language, or in English? I am not sure how we could go about picking words for the glossary. Do you have any suggestion?

Hi!

Sorry, we got the description got a bit confused. The idea isn't to allow consistency with English, just consistency for certain words/phrases within a language. eg for the phrases "Personal Space" and "Add New Space" the term Space should be translated the same. Ideally there'd be some sort of macro system you could use to put in common phrases, but that's probably stretching it a bit. For the moment, if we could just get some sort of glossary page up that people could reference, that would be great.

Cheers,
Anna

I am not sure I follow. Do you want us to somehow detect that somebody used the word "Dashboard" in the translated text and reject such translations? Or if there is "Dashboard" in the original English message, we should not allow people to translate such string? Even if the traget language is, say Mandarin? Could you describe this in more detail?