Implemented as a simple alphabetical table, it looks like this: tag That idea looks like this: GEDCOM or FTW TEXT tag Just add the FTW TEXT tags into the table, so that the reader responds identically to the GEDCOM and FTW TEXT tags. Supporting FTW TEXT is just a matter of supporting the FTW TEXT tags. The only difference between FTW GEDCOM and FTW TEXT is the tags they use. One reason that several vendors decided to support FTW in their GEDCOM readers is that it is not hard to do so. Oneįairly natural approach to building a GEDCOM reader is to use a table that associates each tags with the things the GEDCOM reader must do when it encounters these tags.Ĭonceptually, some part of that table could look like this: GEDCOM tag GEDCOM reader tag tableĪ GEDCOM reader recognises GEDCOM tags and then acts upon the tags. Several vendors do read FTW for compatibilityâs sake. It is a misfeature that no other vendor has duplicated.

Identical to FTW GEDCOM, a GEDCOM dialect that many GEDCOM readers handle successfully.įamily Tree Maker for Windows (FTW) is the only application that writes FTW

It does not discuss whether you should FTW TEXT. How to avoid the mistake many vendors make, and why you should avoid it. This article explains about how to support FTW TEXT in addition to GEDCOM, Magic article explains how to correctly detect GEDCOM and FTW TEXT and To do so, you need to distinguish between GEDCOM and FTW TEXT. One possible solution to those problems is to support FTW TEXT. The FTW TEXT Problem documents the problem that FTW TEXT causes with regular GEDCOM readers. The FTW TEXT article explains what FTW TEXT is.

Ahnenblatt ftw