Re: to do list.

Dave Pawson <[email protected]> Sun, 18 Jan 2004 08:17:33 +0000
Newsgroups gmane.text.docbook.docbook2x.general
Message-ID <[email protected]>
At 19:23 17/01/2004, Steve Cheng wrote:

> > <xsl:strip-space elements="*"/>
>
>Unfortunately that is not enough:        for       example      this    text,
>         or when the XML source is indented
>         like this.
>
>Even spaces _within_ other text must be collapsed:
>
>"  Ordinarily, TeX collapses multiple whitespace characters (space, tab,
>and newline) into a single space.  Info output, on the other hand,
>preserves whitespace as you type it, except for changing a newline into
>a space; this is why it is important to put two spaces at the end of
>sentences in Texinfo documents."


So a translate would do it then Steve, since its just one character.
Otherwise
http://www.dpawson.co.uk/xsl/sect2/N7240.html#d1279e337 would suffice


> > Does the perl do line breaking at 70 chars etc?
> >   Is that what you mean by beautify?
> > http://www.dpawson.co.uk/xsl/sect2/N7240.html#d1279e244
> >   shows an xslt solution
>
>Alright, but this isn't strictly required. makeinfo will do line-wrapping for
>us, actually.  (For Latin-based text, anyway.)

Ok, its there as an option.


> > >All of them, and certain characters are not allowed in node names.
> > >(Being XML people we all see this as being stupid, but there's nothing we
> > >can do about it.)
> >
> > Which brings up xslt 2.0 again? The charmap?
> > Or is it something a translate() could do?
>Yes, you can use translate() for this one.


Thanks for the info Steve.
   If I can help please let me know.
regards DaveP




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn