AW: [docbook-apps] print customization without title page?

with the parameter would be a bonus feature to impress them :) . Regards, Martin -Ursprüngliche Nachricht- Von: Bob Stayton [mailto:[EMAIL PROTECTED] Gesendet: Montag, 30. Juni 2008 00:28 An: Schramm, Martin; docbook-apps@lists.oasis-open.org Betreff: Re: [docbook-apps] print

[docbook-apps] title properties for task / procedure ?

Dear list, for our documentation we use a lot of instructions. So far, we had used ordered lists with titles. But since I have discovered the task element, I think, that this suits our requirements much better. The only problem, I have now, is to adjust the font-size and font-style of the

[docbook-apps] print customization without title page?

Dear list, one of our projects has requested a feature, for which I could not find a solution and therefore ask for your support: My colleagues want to have one customization layer for displaying the whole documents content and another customization producing an FO/PDF output with a very

[docbook-apps] Avoid bridgeheads in running header?

Dear list, in our page layout we generate running headers with our XSL customization. In these headers the chapter and section titles are displayed. The settings look like the following: ... xsl:param name=marker.section.level2/xsl:param xsl:when test=$double.sided = 0 and

AW: [docbook-apps] Change error message in output for missing xinclude?

be even more effective. But we have no influence over it. Best wishes, Martin _ Von: Phil Borlin [mailto:[EMAIL PROTECTED] Gesendet: Montag, 15. Oktober 2007 19:10 An: Schramm, Martin Betreff: Re: [docbook-apps] Change error message in output for missing

[docbook-apps] Change error message in output for missing xinclude?

Dear list, I like to ask you for support in the following case: We have a DB mother document, which contains lots of xinclude references to other files. Many of these referenced files are generated by scripts (containing tables with test results). These generated files are written in valid

[docbook-apps] HTML output informaltable / no space-after?

We have a DocBook file with lots of informaltables, one after the other. When I transform it to HTML, there is no space after theses informaltables. This makes them look as if it was just a single, very long table. I have checked the xsl:attribute-set name=table.properties, but the entries are

[docbook-apps] Omit page break before chapter?

Dear List, we create a lot of documents, from which specific content is filtered out by XSLT filters (conditional text). So we get two versions of the same document: one with all the content and lots and lots of pages and another one, with just an overview - containing just the chapter title and a

[docbook-apps] List of RevHistories from referenced chapters?

Dear List, in our company we create a lot of mother documents (root element: book), which contain several referenced documents from various authors (root element: chapter, referenced by Xinclude). All these documents have revisions in their revision histories (bookinfo- or chapterinfo /

AW: [docbook-apps] FO problem: customizing section title to rule 1.1.1?

- Von: Mauritz Jeanson [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 28. Juli 2007 20:12 An: Schramm, Martin; docbook-apps@lists.oasis-open.org Betreff: RE: [docbook-apps] FO problem: customizing section title to rule 1.1.1? -Original Message- From: Schramm, Martin 1) How can I

AW: [docbook-apps] ulink to open in new window

Hi Sandra, I have had the same problem. In my example, it worked, when I inserted the attribute type=_blank to the ulink element. ulink type=_blank url=http://www.codingstandard.com/HICPPCM/index.html;HICPPCM/ulink Regards, Martin _ Von: Schaffer, Sandra [mailto:[EMAIL

[docbook-apps] FO problem: customizing section title to rule 1.1.1?

Dear list, we have started to write our new coding styles in DocBook. For this, we want to alter our XSLT Stylesheet Customization. On the third section level, all our rules will be listed und therefore should be marked as such with a title prefix Rule So could you help me with following

[docbook-apps] FO-Problem: Visible Hotlinks in FO/PDF?

Dear list, could you please give me a hint, how I could customize my XSL stylesheet in that way, that links, xrefs or ulinks will be presented as visible hotlinks in my FO/PDF output (e.g. underlined or blue colored). Our users usually read our documents as PDF versions on their screen. At the

AW: [docbook-apps] FO Problem: Chapter title without chapter 1: text

] FO Problem: Chapter title without chapter 1: text Hi Martin, Are you sure you have the right context? Maybe you could try l:context name=title (instead of l:context name=xref-number-and-title) and see if that helps. Ken On 6/14/07, Schramm, Martin [EMAIL PROTECTED] wrote: Dear list, some

WG: [docbook-apps] HTML- SVG problem: How to change HTML tags?

transformed by my customization. But this would make everything even more complicated. Best regards, Martin Von: Bob Stayton [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 8. März 2007 18:39 An: Schramm, Martin; docbook-apps@lists.oasis-open.org Betreff: Re: [docbook-apps] HTML- SVG problem