Hi,

while playing with the sdk today I happened to open a file that was located in a folder which name contains a french character, the ç. Instead of working as intended, the “Initialize” method of the KFbxImporter class reported me a “Corrupted or Invalid file” error. I guess it should not.

Is your FBX project compiled as multi-byte character set or unicode character set?
I would try Unicode if not.

Nismael 01 September 2009 09:01 AM

Hi,

while playing with the sdk today I happened to open a file that was located in a folder which name contains a french character, the ç. Instead of working as intended, the “Initialize” method of the KFbxImporter class reported me a “Corrupted or Invalid file” error. I guess it should not.

So is your “regional and language options” set french as the “current language as the non-unicode program”?
If not, the corruption error will show. And this is an known limitation.

Eric Feng, Framestore

Hi,

I just noticed that there is no pathway for wide-character (wchar_t*) filepaths, or filenames with non-english characters in them.

In kfbximporter.h and kfbxexporter.h:
virtual bool Initialize(const char *pFileName, const int pFileFormat = -1)
virtual bool Initialize(const char *pFileName, int pFileFormat = -1)

These functions only take ANSI characters.

Is this correct?  Will support for non-ANSI filenames be added in a future release? 
Or please tell me how to load a filename with non-ANSI characters?

Hello

I am currently working on the SDK and as the answers are pretty old, I’ll ask once again to be sure.

I saw that all functions uses char and not wide char, as when I want to get the chars from a KString, I can get only chars and no wide chars.

As I’m working in a Japanese environment I would prefer to use wide chars if possible, but with the current version of the SDK, only ansi chars are supported right ?

Thanks for you answer.

Ok, Thanks for your answer