cdr import fails with Cyrillic characters in file name

[Hachmann]

From a question in the answers section (https://answers.launchpad.net/inkscape/+question/295699):

------------

Hi guys

I can't import file.cdr with the Cyrillic characters in the name of file. I got error without describe.
Every time I must rename filenames from cyrillic to latin manually

I use the Windows 7/64 at russian edition my home computer and Inkscape 0.91(64).
Thank you

[jazzynico (jazzynico)]

Hi Serg,

Would you be willing to attach a CDR file with Cyrillic characters that doesn't import correctly so that we can try to reproduce?
Thanks!

[jazzynico (jazzynico)]

Just for your information, the CDR import library was updated recently, and thus there are possibilities that the bug is fixed in the next Inkscape version.

[Serg (ssburyachenko)]

Thanks!

2016-06-28 0:58 GMT+06:00 jazzynico <email address hidden>:

> Just for your information, the CDR import library was updated recently,
> and thus there are possibilities that the bug is fixed in the next
> Inkscape version.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1596654
>
> Title:
> cdr import fails with Cyrillic characters in file name
>
> Status in Inkscape:
> Incomplete
>
> Bug description:
> From a question in the answers section
> (https://answers.launchpad.net/inkscape/+question/295699):
>
> ------------
>
> Hi guys
>
> I can't import file.cdr with the Cyrillic characters in the name of
> file. I got error without describe.
> Every time I must rename filenames from cyrillic to latin manually
>
> I use the Windows 7/64 at russian edition my home computer and Inkscape
> 0.91(64).
> Thank you
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/inkscape/+bug/1596654/+subscriptions
>

--
-------
Serg Buryachenko
skype: sburyachenko
mailto:<email address hidden>

[Hachmann (marenhachmann)]

Serg, would you please attach a CDR file that exposes the problem?
The developers are not sure if it was resolved, but they need a file to test.

[Patrick Storz (ede123)]

Duplicate of bug 1416949.

Happens with all non-ASCII characters (e.g. also German umlauts "äöü") and is not fixed in 64-bit builds of current trunk.

[jazzynico (jazzynico)]

Thanks Eduard. I misread the report and thought it was an issue with Cyrillic characters in the content of the file, not in it's name...