RE: [docbook-apps] How do I highlight inline text ?
Another thing to keep in mind is that DocBook already has a large
assortment (some people say too many, but others of us disagree) of
semantic elements available that describe many features of computers.
Before investing in time to create a new class of things by using a
role on emphasis, make sure that there is not already something
available in the elements provided by DocBook. Some of them have
numerous variations added through a class attribute (systemitem has
21 values enumerated for the class value). One of the values of a
semantic markup system is that there are already a number of semantic
bindings available in DocBook. You can customize the CSS style that
is associated with the semantic tags that are already available, too
(that's what the cascading part of cascading style sheet means) if
you want more or different formatting for the semantic you are trying
to represent (not all elements in DocBook have a unique format
associated with them).
You can also extend the class attributes if you pick up a little of
the RelaxNG grammar (there are lots of tutorials about it online).
In using DocBook for a number of years here, we have tended to use
tags like systemitem and add class values rather than using the
role on emphasis, reserving emphasis for the more generic concept of
This is important rather than for semantic bindings. Extending
things through role is simpler, but using class and other more
structured solutions provides better support for the authoring
process since syntax aware editors provide hints to the user for
enumerated values like class.
I think CSS is great fun and it has been well worth the time
invested in it to learn it (I spent an afternoon a few weeks ago
learning how to use DIV elements instead of tables for controlling
positions, which was quite a trip). I also have found the time spent
learning DocBook by referencing The Definitive Guide worthwhile.
There are a lot of elements available, and I don't pretend to know
all of them, but I always look at the table of contents, which lists
the elements, before I set out to extend it. I frequently find the
DocBook team has been there before me and that all I have to do is
tell the writers what element to use instead of inventing something.
Regards,
Larry Rowland
-Original Message-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Sunday, April 11, 2010 4:44 AM
To: Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?
On Sun, 11 Apr 2010 06:22:18 -0400
Robert Lucente rluce...@pipeline.com wrote:
a.. Create a cascading style sheet w/ a file name of key_words.css
w/ the following entry
.key_words { background: yellow; }
Nit picking, use semantic names for the attribute?
I may be wrong here.
[RL Start]
Nathalie Sequeira on April 07, 2010 5:31 PM recommended the following
emphasis role=semantic_function_of_the_emphasissome
text/emphasis
I thought that this was way cool. Then if I wanted to change the how
the semantic was displayed, just change the CSS.
Humm. What am I missing ?
[RL End]
I guessed that 'keyword' wasn't semantic. Was I wrong?
If it does identify a keyword in your xml markup, my apologies.
[RL Start]
I don't know anything about XSL. I will add it to the stuff to go
learn.
Is putting parameters in XSL just a best practice thing ?
I think so. puts all your 'styling' in one place?..
except it's two, one stylesheet importing another.
It makes sense. This way you have all your styling knobs in one spot
as opposed to 2 different spots.
Thanks for the help.
Welcome.
--
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Autodesk Web Help
honyk wrote: There is a navigation with well known buttons Contents/Index/Search/Favorities, but interesting is also the document window. There are small forward, back and top links with the appropriate tooltips as well as Show in content, Add to Favorities and Home links. In the header there is also clickable full logic path to the given page. Another feature I like is a tab approach. Division differs from page to page, here the content is divided into Concept/Procedure/Quick Reference sections. I think all this is generated using some sophisticated tool, but I can imagine to get the same output from my DocBook document. It's just matter of generating a little bit of fancy Javascript code. Also while in general I agree that result looks nice, some features are not general but tied to a specific content -- like this Concept/Procedure/QuickReference tabs for Autodesk. In fact for one customer who insisted on using DITA we have modeled those tabs as separated topics which were linked together using reltables. Similar functionality could be achieved by DocBook assemblies currently discussed in DocBook TC. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://www.kosek.cz -- Profesionální školení a poradenství v oblasti technologií XML. Podrobný přehled školení http://xmlguru.cz/skoleni/ -- Nejbližší termíny školení ** XSLT 19.-22.4. ** XSL-FO 18.-19.5. ** ** XSLT 2.0 9.6. ** Office Open XML 10.6. ** -- http://docbook.czStránky o dokumentačním formátu DocBook http://xmlguru.czBlog mostly about XML for English readers -- signature.asc Description: OpenPGP digital signature
[docbook-apps] XInclude quiestion
Hello Docbook-apps, I'm newby in docbook. I try to include some text file into docbook document using tag xi:include parse=text href=xmllint.txt/ and got an error: Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in section, but no template matches. What I am doing wrong? I am using Apache FOP under Windows to convert docbook into pdf. Marty. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Colored listings
Hello,
I want to get colored listings in docbook output, how I can get it?
Is there a simple way to make text colored, such tags
color color=dark_greenclass/color CMyClass { };
or there is more specialized tags such
cpp-keywordclass/cpp-keyword CMyClass { };
or there is another way to make listings colored?
Marty.
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] XInclude quiestion
Hi Marty, This section of Bob Stayton's indespensible book has lots of good information on xincludes: http://www.sagehill.net/docbookxsl/ModularDoc.html For your specific problem, this section in particular can show you what's necessary: http://www.sagehill.net/docbookxsl/ValidXinclude.html#XincludeDTD David -Original Message- From: Александр Мартынов [mailto:am...@mail.ru] Sent: Monday, April 12, 2010 12:24 PM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] XInclude quiestion Hello Docbook-apps, I'm newby in docbook. I try to include some text file into docbook document using tag xi:include parse=text href=xmllint.txt/ and got an error: Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in section, but no template matches. What I am doing wrong? I am using Apache FOP under Windows to convert docbook into pdf. Marty. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] XInclude quiestion
It sounds like the xincludes are being passed through to the DocBook transforms rather than being resolved before the processing is taking place. Take a look at Bob Stayton's write-up: http://www.sagehill.net/docbookxsl/Xinclude.html His reference on DocBook XSL is excellent. Regards, Larry Rowland -Original Message- From: Александр Мартынов [mailto:am...@mail.ru] Sent: Monday, April 12, 2010 11:24 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] XInclude quiestion Hello Docbook-apps, I'm newby in docbook. I try to include some text file into docbook document using tag xi:include parse=text href=xmllint.txt/ and got an error: Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in section, but no template matches. What I am doing wrong? I am using Apache FOP under Windows to convert docbook into pdf. Marty. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Colored listings
Marty,
Bob Statyton has a good discussion of program listings:
http://www.sagehill.net/docbookxsl/ProgramListings.html
There is a section on syntax highlighting (which differentiates among things
like keywords, constants, and parameters) at the bottom of the ToC on this page.
Regards,
Larry Rowland
-Original Message-
From: Александр Мартынов [mailto:am...@mail.ru]
Sent: Monday, April 12, 2010 11:40 AM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Colored listings
Hello,
I want to get colored listings in docbook output, how I can get it?
Is there a simple way to make text colored, such tags
color color=dark_greenclass/color CMyClass { };
or there is more specialized tags such
cpp-keywordclass/cpp-keyword CMyClass { };
or there is another way to make listings colored?
Marty.
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Autodesk Web Help
Hello, There is a navigation with well known buttons Contents/Index/Search/Favorities, but interesting is also the document window. There are small forward, back and top links with the appropriate tooltips as well as Show in content, Add to Favorities and Home links. In the header there is also clickable full logic path to the given page. It's just matter of generating a little bit of fancy Javascript code. Also while in general I agree that result looks nice, some features are not general but tied to a specific content -- like this Concept/Procedure/QuickReference tabs for Autodesk. yes, I agree that most of the job can be provided using decent CSS styles with a little Javascript code. The most challenging features are, from my POV, searching capabilities (index full-text search) and handling of Favourities. Autodesk uses in its products some solution from http://www.isys-search.com/ but I don't know if this has something to do with this help. In the open source world something like this could be sufficient: http://lucene.apache.org/solr/ but it requires Java container, hosting of which is more expensive than e.g. PHP. In HTML Help these features are already built-in what is, of course, reflected by Autodesk - in the page header there are suppressed Show in Content/Favorities/Home links. In fact for one customer who insisted on using DITA we have modeled those tabs as separated topics which were linked together using reltables. Similar functionality could be achieved by DocBook assemblies currently discussed in DocBook TC. Hmm, I've thought I would use subsections with the specified role attribute. Although this is not recommended, it would ensure backward compatibility. Till now I have no serious reason to abandon db v4.x. Regards, Jan PS: Nice to see there is GSoC project for this topic already ;-) - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] XInclude quiestion
Oops. Larry's right. Your problem is failing to resolve the xincludes before processing with the xsls. I didn't look at your error message closely and assumed it was one you got during validation. In any case, Bob's book does have all the answers :-) David -Original Message- From: David Cramer Sent: Monday, April 12, 2010 12:43 PM To: ? ; docbook-apps@lists.oasis-open.org Subject: RE: [docbook-apps] XInclude quiestion Hi Marty, This section of Bob Stayton's indespensible book has lots of good information on xincludes: http://www.sagehill.net/docbookxsl/ModularDoc.html For your specific problem, this section in particular can show you what's necessary: http://www.sagehill.net/docbookxsl/ValidXinclude.html#XincludeDTD David -Original Message- From: Александр Мартынов [mailto:am...@mail.ru] Sent: Monday, April 12, 2010 12:24 PM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] XInclude quiestion Hello Docbook-apps, I'm newby in docbook. I try to include some text file into docbook document using tag xi:include parse=text href=xmllint.txt/ and got an error: Element include in namespace 'http://www.w3.org/2001/XInclude' encountered in section, but no template matches. What I am doing wrong? I am using Apache FOP under Windows to convert docbook into pdf. Marty. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Testers wanted for Calenco V2
Hi all, after one year of intensive coding, I am glad to announce the availability of Calenco V2 RC1. Calenco is a Web based XML CCMS, with built-in support for DocBook V5. It allows you to: - Store and modify files (XML and images notably) through a WebDAV interface. - Show the tree of dependencies (XIncludes and images) - Store your XSL customization layers - Setup publications (PDF, HTML, RTF, PS, CHM) that are automatically rebuilt when content changes BTW this is Free Software, you can get it at https://sourceforge.net/projects/calenco/ There is also an online demonstration server available here: http://trac.calenco.com/wiki/CalencoV2Demo featuring a preliminary WYSIWYG editor. Looking forward for your feedback, Camille. attachment: camille.vcf- To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] How do I highlight inline text ?
... DocBook ... elements ...
Is the following the official DocBook element reference ?
http://www.docbook.org/tdg/en/html/ref-elements.html
Before investing in time to create a new class of things by using a
role on emphasis, make sure that there is not already something
available in the elements provided by DocBook
Thanks for the suggestion.
I did the classic thing of looking through the docs and stopped looking as
soon as I found the first thing that could solve my problem.
tended to use
tags like systemitem and add class values rather than using the
role on emphasis, reserving emphasis for the more generic concept of
This is important rather than for semantic bindings
Thanks for trying to help me obtain the correct mindset.
-Original Message-
From: Rowland, Larry [mailto:larry.rowl...@hp.com]
Sent: Monday, April 12, 2010 11:44 AM
To: Dave Pawson; Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: RE: [docbook-apps] How do I highlight inline text ?
Another thing to keep in mind is that DocBook already has a large
assortment (some people say too many, but others of us disagree) of
semantic elements available that describe many features of computers.
Before investing in time to create a new class of things by using a
role on emphasis, make sure that there is not already something
available in the elements provided by DocBook. Some of them have
numerous variations added through a class attribute (systemitem has
21 values enumerated for the class value). One of the values of a
semantic markup system is that there are already a number of semantic
bindings available in DocBook. You can customize the CSS style that
is associated with the semantic tags that are already available, too
(that's what the cascading part of cascading style sheet means) if
you want more or different formatting for the semantic you are trying
to represent (not all elements in DocBook have a unique format
associated with them).
You can also extend the class attributes if you pick up a little of
the RelaxNG grammar (there are lots of tutorials about it online).
In using DocBook for a number of years here, we have tended to use
tags like systemitem and add class values rather than using the
role on emphasis, reserving emphasis for the more generic concept of
This is important rather than for semantic bindings. Extending
things through role is simpler, but using class and other more
structured solutions provides better support for the authoring
process since syntax aware editors provide hints to the user for
enumerated values like class.
I think CSS is great fun and it has been well worth the time
invested in it to learn it (I spent an afternoon a few weeks ago
learning how to use DIV elements instead of tables for controlling
positions, which was quite a trip). I also have found the time spent
learning DocBook by referencing The Definitive Guide worthwhile.
There are a lot of elements available, and I don't pretend to know
all of them, but I always look at the table of contents, which lists
the elements, before I set out to extend it. I frequently find the
DocBook team has been there before me and that all I have to do is
tell the writers what element to use instead of inventing something.
Regards,
Larry Rowland
-Original Message-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Sunday, April 11, 2010 4:44 AM
To: Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?
On Sun, 11 Apr 2010 06:22:18 -0400
Robert Lucente rluce...@pipeline.com wrote:
a.. Create a cascading style sheet w/ a file name of key_words.css
w/ the following entry
.key_words { background: yellow; }
Nit picking, use semantic names for the attribute?
I may be wrong here.
[RL Start]
Nathalie Sequeira on April 07, 2010 5:31 PM recommended the following
emphasis role=semantic_function_of_the_emphasissome
text/emphasis
I thought that this was way cool. Then if I wanted to change the how
the semantic was displayed, just change the CSS.
Humm. What am I missing ?
[RL End]
I guessed that 'keyword' wasn't semantic. Was I wrong?
If it does identify a keyword in your xml markup, my apologies.
[RL Start]
I don't know anything about XSL. I will add it to the stuff to go
learn.
Is putting parameters in XSL just a best practice thing ?
I think so. puts all your 'styling' in one place?..
except it's two, one stylesheet importing another.
It makes sense. This way you have all your styling knobs in one spot
as opposed to 2 different spots.
Thanks for the help.
Welcome.
--
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
-
To
