This is the mail archive of the docbook@lists.oasis-open.org mailing list for the DocBook project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [docbook] Parameter entities in XML (DocBook Website) and browser'sinability to recognize their references!


In the NEW version of the website, which is NOT still published:

1. Parameter entities are defined, in order to have only one repository for all entity references.
2. Relative paths are replaced with absolute URIs on the network.
3. XML catalogs are utilized to manage DTD and XSL references in build process.


The error that stopped you in the first step of viewing the XML source in the online version is already fixed, since the second modification above is done.

Using the old style of olinks that rely on system entities is not the problem now, since the value of "targetdocent" attribute is resolvable by the browser, even with parameter entities.

The problems are entity references. For instance, when we use &acro.xml; instead of XML or <acronym>XML</acronym>. The browsers* are not able to resolve such entity references that begin with the ampersand and end with a semicolon.

*. Internet Explorer 6.0 resolves and replaces the values of entity references properly and eventually views the XML source.

In the meantime, I remain sincerely yours.

Sina

Bob Stayton wrote:

I'm not sure I understand the problem.
When I click on the "XML Source" link on one of those
pages, I get an error that it cannot find the DTD.
When I right-click and same the XML content, I
see the DOCTYPE declaration uses a relative
path that doesn't resolve to a location in your
document root.  But that is a DTD problem, not
a parameter entity problem.

I looked at the XML file, and I see you are declaring
a system entity (not parameter entity) in the DOCTYPE.
You refer to the system entity using the old
style of olinks that rely on system entities.  If that is the
only reason you use such system entities, then the new
style of olinks that are resolved by the XSL stylesheet
will let you eliminate those system entities.  That may
solve that part of the problem.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net


----- Original Message ----- From: "Sina K. Heshmati" <she@khakbaz.com>
To: <docbook@lists.oasis-open.org>; "Javad K. Heshmati" <jhe@dixite.com>
Sent: Thursday, December 25, 2003 3:13 PM
Subject: [docbook] Parameter entities in XML (DocBook Website) and browser's
inability to recognize their references!





Dear Bon Stayton,

A website is put together by Javad Heshmati
(http://www.khakbaz.com/javad), using the DocBook Website DTD and XSL,
Apache Ant, etc. In the latest version, which is not still released, my
task as a contributor was to define parameter entities and store all
entities in a repository that derives separate files containing olink
and acronym references--among other things.

I did as I explained and built the website. It works fine, except the
XML sources, which are not viewable, anymore. When the visitors happen
to click on the XML source link, an error occurs because the entity
references are not recognizable by the browser. It can't trace the
entity path by nature. In fact, they can view the source of the error
handled page and that's what they need, but it's not probably pleasant
for them to do so.

I was wondering if I could process my XML sources, before putting them
in evidence. By all means, a processor that can replace the required
entities. For instance, the Apache Ant can handle it, can't it?

Have you already had the similar experience to use parameter entities in
order for all entity references to be stored separately and show the XML
source on a browser at the same time? Although, the XML source of
DocBook documents (a book, for example), does not necessarily need to be
shown, unless it's within an archive. If yes, you've doubtlessly
influenced your XML documents before publishing them. But how? If no,
what do you recommend me to do, to keep my entities in a repository and
have a valid XML? (from browser's viewpoint, because in the new version,
they have all been verified to comply with DocBook Website).

I've read the relevant sections in "DocBook XSL: The Complete Guide" and
found the method that you've proposed to manage olinks (Linking between
pages) matching my case. Is that really, what I need?

In the meantime, I would like to thank you for the decency you shown me
in the preceding problem solving.

Sincerely yours,
Sina

----------------------------------------
Tools utilized along with their versions
----------------------------------------
Platform: Redhat Linux 8.0
DocBook Website: 2.5
Build Tool: Ant 1.5.4
Web Browser: Mozilla 1.5, 1.2.1
Java: j2se 1.4
XSLT Processor: Saxon 7.8
Version Management: CVS 1.11.2-8
----------------------------------------



To unsubscribe from this list, send a post to


docbook-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.










To unsubscribe from this list, send a post to docbook-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]