Urgent question about INI object, INI object settings and Application settings.

[J3sseM]

I hope someone from CT could clarify, Yves! I need you!

I'm going to release my next game DISTRAINT 21st this month!
Okay, I learned a lot from Silence of the Sleep, in this case everything being unicode.

Okay since INI++ is not unicode I'm using INI object. It's unicode, right?

So I found a problem when I created another user to my Windows and named it with some Russian Cyrillic. I'm saving all my data to AppData/Roaming folder cause it does not need admin rights to write in.
Since I'm using so called "normal" INI object I thought everything would work like a charm, but hey, that's not quite what happened! I spent a couple of hours trying to figure why on earth my game fails to create files in AppData folder when Windows username has some foreign characters in it.

After a few hours I was able to narrow the reason to INI object. I tried altering INI object settings, like "Create INI file in application data folder" and "UTF8". Nothing would work! :/

But then, finally! I set "Character encoding options" from application settings, both input and output to UTF-8 (without byte-order mark) AND unticked "UTF8" and "Create INI file in application data" from INI object and it started working!

I'm very, very happy it seems to work. But I can't quite understand why. Why I need to disable UTF8 from INI object? I'm trying to understand why it works, and could it potentially create new problems?

Hoping to get quick response as I aim to send out the demos tomorrow! Yikes!

Jesse

[Jeff]

You might want to send Yves a quick email or a PM on the forums so it on the top of his list to look at.

[J3sseM]

I'll do that, thanks Jeff!

Also noticed, that the file it finally saves, saves in ANSI and not in UTF8 without byte-mark.

[Yves]

I don't see at all why the character encoding options in the app properties would have any effect as they are not used AT ALL by the INI object. They are used by the Load Text / Save Text functions of some objects like Edit box and List Box.

What you need to know about the UTF-8 option in the INI object:

1. If you select this UTF-8 option and provide the INI file with your application, make sure this INI file has no byte-order mark.

2. The full pathname of the INI file is not Unicode, it must use characters from the current user's language. For example if you user is on a Russian machine and has a Greek or Japanese user name this won't work if the INI file is in the user's AppData folder (as the pathname will contain a Greek or Japanese name). Though this case must be quite rare...

PS: if you could send me a simple example that doesn't work and a simple example that works I could probably see better what you mean.

[J3sseM]

Yves, okay, I use byte-mark, so maybe UTF8 option being ticked in INI object was the reason it failed in the first place. Though only when username in Windows had some Cyrillic. O_o

As the AppData problem I'm well aware of that (had this episode with Silence of the Sleep). I'm loading the paths only with unicode objects. This is all good, and atm all seems to work okay.