#248 new indi edit doesn't get BOM

closed-fixed
elsapo
None
5
2007-04-19
2007-04-14
elsapo
No

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.

Discussion

  • elsapo
    elsapo
    2007-04-14

    Logged In: YES
    user_id=1195173
    Originator: YES

    Relevant code for new persons: add_indi_by_edit

    Same bug for new families.

    Relevant code for new families: add_family_by_edit

     
  • elsapo
    elsapo
    2007-04-14

    • assigned_to: nobody --> elsapo
     
  • elsapo
    elsapo
    2007-04-14

    • status: open --> open-fixed
     
  • elsapo
    elsapo
    2007-04-14

    Logged In: YES
    user_id=1195173
    Originator: YES

    Fixed in cvs:

    Checking in ChangeLog;
    /cvsroot/lifelines/lifelines/ChangeLog,v <-- ChangeLog
    new revision: 1.1950; previous revision: 1.1949
    done
    Checking in src/gedlib/nodeio.c;
    /cvsroot/lifelines/lifelines/src/gedlib/nodeio.c,v <-- nodeio.c
    new revision: 1.24; previous revision: 1.23
    done
    Checking in src/hdrs/gedcom.h;
    /cvsroot/lifelines/lifelines/src/hdrs/gedcom.h,v <-- gedcom.h
    new revision: 1.208; previous revision: 1.207
    done
    Checking in src/liflines/add.c;
    /cvsroot/lifelines/lifelines/src/liflines/add.c,v <-- add.c
    new revision: 1.68; previous revision: 1.67
    done

    Success, CVS operation completed

     
  • elsapo
    elsapo
    2007-04-19

    Logged In: YES
    user_id=1195173
    Originator: YES

    Fix included in just-released 3.0.56 beta.

     
  • elsapo
    elsapo
    2007-04-19

    • status: open-fixed --> closed-fixed