Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    Documentation on encoding of layout files

    Scheduled Pinned Locked Moved Bugs
    4 Posts 0 Posters 843 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H Offline
      Helper
      last edited by

      On 17/12/2015 at 03:52, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   17 
      Platform:   Windows  ;  Mac  ;  Mac OSX  ; 
      Language(s) :

      ---------
      The python and R 16 coffee docs

      https://developers.maxon.net/docs/py/2023_2/misc/general_gui.html?highlight=layout

      state that
      The string files are stored in Unicode UTF-8, ....

      There is no other note. But the c++ documentation

      https://developers.maxon.net/docs/cpp/2023_2/page_dialog_layout.html

      states:

      _The string files are stored in Unicode, which means that they handle almost every language there is.

      Note
          The encoding is 7-bit ASCII with other characters encoded as \uHHHH. For example 'Natürlich' is written 'Nat\u00fcrlich'. Byte-order marks are not used._

      So the encoding is actually 7-bit ASCII. This information is missing in the python and coffee docs. On a side note, i think the sentence "The string files are stored in Unicode" is not clear enough. It should probably read "Strings are internally represented in Unicode, which means ..." "However, string table files are encoded in 7-bit ASCII. Non-ASCII characters are written as \uHHH. For example ..."

      Merry XMas,
      Michael

      1 Reply Last reply Reply Quote 0
      • H Offline
        Helper
        last edited by

        On 17/12/2015 at 04:17, xxxxxxxx wrote:

        I am using German umlauts äöüÄÖÜ directly in string files for a while. Used to be 7bit but it is not any more.

        1 Reply Last reply Reply Quote 0
        • H Offline
          Helper
          last edited by

          On 17/12/2015 at 08:55, xxxxxxxx wrote:

          Hi Michael,

          The information in the SDKs documentation for the encoding of resource and string files will be updated with the actual encoding used.

          1 Reply Last reply Reply Quote 0
          • H Offline
            Helper
            last edited by

            On 17/12/2015 at 12:43, xxxxxxxx wrote:

            I had some trouble with non-ASCII chars on my Mac. Hence i found this section in the docs. Now i properly use \uxxxx and it works on Mac and Pc. It also works with R17, fortunately 🙂

            1 Reply Last reply Reply Quote 0
            • First post
              Last post