Question For future use Gedcom 7
- mariannevanharten
- Topic Author
- Offline
- Premium Member
Less
More
1 year 4 months ago #1
by mariannevanharten
For future use Gedcom 7 was created by mariannevanharten
For future use Gedcom 7 in webtrees I appreciate two options:
* a check if the gedcom file to import doesn't have extended ASCII (ë,í, etc.). When exporting and re-importing this will result in duplicate � characters, which will expand the gedcom files larger and larger.
* a place for saving the Gedcom tag TAG and the associed URL
Best regards,
Marianne
* a check if the gedcom file to import doesn't have extended ASCII (ë,í, etc.). When exporting and re-importing this will result in duplicate � characters, which will expand the gedcom files larger and larger.
* a place for saving the Gedcom tag TAG and the associed URL
Best regards,
Marianne
Please Log in or Create an account to join the conversation.
- fisharebest
- Offline
- Administrator
1 year 4 months ago #2
by fisharebest
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Replied by fisharebest on topic For future use Gedcom 7
* a check if the gedcom file to import doesn't have extended ASCII (ë,í, etc.). When exporting and re-importing this will result in duplicate � characters, which will expand the gedcom files larger and larger.
GEDCOM 7 files do not contain a HEAD:CHAR field.
Until webtrees 2.1.16, a missing HEAD:CHAR (and encoding set to "automatic") was assumed to be ASCII (for compatibility with GEDCOM 5.5.1).
Since webtrees 2.1.17, a missing HEAD:CHAR (and encoding set to "automatic") is assumed to be UTF8.
So, 2.1.17 should now import GEDCOM 7 files without needed to select the encoding in the import page.
* a place for saving the Gedcom tag TAG and the associed URL
I'm not sure what you mean. Can you give an example?
GEDCOM 7 files do not contain a HEAD:CHAR field.
Until webtrees 2.1.16, a missing HEAD:CHAR (and encoding set to "automatic") was assumed to be ASCII (for compatibility with GEDCOM 5.5.1).
Since webtrees 2.1.17, a missing HEAD:CHAR (and encoding set to "automatic") is assumed to be UTF8.
So, 2.1.17 should now import GEDCOM 7 files without needed to select the encoding in the import page.
* a place for saving the Gedcom tag TAG and the associed URL
I'm not sure what you mean. Can you give an example?
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- Jefferson49
- Offline
- Senior Member
1 year 4 months ago #3
by Jefferson49
I guess it is about the definition of Gedcom 7 extension tags, which can be defined within a schema in the head:
If I import a Gedcom 7 file in webtrees 2.1.16, HEAD:SCHMA:TAG is currently shown as follows in the header:
Therefore, HEAD:SCHMA:TAG probably needs to be added to the Gedcom7 custom tag definiton.
Replied by Jefferson49 on topic For future use Gedcom 7
* a place for saving the Gedcom tag TAG and the associed URL
I'm not sure what you mean. Can you give an example?
I guess it is about the definition of Gedcom 7 extension tags, which can be defined within a schema in the head:
Code:
0 HEAD
1 SCHMA
2 TAG _SKYPEID http://xmlns.com/foaf/0.1/skypeID
2 TAG _MEMBER http://xmlns.com/foaf/0.1/member
If I import a Gedcom 7 file in webtrees 2.1.16, HEAD:SCHMA:TAG is currently shown as follows in the header:
Therefore, HEAD:SCHMA:TAG probably needs to be added to the Gedcom7 custom tag definiton.
Please Log in or Create an account to join the conversation.
- mariannevanharten
- Topic Author
- Offline
- Premium Member
1 year 4 months ago #4
by mariannevanharten
Replied by mariannevanharten on topic For future use Gedcom 7
Thanks @Jefferson49 for the additional text, Greg asked.
The HEAD:SCHMA is not exported when exporting a Gedcom nor downloading a Gedcom using the module DownloadGedcomWithURL
The HEAD:SCHMA is not exported when exporting a Gedcom nor downloading a Gedcom using the module DownloadGedcomWithURL
Please Log in or Create an account to join the conversation.
- Jefferson49
- Offline
- Senior Member
1 year 4 months ago #5
by Jefferson49
Yes, this is currently not implemented in the Gedcom 7 export of DownloadGedcomWithURL.
Additional comment: It is possible to include all extension tags of GEDCOM-L in HEAD:SCHMA, if "Use GEDCOM-L" is activated in the control panel, see screenshot.
Replied by Jefferson49 on topic For future use Gedcom 7
The HEAD:SCHMA is not exported when exporting a Gedcom nor downloading a Gedcom using the module DownloadGedcomWithURL
Yes, this is currently not implemented in the Gedcom 7 export of DownloadGedcomWithURL.
Additional comment: It is possible to include all extension tags of GEDCOM-L in HEAD:SCHMA, if "Use GEDCOM-L" is activated in the control panel, see screenshot.
Please Log in or Create an account to join the conversation.