|
2011-03-25 17:02
|
JEDI.zip (1,585 bytes) |
|
|
Could you give some more explanations? I'm using it with Delphi XE and the SVN Version of JCL and JVCL. I can't see any problems. Regards Jens |
|
2011-03-31 12:23
|
First run.png (16,696 bytes) |
|
2011-03-31 12:23
|
Second run.png (16,626 bytes) |
|
|
1) Run it once (AppStorage will save the property Text) 2) Run again (AppStorage lost 2 characters from Text property) |
|
|
Ok, I'm not so fimilar with Unicode, but here is my explanation/workaround. 1. In the online help it's stated that the TIniFile is old stuff and that it allways was ansi, so the default is ansi. 2. Open your created ini-file in an unicode editor and change the codepage to utf-8 of the existing file. Restart your test application and from that moment unicode is working. The inifile component detects that the original file is unicode and stores it in the detected codepage. My Problem is, that I do not know how, what will be the best way to enhance the TAppIniStorage for a default codepage. Regards Jens |
|
|
Maybe before flushing first time (creating an INI file) we can create an empty UTF-8 text file (of course only for Unicode Delphi versions), and then call default INI file. And then everything wil work fine. |
|
|
Except that I don't think the ini file handling class can detect UTF-8 from an empty file. Can anyone test this? |
|
|
JvAppIniFileStorage1.IniFile.Encoding := TEncoding.Unicode; Solves the problem. Maybe we can check the delphi version and if it supports unicode, then just set the default encoding to, say, TEncoding.UTF8? |
|
|
The easier way is : JvAppIniFileStorage1.Encoding := TEncoding.Unicode; And the AppIniFileStorage has the default delphi behaviour (in point of ini encoding), so I do not see a need to change anything else. Regards Jens |
|
|
No change needed |
- Anonymous
