Translators, please read

Home Forums General Discussion Translators, please read

This topic contains 16 replies, has 3 voices, and was last updated by  Florian Höch (@fhoech) 5 months ago.

Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #16894

    Florian Höch (@fhoech)
    Administrator
    • Offline

    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 2

    GIT repository: https://github.com/fhoech/displaycal-localization

    Pull requests welcome 🙂

    • This topic was modified 6 months ago by  Florian Höch.
    • This topic was modified 5 months, 1 week ago by  Florian Höch. Reason: Add GitHub repository link
    #17322

    HarryYTM (@harryytm)
    Participant
    • Offline

    Suggest accepting CRLF line ending instead of only accept LF

    Current workaround:
    https://github.com/desktop/desktop/issues/3841#issuecomment-361480731

    • This reply was modified 5 months, 1 week ago by  HarryYTM.
    Attachments:
    You must be logged in to view attached files.
    #17330

    Alex Sikorsky (@alex-5)
    Participant
    • Offline

    Yes, the format is convenient! How to quickly find the changed parts of the text and the new text in it?

    #17344

    HarryYTM (@harryytm)
    Participant
    • Offline

    The layout of the ‘Profile name’ dialog don’t look right to me, maybe need a bug fix?

    • This reply was modified 5 months, 1 week ago by  HarryYTM.
    • This reply was modified 5 months, 1 week ago by  HarryYTM.
    Attachments:
    You must be logged in to view attached files.
    #17352

    Florian Höch (@fhoech)
    Administrator
    • Offline

    Suggest accepting CRLF line ending instead of only accept LF

    Current workaround:
    https://github.com/desktop/desktop/issues/3841#issuecomment-361480731

    Done.

    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 🙂

    #17357

    HarryYTM (@harryytm)
    Participant
    • Offline

    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?

    • This reply was modified 5 months, 1 week ago by  HarryYTM.
    #17359

    HarryYTM (@harryytm)
    Participant
    • Offline

    Here is my repository, the ‘update’ branch is the latest:
    https://github.com/harryytm/DisplayCAL_zh_HK

    #17361

    Florian Höch (@fhoech)
    Administrator
    • Offline

    How 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"

    #17368

    HarryYTM (@harryytm)
    Participant
    • Offline

    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

    #17369

    Florian Höch (@fhoech)
    Administrator
    • Offline

    Thanks. Can you send a pull request?

    #17373

    HarryYTM (@harryytm)
    Participant
    • Offline

    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.

    #17374

    HarryYTM (@harryytm)
    Participant
    • Offline

    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.

    • This reply was modified 5 months, 1 week ago by  HarryYTM.
    #17383

    Alex Sikorsky (@alex-5)
    Participant
    • Offline

    version 3.8 is translated into Russian and Ukrainian languages.

    Attachments:
    You must be logged in to view attached files.
    #17426

    Florian Höch (@fhoech)
    Administrator
    • Offline

    Thanks, synced with GIT repo.

    #17427

    Florian Höch (@fhoech)
    Administrator
    • Offline

    I think now (i.e. next 12-24 hours) would be a good time for a merge.

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic.

Log in or Register

Display Calibration and Characterization powered by ArgyllCMS