Post by Howard Metcalfe on Aug 29, 2008 13:30:56 GMT -5
PAWriter version 82 was posted on Friday, August 29 2008. The following changes were made:
Level 0 FAM tags which have neither subordinate HUSB nor WIFE tags now create a husband with a ? for a surname and an unknown wife, and the family will include any children specified in subordinate CHIL tags. (Previously, these families were ignored and any children orphaned.)
Level 1 AFN tags (allowed for individuals only) are stored in the individual ID fields. The GEDCOM standard defines the REFN tag as "Ancestral File Number (size 1 to 12). A unique permanent record number of an individual record contained in the Family History Department's Ancestral File." (This is unchanged and noted here for completeness.)
Level 1 REFN tags for families are ignored on input. Level 1 REFN tags for individuals are stored in the individual ID fields. The GEDCOM standard defines the REFN tag as "User Reference Number (size 1 to 20). A user-defined number or text that the submitter uses to identify this record. For instance, it may be a record number within the submitter's automated or manual system, or it may be a page and position number on a pedigree chart." Only the first 15 characters are stored in the ID field, five more than in Mac PAF 2.3.1. (This is unchanged and noted here for completeness.)
Level 1 RIN tags are ignored on import. The GEDCOM standard defines the RIN tag as "Automated Record Id (size 1 to 12). A unique record identification number assigned to the record by the source system. This number is intended to serve as a more sure means of identification of a record between two interfacing systems."
Level 1 RFN (allowed for individuals only) tags are ignored on import. The GEDCOM standard defines the RFN tag as "Permanent Record File Number (size 1 to 90). The record number that uniquely identifies this record within a registered network resource. The number will be usable as a cross-reference pointer. The use of the colon ( is reserved to indicate the separation of the 'registered resource identifier' (which precedes the colon) and the unique 'record identifier' within that resource (which follows the colon). If the colon is used, implementations that check pointers should not expect to find a matching cross-reference identifier in the transmission but would find it in the indicated database within a network. Making resource files available to a public network is a future implementation."
Level 1 RESN tags (allowed for individuals only) are ignored on import. The GEDCOM standard defines the RESN tag as "Restriction Notice (size 6 to 7) [locked | privacy]. The restriction notice is defined for Ancestral File usage. Ancestral File download GEDCOM files may contain this data. Where locked = Some records in Ancestral File have been satisfactorily proven by evidence, but because of source conflicts or incorrect traditions, there are repeated attempts to change this record. By arrangement, the Ancestral File Custodian can lock a record so that it cannot be changed without an agreement from the person assigned as the steward of such a record. The assigned steward is either the submitter listed for the record or Family History Support when no submitter is listed. privacy = Information concerning this record is not present due to rights of or an approved request for privacy."
Any subordinate tags for the above-mentioned tags are ignored, as are any for level 1 HUSB, WIFE and CHIL tags.
Date modifiers (ABT, BEF, AFT and BET-AND) are capitalized on export. (Other date modfiers have always resulted in a warning message.)
Place qualifiers (possibly, probably and near) are spelled out in lower-case on export, rather than using the short forms ?, * and ~.
Consecutive question marks as well as consecutive underscores entered or imported into a name field are reduced to a single question mark or a single underscore.
Imported level 1 NOTE tags within the HEAD tag may now contain pointers to note records rather than text. This is non-standard.
Imported SOUR tags with a pointer to a source record may now have subordinate TEXT lines. This is non-standard.
A few other non-standard structures exported by Reunion are now imported and a couple of errors are corrected.
General notes are now exported when the ANSEL or UTF-8 character set is chosen. (Export of these notes can be suppressed by making them private notes; no private notes are exported when using the ANSEL or UTF-8 character set since they are not expected to be shared with others.)
The Reference guide appendix "GEDCOM" has been updated and now includes a grammatical description of the structure of exported GEDCOMs. (This appendix should be viewed only in the browser version of the Reference guide.)
Level 0 FAM tags which have neither subordinate HUSB nor WIFE tags now create a husband with a ? for a surname and an unknown wife, and the family will include any children specified in subordinate CHIL tags. (Previously, these families were ignored and any children orphaned.)
Level 1 AFN tags (allowed for individuals only) are stored in the individual ID fields. The GEDCOM standard defines the REFN tag as "Ancestral File Number (size 1 to 12). A unique permanent record number of an individual record contained in the Family History Department's Ancestral File." (This is unchanged and noted here for completeness.)
Level 1 REFN tags for families are ignored on input. Level 1 REFN tags for individuals are stored in the individual ID fields. The GEDCOM standard defines the REFN tag as "User Reference Number (size 1 to 20). A user-defined number or text that the submitter uses to identify this record. For instance, it may be a record number within the submitter's automated or manual system, or it may be a page and position number on a pedigree chart." Only the first 15 characters are stored in the ID field, five more than in Mac PAF 2.3.1. (This is unchanged and noted here for completeness.)
Level 1 RIN tags are ignored on import. The GEDCOM standard defines the RIN tag as "Automated Record Id (size 1 to 12). A unique record identification number assigned to the record by the source system. This number is intended to serve as a more sure means of identification of a record between two interfacing systems."
Level 1 RFN (allowed for individuals only) tags are ignored on import. The GEDCOM standard defines the RFN tag as "Permanent Record File Number (size 1 to 90). The record number that uniquely identifies this record within a registered network resource. The number will be usable as a cross-reference pointer. The use of the colon ( is reserved to indicate the separation of the 'registered resource identifier' (which precedes the colon) and the unique 'record identifier' within that resource (which follows the colon). If the colon is used, implementations that check pointers should not expect to find a matching cross-reference identifier in the transmission but would find it in the indicated database within a network. Making resource files available to a public network is a future implementation."
Level 1 RESN tags (allowed for individuals only) are ignored on import. The GEDCOM standard defines the RESN tag as "Restriction Notice (size 6 to 7) [locked | privacy]. The restriction notice is defined for Ancestral File usage. Ancestral File download GEDCOM files may contain this data. Where locked = Some records in Ancestral File have been satisfactorily proven by evidence, but because of source conflicts or incorrect traditions, there are repeated attempts to change this record. By arrangement, the Ancestral File Custodian can lock a record so that it cannot be changed without an agreement from the person assigned as the steward of such a record. The assigned steward is either the submitter listed for the record or Family History Support when no submitter is listed. privacy = Information concerning this record is not present due to rights of or an approved request for privacy."
Any subordinate tags for the above-mentioned tags are ignored, as are any for level 1 HUSB, WIFE and CHIL tags.
Date modifiers (ABT, BEF, AFT and BET-AND) are capitalized on export. (Other date modfiers have always resulted in a warning message.)
Place qualifiers (possibly, probably and near) are spelled out in lower-case on export, rather than using the short forms ?, * and ~.
Consecutive question marks as well as consecutive underscores entered or imported into a name field are reduced to a single question mark or a single underscore.
Imported level 1 NOTE tags within the HEAD tag may now contain pointers to note records rather than text. This is non-standard.
Imported SOUR tags with a pointer to a source record may now have subordinate TEXT lines. This is non-standard.
A few other non-standard structures exported by Reunion are now imported and a couple of errors are corrected.
General notes are now exported when the ANSEL or UTF-8 character set is chosen. (Export of these notes can be suppressed by making them private notes; no private notes are exported when using the ANSEL or UTF-8 character set since they are not expected to be shared with others.)
The Reference guide appendix "GEDCOM" has been updated and now includes a grammatical description of the structure of exported GEDCOMs. (This appendix should be viewed only in the browser version of the Reference guide.)