nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Improving translation quality

ChangJoon Lee1

Hi, here goes my suggestions for translate.atlassian.com

1. Let me see an example of each message when I typing the translation.

Let me know what is going to be filled in {0}, {1} parameters.

I can't tell if it will be user name or name of project, or ETC.

2. let us post "recommended term"

Among translators, we would like to share common terms for certain frequently used terms.

Also, let us post translation guideline such as "Do Not translate product's name"

3. Let us change specific words in batch.

such as "Project" to "(Project in my language)"

Also, let the feature can help unify the various terms for the same one.

Also, it will help to correct previous errors.

The batch system may conflict with voting system, it can be mixed between item 2 and 3 above.

Accepted answers

jjaroczynski

Hi,

Thank you for suggestions.

1. That's difficult to do on the TAC web site because the params are filled dynamically by JIRA in runtime.

You may be interested in our fresh InProduct translation plugin for JIRA. It allows to translate JIRA right from its page so you can see all messages and provided translations live in a second. Just install the plugin in JIRA, select "Translate Page" from the user profile menu in JIRA and start translations.

The plugin is available in marketplace: https://marketplace.atlassian.com/plugins/com.atlassian.translations.jira.inproduct
You can install it from the UPM. It works with JIRA 5.1+.

2. You may be interested in https://jira.atlassian.com/browse/TRANS-280. Please vote it if you like it.

3. Currenlty we use something called 'suggestions'. When you list messages to translate on the TAC page their are prefilled with 'suggested' translations (if the same translated message found in other place). That's quite handy but suggested translations are not accepted by default and are not part of the language pack. They require manual voting in order to be included in the language pack.
If you need batch translations then feel free to to raise a ticket at https://jira.atlassian.com/browse/TRANS.

I hope the InProduct translation plugin for JIRA is an answer to all or most of your problems. If you need more features then feel free to vote existing ones or raise new requests at https://jira.atlassian.com/browse/TRANS

Cheers,
Jacek

All comments

jjaroczynski

BTW. If you like the InProduct translation for JIRA and would like to have the same for Confluence then please vote and comment following issue: https://jira.atlassian.com/browse/TRANS-579

jjaroczynski

Hi,

Thank you for suggestions.

1. That's difficult to do on the TAC web site because the params are filled dynamically by JIRA in runtime.

The plugin is available in marketplace: https://marketplace.atlassian.com/plugins/com.atlassian.translations.jira.inproduct
You can install it from the UPM. It works with JIRA 5.1+.

2. You may be interested in https://jira.atlassian.com/browse/TRANS-280. Please vote it if you like it.

Cheers,
Jacek

jjaroczynski

BTW. If you like the InProduct translation for JIRA and would like to have the same for Confluence then please vote and comment following issue: https://jira.atlassian.com/browse/TRANS-579

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

translate

improvement