#4 5.5.1 ROMN/FONE compatibility broken

[Steve Swales]

The ROMN & FONE features from GEDCOM 5.5.1 require a
TYPE, e.g.

1 NAME /?/??
2 ROMN /Su/Wensi
3 TYPE pinyin

The compatibility code just converts the ROMN tag to
_ROMN, but the parse immediately fails when it hits the
required TYPE tag. Furthermore, ROMN and FONE may also
contain name pieces, duplicating those in the initial
name. These would also cause the parser to fail.

The parser should really properly parse FONE and ROMN
when in 5.5.1 compatibility mode and provide the parsed
values, which are very useful for trees with Asian names.

The PAF5 compatibility test provided does not include
either ROMN or FONE entries, so this bug is not being
detected by the test case.
I am working on sample diffs.... guess I should become
a team member :-).