GenoPro Support Forum

Thank you and you're right. The ONLY time when I've imported somenthing at all, was in the beginning, while converting my data from the old program to yours. I think, you should be more rigid in allowing such problematic field names formations during GED import process.

After deleting the problematic custom tag a total MESS/DISORDER has been created between all the remained fields !!! :

In the meanwhile (until the deletion process won't affect the remained database anymore at all), an additional option called "Rename custom tag" is strongly needed ! Please,  pay attention at the fact that all the field names - under Column Properties - are strictly protected. The new "Rename custom tag" option shouldn't affect : the remained database in any way !!! 

Still waiting for your reply,

Alfi

P.S. Any other problematic names I should be aware to ? ::

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.

Edited: Sunday, April 29, 2007 by GenoProSupport

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

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.

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.

UTF-8... by far!

UTF-8, UNICODE, ANSEL or ANSI 

 The software I imported from is FamilySearch Personal Ancestral File Ver 5.2.18.0.

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.

I often notice all these chan;date tags which I systemaically remove and then transfer the info from the baptm and occu tags etc and put them in their places in Genopro.

This is laborious but I wish to remove all custom tags and I am not sure that Ron's XML Tool does all this even though it does a lot.