Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5121

July 31st, 2009 04:00

Problems with special characters

Hi,


We developed our own software to write data on the Centera. The application works fine normally.

Unfortunately we detected a problem with archiving of filenames with special characters and diacritic marks on our Centera like ü,ö,ß,°.


For exemple when we try to archive a file with a path like this: "C.\Brücken.txt" we get the following error back:

System.ApplicationException: process (write) Thread 5:  failed writing file to the clip: FP_FILESYS_ERR ---> error: -10027, error text: FP_FILESYS_ERR, syserror: 0, message: failed to open input file (C:\Brücaken.txt), trace: FPFileStream.FPFileStream (C:\Brücken.txt,rb,16384) C:\Brücken.txt,rb,16384)


We use the Centera runtime v3.2 libraries( pai_module.dll, FPXML.dll, FPUtils.dll, FPStreams.dll, fpparser.dll, fpos32.dll, FPLibrary.dll, FPCore.dll) and the Centera API .NET Wrapper v3.2 (FPSDK.dll)


Has somebody ever had the same problem?


Thanks in advance

2 Intern

 • 

417 Posts

August 4th, 2009 10:00

Yes, it is. But it would have helped if I had told you what the fix was and how to use it!

Basically there is a new class called FPWideFilenameStream, which will handle Windows "wide" characters correctly. There are four derived classes (for Input, Output and Partial versions of both).

For opening a filename with special characters you would instantiate FPWideFilename(filename) instead of FPStream(filename, bufferSize).

2 Intern

 • 

417 Posts

July 31st, 2009 04:00

I have seen similar problems with Asian character sets on Windows platforms where the filenames include these "special" characters.

I wrote a Generic Stream implmentation in C to overcome this (see attached), but have not incorporated it into the .NET wrapper yet. Are you able to test using the C example?

1 Attachment

13 Posts

July 31st, 2009 05:00

Thanks. I will give my feedback as soon as possible.

2 Intern

 • 

417 Posts

July 31st, 2009 06:00

I have attached the preliminary version of this fix for the .NET wrapper, which implements a new FPWideFilenameStream class. It has not yet been released on SourceForge but I believe it should fix this issue. Replace the existing file from the disribution and rebuild the wrapper.

1 Attachment

2 Intern

 • 

417 Posts

August 3rd, 2009 02:00

The wrapper is *only* distributed as source, there is no binary distribution. The next release (which removes the need for Perl to be installed) has not been scheduled, but is likely to be this quarter

Please email (stuart_graham@emc.com) and I will arrange to provide you with a Beta version for you to test with.

13 Posts

August 3rd, 2009 02:00

Thank you very much.

I can not rebuild the wrapper because I do not have Perl installed and get problems with the DebugPatch.bat.

When will your fix released and wherefrom can I get a final compiled FPSDK?

13 Posts

August 4th, 2009 04:00

In the meantime I tried to build the the FPSDK.dll. I downloaded the current FPSDK source code and replaced the existing FPGenericStreams.cs with your one. Unfortunately I got an error from the FPGenericStreams.cs: "The type or namespace name 'FPCallback' could not be found (are you missing a using directive or an assembly reference?)"

It seems that this reference is required. Due to I could not found this dll can you provide me this one?

Thanks in advance

2 Intern

 • 

417 Posts

August 4th, 2009 07:00

Sebastian - I sent you a full zip file of the solution yesterday. Did you receive it?

When I removed the need for Perl a new type was introduced in the FPTypes code, this is what is missing when you simply dropped in the new GenericStream file.

I have attached the entire solution here in case it did not get through your mail filters.

1 Attachment

13 Posts

August 4th, 2009 08:00

No. I did not receive anything from you yesterday.

Thanks for the attached solution. I will test it within the next hour and give the feedback to you.

13 Posts

August 4th, 2009 10:00

Is your FPGenericStreams.cs fix already in the FPSDK solution included?

When yes, I get the same error message. Is there a possibility to check if I'm using your code with the fix?

13 Posts

August 5th, 2009 08:00

Thanks for your great help. It works!
No Events found!

Top