|
Some 3D format, problem when importing/exporting process if contains Non-latin
|
|
02-26-2019, 06:57 AM
Post: #2
|
|||
|
|||
|
RE: Some 3D format, problem when importing/exporting process if contains Non-latin
3ds can't be utf-16, if wings expect that all old files will fail to load,
we would get Mojibake for every old-file which uses ascii or utf-8. 3ds Max may use it internally now but that doesn't help with an old file-format that expects ASCII. The encoding for strings in 3ds, obj and lwo is latin-1/ascii encoded not UTF-8. You may get it work with UTF-8 because UTF-8 is designed to work for ASCII, but then you will break Latin-1 encoded files. Wings could guess on import which encoding was used but that is still just a guess, and when doing export the only correct way is to encode in Latin-1 for old formats that have not specified the encoding format. So if you want to use old file-formats stay with ASCII characters, that is the only thing that will work. If you need to Unicode characters use newer formats with a specified encoding. |
|||
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Some 3D format, problem when importing/exporting process if contains Non-latin - tkbd - 02-09-2019, 07:30 AM
RE: Some 3D format, problem when importing/exporting process if contains Non-latin - dgud - 02-26-2019 06:57 AM
RE: Some 3D format, problem when importing/exporting process if contains Non-latin - tkbd - 02-27-2019, 09:41 AM
RE: Some 3D format, problem when importing/exporting process if contains Non-latin - dgud - 02-27-2019, 12:38 PM
|
User(s) browsing this thread: 1 Guest(s)



