search

giellalt / bugzilla-dummy

0 stars 0 forks source link

corpus.dtd seems flawed (Bugzilla Bug 884) #216

Closed albbas closed 13 years ago

albbas commented 14 years ago

This issue was created automatically with bugzilla2github

Bugzilla Bug 884

Date: 2010-10-20T19:44:16+02:00 From: Trond Trosterud <> To: Ciprian Gerstenberger <> CC: ciprian.gerstenberger, sjur.n.moshagen, trond.trosterud

Last updated: 2011-05-04T20:32:55+02:00

albbas commented 14 years ago

Comment 3473

Date: 2010-10-20 19:44:16 +0200 From: Trond Trosterud <>

It turns up as error msg under corpus conversion.

xmllint (can that be used for dtd check?) says

~/gtsvn/gt/dtd$xmllint corpus.dtd corpus.dtd:7: parser error : StartTag: invalid element name <!ENTITY % common.att ' ^ corpus.dtd:7: parser error : Extra content at the end of the document <!ENTITY % common.att ' ^ ~/gt

albbas commented 13 years ago

Comment 3882

Date: 2011-04-22 17:23:17 +0200 From: Trond Trosterud <>

Obsolete.

albbas commented 13 years ago

Comment 3926

Date: 2011-04-26 09:03:03 +0200 From: Sjur Nørstebø Moshagen <>

It isn't obsolete. The DTD and the files should agree. Either it is fixed, or it is not. Reopened until confirmed or tested.

Don't close a bug before discussing it with the asignee or other stakeholders, or providing tests that documents that it has been fixed. Being old doesn't mean being irrelevant or obsolete.

albbas commented 13 years ago

Comment 4016

Date: 2011-05-02 19:04:30 +0200 From: Trond Trosterud <>

Quoting the svn log from a couple of weeks before easter:

dtd$svn log corpus.dtd

r41276 | boerre | 2011-04-05 18:14:29 +0200 (tir, 05 apr 2011) | 2 lines

Make this file valid according to xmllint

First: As earlier, xmllint reacts against the initial <! symbol string, since dtd is not xml, it declares xml.

We get: corpus.dtd:7: parser error : StartTag: invalid element name <!ENTITY % common.att ' ^

But this is a result you will get from running any dtd through xmllint: gt_dictionary.dtd:1: parser error : StartTag: invalid element name <!ELEMENT r (lics?, e+, xhtml:script?) > ^ So, my bug report should have been closed or changed already there.

But there are actually ways of validating dtd; this for example:

http://www.validome.org/grammar/validate/

and no doubt also other ways.

In any case, the corpus.dtd is valid (to repeat: copy content of corpus.dtd onto the webpage above), so please close this bug.

albbas commented 13 years ago

Comment 4055

Date: 2011-05-04 20:32:55 +0200 From: Ciprian Gerstenberger <>

(In reply to comment #3)

Quoting the svn log from a couple of weeks before easter:

dtd$svn log corpus.dtd

r41276 | boerre | 2011-04-05 18:14:29 +0200 (tir, 05 apr 2011) | 2 lines

Make this file valid according to xmllint

  • add a default value to each ATTLIST

First: As earlier, xmllint reacts against the initial <! symbol string, since dtd is not xml, it declares xml.

We get: corpus.dtd:7: parser error : StartTag: invalid element name <!ENTITY % common.att ' ^

But this is a result you will get from running any dtd through xmllint: gt_dictionary.dtd:1: parser error : StartTag: invalid element name <!ELEMENT r (lics?, e+, xhtml:script?) > ^ So, my bug report should have been closed or changed already there.

But there are actually ways of validating dtd; this for example:

http://www.validome.org/grammar/validate/

and no doubt also other ways.

In any case, the corpus.dtd is valid (to repeat: copy content of corpus.dtd onto the webpage above), so please close this bug.

Trond's comments are convincing.

Dein Wunsch ist mir Befehl, Trond! Bug closed!