Transifex provides a glossary function per language, but what we are missing is a glossary which gives the context for the English terms. Sometimes you can use the tags in Transifex to work out where a given text is actually used, but other times it’s still not clear. And some terms are ambiguous when translated, so extra context is needed.
The aim here is not to provide a context per tag, nor for every single word, but if a translator finds a given word ambiguous, he/she should be able to come here and get help. I don’t know if it’s best to do a big wiki or what, but something is better than nothing.
I also think that the English developers should get into the habit of coming here to confirm their terminology too: fairly often there are inconsistencies in the original text, which make extra work for everyone. (Dear devs, every time you change a word, that is numeber_of_languages people who have to review/check/translate something )
I feel you, I had similar issues for a long time. My current workflow allows me to reach the commit behind the need for translation very easily, though. I can also see what has changed easily. That’s because I realized I can have the Git blame of the English locale file opened. For instance here is the blame of server.en.yml:
Note that you will most likely need a couple of refreshes to open it because the document is so massive. Github server can barely calculate the blame for the two major locale files, server and client.
Rapid editing of same strings is an issue, I agree. Has happened a couple of times recently. It’s especially problematic because the stable release is so near. If not translated again before the release, the string will remain untranslated for 4-5 months for everyone using the stable branch. More careful proof-reading before committing would certainly ease the burden of translators.
Initially we used the term “Private Message (PM)”, but since they aren’t private, we changed to “Personal Message (PM)”.
And since less word is always better we now tend to use “Message” (as opposed to “Topic”).
Yup.
Pinned topics are topics that are at the top of topics lists (either in a category or globally).
Featured topics are topics that are featured in a category (used only in /categories and in category “boxes”)
Hot topics are topics which have a burst of activity (usually due to a topic). They might be subject to “temporary read-only mode”
Banner topics are topics that are shown above the topics lists.
My OCD would like to, but that might not always be possible.
There are Archived topics, but I don’t think we use Archive to talk about Backup, do we?
)
标记的主题）。它们可能会进入“临时只读模式”。
topic). They might be subject to “temporary read-only mode”