[tonyelit]

Using the Bonsai Desktop, I have imported my old outlines from PocketThinker, containing greek characters. I tried OPML , shadow XML and csv format.In outlines created from all imports, the greek character items would display correctly initially on the PDA, (Windows mobile 2003) but when the outline was saved on the PDA after a change, then the greek character items would change to unreadable. This problem can be reproduced. I am running the 2961 build on the pda and PC

[Richard Murphy]

This is not a known issue. Could you reply and attach a sample file that will reproduce this issue? Thanks.

[milkytooth]

Hi Richard,

I have to concur with tonyelit. The Traditional Chinese characters that I entered on Bonsai sometimes become completely illegible after synching with my Treo. I wonder if Bonsai supports unicode (is that the problem?)...

[tonyelit]

Richard Murphy, on Dec 23 2008, 07:45 PM, said:

This is not a known issue. Could you reply and attach a sample file that will reproduce this issue? Thanks.

Hi
Sorry for the (very) long delay
here is such a file.
As soon as it is saved in the pda , many characters will be converted to questionmarks ("?")
It seems to affect the pda version only as the greek charaxcters are viewable in the desktop app
The chosen font was tahoma (6pt) should i have made any other choice ?


Thank you for looking into the issue.

Attached File(s)

•  TestGreekChars_BeforeSaveinPda.zip (939bytes)
  Number of downloads: 63

This post has been edited by tonyelit: 13 April 2009 - 08:33 AM

[Richard Murphy]

What font are you using in Bonsai on the PC? It is configured in the View/Global Settings menu, font tab. Click the font button to view which font is being used.

[tonyelit]

Richard Murphy, on Apr 13 2009, 09:00 PM, said:

What font are you using in Bonsai on the PC? It is configured in the View/Global Settings menu, font tab. Click the font button to view which font is being used.

Arial both for outline items and notes , and the script is set to Greek

[tonyelit]

tonyelit, on Apr 14 2009, 06:55 AM, said:

Arial both for outline items and notes , and the script is set to Greek

Please also note that the aforemenioned problem occurs even to a new file created by bonsai desktop.
The attached file was created by Bonsai Desktop, synced to the pda and then edited on the pda.
When edited on the pda, the Greek characters were made unviewable on the PDA side (replaced by "?" chars) while on the Desktop the file was viewed normally.

Thank you again for your immediate response

[Richard Murphy]

I have a fix for this issue which will be in the next beta. It requires that the regional setting for the Windows Mobile device for language be set to Greek (configured from the Start/Settings/System/Regional Settings tool). Assuming your device is configured as such, you should be able to edit the outline on the handheld without losing your Greek characters.
While this works, I consider the proper solution will need to want until Bonsai on the PC can be updated to use a UTF-8 character set and eliminate possible code page problems for good.
Thanks for providing the test outline. This really helped me understand what was causing this problem.

[Ralph Baek]

Richard,

Additionally,

Bonsai for PPC has same problem.

Procedure
1. Write Text data: (Korean character set. UTF-8 or euc-kr)
2. Save outline
3. Open outline
4. data has broken: all character change ???
5. I am checked outline file
6. 1st line, encoding="windows-1252" ==> incorrect.

Korean XML data has enoding="euc-kr" or "UTF-8".

Please update next version

(Bonsai for PC: outline file has encoding="euc-kr". And all good working)

Thanks you.

This post has been edited by Ralph Baek: 16 April 2009 - 06:46 PM

[Richard Murphy]

Ralph,
Thanks for the additional detail. While I am still investigating this issue, I plan to have this fixed as well for other code pages (including Korean) for the next beta. My preference is to always use UTF-8 on the PPC version, but I was under the impression that the sync component and Bonsai on the PC would not support UTF-8 (at least not properly with the current code).

[Richard Murphy]

The latest beta build 3100 should resolve the issues you have encountered with corruption of non-English characters. For this to properly work, both the PC and the Windows Mobile device must have their regional settings configured for the appropriate language settings as the Bonsai desktop still uses the "local code page" for encoding the outline file. The Bonsai app on the handheld now uses UTF-8 encoding, so it should work properly regardless of the regional settings, but the sync engine will update the handheld outline files in "local code page" encoding and hence the need for the PC and WM regional settings to match. In the future, Bonsai on the PC will be updated to use UTF-8 as well and eliminate any issues from regional configuration settings, but this will need to wait until after the release of the Bonsai WM product release.
Please let me know what your results are, good or bad.