Somehow all occurrences of the entity (non-breaking space) were changed to   (moved); in Tor Launcher's network-settings.dtd files.
I am not sure where things went wrong, but at this point the strings on Transifex are bad. They were correct prior to commit 7ffed96e51cdb4207980810ece44c58d2d25fda6
We could:
Remove the non-breaking space characters (which arguably makes the text a little harder to read).
Fix the files in Tor Launcher and hope the problem does not recur.
Fix the strings via transifex.com and hope the problem does not recur.
Mike, do you have any theories about how this happened and how we can avoid it in the future (and what should we do right now)?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
If we can fix these strings in transifex such that it does not decide to invalidate them, that is probably the best approach. I am not sure how to do that, though.
I think mttp and/or phoul are in contact with the transifex people. Perhaps they can offer some suggestion.
Trac: Cc: mikeperry, brade to mikeperry, brade, mttp, phoul
It appears that there is indeed an issue on Transifex's side. While the updated strings appear in the editor, the actual translations we pull down (or if we pull down their copy of our source file), the "  (moved)" issue remains.
I have contacted OpenITP, and will update this ticket once I hear back.
I am not sure what happened, and I don't know how things were fixed on the Transifex side, but maybe someone edited strings in the above files on Transifex recently and that somehow "locked in" the bad   (moved); sequences? That is just a guess though.
Trac: Status: closed to reopened Resolution: fixed toN/A
These are languages that have been removed from Transifex, but have not yet been removed from our Git. I will be working on resolving this over the weekend, please see #11754 (moved).
These are languages that have been removed from Transifex, but have not yet been removed from our Git. I will be working on resolving this over the weekend, please see #11754 (moved).
Sorry; I forgot about that. If it is helpful to you, brade or myself could remove the odl locales from tor-launcher.git (we would just need a list of locales).
I have fixed the issue for the tr & zh_TW teams, as these are teams that actually exist and had mistranslated . This fix should appear in git in the next couple hours. As for the other teams, I will be removing them from git tomorrow.
My current list is:
af-ZA
am-ET
bg-BG
bn-BD
ca-ES
cs-CZ
el-GR
es-NI
sq-AL
zh-CN.GB2312
zh
When Mike Perry updated translations recently, we picked up this file (brade and I just fixed it manually in Tor Launcher). This problem will continue to recur until it is fixed at Transifex and/or in translation.git.
phoul -- Can you please look at this problem? Thanks!
No, the fix was global. The problem here is that certain teams are attempting to "translate" , and are doing so incorrectly. In this case, " " had become "  (moved)." in many of the strings, which caused the issue to reappear.
I have fixed this issue with the pt_BR team. One thing that might be useful here is adding a TRANSLATORS comment to the strings that include " " that specifically says not to translate it.