- This topic has 18 replies, 3 voices, and was last updated 3 years, 3 months ago by
.
-
Posts
-
Hi dear translators,
I’ll use this topic to inform you about upcoming changes to the language file format, which will switch from JSON to YAML with the next update (it already has in SVN).
Please do not worry if you are still working on a JSON file – you can continue working on it, and I will merge the changes to the new format.
The reasons for this change are multiple, most importantly, easier multi-line editing, and getting rid of the necessity to escape special characters like tabs and line breaks, which was necessary with the JSON format. I chose YAML instead of rolling my own format (which I considered briefly) because it is quite readable for both humans and machines. I’m also using a restricted subset of YAML for the language files, as I do not need the more advanced markup. Please heed this when making changes on local copies.
A brief preview of the YAML format can be seen below, in case you are not yet familiar:
"key1": |- Value 1 line 1 Value 1 line 2 Value 1 line 4 (preceding line left blank intentionally) "key2": |- Value 2GIT repository: https://github.com/fhoech/displaycal-localization
Pull requests welcome 🙂
Suggest accepting CRLF line ending instead of only accept LF
Current workaround:
https://github.com/desktop/desktop/issues/3841#issuecomment-361480731Yes, the format is convenient! How to quickly find the changed parts of the text and the new text in it?
Suggest accepting CRLF line ending instead of only accept LF
Current workaround:
https://github.com/desktop/desktop/issues/3841#issuecomment-361480731Done.
Yes, the format is convenient! How to quickly find the changed parts of the text and the new text in it?
A search for
"*should find all newly added strings. Other than these additions, I don’t think there have been any changes.The layout of the ‘Profile name’ dialog don’t look right to me, maybe need a bug fix?
Seems like GetTextExtent cannot figure out the correct width of the tab character and so the line breaks. I’ve fixed this by adding a bit more spacing (no change needed in translation file).
GIT repository is now live: https://github.com/fhoech/displaycal-localization
Pull requests welcome 🙂
GIT repository is now live: https://github.com/fhoech/displaycal-localization
Pull requests welcome
How do I start a branch? Or I should fork the repo? Any rules here?
Here is my repository, the ‘update’ branch is the latest:
https://github.com/harryytm/DisplayCAL_zh_HKHow do I start a branch? Or I should fork the repo? Any rules here?
No rules yet. we’ll figure these out as we go I guess.
There’s currently two strings in your zh_hk.yaml that need to be updated/added:
"*info.display_tech"(addition of QLED info)
"*measureframe.center.manual"There’s currently two strings in your zh_hk.yaml that need to be updated/added:
"*info.display_tech"(addition of QLED info)
"*measureframe.center.manual"Merged in c532d7a50690d2e7a35be13864df6c621e495645
Maybe it’s a good idea to do it in the merge window for next release because I consider my changes are just minor, let me know when you decided the next merge window.
There’s currently two strings in your zh_hk.yaml that need to be updated/added:<br>
"*info.display_tech"(addition of QLED info)<br>
"*measureframe.center.manual"Merged in c532d7a50690d2e7a35be13864df6c621e495645
I am most likely deprecate my repository and only maintain the fork repository if the fork workflow works well.
