bugGhosts (Genealogy... Software) - Bugs: bug #8662, Bad behavior in case of TAG in ID...

 
 

bug #8662: Bad behavior in case of TAG in ID or value of a GEDCOM item

Submitter:  Cyril Picard <cpcp>
Submitted:  Thu 22 Apr 2004 08:10:08 PM UTC
   
 
Category:  GEDCOM Parser Severity:  2 - Major
Item Group:  None Status:  None
Privacy:  Public Assigned to:  cpcp
Open/Closed:  Open Release:  * GHOSTS_20040329
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 22 Apr 2004 08:16:30 PM UTC, comment #1: 

The problem has not been reproduced when the TAG is included in the value

Cyril Picard <cpcp>
Group administrator
Thu 22 Apr 2004 08:10:08 PM UTC, original submission:  

In some cases the gedcom parser may recognize a string as a TAG, but it should not. It occurs when the tag is in the ID of the GEDCOM item, for instance:

  1. @FAM1@ FAM

Here the 3 first characters are recognized a the TAG for a FAM_RECORD, although they should be considered as  included in the ID of the FAM_RECORD.
May be a similar problem can occur when the TAG is recognized in the value for instance
1 NOTE this includes a FAM tag

Cyril Picard <cpcp>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #1240:  BAD_PARSING.GED added by cpcp (394B - application/octet-stream - GEDCOM file to reproduce the problem (0 @FAM1@ FAM))

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follows 1 latest change.

Date Changed by Updated Field Previous Value => Replaced by
2004-04-22 cpcp Attached File- Added BAD_PARSING.GED, #1224

Back to the top

Powered by Savane 3.13-d3ae.
Corresponding source code