Comment 21 for bug 1785191
Revision history for this message
| jean-pierre charras (jp-charras) wrote | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
In fact kicad2step itself has no I18n strings, so no existing translation I am aware of.
In fact, I found different issues.
Inside kicad2step code, non ASCII7 strings (read: filenames) are incorrectly managed.
(For instance, I found at least one filename converted in UTF8, and the resulting string converted to UTF8 a second time, giving some strange filename).
Currently I am trying to clean the way filenames are managed inside kicad2step code.
I am guessing there are also issues for 3D step models filenames.
A second issue is the fact OCE uses (AFAIK) a c string in filename, not wide string (but I am not sure: OCE is a big library...).
(But it can be solved easily, by using a temporary filename)
I will test it on Linux.