Unicode 'c4d_string.str' troubles



  • 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



  • 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



  • 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!



  • 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,


Log in to reply