If it's not considered to always be desireable, perhaps an option
could be added (by users through user/options) to control whether
the byte order mark gets inserted at the beginning of a Gedcom
This also serves to identify the data as being in the UTF-8 encoding
to programs that are importing the data, if the exported data is in
UTF-8. In that case the byte order mark is $ef$bb$bf (not
sensitive to byte order). Keeping it optional would be good, since
some programs make still look for the "0 " as the first characters
of a Gedcom file. In which case, those programs should allow
specification of imported data as being in the UTF-8 encoding.
This option would have to be sensitive to the GedcomCodeset
If UTF-16 or UTF-32 where an option, then the byte order mark
should probably be handled as a character so that a system's byte
order would apply to it as well.
Log in to post a comment.