dgud,Thank you for reply.
Especially,The encoding for file formats is useful for me.
I surprised that obj file format latin only support.
I have met terrible utf8 data in an obj 3D file saved by Photoshop(Japanese ver) before.
OK,Basically to treat for 3D data,It only use ascii character ,but it use newer format that Collada and/or glTF if using utf8 string need.
I agree for your advice that how to naming of files and treat about Mojibake.
By the way,Is Texture file linking problem also deeply relation to the file format encoding?
I wish that at least the texture link will be solve if possibility...
Even Mojibake occurring, if the texture linking successfully, it will be solved by an User could renaming the texture name to the latin string on Outliner.
Especially,The encoding for file formats is useful for me.
I surprised that obj file format latin only support.
I have met terrible utf8 data in an obj 3D file saved by Photoshop(Japanese ver) before.
OK,Basically to treat for 3D data,It only use ascii character ,but it use newer format that Collada and/or glTF if using utf8 string need.
I agree for your advice that how to naming of files and treat about Mojibake.
By the way,Is Texture file linking problem also deeply relation to the file format encoding?
I wish that at least the texture link will be solve if possibility...
Even Mojibake occurring, if the texture linking successfully, it will be solved by an User could renaming the texture name to the latin string on Outliner.