#1 Adapt codeset of import GEDCOM
If my database is empty, and I'm importing a GEDCOM,
it would seem convenient to have the option to adopt
its codeset as my internal codeset of the current
database (which is about to be full of that GEDCOM's
contents).
Or perhaps the program could offer me three options ?
If current database is empty,
a) - Use UTF-8 as internal codeset, and convert
as required
b) - Adapt codeset of incoming GEDCOM
c) - Specify now the internal codeset desired
d) - Proceed with no codeset information or conversion
Case (a) is really a special case of case (c), but
it is the recommended and preferred case, so I'd
like to give it top billing.
It would also be clever if the actual codeset of the
incoming GEDCOM were checked & used to
adjust the questions above--eg, if incoming
GEDCOM happens to UTF-8, then (a)==(b).
Also, the choices could be adjusted slightly
depending on whether there is a current internal
codeset. Eg, here is wordings when we're
being clever enough to reflect known information:
a) - Change from ISO-8859-15 to UTF-8 as the
internal codeset (and incoming GEDCOM will
be converted from ANSEL to UTF-8). This is
recommended.
b) - Change from ISO-8859-15 to ANSEL as the
incoming codeset (the codeset of the
incoming GEDCOM)
c) - Specify now an alternative internal codeset
[In this case option (d) is removed, as we have
an internal codeset, and the incoming GEDCOM
was recognized as ANSEL, so we expect to do
conversion.]
Logged In: YES
user_id=60964
I've just started parsing the incoming GEDCOM header.