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
    • Recent
    • Tags
    • Users
    • Register
    • Login

    Unicode 'c4d_string.str' troubles

    Scheduled Pinned Locked Moved SDK Help
    4 Posts 0 Posters 503 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

      THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

      On 20/01/2005 at 12:59, xxxxxxxx wrote:

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

      ---------
      I have UniPad. The file is saved as UTF-8 Unicode. The plugin fails to load (so no errors, no idea). I use GeLoadString() for all resource strings. Would this affect folder/file names stored in c4d_string.str and used for Filename classes, even if in English?

      Thanks,
      Robert

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

        THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

        On 20/01/2005 at 14:50, xxxxxxxx wrote:

        Oh, I see. Don't tell anybody that it has to be ASCII+UCN with Byte Order Mark turned off, but keep insisting on UTF-8.

        Get it right, guys!!!

        Robert

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

          THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

          On 21/01/2005 at 09:51, xxxxxxxx wrote:

          That seems to be an error in the documentation, if by "insist" you mean the one reference on the Dialog layout page: "The string files are stored in Unicode UTF-8...". I'll change this for the R9 docs. Thanks for reporting!

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

            THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

            On 21/01/2005 at 10:57, xxxxxxxx wrote:

            It also shows up (at least in 8.0 docs) in String class, GetCStringLen() and SetCString(), and under StringEncoding. This is misleading since it isn't strict UTF-8, but ASCII+UCN, which is with what the non-English Resource strings are encoded.

            What is interesting is that the English strings appear to be UTF-8 encoded, but luckily for me (when the trouble arose), I had the full language pack installed on one of my C4D installs. With them, I was able to see the different encoding for them in UniPad.

            The ASCII+UCN encoding seems to work cross-platform (though this could be an artifact of MacOS 10.3.7 and C4D R9 and widening of compliances between the platforms).

            Thanks Mikael,

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