Open GoogleCodeExporter opened 9 years ago
I cannot reproduce it. Could you attach a tiny .knt file in Chinese with a pair
of
nodes, and indicate exactly what command and options are you using?
Original comment by dpra...@gmail.com
on 4 Jun 2010 at 6:29
attached files are
1. screenshot of Keynote running
2. output result
3. keynote file
and thank you for your help
Original comment by jeromes...@gmail.com
on 6 Jun 2010 at 10:42
Attachments:
Issue 332 has been merged into this issue.
Original comment by dpra...@gmail.com
on 12 Jun 2010 at 9:40
Could you see if your files 'nodehead.rtf' and 'notehead.rtf' contains a tag
such as ansicpg1250?
If so, could you try to modify that files, keeping something like the following?
{\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset1{\*\fname ...
Also, node names are saved inside .knt in ANSI, not in UTF8. Did you write the
node names with the region setting in chinese and later change your region
settings to english?
Original comment by dpra...@gmail.com
on 6 Jan 2013 at 12:56
Last comment is not correct: from version 1.7.7 node names and note names are
saved in UTF8 without BOM in .knt
Original comment by dpra...@gmail.com
on 6 Jan 2013 at 1:25
Wait, KeyNote is really saving that fields in UTF8 only when the text is not
valid in ANSI for the system codepage (usually it would show '??..') This was
done to maximize backward compatibility so that the node names are recorded in
ANSI in most cases.
In this situation, changing regional settings will affect the way node names
are interpretted.
I'm thinking of saving these fields in UTF8 in all cases...
Original comment by dpra...@gmail.com
on 6 Jan 2013 at 1:39
Fixed in revision r171
Original comment by dpra...@gmail.com
on 7 Jan 2013 at 1:00
I have just released a new version of KeyNote NF: 1.7.9 Beta 4
Could you verify and confirm if the issues are correctly resolved?
Thanks
Daniel
Original comment by dpra...@gmail.com
on 7 Jan 2013 at 7:43
Original issue reported on code.google.com by
jeromes...@gmail.com
on 3 Jun 2010 at 3:56