|
|
|
|
Forum Members
Last Login: Thursday, May 1, 2025
Posts: 3,
Visits: 19
|
Thanks Ron. I have sent this to my cousin. He replies:
getting an error: Error at line 242, position 8 (Code/Utils.js): Exception thrown and not caught Microsoft JScript runtime error 800A139E
What do you think is happening? Thanks.
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Monday, June 9, 2025
Posts: 3,429,
Visits: 26,550
|
Well I have never known this error to occur before now but it suggests that the GenoPro XML is invalid i.e. syntactically incorrect. GenoPro holds its data in a zipped XML data file, saved as .gnoThe GenoPro Report Generator provides an interface allowing the report script to obtain the underlying XML text ( ReportGenerator. Document.GetTextXml) The gedcom script then tries to load it into a DOM using Microsoft XML parser which is when the error occurs. To help diagnose the cause of this previously unreported issue could you ask your cousin to use GenoPro's menu function File / Export / Export to XML to obtain the XML in a file for you. Then opening the XML file with IE or Chrome should flag the first invalid XML in the file. Report any findings here, Also if possible email me a copy of the XML file by attaching to an email sent via the email button on the left of this post under my user id.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Members
Last Login: Thursday, May 1, 2025
Posts: 3,
Visits: 19
|
Thank you Ron.
My cousin reports: "This page contains the following errors: error on line 18591 at column 7335: xmlParseCharRef: invalid xmlChar value 11Below is a rendering of the page up to the first error."I will email you the XML file - and thanks. Joyaa
Edited: Tuesday, February 18, 2020 by
Joyaa
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: Monday, June 9, 2025
Posts: 3,429,
Visits: 26,550
|
On further investigation of this issue I discovered that GenoPro allows characters to be stored in text that are actually invalid for XML files unless embedded within CDATA delimitiers. Characters with decimal code values below 32, i.e.below the space character in the ASCII character set, are 'control' characters. The only control characters allowed other than in CDATA sections in XML are 9 (tab) , 10 (linefeed) and 13 (carriage return). The character causing the problem in Joyaa's case is decimal code 11, which is known as VT or Vertical Tab. I presume this was imported via a gedcom file or copied and pasted from another source.
An error is flagged if XML data containing invalid characters is read/parsed using any standard XML parser. I have amended the script to remove invalid control characters before loading. This allows a gedcom file to be produced but note that the invalid characters will still remain in the output .ged as the data for it is obtained directly via the GenoPro Report Generator API and not via the XML. Joyaa's file also contained Tab characters which in fact are also illegal in Gedcom files. If the package you use to import the .ged file objects to these characters then I suggest you edit the .ged with a good text editor such as NotePad++ that allows find and replace for control characters via hexadecimal values. To use the amended report skin download the attached zipped folder and unzip into your GenoPro Report Skins folder replacing the existing {EN} Export to Gedcom folder
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
{EN} Export to Gedcom.zip
(18 views,
41.45 KB)
|