|
|
|
Grand Master
 
Group: Customers
Last Login: Today @ 5:05:09 PM
GenoPro Version: 2.0.1.5
Posts: 1,082,
Visits: 4,952
|
|
Hi again Nina, now that I have your file I discover the problem is invalid Unicode characters in your data. Some of the Comment fields contain a Hex(0B) character, encoded by GenoPro to . This is apparently invalid Unicode. In fact if your export your .gno file as an XML file and then try and open it with IE or an XML Editor then they also flag the invalid data. Note that these codes are only visible in the XML, not via the GenoPro Property Dialogues.In ASCII Hex(0B) is a vertical tab, although MS Word uses it as a newline code. One way to correct your data is to export to XML using GenoPro's File, Export Menu item and then edit the XML file with Notepad replacing all  with either (i.e. newline), with 	 (horizontal tab) or a space. Then open this edited file with GenoPro and save again as a .gno. The Report will then be fine. Could you let us know which product the data was imported from in case others hit this issue. Note that you do not need to rename or remove CHAN.DATE or CHAN.DATE.TIME tags. This is because the DATE component here is not a built-in GenoPro Date object, but another Custom Tag. Only the built-in GenoPro Date fields have the problem with Custom Tags below them. Many packages use these CHAN tags to record when an item was last changed. To remove then from the 'Additional Information' in a Report simply move them to a Custom Tag Layout that has an underscore as the 1st character of its description. Perhaps in future Dan can filter out this invalid code on import. meanwhile I am producing a version of the skin that will flag this error but continue without processing any Custom Tags.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Newbie
Group: Customers
Last Login: 4/24/2007 9:52:20 PM
GenoPro Version: 2.0.0.4
Posts: 7,
Visits: 24
|
|
| Thanks, I will try this. That explains why some of my files work and some don't. The software I imported from is FamilySearch Personal Ancestral File Ver 5.2.18.0.
|
|
|
|
|
Forum Newbie
Group: Customers
Last Login: 4/24/2007 9:52:20 PM
GenoPro Version: 2.0.0.4
Posts: 7,
Visits: 24
|
|
| Okay, given your information above, I have one more question. The FamilySearch Personal Ancestral File has different options for exporting GED FILES. In the future which one would be best for GenoPro to import? UTF-8, UNICODE, ANSEL or ANSI
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:00:02 PM
GenoPro Version: 2.0.1.6
Posts: 3,427,
Visits: 14,248
|
|
46785 (4/24/2007)
The FamilySearch Personal Ancestral File has different options for exporting GED FILES. In the future which one would be best for GenoPro to import? UTF-8, UNICODE, ANSEL or ANSI UTF-8... by far!
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 5:05:09 PM
GenoPro Version: 2.0.1.5
Posts: 1,082,
Visits: 4,952
|
|
GenoProSupport (4/24/2007)
UTF-8... by far!I agree, Also I'm not sure what they actually mean by 'UNICODE' as a file encoding, unless they meant to say UTF-16. I suspect that PAF will still pass Hex(0B) through via UTF-8 however. Such values need to be filtered out before GenoPro converts the data to XML. A correction to my earlier posts, the Hex(0B) character is not actually invalid Unicode, but is an invalid XML 1.0 data character. Of the ASCII character codes below decimal 32, XML 1.0 can only legally contain 9 (tab), 10 (linefeed) or 13 (carriage return) I.e. Hex 09, 0A & 0D respectively. These character are valid in XML 1.1 , except NUL i.e. Hex 00. At the moment I am unsure of the implications of using XML 1.1.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:00:02 PM
GenoPro Version: 2.0.1.6
Posts: 3,427,
Visits: 14,248
|
|
Ron (4/25/2007)
I suspect that PAF will still pass Hex(0B) through via UTF-8 however. Such values need to be filtered out before GenoPro converts the data to XML.GenoPro should filter out those values. I verified the code again to confirm all values below Unicode point 32 (space) are replaced by a space except the tab, line feed and carriage return. Of course values already imported into GenoPro are kept as as is. One thing I can do is adding a routine to clean existing .xml files.
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: Today @ 2:41:30 PM
GenoPro Version: 2.0.1.5
Posts: 303,
Visits: 4,158
|
|
GenoProSupport (4/22/2007)
[quote][b]If you have something like death.date.comment, just rename your tag to death.date_comment and it will work. The ONLY problem is that the so-called "death.date.comment" field was NEVER defined BY ME, but only by the initial program bought from you. Anyway, even if I wish, I cannot find any place under the TOOLS option, where to change this name. Please answer me urgently, Alfi
additional email: finkea@mail.biu.ac.il ARIGATO-GOZAIMASU(jp) DAKUJEM(sk) DANKE(d) EVHARISTIES(gr) GRAZIE(it) MERCI(f) MULTUMESC(ro) SPASIVA(ru) THANKS(gb) THODAH(il)
|
|
|
|
|
IT Director GenoPro
Group: Customers
Last Login: Today @ 10:16:21 PM
GenoPro Version: 2.0.1.6
Posts: 444,
Visits: 5,833
|
|
Alfi (4/28/2007)
The ONLY problem is that the so-called "death.date.comment" field was NEVER defined BY ME, but only by the initial program bought from you.The custom tag has been imported probably from a GEDCOM file. To delete a custom tag, right-click on the column from the table layout and select the menu item Delete Custom Tag. 
If the facts don't fit the theory, change the facts.
-- Albert Einstein Jean-Claude Morin
Information Technology Director, GenoPro.
http://www.genopro.com
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: Today @ 2:41:30 PM
GenoPro Version: 2.0.1.5
Posts: 303,
Visits: 4,158
|
|
| | |