|
[fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
|
|
12-31-2016, 01:07 AM
(This post was last modified: 01-31-2017 05:47 AM by micheus.)
Post: #1
|
|||
|
|||
|
[fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
This problem is related to compatibility between multiple formats and other 3D Applications.
I focused to the problem to find the minimum necessary fix. Also chose four 3d DATA formats: dae, obj, 3ds, stl. (Because Blender can export these format.) The conclusion for this problem solve on Wings3D is narrowed down to two.
The following is the findings I did. At first I exported data(obj , 3ds , dae and stl) by Blender. (Because Blender can treat UTF8 chrcode in DATA strings) These data including utf8 character string in material and object name etc. Then for confirm and comparation, I have imported these files(obj , 3ds , dae and stl) with Wings 3D, Cheetah 3D and Blender. In Wings3D Obj and 3ds got mojibake, but I was able to import 3D data. But in both the case of dae and stl crashed. In Obj file format,Blender and Cheetah 3D correctly imported the file that contains UTF8 string. In 3ds file format,Import will succeed.But all 3D software can't indicate name properly. In dae(Collada) file format only OK at Blender.(Cheetah3D not support .dae). In Stl file format,Blender and Cheetah 3D, it seems that it has been forcibly renamed to a safe name. See a following images. ![]() ![]() ![]() And Error logs are here(3ds,Collada(dae) and Stl). 3ds case: 47,85,115,101,114,115,47 means "/Users/" Code: wings_wm:821: Dropped Event autosaver: redrawCollada case: 12510,12486,12522,12450,12523 means "マテリアル" Code: Version: 2.1.5stl case: Code: +---------------------------------------------------------------+ |
|||
|
12-31-2016, 08:34 AM
Post: #2
|
|||
|
|||
|
RE: (UTF8 DATA Import)Crashed or Mojibaked when import with an data name that contain UTF
Thanks for your thorough tests, Tkdb.
Can you posts the exported models somewhere so we can test the fixes? The other bugs I think can test myself. |
|||
|
12-31-2016, 11:44 AM
Post: #3
|
|||
|
|||
|
RE: (UTF8 DATA Import)Crashed or Mojibaked when import with an data name
dgud,OK,I uploaded the data to a following URL.
http://brace.client.jp/wings3d_141/file2.html utf8_test_files.zip (I made a cushion page,because we can't DL file with the direct link )There archive has dae,stl,3ds,mtl,obj,mtl and some imagefiles It also contains wings and blend files. |
|||
|
01-31-2017, 05:46 AM
(This post was last modified: 01-31-2017 05:59 AM by micheus.)
Post: #4
|
||||
|
||||
|
RE: Crashed or Mojibaked when import with an data name that contain UTF
Fixed crashes for "3ds case", "Collada case" and "stl case". FixesImpUTF8.zip (includes the fix for Image Viewer too)
(UTF8 DATA Export)Crashed when export with an data name that contain UTF8: In case of export to these formats it's possible to still get some crashing during file writing process. I couldn't find a way to prevent it for .dae files, for instance.
|
||||
|
01-31-2017, 11:18 AM
Post: #5
|
|||
|
|||
|
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
Micheus,thanks for files. I installed all them in Wings3D v2.1.5 and tested it immediately.
It seems that STL import and ImageView are fixed. I got an object which named "STL Object" ![]() But others,when an image generateed by AutoUV for UTF8 name object,when change Material bame, obj and collada input/output these will crash when trying test file. I think that location of installed files are should be correct. Tried Import wings case: Code: Dump written 2017-1-31_20-3Tried Import Collada case: Code: Dump written 2017-1-31_19-34Tried to Rename Material(to UTF8 name) Code: Internal ErrorAutoUV Code: Dump written 2017-1-31_19-43*** Current test progress *** Code: Preview for UTF8 image file name :OKAnyway,I will continue testing
|
|||
|
02-01-2017, 01:58 AM
Post: #6
|
||||
|
||||
|
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
As most of the other UTF8 bugs you reported, every time you read "list_to_atom" in the bug report that error I cannot fix. We need to wait by dgud.
As it's in the Erlang documentation, by now, "atoms are restricted to the same ISO Latin-1 range".
|
||||
|
02-01-2017, 09:44 AM
Post: #7
|
|||
|
|||
|
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
I see.
Certainly,it is inescapable from the limited of Erlang specification. |
|||
|
02-01-2017, 10:17 PM
(This post was last modified: 02-01-2017 10:18 PM by tkbd.)
Post: #8
|
|||
|
|||
|
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
Hum...,side effect is occurring.
In Wings which replaced your test plugin files. I put into "ebin" folder: wings_ff_wings.beam wings_image_viewer.beam wings_material.beam and put Into "plugin/import_export": wpc_collada.beam wpc_stl.beam When loading a simple wings file saved before, a crash log is output. Only Latin charactors are used in a data in this file. Apparently wings_ff_wings.beam seems to be involved. Crash Log is here. Quote:Internal Error Is this crash related to atom limitation? Or is it a simple bug? If it is related to the limitation, I won't deepen about it.
|
|||
|
02-01-2017, 10:39 PM
Post: #9
|
||||
|
||||
RE: [fixed] (UTF8 DATA Import)Crashed when import with an data name that contain UTF8
(02-01-2017 10:17 PM)tkbd Wrote: Is this crash related to atom limitation? Or is it a simple bug?Thanks for report this. Was it working without the replaced files, right? I don't have time to check this until Sunday, so I'm going do delay a little to answer your question.
|
||||
|
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> 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.
|
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)







)
@MicheusVieira
MicheusVieira
Micheuss
micheus4wings3d