-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle task localizationUpdate does not work #3573
Comments
I think, I can work on that in January. Meanwhile, you should be able to log in at crowdin and remove the key there. Need to make you maintainer there, though. |
Please DO NOT remove obsolete keys in other language files. This is done by crowdin automatically: #3585 I will remove the task completely or have it output that there is no need for a check, because of crowdin! |
@koppor Right now we have tests in place that require to remove obsolete language keys from other languages. It would be nice if we could remove the |
I thought, I adapted the tests. Seems, I missed something. Have to check...
Am 05.01.2018 12:01 schrieb "Tobias Diez" <notifications@github.com>:
… @koppor </~https://github.com/koppor> Right now we have tests in place that
require to remove obsolete language keys from other languages. It would be
nice if we could remove the localizationUpdate step completely (less
things to do manually), but then the tests should be adopted accordingly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3573 (comment)>, or mute
the thread
</~https://github.com/notifications/unsubscribe-auth/ABTaftbvUCzp6PiQbYoCZPnhgV_ph9zcks5tHgECgaJpZM4RLq3L>
.
|
This test fails if you remove language keys from the english file but not from the others: jabref/src/test/java/org/jabref/logic/l10n/LocalizationConsistencyTest.java Lines 50 to 51 in 3b2d35f
(If crowdin handles this case automatically, then there is no need for this test, right?) A few other tests still refer to the jabref/src/test/java/org/jabref/logic/l10n/LocalizationConsistencyTest.java Lines 140 to 142 in 3b2d35f
|
It is not as straight-forward as I thought. English escapes more characters than non-English:
German:
|
Any updates on this? I think we don't need the script anylonger or? |
An admin might still need it. Quoting: #3635 (comment)
I think, I just close it and put an "on-hold" label on it. |
Maybe we need to rework the quotes in the English file. |
Finally I found some time to take a closer look at the syncLang.py script. To be honest, it's pretty difficult to determine the exact origin of this problem. My very first thought was that there might be a problem with different character encodings. The script always assumes the content of the property files is written in UTF-8 encoding. But Eclipse is using ISO-8859-1 encoding by default which is determined by the content type. After some more research within the script I found some really nasty little mistake, if you have a closer look at lines 52 and 53: Lines 52 to 53 in 01d3d4b
I'm not 100% certain if this will fix the whole problem but we're going to find out real soon, I guess. I pushed the fix for this issue here: Additionally I added a new class that allows the script to locate it's position within the repository. UPDATE: I DID IT! I found a logical issue deep within the merging process of the files. Have a look here: Lines 307 to 308 in 01d3d4b
Missing keys are added as empty Strings to the dictionary... So far so good. But then: Lines 314 to 321 in 01d3d4b
Keys that contain empty Strings are not written to the new properties file which leads to missing keys over and over again. I simply removed the if and everything worked perfectly fine. New commit: |
localizationUpdate
leads to resorting and adding of many language keys due to the recent changes. Thus, at the moment it is not possible to remove a pair from the english file and propagate this change to the other languages.The text was updated successfully, but these errors were encountered: