Please be more specific in your request.
wphfr is entirely developed with unicode strings and unicode-enabled widgets.
Which part of the software lacks unicode support in your opinion?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Lorenzo,
There are 2 problems:
(1) It cannot read double byte characters from the phone book (attachment);
(2) It saves phone number entry to the phone book in western characters only. Therefore, all the double byte characters are lost after being saved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Got it. You are correct. Input-output on CSV files was done using ansi.
Release 0.4.9 handles CSV address book using UTF8 - thus ensuring compatibility with ansi, while allowing unicode characters.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please be more specific in your request.
wphfr is entirely developed with unicode strings and unicode-enabled widgets.
Which part of the software lacks unicode support in your opinion?
Hi Lorenzo,
There are 2 problems:
(1) It cannot read double byte characters from the phone book (attachment);
(2) It saves phone number entry to the phone book in western characters only. Therefore, all the double byte characters are lost after being saved.
Got it. You are correct. Input-output on CSV files was done using ansi.
Release 0.4.9 handles CSV address book using UTF8 - thus ensuring compatibility with ansi, while allowing unicode characters.
Very Beautiful. The default phone book can read and save Asian fonts now! Thank You! ^^