Skip Menu |

This queue is for tickets about the Genealogy-Gedcom CPAN distribution.

Report information
The Basics
Id: 86280
Status: rejected
Priority: 0/
Queue: Genealogy-Gedcom

People
Owner: Nobody in particular
Requestors: bob.coret [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: issue with TIME tag
Date: Thu, 20 Jun 2013 16:21:09 +0200
To: bug-genealogy-gedcom [...] rt.cpan.org
From: Bob Coret <bob.coret [...] gmail.com>
Hi, I'm using the Genalogy-Gedcom-Lexer (v.0.8.2) to validate GEDCOM's I produce. The validation incorrectly warns me about "The unknown tag TIME was detected". Partial GEDCOM: 0 HEAD 1 SOUR PLUS_GEN 2 VERS 0.2 2 NAME PlusGenealogie 2 CORP Coret Genealogie 3 WWW http://genealogie.coret.org/ 1 DATE 20 JUN 2013 2 TIME 16:04 Debug log: tag_lineage(1, '0 HEAD') tag_header(1, '0 HEAD') tag_approved_system_id(2, '1 SOUR PLUS_GEN') tag_version_number(3, '2 VERS 0.2') tag_name_of_product(4, '2 NAME PlusGenealogie') tag_name_of_business(5, '2 CORP Coret Genealogie') tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') tag_publication_date(8, '1 DATE 20 JUN 2013') tag_trailer(9, '2 TIME 16:04') Line: 9. The unknown tag TIME was detected GEDCOM 5.5 spec (same for 5.5.1): *HEADER:* = n HEAD {1:1} +1 SOUR <APPROVED_SYSTEM_ID <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#APPROVED_SYSTEM_ID>> {1:1} +2 VERS <VERSION_NUMBER <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#VERSION_NUMBER>> {0:1} +2 NAME <NAME_OF_PRODUCT <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_PRODUCT>> {0:1} +2 CORP <NAME_OF_BUSINESS <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_BUSINESS>> {0:1} +3 <<ADDRESS_STRUCTURE <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#ADDRESS_STRUCTURE>>> {0:1} +2 DATA <NAME_OF_SOURCE_DATA <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_SOURCE_DATA>> {0:1} +3 DATE <PUBLICATION_DATE <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#PUBLICATION_DATE>> {0:1} +3 COPR <COPYRIGHT_SOURCE_DATA <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#COPYRIGHT_SOURCE_DATA>> {0:1} +1 DEST <RECEIVING_SYSTEM_NAME <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#RECEIVING_SYSTEM_NAME>> {0:1*} +1 DATE <TRANSMISSION_DATE <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TRANSMISSION_DATE>> {0:1} +2 TIME <TIME_VALUE <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TIME_VALUE>> {0:1}.... Regards, Bob Coret Coret Genealogie <http://genealogie.coret.org/>
Subject: Re: [rt.cpan.org #86280] issue with TIME tag
Date: Fri, 21 Jun 2013 08:46:50 +1000
To: bug-Genealogy-Gedcom [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Bob Hmmm. The code has time-handling in it. The test data file (royal.ged) even has a time in it. But my other test data does not. I'll have to investigate. On 21/06/13 00:21, Bob Coret via RT wrote: Show quoted text
> Thu Jun 20 10:21:31 2013: Request 86280 was acted upon. > Transaction: Ticket created by bob.coret@gmail.com > Queue: Genealogy-Gedcom > Subject: issue with TIME tag > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: bob.coret@gmail.com > Status: new > Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> > > > Hi, > > I'm using the Genalogy-Gedcom-Lexer (v.0.8.2) to validate GEDCOM's I > produce. > > The validation incorrectly warns me about "The unknown tag TIME was > detected". > > Partial GEDCOM: > > 0 HEAD > 1 SOUR PLUS_GEN > 2 VERS 0.2 > 2 NAME PlusGenealogie > 2 CORP Coret Genealogie > 3 WWW http://genealogie.coret.org/ > 1 DATE 20 JUN 2013 > 2 TIME 16:04 > > Debug log: > > tag_lineage(1, '0 HEAD') > tag_header(1, '0 HEAD') > tag_approved_system_id(2, '1 SOUR PLUS_GEN') > tag_version_number(3, '2 VERS 0.2') > tag_name_of_product(4, '2 NAME PlusGenealogie') > tag_name_of_business(5, '2 CORP Coret Genealogie') > tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') > tag_publication_date(8, '1 DATE 20 JUN 2013') > tag_trailer(9, '2 TIME 16:04') > Line: 9. The unknown tag TIME was detected > > GEDCOM 5.5 spec (same for 5.5.1): > > *HEADER:* = > > n HEAD {1:1} > +1 SOUR<APPROVED_SYSTEM_ID > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#APPROVED_SYSTEM_ID>> > {1:1} > +2 VERS<VERSION_NUMBER > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#VERSION_NUMBER>> > {0:1} > +2 NAME<NAME_OF_PRODUCT > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_PRODUCT>> > {0:1} > +2 CORP<NAME_OF_BUSINESS > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_BUSINESS>> > {0:1} > +3<<ADDRESS_STRUCTURE > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#ADDRESS_STRUCTURE>>> > {0:1} > +2 DATA<NAME_OF_SOURCE_DATA > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_SOURCE_DATA>> > {0:1} > +3 DATE<PUBLICATION_DATE > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#PUBLICATION_DATE>> > {0:1} > +3 COPR<COPYRIGHT_SOURCE_DATA > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#COPYRIGHT_SOURCE_DATA>> > {0:1} > +1 DEST<RECEIVING_SYSTEM_NAME > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#RECEIVING_SYSTEM_NAME>> > {0:1*} > +1 DATE<TRANSMISSION_DATE > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TRANSMISSION_DATE>> > {0:1} > +2 TIME<TIME_VALUE > <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TIME_VALUE>> > {0:1}.... > > > Regards, > > Bob Coret > Coret Genealogie<http://genealogie.coret.org/> >
-- Ron Savage http://savage.net.au/ Ph: 0421 920 622
Subject: Re: [rt.cpan.org #86280] issue with TIME tag
Date: Fri, 21 Jun 2013 09:22:14 +1000
To: bug-Genealogy-Gedcom [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Bob No problem here using V 0.82. Data: 0 HEAD 1 SOUR PLUS_GEN 2 VERS 0.2 2 NAME PlusGenealogie 2 CORP Coret Genealogie 3 WWW http://genealogie.coret.org/ 1 DATE 20 JUN 2013 2 TIME 16:04 0 TRLR Log: ron@zigzag:~/perl.modules/Genealogy-Gedcom$ perl -Ilib scripts/lex.pl -i data/sample.5.ged -s 1 -maxlevel debug tag_lineage(1, '0 HEAD') tag_header(1, '0 HEAD') tag_approved_system_id(2, '1 SOUR PLUS_GEN') tag_version_number(3, '2 VERS 0.2') tag_name_of_product(4, '2 NAME PlusGenealogie') tag_name_of_business(5, '2 CORP Coret Genealogie') tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') tag_transmission_date(7, '1 DATE 20 JUN 2013') tag_time_value(8, '2 TIME 16:04') tag_trailer(10, '0 TRLR') Notice that your output says: tag_publication_date(8, '1 DATE 20 JUN 2013') tag_trailer(9, '2 TIME 16:04') whereas mine says: tag_transmission_date(7, '1 DATE 20 JUN 2013') tag_time_value(8, '2 TIME 16:04') tag_trailer(10, '0 TRLR') I suggest you (re-)install V 0.82, run using the same test data as I used above, and see what happens. On 21/06/13 08:48, ron@savage.net.au via RT wrote: Show quoted text
> Queue: Genealogy-Gedcom > Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> > > Hi Bob > > Hmmm. The code has time-handling in it. The test data file (royal.ged) > even has a time in it. But my other test data does not. I'll have to > investigate. > > On 21/06/13 00:21, Bob Coret via RT wrote:
>> Thu Jun 20 10:21:31 2013: Request 86280 was acted upon. >> Transaction: Ticket created by bob.coret@gmail.com >> Queue: Genealogy-Gedcom >> Subject: issue with TIME tag >> Broken in: (no value) >> Severity: (no value) >> Owner: Nobody >> Requestors: bob.coret@gmail.com >> Status: new >> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >> >> >> Hi, >> >> I'm using the Genalogy-Gedcom-Lexer (v.0.8.2) to validate GEDCOM's I >> produce. >> >> The validation incorrectly warns me about "The unknown tag TIME was >> detected". >> >> Partial GEDCOM: >> >> 0 HEAD >> 1 SOUR PLUS_GEN >> 2 VERS 0.2 >> 2 NAME PlusGenealogie >> 2 CORP Coret Genealogie >> 3 WWW http://genealogie.coret.org/ >> 1 DATE 20 JUN 2013 >> 2 TIME 16:04 >> >> Debug log: >> >> tag_lineage(1, '0 HEAD') >> tag_header(1, '0 HEAD') >> tag_approved_system_id(2, '1 SOUR PLUS_GEN') >> tag_version_number(3, '2 VERS 0.2') >> tag_name_of_product(4, '2 NAME PlusGenealogie') >> tag_name_of_business(5, '2 CORP Coret Genealogie') >> tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') >> tag_publication_date(8, '1 DATE 20 JUN 2013') >> tag_trailer(9, '2 TIME 16:04') >> Line: 9. The unknown tag TIME was detected >> >> GEDCOM 5.5 spec (same for 5.5.1): >> >> *HEADER:* = >> >> n HEAD {1:1} >> +1 SOUR<APPROVED_SYSTEM_ID >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#APPROVED_SYSTEM_ID>> >> {1:1} >> +2 VERS<VERSION_NUMBER >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#VERSION_NUMBER>> >> {0:1} >> +2 NAME<NAME_OF_PRODUCT >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_PRODUCT>> >> {0:1} >> +2 CORP<NAME_OF_BUSINESS >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_BUSINESS>> >> {0:1} >> +3<<ADDRESS_STRUCTURE >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#ADDRESS_STRUCTURE>>> >> {0:1} >> +2 DATA<NAME_OF_SOURCE_DATA >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_SOURCE_DATA>> >> {0:1} >> +3 DATE<PUBLICATION_DATE >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#PUBLICATION_DATE>> >> {0:1} >> +3 COPR<COPYRIGHT_SOURCE_DATA >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#COPYRIGHT_SOURCE_DATA>> >> {0:1} >> +1 DEST<RECEIVING_SYSTEM_NAME >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#RECEIVING_SYSTEM_NAME>> >> {0:1*} >> +1 DATE<TRANSMISSION_DATE >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TRANSMISSION_DATE>> >> {0:1} >> +2 TIME<TIME_VALUE >> <http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TIME_VALUE>> >> {0:1}.... >> >> >> Regards, >> >> Bob Coret >> Coret Genealogie<http://genealogie.coret.org/> >>
>
-- Ron Savage http://savage.net.au/ Ph: 0421 920 622
Subject: Re: [rt.cpan.org #86280] issue with TIME tag
Date: Fri, 21 Jun 2013 09:00:03 +0200
To: bug-Genealogy-Gedcom [...] rt.cpan.org
From: Bob Coret <bob.coret [...] gmail.com>
Hi Ron, I installed 0.82 yesterday (fresh machine) and royal.ged doesn't complain about TIME. I've narrowed the issue down to the "2 DATA" line. When I remove this line (which is a valid line), then there's no issue with TIME. 0 HEAD 1 SOUR PLUS_GEN 2 VERS 0.2 2 NAME PlusGenealogie 2 CORP Coret Genealogie 3 WWW http://genealogie.coret.org/ ** 2 DATA WieWasWie ** 1 DATE 20 JUN 2013 2 TIME 17:13 I guess the lexer thinks it's an HEAD > SOUR > DATA > DATE (tag_publication_date) but it's really HEAD > SOUR > DATE (tag_transission_date). Bob mvg, Bob Coret On Fri, Jun 21, 2013 at 1:23 AM, ron@savage.net.au via RT < bug-Genealogy-Gedcom@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=86280 > > > Hi Bob > > No problem here using V 0.82. > > Data: > 0 HEAD > 1 SOUR PLUS_GEN > 2 VERS 0.2 > 2 NAME PlusGenealogie > 2 CORP Coret Genealogie > 3 WWW http://genealogie.coret.org/ > 1 DATE 20 JUN 2013 > 2 TIME 16:04 > 0 TRLR > > Log: > ron@zigzag:~/perl.modules/Genealogy-Gedcom$ perl -Ilib scripts/lex.pl -i > data/sample.5.ged -s 1 -maxlevel debug > tag_lineage(1, '0 HEAD') > tag_header(1, '0 HEAD') > tag_approved_system_id(2, '1 SOUR PLUS_GEN') > tag_version_number(3, '2 VERS 0.2') > tag_name_of_product(4, '2 NAME PlusGenealogie') > tag_name_of_business(5, '2 CORP Coret Genealogie') > tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') > tag_transmission_date(7, '1 DATE 20 JUN 2013') > tag_time_value(8, '2 TIME 16:04') > tag_trailer(10, '0 TRLR') > > Notice that your output says: > > tag_publication_date(8, '1 DATE 20 JUN 2013') > tag_trailer(9, '2 TIME 16:04') > > whereas mine says: > > tag_transmission_date(7, '1 DATE 20 JUN 2013') > tag_time_value(8, '2 TIME 16:04') > tag_trailer(10, '0 TRLR') > > I suggest you (re-)install V 0.82, run using the same test data as I > used above, and see what happens. > > On 21/06/13 08:48, ron@savage.net.au via RT wrote:
> > Queue: Genealogy-Gedcom > > Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> > > > > Hi Bob > > > > Hmmm. The code has time-handling in it. The test data file (royal.ged) > > even has a time in it. But my other test data does not. I'll have to > > investigate. > > > > On 21/06/13 00:21, Bob Coret via RT wrote:
> >> Thu Jun 20 10:21:31 2013: Request 86280 was acted upon. > >> Transaction: Ticket created by bob.coret@gmail.com > >> Queue: Genealogy-Gedcom > >> Subject: issue with TIME tag > >> Broken in: (no value) > >> Severity: (no value) > >> Owner: Nobody > >> Requestors: bob.coret@gmail.com > >> Status: new > >> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> > >> > >> > >> Hi, > >> > >> I'm using the Genalogy-Gedcom-Lexer (v.0.8.2) to validate GEDCOM's I > >> produce. > >> > >> The validation incorrectly warns me about "The unknown tag TIME was > >> detected". > >> > >> Partial GEDCOM: > >> > >> 0 HEAD > >> 1 SOUR PLUS_GEN > >> 2 VERS 0.2 > >> 2 NAME PlusGenealogie > >> 2 CORP Coret Genealogie > >> 3 WWW http://genealogie.coret.org/ > >> 1 DATE 20 JUN 2013 > >> 2 TIME 16:04 > >> > >> Debug log: > >> > >> tag_lineage(1, '0 HEAD') > >> tag_header(1, '0 HEAD') > >> tag_approved_system_id(2, '1 SOUR PLUS_GEN') > >> tag_version_number(3, '2 VERS 0.2') > >> tag_name_of_product(4, '2 NAME PlusGenealogie') > >> tag_name_of_business(5, '2 CORP Coret Genealogie') > >> tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') > >> tag_publication_date(8, '1 DATE 20 JUN 2013') > >> tag_trailer(9, '2 TIME 16:04') > >> Line: 9. The unknown tag TIME was detected > >> > >> GEDCOM 5.5 spec (same for 5.5.1): > >> > >> *HEADER:* = > >> > >> n HEAD {1:1} > >> +1 SOUR<APPROVED_SYSTEM_ID > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#APPROVED_SYSTEM_ID
> >> > >> {1:1} > >> +2 VERS<VERSION_NUMBER > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#VERSION_NUMBER
> >> > >> {0:1} > >> +2 NAME<NAME_OF_PRODUCT > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_PRODUCT
> >> > >> {0:1} > >> +2 CORP<NAME_OF_BUSINESS > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_BUSINESS
> >> > >> {0:1} > >> +3<<ADDRESS_STRUCTURE > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#ADDRESS_STRUCTURE
> >>>
> >> {0:1} > >> +2 DATA<NAME_OF_SOURCE_DATA > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_SOURCE_DATA
> >> > >> {0:1} > >> +3 DATE<PUBLICATION_DATE > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#PUBLICATION_DATE
> >> > >> {0:1} > >> +3 COPR<COPYRIGHT_SOURCE_DATA > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#COPYRIGHT_SOURCE_DATA
> >> > >> {0:1} > >> +1 DEST<RECEIVING_SYSTEM_NAME > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#RECEIVING_SYSTEM_NAME
> >> > >> {0:1*} > >> +1 DATE<TRANSMISSION_DATE > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TRANSMISSION_DATE
> >> > >> {0:1} > >> +2 TIME<TIME_VALUE > >> <
> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TIME_VALUE
> >> > >> {0:1}.... > >> > >> > >> Regards, > >> > >> Bob Coret > >> Coret Genealogie<http://genealogie.coret.org/> > >>
> >
> > -- > Ron Savage > http://savage.net.au/ > Ph: 0421 920 622 > >
Subject: Re: [rt.cpan.org #86280] issue with TIME tag
Date: Sat, 22 Jun 2013 10:02:23 +1000
To: bug-Genealogy-Gedcom [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Bob On 21/06/13 17:00, Bob Coret via RT wrote: Show quoted text
> Queue: Genealogy-Gedcom > Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> > > Hi Ron, > > I installed 0.82 yesterday (fresh machine) and royal.ged doesn't complain > about TIME.
OK. Show quoted text
> I've narrowed the issue down to the "2 DATA" line. When I remove this line > (which is a valid line), then there's no issue with TIME. > > 0 HEAD > 1 SOUR PLUS_GEN > 2 VERS 0.2 > 2 NAME PlusGenealogie > 2 CORP Coret Genealogie > 3 WWW http://genealogie.coret.org/ > ** 2 DATA WieWasWie ** > 1 DATE 20 JUN 2013 > 2 TIME 17:13 > > I guess the lexer thinks it's an HEAD> SOUR> DATA> DATE > (tag_publication_date) but it's really HEAD> SOUR> DATE > (tag_transission_date).
This is important info, but wouldn't it be: HEAD > DATE going by their levels of 0 > 1? Either way, I have a target for investigations. $many $thanx; Show quoted text
> Bob > > > > mvg, > > Bob Coret > > > On Fri, Jun 21, 2013 at 1:23 AM, ron@savage.net.au via RT< > bug-Genealogy-Gedcom@rt.cpan.org> wrote: >
>> <URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >> >> Hi Bob >> >> No problem here using V 0.82. >> >> Data: >> 0 HEAD >> 1 SOUR PLUS_GEN >> 2 VERS 0.2 >> 2 NAME PlusGenealogie >> 2 CORP Coret Genealogie >> 3 WWW http://genealogie.coret.org/ >> 1 DATE 20 JUN 2013 >> 2 TIME 16:04 >> 0 TRLR >> >> Log: >> ron@zigzag:~/perl.modules/Genealogy-Gedcom$ perl -Ilib scripts/lex.pl -i >> data/sample.5.ged -s 1 -maxlevel debug >> tag_lineage(1, '0 HEAD') >> tag_header(1, '0 HEAD') >> tag_approved_system_id(2, '1 SOUR PLUS_GEN') >> tag_version_number(3, '2 VERS 0.2') >> tag_name_of_product(4, '2 NAME PlusGenealogie') >> tag_name_of_business(5, '2 CORP Coret Genealogie') >> tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') >> tag_transmission_date(7, '1 DATE 20 JUN 2013') >> tag_time_value(8, '2 TIME 16:04') >> tag_trailer(10, '0 TRLR') >> >> Notice that your output says: >> >> tag_publication_date(8, '1 DATE 20 JUN 2013') >> tag_trailer(9, '2 TIME 16:04') >> >> whereas mine says: >> >> tag_transmission_date(7, '1 DATE 20 JUN 2013') >> tag_time_value(8, '2 TIME 16:04') >> tag_trailer(10, '0 TRLR') >> >> I suggest you (re-)install V 0.82, run using the same test data as I >> used above, and see what happens. >> >> On 21/06/13 08:48, ron@savage.net.au via RT wrote:
>>> Queue: Genealogy-Gedcom >>> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >>> >>> Hi Bob >>> >>> Hmmm. The code has time-handling in it. The test data file (royal.ged) >>> even has a time in it. But my other test data does not. I'll have to >>> investigate. >>> >>> On 21/06/13 00:21, Bob Coret via RT wrote:
>>>> Thu Jun 20 10:21:31 2013: Request 86280 was acted upon. >>>> Transaction: Ticket created by bob.coret@gmail.com >>>> Queue: Genealogy-Gedcom >>>> Subject: issue with TIME tag >>>> Broken in: (no value) >>>> Severity: (no value) >>>> Owner: Nobody >>>> Requestors: bob.coret@gmail.com >>>> Status: new >>>> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >>>> >>>> >>>> Hi, >>>> >>>> I'm using the Genalogy-Gedcom-Lexer (v.0.8.2) to validate GEDCOM's I >>>> produce. >>>> >>>> The validation incorrectly warns me about "The unknown tag TIME was >>>> detected". >>>> >>>> Partial GEDCOM: >>>> >>>> 0 HEAD >>>> 1 SOUR PLUS_GEN >>>> 2 VERS 0.2 >>>> 2 NAME PlusGenealogie >>>> 2 CORP Coret Genealogie >>>> 3 WWW http://genealogie.coret.org/ >>>> 1 DATE 20 JUN 2013 >>>> 2 TIME 16:04 >>>> >>>> Debug log: >>>> >>>> tag_lineage(1, '0 HEAD') >>>> tag_header(1, '0 HEAD') >>>> tag_approved_system_id(2, '1 SOUR PLUS_GEN') >>>> tag_version_number(3, '2 VERS 0.2') >>>> tag_name_of_product(4, '2 NAME PlusGenealogie') >>>> tag_name_of_business(5, '2 CORP Coret Genealogie') >>>> tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') >>>> tag_publication_date(8, '1 DATE 20 JUN 2013') >>>> tag_trailer(9, '2 TIME 16:04') >>>> Line: 9. The unknown tag TIME was detected >>>> >>>> GEDCOM 5.5 spec (same for 5.5.1): >>>> >>>> *HEADER:* = >>>> >>>> n HEAD {1:1} >>>> +1 SOUR<APPROVED_SYSTEM_ID >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#APPROVED_SYSTEM_ID
>>>> >>>> {1:1} >>>> +2 VERS<VERSION_NUMBER >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#VERSION_NUMBER
>>>> >>>> {0:1} >>>> +2 NAME<NAME_OF_PRODUCT >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_PRODUCT
>>>> >>>> {0:1} >>>> +2 CORP<NAME_OF_BUSINESS >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_BUSINESS
>>>> >>>> {0:1} >>>> +3<<ADDRESS_STRUCTURE >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#ADDRESS_STRUCTURE
>>>>>
>>>> {0:1} >>>> +2 DATA<NAME_OF_SOURCE_DATA >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_SOURCE_DATA
>>>> >>>> {0:1} >>>> +3 DATE<PUBLICATION_DATE >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#PUBLICATION_DATE
>>>> >>>> {0:1} >>>> +3 COPR<COPYRIGHT_SOURCE_DATA >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#COPYRIGHT_SOURCE_DATA
>>>> >>>> {0:1} >>>> +1 DEST<RECEIVING_SYSTEM_NAME >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#RECEIVING_SYSTEM_NAME
>>>> >>>> {0:1*} >>>> +1 DATE<TRANSMISSION_DATE >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TRANSMISSION_DATE
>>>> >>>> {0:1} >>>> +2 TIME<TIME_VALUE >>>> <
>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TIME_VALUE
>>>> >>>> {0:1}.... >>>> >>>> >>>> Regards, >>>> >>>> Bob Coret >>>> Coret Genealogie<http://genealogie.coret.org/> >>>>
>>>
>> >> -- >> Ron Savage >> http://savage.net.au/ >> Ph: 0421 920 622 >> >>
>
-- Ron Savage http://savage.net.au/ Ph: 0421 920 622
Subject: Re: [rt.cpan.org #86280] issue with TIME tag
Date: Wed, 26 Jun 2013 13:48:55 +1000
To: bug-Genealogy-Gedcom [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Bob OK. It's an error in the data, not the code. Consider these 2 data files: 0 HEAD 1 SOUR PLUS_GEN 2 VERS 0.2 2 NAME PlusGenealogie 2 CORP Coret Genealogie 3 WWW http://genealogie.coret.org/ 1 DATE 20 JUN 2013 2 TIME 16:04 0 TRLR 0 HEAD 1 SOUR PLUS_GEN 2 VERS 0.2 2 NAME PlusGenealogie 2 CORP Coret Genealogie 3 WWW http://genealogie.coret.org/ 2 DATA WieWasWie 3 DATE 20 JUN 2013 0 TRLR They are both correct. Case 1: If you have a 1 DATE, then you /can/ have a 2 TIME. Case 2: The standard says that if you have a 2 DATA, then you can have a 3 DATE but you /cannot/ have a 4 TIME. You are getting confused over the 2 different types of dates. One take a time and one does not. On 22/06/13 10:02, ron@savage.net.au via RT wrote: Show quoted text
> Queue: Genealogy-Gedcom > Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> > > Hi Bob > > On 21/06/13 17:00, Bob Coret via RT wrote:
>> Queue: Genealogy-Gedcom >> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >> >> Hi Ron, >> >> I installed 0.82 yesterday (fresh machine) and royal.ged doesn't complain >> about TIME.
> > OK. >
>> I've narrowed the issue down to the "2 DATA" line. When I remove this line >> (which is a valid line), then there's no issue with TIME. >> >> 0 HEAD >> 1 SOUR PLUS_GEN >> 2 VERS 0.2 >> 2 NAME PlusGenealogie >> 2 CORP Coret Genealogie >> 3 WWW http://genealogie.coret.org/ >> ** 2 DATA WieWasWie ** >> 1 DATE 20 JUN 2013 >> 2 TIME 17:13 >> >> I guess the lexer thinks it's an HEAD> SOUR> DATA> DATE >> (tag_publication_date) but it's really HEAD> SOUR> DATE >> (tag_transission_date).
> > This is important info, but wouldn't it be:
> HEAD> DATE going by their levels of 0> 1?
> > Either way, I have a target for investigations. > > $many $thanx; > >
>> Bob >> >> >> >> mvg, >> >> Bob Coret >> >> >> On Fri, Jun 21, 2013 at 1:23 AM, ron@savage.net.au via RT< >> bug-Genealogy-Gedcom@rt.cpan.org> wrote: >>
>>> <URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >>> >>> Hi Bob >>> >>> No problem here using V 0.82. >>> >>> Data: >>> 0 HEAD >>> 1 SOUR PLUS_GEN >>> 2 VERS 0.2 >>> 2 NAME PlusGenealogie >>> 2 CORP Coret Genealogie >>> 3 WWW http://genealogie.coret.org/ >>> 1 DATE 20 JUN 2013 >>> 2 TIME 16:04 >>> 0 TRLR >>> >>> Log: >>> ron@zigzag:~/perl.modules/Genealogy-Gedcom$ perl -Ilib scripts/lex.pl -i >>> data/sample.5.ged -s 1 -maxlevel debug >>> tag_lineage(1, '0 HEAD') >>> tag_header(1, '0 HEAD') >>> tag_approved_system_id(2, '1 SOUR PLUS_GEN') >>> tag_version_number(3, '2 VERS 0.2') >>> tag_name_of_product(4, '2 NAME PlusGenealogie') >>> tag_name_of_business(5, '2 CORP Coret Genealogie') >>> tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') >>> tag_transmission_date(7, '1 DATE 20 JUN 2013') >>> tag_time_value(8, '2 TIME 16:04') >>> tag_trailer(10, '0 TRLR') >>> >>> Notice that your output says: >>> >>> tag_publication_date(8, '1 DATE 20 JUN 2013') >>> tag_trailer(9, '2 TIME 16:04') >>> >>> whereas mine says: >>> >>> tag_transmission_date(7, '1 DATE 20 JUN 2013') >>> tag_time_value(8, '2 TIME 16:04') >>> tag_trailer(10, '0 TRLR') >>> >>> I suggest you (re-)install V 0.82, run using the same test data as I >>> used above, and see what happens. >>> >>> On 21/06/13 08:48, ron@savage.net.au via RT wrote:
>>>> Queue: Genealogy-Gedcom >>>> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >>>> >>>> Hi Bob >>>> >>>> Hmmm. The code has time-handling in it. The test data file (royal.ged) >>>> even has a time in it. But my other test data does not. I'll have to >>>> investigate. >>>> >>>> On 21/06/13 00:21, Bob Coret via RT wrote:
>>>>> Thu Jun 20 10:21:31 2013: Request 86280 was acted upon. >>>>> Transaction: Ticket created by bob.coret@gmail.com >>>>> Queue: Genealogy-Gedcom >>>>> Subject: issue with TIME tag >>>>> Broken in: (no value) >>>>> Severity: (no value) >>>>> Owner: Nobody >>>>> Requestors: bob.coret@gmail.com >>>>> Status: new >>>>> Ticket<URL: https://rt.cpan.org/Ticket/Display.html?id=86280> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> I'm using the Genalogy-Gedcom-Lexer (v.0.8.2) to validate GEDCOM's I >>>>> produce. >>>>> >>>>> The validation incorrectly warns me about "The unknown tag TIME was >>>>> detected". >>>>> >>>>> Partial GEDCOM: >>>>> >>>>> 0 HEAD >>>>> 1 SOUR PLUS_GEN >>>>> 2 VERS 0.2 >>>>> 2 NAME PlusGenealogie >>>>> 2 CORP Coret Genealogie >>>>> 3 WWW http://genealogie.coret.org/ >>>>> 1 DATE 20 JUN 2013 >>>>> 2 TIME 16:04 >>>>> >>>>> Debug log: >>>>> >>>>> tag_lineage(1, '0 HEAD') >>>>> tag_header(1, '0 HEAD') >>>>> tag_approved_system_id(2, '1 SOUR PLUS_GEN') >>>>> tag_version_number(3, '2 VERS 0.2') >>>>> tag_name_of_product(4, '2 NAME PlusGenealogie') >>>>> tag_name_of_business(5, '2 CORP Coret Genealogie') >>>>> tag_address_web_page(6, '3 WWW http://genealogie.coret.org/') >>>>> tag_publication_date(8, '1 DATE 20 JUN 2013') >>>>> tag_trailer(9, '2 TIME 16:04') >>>>> Line: 9. The unknown tag TIME was detected >>>>> >>>>> GEDCOM 5.5 spec (same for 5.5.1): >>>>> >>>>> *HEADER:* = >>>>> >>>>> n HEAD {1:1} >>>>> +1 SOUR<APPROVED_SYSTEM_ID >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#APPROVED_SYSTEM_ID
>>>>> >>>>> {1:1} >>>>> +2 VERS<VERSION_NUMBER >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#VERSION_NUMBER
>>>>> >>>>> {0:1} >>>>> +2 NAME<NAME_OF_PRODUCT >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_PRODUCT
>>>>> >>>>> {0:1} >>>>> +2 CORP<NAME_OF_BUSINESS >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_BUSINESS
>>>>> >>>>> {0:1} >>>>> +3<<ADDRESS_STRUCTURE >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#ADDRESS_STRUCTURE
>>>>>>
>>>>> {0:1} >>>>> +2 DATA<NAME_OF_SOURCE_DATA >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NAME_OF_SOURCE_DATA
>>>>> >>>>> {0:1} >>>>> +3 DATE<PUBLICATION_DATE >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#PUBLICATION_DATE
>>>>> >>>>> {0:1} >>>>> +3 COPR<COPYRIGHT_SOURCE_DATA >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#COPYRIGHT_SOURCE_DATA
>>>>> >>>>> {0:1} >>>>> +1 DEST<RECEIVING_SYSTEM_NAME >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#RECEIVING_SYSTEM_NAME
>>>>> >>>>> {0:1*} >>>>> +1 DATE<TRANSMISSION_DATE >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TRANSMISSION_DATE
>>>>> >>>>> {0:1} >>>>> +2 TIME<TIME_VALUE >>>>> <
>>> http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#TIME_VALUE
>>>>> >>>>> {0:1}.... >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Bob Coret >>>>> Coret Genealogie<http://genealogie.coret.org/> >>>>>
>>>>
>>> >>> -- >>> Ron Savage >>> http://savage.net.au/ >>> Ph: 0421 920 622 >>> >>>
>>
>
-- Ron Savage http://savage.net.au/ Ph: 0421 920 622
As explained in the previous email, the user's data is defective. So, I'm rejecting this bug.