RCPReaderSample - reading rcp files from non ascii paths

[martin.graner]

Since the SDK is now released:

We are still not able to import rcp files with the SDK in non ASCII paths.

I have created a "small" project for windows:

RealitySDKSampleX64.zip

In there you will find two folders:

-Release -> This is just the compiled x64 folder from the RCSamples.sln with all dll, exe, ...

-αρμ -> A folder where I placed the rcp test project RealitySolutionSDKSampleProject.rcp and a batch file to call RCPReaderSample.exe with the right commands (-i path2RCPFile -o dirToWritexyz)

Much appreciated if someone could tell me if this is a bug in the SDK or where my mistake is.

Perhaps someone is able to share his compiled RCPReaderSample.exe with me so I can test the non ascii path with that as well.

Thanks in advance.

[martin.graner]

In addition to that above:

I have the same challange when I want to use importFiles(), when the e57 files I'd like to import are in non ASCII Paths then I am not able to import. In contrast: If the location where I'd like to create the RCP Project is in a non ASCII Path, but the e57 files are not (they are in an only ASCII path), then I can import.

I have checked the RCString (if the path I put in vs the path I get out with RCString::getWString()) is identical and correct, and I found no error (the special charakters are displayed correctly).

[yan.fu]

Hi @martin.graner,

Thank you for your feedback. 

The team looked into this issue but could not reproduce it. 

We will continue looking into this issue and contact you for your help when necessary.

Thanks for your cooperation.

Best,

Yan

[benglin · Accepted solution]

Hi @martin.graner, thanks for sharing your binaries with us, it did help identifying the problem that could not be reproduced earlier. The same goes to the issue that you brought up with *.e57, both are now resolved in our latest internal build.

The fixes will be in the next SDK release, but for now you may have to go with the workaround -- storing files under ASCII-only file paths.

Thanks again for your feedback and understanding in this matter.