new indi edit doesn't get BOM
On Win32, when the editor codeset is UTF-8, editing an existing INDI gives a file with a BOM (byte order mark at the top).
But add indi gives a template file with no BOM.
Logged In: YES
Relevant code for new persons: add_indi_by_edit
Same bug for new families.
Relevant code for new families: add_family_by_edit
Fixed in cvs:
Checking in ChangeLog;
/cvsroot/lifelines/lifelines/ChangeLog,v <-- ChangeLog
new revision: 1.1950; previous revision: 1.1949
Checking in src/gedlib/nodeio.c;
/cvsroot/lifelines/lifelines/src/gedlib/nodeio.c,v <-- nodeio.c
new revision: 1.24; previous revision: 1.23
Checking in src/hdrs/gedcom.h;
/cvsroot/lifelines/lifelines/src/hdrs/gedcom.h,v <-- gedcom.h
new revision: 1.208; previous revision: 1.207
Checking in src/liflines/add.c;
/cvsroot/lifelines/lifelines/src/liflines/add.c,v <-- add.c
new revision: 1.68; previous revision: 1.67
Success, CVS operation completed
Fix included in just-released 3.0.56 beta.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.