Page 1 of 1

Declared entities not being found in Oxygen 7

Posted: Tue Feb 07, 2006 7:42 am
by rhache
Hello everyone,

I just upgrade to Oxygen 7, and I was previously using version 5. I use Oxygen mainly for a personal Docbook project.

As soon as I upgraded to Oxygen 7, my referenced entities are showing up as errors, although I changed nothing in my files. I assume I need to change something in the program settings, but I'm a loss to exactly what.

Thanks,
Rene

Posted: Tue Feb 07, 2006 11:17 am
by sorin_ristache
Hello Rene,

The errors you are seeing when you open the document are marked by the validation-as-you-type feature introduced by version 7.0 of <oXygen/>. But the validation result is the same as for the Validate action available on the Document toolbar. You can disable the feature at any time from Options -> Preferences -> Editor / Document Checking -> Validate as you type.

If an entity reference is marked as validation error it is possible that the definition of the entity could not be found, for example because it was removed between running the <oXygen/> 5 and <oXygen/> 7 versions. In order to receive further help please specify the full error message and post a small sample file of the document with the validation errors, and if you created the entity yourself also post a sample of the entity definition file. If you did not create the entity file but you only refer to it in your document please specify the full path of the entity definition file.

Regards,
Sorin

Still not finding my DocBook entities

Posted: Thu Feb 09, 2006 9:13 am
by rhache
Sorin,

Thanks for your reply. Now, the entity errors could not have been affected by the installation, since the Docbook DTD that I was using was not the one that gets installed with oXygen.

All my entities are declared in the "dbgenent.mod" that comes with the DocBook DTD (which I believe is where you are supposed to put your custom entities). Other than that, I have not touched the DocBook DTD. And whether validation as you type is turned on or off makes no difference. I should point out that any validation I get doesn't work, not just validate as you type.

For all of my entities, the exact error message I get is the following:
The entity "entityname" was referenced, but not declared"

I don't really see the point of uploading a docbook file, since I would also have to upload the dbgenent.mod file with it. I tried creating a new file, referencing the same DTD, and created a simple entity in dbgenent.mod, and it didn't work. Still wasn't finding the entity.

The only thing that I think might be the problem is the "Custom Validation" tab in the program options, but I don't know what to do in there.

I should be clear that the only change that was made was in installing oXygen 7. Work fine a few minutes earlier when I was using version 5.

Thanks,
Rene

Re: Still not finding my DocBook entities

Posted: Thu Feb 09, 2006 12:17 pm
by sorin_ristache
Hello,
rhache wrote:All my entities are declared in the "dbgenent.mod" that comes with the DocBook DTD (which I believe is where you are supposed to put your custom entities). Other than that, I have not touched the DocBook DTD. And whether validation as you type is turned on or off makes no difference. I should point out that any validation I get doesn't work, not just validate as you type.

For all of my entities, the exact error message I get is the following:
The entity "entityname" was referenced, but not declared"
Look in the Information view (Perspective -> Show view -> Information) to see the full path of the schema used for validation. Usually the content of the Information view helps you in this kind of situation. Also if the schema references are resolved with an XML Catalog you should enable verbosity in Options -> Preferences -> XML / XML Catalog to see if any reference is resolved with a catalog. The default catalog predefined in <oXygen/> resolves Web references like http://www.docbook.org/xml/4.4/docbookx.dtd to the local copy of the DocBook DTD which comes with <oXygen/>. If you want to disable the default catalog go to Options -> Preferences -> XML / XML Catalog -> Use default catalog.
rhache wrote:The only thing that I think might be the problem is the "Custom Validation" tab in the program options, but I don't know what to do in there.
Custom Validation uses other validation engine than the Validate action and the validate as you type feature. If you get errors with Validate or validate as you type they are not connected to the configuration of a custom validation engine in the Preferences dialog.

Regards,
Sorin

Thanks

Posted: Thu Feb 09, 2006 7:17 pm
by rhache
Sorin,

The XML catalog did it! Thanks,

Rene