New Gradle Task: sort Localization Keys#1933
Conversation
|
Just to make sure: Will this PR keep empty entries at the bottom of the file? (that makes localization much easier) |
|
|
|
Thanks for your quick reply. |
|
@mlep I think for new entries (not yet present in English), they will be still stay and added at the bottom. |
| Nothing_to_undo=Ingenting_\u00e5_angre | ||
|
|
||
| # The next is used like in "References found\: 1 Number of references to fetch?" | ||
| #Thenextisusedlikein"Referencesfound\:1Numberofreferencestofetch?" |
There was a problem hiding this comment.
The spaces are already missing in the current English localization.
Comments in languages other than English overridden by the English one.
https://github.com/JabRef/jabref/blob/master/src/main/resources/l10n/JabRef_en.properties#L520
I'll fix them.
Edit: do we even need those comments? They are both the same and doesn't seem to address the line below.
As soon as you have a PR which adds new localization propertires and another PR with new localization gets merged you have to solve these conflicts which is just annoying.
With this gradle task the keys in the Localization files get rearranged according to the English file.
The top 3 comment lines of each file stay the same (some files have different encoding) but everything else (comments, blank lines) are getting synced with the English file.
The localization file are only sorted if they have no missing, obsolete, or duplicate keys.
A colored output is printed to inform the developer.
When this PR has passed I plan to refactor
syncLang.py, code and output wise.