fix(trans): Make all translations contain same fields#478
fix(trans): Make all translations contain same fields#478chinesedfan merged 8 commits intogitpoint:masterfrom
Conversation
It would be good to check it, but how did you do it? |
|
@lex111 By a Node.js script, it is easy. You can image it as a test suite file. |
|
I just integrated the check to travis ci. You can find that |
|
@chinesedfan great and useful script! Can invite translators here? |
|
Hey guys, I need your help here. Can you translate those missing fields, please? Of course, anybody can help even not mentioned below.
By the way, we'd better maintain translators list somewhere. |
|
Could you create a word list? Like #408 |
|
@abdurrahmanekr The missing words are different for different languages. Can you comment directly? For example, |
|
@chinesedfan awesome work! If we make this part of the travis check, could we define the guidelines that new translations should be added as "TRANSLATE_ME" instead of the english sentence or a poorly google translated string ? Or we can have a second script running in pre-commit that does that automatically. The translators list is already somehow available in CONTRIBUTORS.md. Translators have the |
|
And here are the missing translations for fr: (@Antoine38660, watcher = abonné sounds ok to you?) |
|
👍 @chinesedfan , here are the missing translations for TR: |
|
@machour Marking untranslated strings as TRANSLATE_ME really makes it easy to be discovered. But it may also make the app displays wired. I know we can find translators in CONTRIBUTORS.md, but don't know who is good at which language. @abdurrahmanekr Thanks again! |
|
@chinesedfan it makes the app display weird only when browsing it in translated mode using master. Which is mostly used by people who actually can translate the missing things they spot. This would also allow to perform a quick check for releases: if there's a TRANSLATE_ME somewhere, we're not ready to release. (and if the translator is unavailable, then we can swap with an english string just for the release) Seems like a fair trade-off when dealing with quality translations. |
src/locale/languages/ru.js
Outdated
| searchMessage: 'Поиск {{type}}', | ||
| repository: 'репозиториев', | ||
| user: 'пользователей', | ||
| noUsersFound: 'No users found :(', |
src/locale/languages/ru.js
Outdated
| repository: 'репозиториев', | ||
| user: 'пользователей', | ||
| noUsersFound: 'No users found :(', | ||
| noRepositoriesFound: 'No repositories found :(', |
src/locale/languages/ru.js
Outdated
| applyLabelTitle: 'Добавить ярлык к этой задаче', | ||
| }, | ||
| comment: { | ||
| commentActions: 'Comment Actions', |
src/locale/languages/ru.js
Outdated
| }, | ||
| comment: { | ||
| commentActions: 'Comment Actions', | ||
| editCommentTitle: 'Edit Comment', |
src/locale/languages/ru.js
Outdated
| comment: { | ||
| commentActions: 'Comment Actions', | ||
| editCommentTitle: 'Edit Comment', | ||
| editAction: 'Edit', |
src/locale/languages/ru.js
Outdated
| commentActions: 'Comment Actions', | ||
| editCommentTitle: 'Edit Comment', | ||
| editAction: 'Edit', | ||
| deleteAction: 'Delete', |
@chinesedfan see #481 |
* fix(trans): Correct Polish translation wording - typos - changed wording to work better in UI context * feat(trans): New resource keys translation. See #478
src/locale/languages/de.js
Outdated
| membersTitle: 'MITGLIEDER', | ||
| descriptionTitle: 'BESCHREIBUNG', | ||
| }, | ||
| organizationActions: 'Organization Actions', |
src/locale/languages/de.js
Outdated
| openIssueSubTitle: '#{{number}} wude vor {{time}} von {{user}} geöffnet', | ||
| closedIssueSubTitle: | ||
| '#{{number}} von {{user}} wurde vor {{time}} geschlossen', | ||
| issueActions: 'Issue Actions', |
src/locale/languages/de.js
Outdated
| abbreviations: { | ||
| thousand: 't', | ||
| }, | ||
| openInBrowser: 'Open in Browser', |
|
@machour yes... watchers can be abonnés (but looks bizarre 😉) |
|
@chinesedfan using @nersoh @arthurdenner I know you guys are Brazilians also, what do you think about? |
|
I think it's fine as well. We usually use |
|
Thank you all for this <3 @chinesedfan definitely would love to have a translations script check as part of our CI pipeline in |
|
@housseindjirdeh I already integrated the check script in this PR. But if you persist, I can separate it out. |
.travis.yml
Outdated
| - 'yarn' | ||
| script: | ||
| - yarn run eslint | ||
| - node __tests__/locales.test.js |
This reverts commit 66b3228.
|
Can we merge this PR first? It is hard to find translators for eo/nl, and we used to keep words in English if no one can help. @housseindjirdeh @lex111 |
|
+1 on moving forward with this and have Travis as a goal keeper for translations keys. |
I use a script to find out these missing fields.
How about adding a translations check task in Travis CI?