Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 
Share Thread:
Reddit Facebook Twitter
[fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
02-04-2017, 12:13 AM
Post: #10
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
Micheus Wrote:Was it working without the replaced files, right?
Yes it was,I tried.
and only replacing wings_ff.beam with the previous file,then Wings3D works fine.
So,I'm currently use material name without UTF8 string for test.

By the way, I found something new about Wings3d collada import.
In Blender doesn't bind a texture file to Collada data unless mapping type is UV.
Previous time,didn't notice it....I'm sorry.

Also,Blender possibly output collada texture file name by percent-encoding when Non Latin(UTF8 ) image file name using.
(Strangely, except for that part, Blender had been successfully encoded all UTF8 strings for collada export.)

For example a part in a collada file that export by Blender
%E7%94%BB%E5%83%8F is a coded string of 画像
Quote: <library_images>
<image id="画像_png" name="画像_png">
<init_from>%E7%94%BB%E5%83%8F.png</init_from>
</image>
</library_images>

About percent-encoding,see a following URL
https://en.wikipedia.org/wiki/Percent-encoding

Wings3D Log when Collada file importing.
Quote:Failed to load "/Users/***/utf8_test_files/%E7%94%BB%E5%83%8F.png": unknown POSIX error

Solving to file name encoding should be also useful in importing other file formats maybe. Smile
Reply


Messages In This Thread
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8 - tkbd - 02-04-2017 12:13 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)