Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 am)
Welcome to the Poser Technical Forum.
Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)
This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.
New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.
stewer mentions in this post -> http://www.renderosity.com/mod/forumpro/showthread.php?message_id=2868513&ebot_calc_page#message_2868513
that Poser 7 is using UTF-8 with no BOM for PZ3's.
Hopefully this is the same for all files.
Okay. This appears to be the case for this Poser 5 file as well (there is no BOM). But then he mentions troubles between Windows and Mac, Japanese Kana/Kanji in previous versions. This seems to implicate that earlier versions used a variety of formats - but I see possible UTF-16 (but this could be S-JIS or some other encoding - getting lucky?). This will make it difficult to cover a variety of situations where non-ASCII characters are in use...
Let me know if you bump into anything else.
Thanks,
Robert
C makes it easy to shoot yourself in the
foot. C++ makes it harder, but when you do, you blow your whole leg
off.
-- Bjarne
Stroustrup
Contact Me | Kuroyume's DevelopmentZone
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
This has gone without much ado as long as the text is part of a name (or internal name). But it does become a stink if international characters are used for file references (figureResFile and so on). I haven't yet been able to determine what format Poser uses to store the names - say something like this (which happens to be a name not a file reference): ƒtƒBƒMƒ…ƒA
Since there are quite a few possibilties here (EBCDIC, ASCII-ANSI, Unicode: UTF-8 and UTF-16, and variations anon) it is difficult to ascertain the format being employed. My feeling is that this is a two-byte representation which will limit the choices to Unicode UTF-16. This seems to be verified in Sci UniPad entering the two character hexadecimals (U+). In this case, the result is kanji as expected from a Japanese source.
Any verification?
Thanks!
Robert
C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.
-- Bjarne Stroustrup
Contact Me | Kuroyume's DevelopmentZone