#GEDCOM EDITOR SOFTWARE#
#GEDCOM EDITOR CODE#

#GEDCOM EDITOR SOFTWARE#

When wide support for GEDCOM 5.5.2 is attained, GEDCOM readers can optimize their software to read 5.5.2 documents without special handling required by GEDCOM 5.5.1 and GEDCOM 5.5. GEDCOM writers must not specify 5.5.2 in the subrecord unless they make the requisite changes to ensure they meet the specification. Software authors should review the Implementation Notes for details. Because GEDCOM 5.5.1 features have been removed, a valid GEDCOM 5.5.1 document that uses those features is not a valid GEDCOM 5.5.2 document.Д«ecause the changes are minor, GEDCOM readers can typically support GEDCOM 5.5.2 with relatively minor changes.

When compared to the GEDCOM 5.5.1 specification, the GEDCOM 5.5.2 specificiation has Changes, Inconsequential Changes, and Documentation Changes.Д¬hanges includes the removal of obsolete features and minor changes to resolve errors and ambiguities. For those and other reasons, some software authors may ignore GEDCOM 5.5.2 as they have ignored all prior attempts to replace or extend GEDCOM, version 5.5.1 or otherwise. The exceptions are listed in the Changes section.ДЄny change may be controversial and all changes represent work for software authors. With a relatively small set of exceptions, a GEDCOM 5.5.2 document uses a subset of the rules for a GEDCOM 5.5.1 document. Its goal is to reduce compliance barriers without introducing significant changes. GEDCOM 5.5.2 corrects flaws and ambiguities in GEDCOM 5.5.1. Non-compliance increases the difficulty of implementing software to read GEDCOM documents and introduces unnecessary challenges for users of genealogy software. Others export GEDCOM 5.5 documents that include GEDCOM 5.5.1 subrecords or values. Some programs export GEDCOM 5.5.1 documents with minor or even major compliance issues. In the many years since the release of the GEDCOM 5.5.1 specification, most popular genealogy programs have implemented some or all of its features.Дue to the issues in the specification and other factors, many programs do not comply with the GEDCOM 5.5.1 specification. There are several flaws and ambiguous statements in the GEDCOM 5.5.1 specification, and the specification has been abandoned by its creators.Д®ven though the specification document was labeled 'DRAFT' and included an instruction that it 'must not be used for programming of genealogical software while in draft', GEDCOM 5.5.1 was implemented in software programs shortly after its release. The GEDCOM STANDARD DRAFT Release 5.5.1 ('GEDCOM 5.5.1') dated 2 October 1999 and prepared by the Family History Department of The Church of Jesus Christ of Latter-day Saints describes the most recent, widely-adopted specification for the interchange of data between genealogy applications using GEDCOM. In some cases, the removed text will be replaced. They will be removed after the first public review.

They may be removed or changed prior to the official release of GEDCOM 5.5.2.Д®ntries with a red border are marked for deletion. Implementers are urged to follow these practices, but the recommendations are not requirements.Д®ntries with a yellow border are provisional.

The actual text in a GEDCOM document must use the given Unicode character, not the characters that appear in the symbol itself.Д®ntries with a green border are best practice recommendations. Non-visible characters are rendered in this document as follows: Symbol Incorrect text is used in contrast to correct examples. Text formatted like this represents an incorrect keyword, value, or syntax.It is also used for example text that might appear in a GEDCOM document. Text formatted like this represents text that is used in a GEDCOM document exactly as shown.That is a GEDCOM reader/writer implementation detail that is not material to this specification.

#GEDCOM EDITOR CODE#

Unicode code points may require 1, 2, or more bytes when read from a UTF-8 document. There are exceptions where code point is used because the distinction is critical.ДЄny length constraints are given in characters, not bytes.

This document uses the term character where code point would be more accurate.

GitHub Project GEDCOM-5.5.2 Public URL of Document Associated documents Document Conventions A future version of this document will remove its Draft status. You may create a pull-request to propose and collaborate on changes to the document. Feedback and comments on this specification are welcome. GEDCOM 5.5.2 corrects flaws and resolves ambiguities in GEDCOM 5.5.1 to improve interoperability and reduce compliance barriers. GEDCOM 5.5.2 is a minor revision to GEDCOM 5.5.1. Everyone is permitted to copy and distribute verbatim copies of this document, but changing it is not allowed.

Gedcom editor