Re: DOCBOOK-APPS: indexing for print with DSSSL / OpenJade / JadeTex
Deborah Greenberg Lidl writes: - What do I need to do to make entries that reference zones show a page number in the printed index? tell me precisely what it has in the .tex file at the point where the page number should be printed sebastian -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: A perspective on DocBook and DSSSL
Richard Sharpe writes: I have managed to get DocBook/DSSSL to do a lot of the things I want, and wonder if XSLT or other approaches will be better for me? ... I have separate title pages for each chapter/section with a black block with a white section number on it, with branding graphics on the front page of each section. easy enough I have a separate title page for the book, with everything starting on the correct pages. ditto I have headers and footers with underbars and over bars mostly working, with different footers on recto and verso pages so that you can read the string across the spine of book when it is layed open. most XSL FO implementations will do this OK I have problems in the headers and footers which appear to be related to TeX/JadeTeX interactions. Sometimes they just do funny things. :-} I want to use multiple columns or tables on title pages so I can align graphics and text with each other. thats going to be amusing with DSSSL or XSL FO I do not understand yet how to maintain version numbers of documents automatically? surely not a DSSSL or FO issue? So, I wonder if I can do all this easily with XSL? in theory I also wonder what the learning curve is? if you grok DSSSL, its easy sebastian -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Jadetex - Page numbers: Roman, Arabic - Confused
looks like a fair diagnosis of me not doing the whole job in jadetex
of page number formatting. i plead guilty. expect jadetex 3.7 shortly.
does
\def\insertPageNumber#1{#1%
\csname PageNumbering@\PageNumberFormat\endcsname\c@page}
do what you expect?
sebastian
--
To unsubscribe from this elist send a message with the single word
unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Aaargh, text with {...} causes pdfjadetex to blow up...
Here is what OpenJade produces by the way of TeX:
{1}\def\KeepWithNext%
{1}}\{str1,str2 ...\}\def\HeadingText{%
\str1,str2 ...\}%
\endHeadPar{}\endNode{}\Node%
I have not tested this, but look at the code in TeXFotBuilder.cxx
for
void TeXFOTBuilder::characters(const Char *s, size_t n)
see where it says
case '\\':
case '^':
case '_':
case '~':
os() \\char int(*s) {};
add in '{' and '}' here, and delete them from their place later in the
case statement. I would expect that to work.
this is also the place to fix the problem of -- and . I would
very strongly urge someone involved in OpenJade to look at this, and
the patches on http://indev.insu.com/openjade/, and see if we can get
a new clean unified TeXFOTBuilder out there for all to use. You are
the most active, Richard, I'd be really pleased if you could push this
forward.
Sebastian
--
To unsubscribe from this elist send a message with the single word
unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Examples
On Fri, Apr 20, 2001 at 02:59:12PM +0200, KRUMPOLEC Martin wrote: Please can you point me to some more complex DocBook examples e.g. for open source software ? All the FreeBSD documentation is in DocBook. See a list of the docs at http://www.freebsd.org/docs.html You can see the source in CVS using http://www.freebsd.org/cgi/cvsweb.cgi/doc/ or any of the methods listed to access the CVS repository listed at http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/synching.html The contents of http://www.freebsd.org/doc/en_US.ISO_8859-1/books/fdp-primer/ should also be very useful to you (in particular, section 4.2). N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery PGP signature
DOCBOOK-APPS: Re: DOCBOOK: Including a DocBook document in a DocBookdocument
This thread is from the Docbook mailing list, but my follow-up question is taking it in a direction more appropriate for Docbook-apps, so I'm posting it here. Suppose you are working on a book with chapters that are file entities in a master book file. You can use wrappers, as Jirka explains, to validate or process the individual chapters, but to edit one of those chapters with the help that tools like emacs and XMetaL provide, you have to add the doctype from the containing document, do your editing, and then remember to delete it before saving. Is there a way around this? For example, is there a way to let emacs or XMetaL know that a document gets its document type declaration from another document? Thanks, David -- Rune Enggaard Jensen wrote: We are a number of people working on a large document, written using a customazition of DocBook XML 4.1.2. We would like parts of this document to be printable af separate documents. We would like a construction like this: Chap1: !DOCTYPE chapter PUBLIC ... chapter . . /chapter Is there any way we can get this to work? Omit !DOCTYPE from individual chapters and create small wrapper, which will include just one chapter you want to process separately: !DOCTYPE book ... [ !ENTITY chapn SYSTEM chapn.xml ] book chapn; /book Now you can process single chapter by using this file. - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Re: DOCBOOK: Including a DocBook document in aDocBook document
On Sun, Apr 22, 2001 at 06:25:32PM -0500, David Cramer wrote: Is there a way around this? For example, is there a way to let emacs or XMetaL know that a document gets its document type declaration from another document? Put this at the end of the file: !-- Local Variables: -- !-- sgml-parent-document: toplevel.sgml -- !-- End: -- Tim. */ PGP signature
DOCBOOK-APPS: Different margins for recto and verso pages forbinding/spine
Hi, Has anyone been able to use different margins for recto and verso pages so that you can account for the binding of a document? Regards --- Richard Sharpe, [EMAIL PROTECTED] Samba (Team member, www.samba.org), Ethereal (Team member, www.ethereal.com) Contributing author, SAMS Teach Yourself Samba in 24 Hours Author, Special Edition, Using Samba -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Re: DOCBOOK: Including a DocBook document in aDocBook document
DC == David Cramer [EMAIL PROTECTED] writes: DC Suppose you are working on a book with chapters that are file DC entities in a master book file. You can use wrappers, as Jirka DC explains, to validate or process the individual chapters, but to DC edit one of those chapters with the help that tools like emacs DC and XMetaL provide, you have to add the doctype from the DC containing document, do your editing, and then remember to DC delete it before saving. DC Is there a way around this? For example, is there a way to let DC emacs or XMetaL know that a document gets its document type DC declaration from another document? I use the following approach: All my subdocuments contain their *own* DOCTYPE declaration. I include them in the main document via a system entity referring to them with a *special file extension* (e.g. .sgm instead of .sgml). I've got a makefile that generates the .sgm form of the subdocuments with sgmlnorm: sgmlnorm -wno-idref -iDOC.INCLUDE subdocument.sgml subdocument.sgm Then I can process both the main document and a single sub-document simply with `make thedocument.ps' and there is no need for special wrappers and/or changes in the documents. Milan Zamazal -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
RE: DOCBOOK-APPS: sgml-parent-document
I did have the local variables in the entity documents but I had it at the _start_ of the files. Of course it would work when I created the file because the start of the file is also the end of the file without any content present. Once content was created it would not work anymore. Thanks for the help. -Original Message- From: Mark Johnson [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 21, 2001 12:57 AM To: Kunath, Marcel Cc: [EMAIL PROTECTED] Subject: Re: DOCBOOK-APPS: sgml-parent-document Kunath, Marcel writes: I write a master file in NTEmacs with linking to sub content... and open one of the sub content files and it errors on me: External entity CHAPTER not found Marcel, Put the local variables statement in the *entity* document(s), not in the parent doc file. In your case, you could put something like: !-- Keep this comment at the end of the file Local Variables: sgml-parent-document: (index.sgml Book chapter) End: -- at the end of your chapter file named ar.sgml, like so: chapter id=ar titletitle/title paratext/para ... /chapter !-- Keep this comment at the end of the file Local Variables: sgml-parent-document: (index.sgml Book chapter) End: -- The pattern that works for me is: *ml-parent-document: (parent-filename top-element-of-parent-file top-element-of-current-file) (I never use the optional 4th has-seen-element entry.) Hope that helps, Mark _ Mark Johnson Senior Lecturing Fellow 111 Physics Bldg., Box 90305 Department of Physics Duke University Durham, NC 27708-0305 (919) 660-2504 Fax: (919) 660-2525 -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED] -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Examples
Martin, Please can you point me to some more complex DocBook examples e.g. for open source software ? Our (e-smith) user manual (done as a DocBook 'book) is available in DocBook SGML as well as HTML and PDF at: http://www.e-smith.org/docs/manual/ We have several HOWTO documents available with the DocBook SGML source (as a DocBook 'article') at: http://www.e-smith.org/docs/howto/ Also, the Linux Documentation Project makes available DocBook SGML versions of most all of the HOWTO docs: http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/docbook/ http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/other-formats/docbook/ (some LDP HOWTO docs are still in the older LinuxDoc SGML format and therefore do not (yet) have a DocBook version.) The LDP also has some much longer and more complex documents available that are guides and can be found on this page: http://www.linuxdoc.org/guides.html Most of them have a link for other formats that include DocBook SGML or XML. Hope this helps, Dan -- Dan York, Director of Training[EMAIL PROTECTED] Ph: +1-613-751-4401 Mobile: +1-613-263-4312 Fax: +1-613-564-7739 e-smith, inc. 150 Metcalfe St., Suite 1500, Ottawa,ON K2P 1P1 Canada http://www.e-smith.com/open source, open mind -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: DocBook DSSSL FAQ
Michael, Anybody who wants to contribute to the FAQ or has suggestions how to do it in another way, is invited to contact me privately or discuss it on this list. FYI, I'll be glad to contribute to the FAQ and I'll send you some comments privately based on some of the problems I've been through lately. But in any case I would recommend you to switch DocBook qandaset way of doing FAQs. DocBook is able to markup FAQs and both DSSSL and XSL stylesheets supports this markup. It is like promoting BMW car sitting in Volkswagen. Jirka, good idea and it's great to see that this is supported in the stylesheets. I have thought for sometime of modifying makefaq to support the DocBook qandaset, but it's overkill for what I needed for the FAQs I was maintaining and that others are using. And since openjade/jade support it, there's little reason for me to do. Still, it might be something I add at some point, purely for the exercise of working with XML in python. Regards, Dan -- Dan York, Director of Training[EMAIL PROTECTED] Ph: +1-613-751-4401 Mobile: +1-613-263-4312 Fax: +1-613-564-7739 e-smith, inc. 150 Metcalfe St., Suite 1500, Ottawa,ON K2P 1P1 Canada http://www.e-smith.com/open source, open mind -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Examples
Hi! I would like to add to this list: The PostgreSQL manual which comes with the PostgreSQL 7.1 source code. The source is available from http://www.postgresql.org (or one of the mirrors). I consider it valuable since it consists of a set of books, thus giving you an example of how to create a large piece of documentation. It also contains a reference manual showing you how to mark up Unix-style man pages using DocBook. In addition, the doc subdirectory of FreeBSD is a very good resource for larger books marked up using DocBook. You can obtain it using anonymous CVS access. See http://www.freebsd.org for details. Greetings, Holger -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
RE: DOCBOOK-APPS: Examples
Hi folks, Thank you all for references to DocBook examples, I'll take a look at them and maybe learn from them :-) Martin -- Martin Krumpolec [EMAIL PROTECTED] -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Re: DOCBOOK: Including a DocBook document in aDocBookdocument
David Cramer wrote: Suppose you are working on a book with chapters that are file entities in a master book file. You can use wrappers, as Jirka explains, to validate or process the individual chapters, but to edit one of those chapters with the help that tools like emacs and XMetaL provide, you have to add the doctype from the containing document, do your editing, and then remember to delete it before saving. Is there a way around this? For example, is there a way to let emacs or XMetaL know that a document gets its document type declaration from another document? Emacs solution was already posted here. In XMetaL you can open main document. Each referenced entity is displayed as small box with entity name on it. If you double-click on the box, referenced entity is open in a new window and you can edit it in the same way as full-fledged XML/SGML document. - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
DOCBOOK-APPS: qandaentry/question id
Carsten Wartmann pointed me to a problem in the generated HTML version of the DocBook DSSSL FAQ: All links for questions were pointing to #.QQ because of missing id's for every question. After supplying every question with a 'id' attribute the links are correct (pointing e.g. to '#H1'). Is there a more or less automatic procedure to generate the id's instead of doing this by hand? Michael -- [EMAIL PROTECTED] http://www.miwie.org [EMAIL PROTECTED] -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: qandaentry/question id
Michael Wiedmann wrote: All links for questions were pointing to #.QQ because of missing id's for every question. After supplying every question with a 'id' attribute the links are correct (pointing e.g. to '#H1'). Is there a more or less automatic procedure to generate the id's instead of doing this by hand? XSL stylesheet generates missing IDs automaticaly. - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
Re: DOCBOOK-APPS: Aaargh, text with {...} causes pdfjadetex to blow up...
At 08:38 PM 4/22/01 +0100, Sebastian Rahtz wrote:
[Sebastian's coding suggestions deleted in the interests of brevity ... ]
OK, I have a simple fix for the moment ...
Run sed over the .tex output and convert all to {} and all to {}
and it works ...
Regards
---
Richard Sharpe, [EMAIL PROTECTED]
Samba (Team member, www.samba.org), Ethereal (Team member, www.ethereal.com)
Contributing author, SAMS Teach Yourself Samba in 24 Hours
Author, Special Edition, Using Samba
--
To unsubscribe from this elist send a message with the single word
unsubscribe in the body to: [EMAIL PROTECTED]
DOCBOOK-APPS: Solved problems with rules above footers ...
Hi, Well, I solved my problems with rules above the footers ... Blush, you need a 'lenght: some-length' in a (make rule ...) if you want the rule to reliably print. I don't know why, but JadeTex would print out the full hrule, even though Length was zero, or would print out two half rules or something, except when a table preceeded the bottom of the page. Regards --- Richard Sharpe, [EMAIL PROTECTED] Samba (Team member, www.samba.org), Ethereal (Team member, www.ethereal.com) Contributing author, SAMS Teach Yourself Samba in 24 Hours Author, Special Edition, Using Samba -- To unsubscribe from this elist send a message with the single word unsubscribe in the body to: [EMAIL PROTECTED]
