Re: rarr; in DnI documentation

2004-10-26 Thread Simon Pepping
Clay,

Sorry for not answering earlier. I have a couple of other things to do
these weeks.

On Thu, Oct 21, 2004 at 02:25:12PM -0700, Clay Leeds wrote:
 I'd also like to resolve the error in Forrest if possible, so the rest 
 of this POST deals with that.
 
 I suspect the problem is related to the fact that properties.xml 
 references a dtd like this:
 
 !--
 !DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.2//EN
  docbookx.dtd
 --
 
 A couple of things I note here:
 1. It's commented out

It is commented out so it should not have any influence. It is there
so that I can uncomment and use it during editing.

 2. this is a relative/local link, but the 'docbookx.dtd' is not local
(I also tried 
 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd' and
'http://www.oasis-open.org/docbook/xml/4.2/' and as expected neither 
 works.)

Because it is only used during editing I have not bothered to make it
absolute. The file book.xml has an absolute path for the DTD, and that
is the one that matters.

 3. fwiw, iso-num.ent is at
http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent

The dtd that one uses, should have correct relative links to the
entities files. In that way they are loaded without anyone having to
bother about them.

 I'm not very 'up' on DocBook, so this may be how it's 'supposed' to 
 work. Nevertheless, rarr; is the only thing in 'properties.xml' that 
 doesn't validate during the /forrest/ run (unless I replace rarr; with 
 #8594; or #x2192;).

Once the document and the stylesheets have been written, nothing is
very docbook specific. Only correct absolute paths or good catalogs
matter at that stage. Nevertheless, docbook is a very complex DTD that
uses the whole DTD machinery. I am glad it works.

Regards, Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl



Re: rarr; in DnI documentation

2004-10-21 Thread Simon Pepping
Clay,

I am a bit surprised. The docbook dtd clearly defines the entity
rarr; in iso-num.ent:
!ENTITY rarr   #x2192; !-- RIGHTWARDS DOUBLE ARROW --
Why does not the forrest build see this? Does it not read the DTD?

I do not like character entities in decimal numbers. I can never
figure out what they refer to. IMO character codes should be given in
hexadecimal notation; all Unicode documentation uses this. Then it
becomes #x2192; as shown above.

Regards, Simon

On Tue, Oct 19, 2004 at 11:57:00AM -0700, Clay Leeds wrote:
 Simon,
 
 One of the characters in your documentation is causing problems in the 
 Forrest build process.
 
 I'd like to swap the rarr; (amp;rarr;) characters with either 'gt;' 
 (amp;gt;) or '--gt;' (--amp;gt;)?
 
 Or... after some looking I found the rarr; numeric entity: #8594; 
 [amp;#8594;].  I found the rarr; in a bunch of places but the numeric 
 entity took a while...
 
 xml-fop/src/documentation/content/xdocs/DnI/properties.xml Lines 
 2243-2248:
 
 listitem
   
 paraliteralpcBase.getDimension/literal;
 dimension: type of integer, int rarr; 0, length rarr; 1; used by
 literalPercentBase/literal and literalNumericProperty/literal;
 literalLengthBase/literal has a dimension of 1/para
 /listitem
 
 Do you have any objections to this change?
 
 listitem
   
 paraliteralpcBase.getDimension/literal;
 dimension: type of integer, int #8594; 0, length #8594; 1; used by
 literalPercentBase/literal and literalNumericProperty/literal;
 literalLengthBase/literal has a dimension of 1/para
 /listitem
 
 Thanks!
 
 Web Maestro Clay
 -- 
 Clay Leeds - [EMAIL PROTECTED]
 Webmaster/Developer - Medata, Inc. - http://www.medata.com/
 PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
 

-- 
Simon Pepping
home page: http://www.leverkruid.nl



Re: rarr; in DnI documentation

2004-10-21 Thread Clay Leeds
On Oct 20, 2004, at 11:32 AM, Simon Pepping wrote:
Clay,
I am a bit surprised. The docbook dtd clearly defines the entity
rarr; in iso-num.ent:
!ENTITY rarr   #x2192; !-- RIGHTWARDS DOUBLE ARROW --
Why does not the forrest build see this? Does it not read the DTD?
I do not like character entities in decimal numbers. I can never
figure out what they refer to. IMO character codes should be given in
hexadecimal notation; all Unicode documentation uses this. Then it
becomes #x2192; as shown above.
Regards, Simon
Changing rarr; to #x2192; is an acceptable solution. The xml-fop 
/forrest/ build does not error out when it tries to validate 
'properties.xml'. I made the change and checked it in.

I'd also like to resolve the error in Forrest if possible, so the rest 
of this POST deals with that.

I suspect the problem is related to the fact that properties.xml 
references a dtd like this:

!--
!DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.2//EN
 docbookx.dtd
--
A couple of things I note here:
1. It's commented out
2. this is a relative/local link, but the 'docbookx.dtd' is not local
   (I also tried 
'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd' and
   'http://www.oasis-open.org/docbook/xml/4.2/' and as expected neither 
works.)
3. fwiw, iso-num.ent is at
   http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent

I'm not very 'up' on DocBook, so this may be how it's 'supposed' to 
work. Nevertheless, rarr; is the only thing in 'properties.xml' that 
doesn't validate during the /forrest/ run (unless I replace rarr; with 
#8594; or #x2192;).

Web Maestro Clay
--
Clay Leeds - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


Re: rarr; in DnI documentation

2004-10-19 Thread J.Pietschmann
Clay Leeds wrote:
I found the rarr; in a bunch of places but the numeric 
entity took a while...
Bookmark this:
 http://www.w3.org/TR/html4/sgml/entities.html
Ctrl-F and type in the entity name, the decimal or the hex
numbers.
For completeness bookmark
 http://www.unicode.org/charts/charindex.html
J.Pietschmann


Re: rarr; in DnI documentation

2004-10-19 Thread Clay Leeds
On Oct 19, 2004, at 12:50 PM, J.Pietschmann wrote:
Bookmark this:
 http://www.w3.org/TR/html4/sgml/entities.html
Ctrl-F and type in the entity name, the decimal or the hex
numbers.
For completeness bookmark
 http://www.unicode.org/charts/charindex.html
J.Pietschmann
Thanks! Might as well get it from the horse's mouth! Of course I've 
always found specs to be such a pain to read. I guess that's where this 
comes in handy:

AListApart.com's How to Read W3C Specs
http://www.alistapart.com/articles/readspec/
After I am able to run forrest and get a BUILD SUCCESSFUL, I'll be 
adding those links to the FOP Resources page... :-p

Web Maestro Clay
--
Clay Leeds - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc