-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was reviewing the entities in the current --- fedora-entities-en.ent. And noticed a rather peculiar behavior. One which I assume was expected to behave in a different fashion.
It has to do with: LEGALNOTICE-RELNOTES
Now I put this entity in my bookinfo/articleinfo element. Anyways, upon building the source, the xml processor is directed to generate a link labeled "Legal Notice". This in effect generates a seperate page entirely with the content of the LEGALNOTICE-RELNOTES entity and it is pointed to from this link. This page is entirely blank minus the content of the entity. No header or footer etc.... No good.
http://www.buddhalinux.com/images/snapshot5.png
I don't believe that this is the intended behavior. It is my assumption[yeah i know] that (like many other doc projects) that this entity was intended to be called from the abstract element of bookinfo/articleinfo. Personally, i think it provides a better reference to the licensing than a simple link. However, in order to do so. There must be a change to the content of the common file - --- legalnotice-relnotes-en.xml.
In essence, this file contains common elements like that of legalnotice-content-en.xml. A simple removal of the legalnotice element parent in legalnotice-relnotes-en.xml corrects the problem and the entities behave as is expected.
http://www.buddhalinux.com/images/snapshot4.png
I have generated a diff against the current cvs:
Index: docs-common/common/legalnotice-relnotes-en.xml =================================================================== RCS file: /cvs/docs/docs-common/common/legalnotice-relnotes-en.xml,v retrieving revision 1.2 diff -u -r1.2 legalnotice-relnotes-en.xml - --- docs-common/common/legalnotice-relnotes-en.xml 19 Jul 2005 20:41:03 -0000 1.2 +++ docs-common/common/legalnotice-relnotes-en.xml 29 Jul 2005 04:13:57 -0000 @@ -7,9 +7,7 @@
]> --> - -<legalnotice id="legalnotice"> - - <para> This document is released under the terms of the GNU Free Documentation +<para> This document is released under the terms of the GNU Free Documentation License. For more details, read the full legalnotice in <xref - - linkend="sn-legalnotice" />. - - </para> - -</legalnotice> + linkend="sn-legalnotice" />. +</para>
On Thu, 2005-07-28 at 11:26 -0500, Thomas Jones wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was reviewing the entities in the current --- fedora-entities-en.ent. And noticed a rather peculiar behavior. One which I assume was expected to behave in a different fashion.
It has to do with: LEGALNOTICE-RELNOTES
This entity is intended to be used for the release notes only, especially when printing no-chunks HTML. It's purpose is to leave the semantic <legalnotice> entity with meaningful content, but to move most of the text out of the way. Otherwise, in no-chunks output the legalnotice is predominant and distracting.
You want to use the traditional LEGALNOTICE, which calls in docs- common/common/legalnotice-en.xml. Within that file is called LEGALNOTICE-CONTENT. There is your actual license et al.
Now I put this entity in my bookinfo/articleinfo element. Anyways, upon building the source, the xml processor is directed to generate a link labeled "Legal Notice". This in effect generates a seperate page entirely with the content of the LEGALNOTICE-RELNOTES entity and it is pointed to from this link. This page is entirely blank minus the content of the entity. No header or footer etc.... No good.
When LEGALNOTICE-RELNOTES is used, the <legalnotice /> appears where the element may be used in DocBook. The content is minimal, and it points at a <section> that exists otherwise. In that <section>, the entity LEGALNOTICE-CONTENT is called in.
I should probably rename -RELNOTES to LEGALNOTICE-NOCHUNKS, as its main purpose is when doing a no-chunks HTML build.
hth - Karsten
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday 29 July 2005 02:36, Karsten Wade wrote:
When LEGALNOTICE-RELNOTES is used, the <legalnotice /> appears where the element may be used in DocBook. The content is minimal, and it points at a <section> that exists otherwise. In that <section>, the entity LEGALNOTICE-CONTENT is called in.
I should probably rename -RELNOTES to LEGALNOTICE-NOCHUNKS, as its main purpose is when doing a no-chunks HTML build.
hth - Karsten
Ugghhh. Assumptions.