bugGhosts (Genealogy... Software) - Bugs: bug #1492, parsing of dates ranges or period...

 
 

bug #1492: parsing of dates ranges or period starting with a calendar escape

Submitted by:  Cyril Picard <cpcp>
Submitted on:  Wed 23 Oct 2002 09:40:30 PM UTC  
 
Category: GEDCOM ParserSeverity: 0 - Enhancement
Item Group: NoneStatus: Wont Fix
Privacy: PublicAssigned to: Cyril Picard <cpcp>
Open/Closed: ClosedRelease: Not Applicable

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 23 Oct 2002 09:40:30 PM UTC, original submission:

The date "@#DJULIAN@ BEF 1570" is not parsable. In fact this expression does not comply with the GEDCOM specification ; it should be "BEF @#DJULIAN@ 1570". However if many GEDCOM writers use this syntax, may be should we accept it.

Cyril Picard <cpcp>
Project AdministratorIn charge of this item.

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 6 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Mon 06 Jun 2005 07:55:05 PM UTCcpcpStatusNone=>Wont Fix
  Assigned toNone=>cpcp
  Open/ClosedOpen=>Closed
  Release=>Not Applicable
Wed 23 Oct 2002 09:46:24 PM UTCcpcpCategoryNone=>(Error - Not Found)
  Summary(evolution) parsing of dates ranges or period starting with a calendar escape=>

Back to the top


Powered by Savane 3.1-cleanup1