GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 
How to make changes to the dictionary work ?


https://support.genopro.com/Topic26404.aspx
Print Topic | Close Window

By temmery - Sunday, August 29, 2010
Hi,

I'm using the English narrative report to export data in Gedcom format. When importing the result in Geneanet, the place names are scrambled and the Gedcom code (for a person) appears under personal notes. This seems due to code produced by the dictionary: FORM LINKAGE-LINKED and FORM URL. When removing these code lines from the Gedcom output file, then the issues are solved, except for the tree-root still showing the personal Gecom code. I've adjusted the code in the dictionary (Skins > Customized Export to Gedcom) but it does not change export results.

What do I need to do to create Gedcom output, using the modified dictionary ? And what do I need to change to remove the Gedcom code from the tree root ?

Tom Emmery
By genome - Monday, August 30, 2010
I am sorry Tom, but I find your post very confused. You write about the 'English Narrative Report' but then refer to Gedcom. The Narrative Report skin generates an HTML report for publishing on the internet. The 'Export to Gedcom' skin as you must be aware, creates a .ged file from your data.

If you have produced a customised report skin for the 'Export to Gedcom' report and made changes to the Dictionary.xml file in that customised report skin, then when attempting to generate a a Gedcom file using your modified Dictionary.xml then all you need to do to generate a .ged file using that skin is select your 'Customised Export to Gedcom' skin folder in the drop down list of the GenoPro 'Generate Report' dialog. and click 'Generate'
By temmery - Thursday, September 2, 2010
Hi Ron,

I'm sorry, I meant the Export to Gedcom report. Which XML code do I need to change to take out the following Gedcom output :

3 FORM addr1, state

Thanks in advance !

Tom
By temmery - Saturday, September 4, 2010
In the meantime I've solved this by taking out the corresponding code-line 417 from Gedcom.js

Export to Geneanet is now working perfectly.

Tom