RE: [docbook-apps] Python to PDF via XSL-FO
I am a newbie to DocBook and so take my comments w/ a grain of salt. Check out http://www.reportlab.com/software/opensource/rl-toolkit/ Why not go from Python to PDF directly? -Original Message- From: John W. Shipman [mailto:j...@nmt.edu] Sent: Monday, May 07, 2012 1:54 PM To: docbook-apps mailing list Cc: John Shipman Subject: [docbook-apps] Python to PDF via XSL-FO As much as I love XSLT (half-kidding here), I have several applications to generate PDFs from databases, and from other sources that XSLT can't reach directly. Since I discovered SQLAlchemy (http://www.sqlalchemy.org), life is much nicer: In Python, I can pull data from SQL databases without getting any actual SQL on my paws. These applications use Python and its wonderful lxml module to produce XSL-FO files, which I can then run through XEP or FOP. I've built a little Python module to assist in the generation of XSL-FO: http://www.nmt.edu/tcc/projects/fohelpers If anyone finds this module useful, or if you have feedback on its usefulness, I would be delighted to hear from you. Are there other mailing lists that might reach potential users? Best regards, John Shipman (j...@nmt.edu), Applications Specialist, NM Tech Computer Center, Speare 146, Socorro, NM 87801, (575) 835-5735, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber - 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] My eContent Wish List - A TOC Webcast
I think that the O'Reilly webinar might be of interest to members of this mailing list. Please note that I receive no direct or indirect compensation from O'Reilly. -Original Message- From: O'Reilly Webcasts [mailto:webc...@oreilly.com] Sent: Tuesday, December 07, 2010 2:42 PM To: rluce...@pipeline.com Subject: My eContent Wish List - A TOC Webcast If you would like to view this information in your browser, click here: http://post.oreilly.com/rd/9z1zrrnfvdv6oppd8n8dn45o55a7pa6e9hhk2nghqag Join us for this free, live webcast: My eContent Wish List - A TOC Webcast Presented by: Joe Wikert, General Manager and Publisher for O'Reilly Media Despite the recent surge in ebook sales we're still very much in the early stages of this new platform. In this webcast Joe Wikert of O'Reilly will talk about the current state of the econtent world and present more than 10 different improvements and enhancements he would like to see. Some of them are minor while others will require changes to ereader apps and distribution models. All of them will make econtent more appealing to a broader consumer audience. === Attendance is limited, so register now. We'll send you a reminder before the webcast. And please feel free to share this invitation with others. Date: Thursday, December 16 at 10 am PT Price: Free Duration: Approximately 60 minutes To register: http://post.oreilly.com/rd/9z1zd7in1l0j72cmm8m8b8ini6ekq2j9r2qhd4g4reg Questions? Please send email to webc...@oreilly.com === Joe Wikert is General Manager Publisher at O'Reilly Media, Inc., where he manages the sales and editorial groups. He's the author of the Publishing 2020 blog where he's provided industry insights for the past 4+ years. Joe is also a Kindle owner and blogger; you can find his thoughts about this device on Kindleville. Prior to joining O'Reilly Joe was Vice President and Executive Publisher at John Wiley Sons, Inc., in their P/T division. === About O'Reilly O'Reilly Media spreads the knowledge of innovators through its books, online services, magazines, and conferences. Since 1978, O'Reilly Media has been a chronicler and catalyst of cutting-edge development, homing in on the technology trends that really matter and spurring their adoption by amplifying faint signals from the alpha geeks who are creating the future. An active participant in the technology community, the company has a long history of advocacy, meme-making, and evangelism. # # # O'Reilly is a registered trademark of O'Reilly Media, Inc. All other trademarks are property of their respective owners. === You are receiving this message because you expressed interest in hearing about O'Reilly Webcasts. Forward this invitation to a friend: http://post.oreilly.com/f2f/9z1z1j4fpssmtql13dq3j4ub4act08tgn98a33jhoi0 For assistance, or if you no longer wish to receive notifications about O'Reilly Webcasts, send an email to webc...@oreilly.com. O'Reilly Media, Inc. 1005 Gravenstein Highway North, Sebastopol, CA 95472 (707) 827-7000 - 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] JavaHelp index
Why not just use JavaDoc ? What is the value add to use JavaHelp ? http://www.oracle.com/technetwork/java/javase/documentation/index-jsp-135444 .html -Original Message- From: Jean-Christophe Helary [mailto:jean.christophe.hel...@gmail.com] Sent: Sunday, August 22, 2010 5:52 PM To: DocBook Apps Subject: Re: [docbook-apps] JavaHelp index On 23 août 10, at 02:30, Mauritz Jeanson wrote: By the way, my impression is that interest in JavaHelp is waning. Nothing much seems to happen with the technology and discussion forum activity is low. But perhaps you have another opinion? Is there any other way to simply create a help system for Java applications ? Jean-Christophe Helary fun: http://mac4translators.blogspot.com work: http://www.doublet.jp (ja/en fr) tweets: http://twitter.com/brandelune - 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] blogging using DocBook articles or so ...
We have to be very conscious of who is the intended audiance. Warning pontification: You can't be everything to everybody. Creating DocBook XML and then getting the processing chain to work to convert XML to HTML and then screwing around to get something to look exactly the way you want it to in order to create a blog seems like way overkill. If something is not long or if the aesthetics are very critical, perhaps DocBook is not the tool ? I am not trying to start a flame war, just trying to look at things from everybody's perspective. -Original Message- From: jochen+oasis-o...@hayek.name [mailto:jochen+oasis-o...@hayek.name] Sent: Sunday, July 18, 2010 9:43 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] blogging using DocBook articles or so ... So far I have been blogging on a couple of blogger.com blogs of mine, and I got quite used to the capabilities there, I mean WYSIWYG is not that disgusting, even for an open-minded emacs guy as me, but then … … maybe there has already been an attempt to use DocBook for blogging? I mean, *what* *is* a *blog* *really*??? A time-consecutive list of articles, together with a commenting facility (but that's not most important, I think), and automatically supplied RSS and/or atom feeds. Would be exciting to use DocBook also for that. Kind regars, J. -- As nice as you guys here are, pls usually only reply to my post right on this mailing list. I honestly do follow this list. Of course, if you want to tell me, how silly I am, then let's keep that private ;-) but usually it's only my Bad Simple English, not my ideas. - 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] Re: blogging using DocBook articles or so ...
And IMHO DocBook output *is* nice. Ooops. Did not mean to imply otherwise. O'Reilly books (all/some/a few?!?) are written in DocBook Yes, I am aware. Please note that O'Reilly focuses on the tech market. Maybe blogging sharing would get far more often done, if the means were easier. Please name the one specific thing that you would like to be easier. glues separate documents together I am confused. If we are talking about a simple blogg, why are we talking about glueing documents together ? Please note that I am a newbie and trying to figure out where the various tool sets fit in. So, if I am making silly comments or asking silly questions, request your patience. -Original Message- From: jochen+oasis-o...@hayek.name [mailto:jochen+oasis-o...@hayek.name] Sent: Sunday, July 18, 2010 10:16 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] Re: blogging using DocBook articles or so ... Robert Lucente writes: We have to be very conscious of who is the intended audiance. Warning pontification: You can't be everything to everybody. Creating DocBook XML and then getting the processing chain to work to convert XML to HTML and then screwing around to get something to look exactly the way you want it to in order to create a blog seems like way overkill. My standards a lower there. Aesthetics are important but not prio 1. And IMHO DocBook output *is* nice. And you do know, that O'Reilly books (all/some/a few?!?) are written in DocBook nowadays, don't you? Maybe bloggingsharing would get far more often done, if the means were easier. My current experience is DocBook Website, which glues separate documents together using a layout.xml, which serves quite a few different purposes including customization. I would even regard it as acceptable to maintain something like the source of the RSS/atom feeds, which could be the corresponding thing to that layout.xml. If something is not long or if the aesthetics are very critical, perhaps DocBook is not the tool ? I am not trying to start a flame war, just trying to look at things from everybody's perspective. Fair enough. Thanks for your contribution. I just wanted to ask around and maybe suggest and idea. Sometimes it take a spark, you know, in order to start projects, tiny ones and big ones. Just my $0.05. - 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] Re: blogging using DocBook articles or so ...
I think that the various perspectives have been adequately presented and each user must decide for themselves what is the appropriate tool to use. -Original Message- From: jochen+oasis-o...@hayek.name [mailto:jochen+oasis-o...@hayek.name] Sent: Sunday, July 18, 2010 11:51 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] Re: blogging using DocBook articles or so ... Robert Lucente writes: And IMHO DocBook output *is* nice. Ooops. Did not mean to imply otherwise. O'Reilly books (all/some/a few?!?) are written in DocBook Yes, I am aware. Please note that O'Reilly focuses on the tech market. That's O'Reilly, not necessarily you and me. *** THIS IS NOT A FLAME, HONEST *** What makes DocBook unsuited for others than the tech market? Is is it the same with LaTex? Because you can write math. formulas with it, you can't write prose with it? Alright… people writing prose might not want to get bothered with something as profane as XML tags resp. LaTeX markup? I used to use troff Memorandum Macros, and not just for the job. Do you think the addressees bothered, whether my letters were written in that incredible markup language? Maybe blogging sharing would get far more often done, if the means were easier. Please name the one specific thing that you would like to be easier. I hate to edit text outside the emacs universe. I hate it to edit text in a web browser. I hate it to not be able to use Control-S to save my text every couple of seconds, w/o even being really aware, that I have done it again. Too much hatred, I know. Again: this is not a flame. I am just not a WYSIWYG guy. Yes, occasionally I like using formatted e-mail in Google Mail, yes, it is a serious temptation. Yes, I am Google Buzzing a lot. But there again: I use old-fashioned markup there, too. I prefer focussing on content, and *marking* *up* my text, yes with some kind of eagerness for perfection. Your mileage may vary, they say. With your preferred editor – do you actually type the end tag or does your editor achieve that for you? My editor does it for me, so I don't bother. I think end tags do help. But than I am also one of the guys out there (with Ada being my 5th programming language or so), who loves end if, end case, and that sort of stuff, and with perl and ruby and whatever I add it myself as a comment. glues separate documents together I am confused. If we are talking about a simple blogg, why are we talking about glueing documents together ? To keep things simple, one approach may be to regard every blog article a document of its own. Alright? But if the blog is sort of DocBook Blog, then what keeps the articles together? I assume you are familiar with blog subscription features, like adding the blog's RSS resp. atom feed to your preferred feed reader. What creates the RSS resp. atom feed in the case of DocBook Blog? Well in the case of DocBook Website there is a meta-document called layout.xml, which is not really DocBookish but (at least) XML with a defined DTD/schema. Maybe there will be sort of layout.xml for DocBook Blog as well. I am sorry, you must be bored by this, as I keep reusing my own words. Please note that I am a newbie and trying to figure out where the various tool sets fit in. So, if I am making silly comments or asking silly questions, request your patience. If I am not patient enough: pls forgive me! And see: I am still here :-) Maybe DocBook Blog is serious enough for a student's thesis an whatever level. No idea. Just suggesting… Another approach may well be to regard the entire blog as a book, with the articles being sections of level 1. But then: as the blog grows article by article the generation process for the whole will more and more degrade. And I just thought, that's not a good idea. And why start there, if we know that from the very beginning. Just my $0.05. Sic. - 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] Compact DocBook ?
On topic though, so why not! Thanks for the help on what is appropriate etiquette. By the looks of it, Leo is GUI ? Leo is a GUI in the sense that it displays nodes hierarchically just like Windows explorer displays folders/directories hierarchically. I am a novice at DocBook, Leo, literate programming and the like. The best thing would be to look at the Leo doco Chapter 6: Leo and Literate Programming at http://webpages.charter.net/edreamleo/design.html#chapter-6-leo-and-literate -programming -Original Message- From: Dave Pawson [mailto:da...@dpawson.co.uk] Sent: Monday, July 12, 2010 7:38 AM To: Robert Lucente Subject: Re: [docbook-apps] Compact DocBook ? On Mon, 12 Jul 2010 06:11:46 -0400 Robert Lucente rluce...@pipeline.com wrote: Think of it the other way round? Embed java code in Docbook? Nice ! Tangle and weave are the ideas, Literate Programming the background. At one point, I started using Leo to do literate programming. The thing that I like about Leo is that it is an outliner w/ hoist and node cloning. The downside is that it has a steep learning curve. http://webpages.charter.net/edreamleo/front.html I still use an old versio of Leo but don't do full Literate programming. So far, the price of the learning curve is not worth it. I did not post this in the docbook group because it did not seem appropriate. If I am wrong, please correct me. Some are interested in literate programming in general, so there may be some interest, but I guess it's low. On topic though, so why not! By the looks of it, Leo is GUI? I'm not sure how that helps for litprog? I use emacs, or (a java environment, then paste/include into emacs for the Docbook) regards -- 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
[docbook-apps] An interesting article about DocBook in WebWorkerDaily
http://webworkerdaily.com/2010/05/18/defining-and-finding-truly-great-tools/ The part that got my interest was Later, I was introduced to DocBook, an XML schema that allows the identification of pieces of content as small as individual letters. Here, for me, was an actual revolution in the way I worked. DocBook represented a new way of thinking about my content and suited my thought patterns much better than did the blank page of a word processing file, implying as it did a linear flow and a single voice. The fact that this tool suited my brain better than did word processing tools allowed me to think about information and communication differently: instead of battling (albeit subconsciously) with the restrictions of my tools, I was free to approach content in a way that really suited me, and was shown a completely new perspective on my work at the same time. Where content management tools made my life easier and improved my product, DocBook effectively allowed me to evolve my practice. - 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] Annotating program listings - Callouts - Chapter 27. Program listings - minor / nit typo ?
Yesterday I asked a C language guru and he said that amp; has nothing to do w/ C. I think that there are 2 possibilities 1) The amp; has not been properly escaped from the DocBook perspective. This is a possibility because the program listing is not in CDATA 2) It could be an HTML thing http://htmlhelp.com/reference/html40/entities/special.html Perhaps there are other possibilities ? -Original Message- From: Bob Stayton [mailto:b...@sagehill.net] Sent: Saturday, April 24, 2010 4:40 PM To: Robert Lucente; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Annotating program listings - Callouts - Chapter 27. Program listings - minor / nit typo ? Hi Robert, Thanks for taking the time to comment. No, it isn't a typo. The programlisting is not in a CDATA section, so any XML characters like must be escaped as character entities. That character is intended to be a literal ampersand in the program listing. If you are asking me if the code itself makes sense with an ampersand, I can't answer that. I just cut and pasted it from somewhere. 8^) Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Robert Lucente To: docbook-apps@lists.oasis-open.org Sent: Saturday, April 24, 2010 12:25 PM Subject: [docbook-apps] Annotating program listings - Callouts - Chapter 27. Program listings - minor / nit typo ? url: http://www.sagehill.net/docbookxsl/AnnotateListing.html#Callouts The program listing has virtual int parse(MyFetch amp;fetcher) = 0; I think that amp is a typo in the above line of code ? This has probably already been found but just in case.
RE: [docbook-apps] Annotating program listings - Callouts - Chapter 27. Program listings - minor / nit typo ?
Thanks. I guess I have demonstrated my newbie status in C++. :-) -Original Message- From: Stefan Seefeld [mailto:seef...@sympatico.ca] Sent: Sunday, April 25, 2010 10:06 AM To: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Annotating program listings - Callouts - Chapter 27. Program listings - minor / nit typo ? On 04/25/2010 08:47 AM, Robert Lucente wrote: Yesterday I asked a C language guru and he said that *amp;* has nothing to do w/ C. The code snippet is not C but C++. And as such it is perfectly fine. Stefan -- ...ich hab' noch einen Koffer in Berlin... - 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] Annotating program listings - Callouts - Chapter 27. Program listings - minor / nit typo ?
url: http://www.sagehill.net/docbookxsl/AnnotateListing.html#Callouts The program listing has virtual int parse(MyFetch amp;fetcher) = 0; I think that amp is a typo in the above line of code ? This has probably already been found but just in case.
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
RE: [docbook-apps] How do I highlight inline text ?
Comments below start w/ [RL]
-Original Message-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Sunday, April 11, 2010 2:42 AM
To: Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?
Just one comment.
On Sat, 10 Apr 2010 19:29:20 -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]
a.. Create a DOS batch file setting the following parameters
1.. emphasis.propagates.style: 1
2.. html.stylesheet: file://localhost/C:\ypl\doc_book\key_words.css
a.. The DOS batch file name was using_role_as_class_name.bat and it
contained the following contents
REM
REM Set the classpath
REM
set classpath=.;
REM
REM
REM Output contents of environment variables
REM
set
REM
REM
REM Generate HTML from DocBook XML
REM
C:\Program Files\Java\jre1.5.0_22\bin\java ^
-cp C:\ypl\java\xalan.jar;C:\ypl\java\serializer.jar
org.apache.xalan.xslt.Process ^
-v ^
-xsl C:\ypl\doc_book\xsl_1.75.2\html\chunk.xsl ^
-in using_role_as_class_name.doc_book_xml ^
This is my disagreement with how you have done it.
-param emphasis.propagates.style 1 ^
-param html.stylesheet
file://localhost/C:\ypl\doc_book\key_words.css ^ -param base.dir
html/ EXIT
I do it differently is the best way I can say this.
1. I didn't know I could set parameters on the command line :-)
2. I always use an 'import' method to set my parameters
Create a normal stylesheet
First statement inside xsl:stylesheet
xsl:import href='ypl/doc_book/xsl_1.75.2/html\chunk.xsl'
the set your parameters
xsl:param name='emphasis.propagates.style' select='1'/
xsl:param name='html.stylesheet'
select='/ypl/doc_book/key_words.css'/
/xsl:stylesheet
Note the quoted css file
Note the forward / not \
[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 ?
It makes sense. This way you have all your styling knobs in one spot
as opposed to 2 different spots.
Thanks for the help.
[RL End]
HTH
--
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
RE: [docbook-apps] How do I highlight inline text ?
Hi guys,
Thanks for all your help. I got it to work.
Request a quick review to make sure that I did not do something silly.
In case the email below is hard to read, please go to
http://www.ypl.com//build_windows_machines/install_applications/doc_book_to_
html/html_deep/ch09s03.html
a.. Create a cascading style sheet w/ a file name of key_words.css w/ the
following entry
.key_words { background: yellow; }a.. Create a file containing DocBook xml
tags w/ a file name of using_role_as_class_name.doc_book_xml w/ the
following entries
!DOCTYPE book SYSTEM
file://localhost/C:\ypl\doc_book\dtd_xml_4.5b1\docbookx.dtd
book
title
Some Book Title
/title
chapter
title
Some Chapter Title
/title
para
First sentence with no highlighting.
/para
para
Second sentence with highlighting which emphasis role=key_wordsstarts
here and goes until here/emphasis but does not highlight entire sentence.
/para
/chapter
/booka.. Create a DOS batch file setting the following paramters
1.. emphasis.propagates.style: 1
2.. html.stylesheet: file://localhost/C:\ypl\doc_book\key_words.css
a.. The DOS batch file name was using_role_as_class_name.bat and it
contained the following contents
REM
REM Set the classpath
REM
set classpath=.;
REM
REM
REM Output contents of environment variables
REM
set
REM
REM
REM Generate HTML from DocBook XML
REM
C:\Program Files\Java\jre1.5.0_22\bin\java ^
-cp C:\ypl\java\xalan.jar;C:\ypl\java\serializer.jar
org.apache.xalan.xslt.Process ^
-v ^
-xsl C:\ypl\doc_book\xsl_1.75.2\html\chunk.xsl ^
-in using_role_as_class_name.doc_book_xml ^
-param emphasis.propagates.style 1 ^
-param html.stylesheet
file://localhost/C:\ypl\doc_book\key_words.css ^
-param base.dir html/
EXIT
-Original Message-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Thursday, April 08, 2010 6:50 AM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?
On Thu, 8 Apr 2010 06:13:09 -0400
Robert Lucente rluce...@pipeline.com wrote:
Thanks for reminding me about color blind people and the link to the
colors.
Since I am interested in Highlight text (text with a background
color), I should really be using the CSS background-color property.
My bad.
No, not bad. My favourite quote. Everyone needs the idiot sheet
at least once.
I certainly did. I'm now a confirmed CSS convert. Just
irritated that it hasn't kept pace with other developments,
or at least not in the browsers.
Its nearly brilliant. It's certainly good.
regards
--
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
RE: [docbook-apps] How do I highlight inline text ? - OT
i.e., ending each statement with a semicolon.
Thanks for the very meticulous review.
Let me work through some of the references that you provided to get an idea
of what CSS is all about.
-Original Message-
From: Nathalie Sequeira [mailto:n...@n-faktor.net]
Sent: Thursday, April 08, 2010 2:46 AM
To: Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ? - OT
Hi Robert,
glad that helped you find a good perspective on docBook :)
So, is it as easy as adding the following entry ?
.key_words {color: yellow}
I am attempting to be lazy and avoid working my way through
http://www.w3.org/Style/CSS
Yes that would work, whereby best practice would be
.key_words {color: yellow;}
i.e., ending each statement with a semicolon.
CSS really is very easy.
Don't start with the specs though - you can find a quick introduction at
http://w3schools.com/css/default.asp
You'll find a more solid and in-depth introduction at
http://westciv.com/style_master/house/index.html
There are lots of resources there, including a hands on tutorial and a
more theoretical CSS guide (with detailed descriptions of the types of
CSS selectors and properties).
And another, perhaps more actively maintained reference:
http://reference.sitepoint.com/css
Have fun exploring :)
Nathalie Sequeira
-
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 ?
Thanks for reminding me about color blind people and the link to the colors.
Since I am interested in Highlight text (text with a background color), I
should really be using the CSS background-color property. My bad.
-Original Message-
From: Dave Pawson [mailto:da...@dpawson.co.uk]
Sent: Thursday, April 08, 2010 3:06 AM
To: Robert Lucente
Cc: n...@n-faktor.net; docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?
On Wed, 7 Apr 2010 19:46:52 -0400
Robert Lucente rluce...@pipeline.com wrote:
[lazily :-)]
It was big help.
The generic explanation followed by the specific example of wanting to
change from yellow to blue really hit the point home.
don't forget the 3 of your readers who are color blind.
The rest is a CSS question IMHO
How do I go about figuring out the magic words for the CSS stylesheet
entry ?
And now a worked example: p {color: blue; font-size: 120%; }
So, is it as easy as adding the following entry ?
.key_words {color: yellow}
Yes, but a little effort will produce very good results?
CSS is great for instant reward.
I use the O'Reilly CSS The definitive guide.
Again and again and again.
p.emphasis {
font-weight: bold;
color: yellow;
}
As each property is added, finish it with the semi-colon.
Get the colors from http://html-color-codes.info/#HTML_Color_Picker
or google CSS color chart
I am attempting to be lazy and avoid working my way through
http://www.w3.org/Style/CSS
I generally find a book easier than the rec, they are
written for implementers, not users.
HTH
--
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
[docbook-apps] How do I highlight inline text ?
Hi, I am a newbie in getting DocBook XML to generate HTML. I have it working and documented what the processing elements are at a high level as well as detailed steps for installation in Windows for newbies at http://www.ypl.com//build_windows_machines/install_applications/doc_book_to_ html/html_deep/index.html Perhaps this exists somewhere already and I just did not find it ? Request help in figuring out how to highlight inline text. It seems that the way to go is to use something like emphasis role=yellowsome text/emphasis. I got the idea from 1) The sql syntax example at http://www.sagehill.net/docbookxsl/UsingCSS.html 2) The following email from the docbook-apps mailing list Subject: Re: [docbook-apps] Coloring body text portions - May 18, 2004 3:54:58 pm For HTML output, it is easier to export a class attribute on some HTML element and then write a CSS stylesheet to apply styles such as color. A few elements like phrase and emphasis can export their role attribute value as a class attribute if you set the right stylesheet parameter. If the way to go is to follow the example in sagehill.net, then request help w/ Question: What should be the CSS stylesheet entry ? Question: What should I add to the stylesheet customization layer ? Question: Perhaps the above entire approach is inappropriate and another approach should be used Pontification type of question: It seems like highlighting text w/ color should be a standard feature ? Since its not, I am missing the mind set associated w/ DocBook. What is the mind set w/ which to approach DocBook and its processing chain such that it makes sense that color highlighting is not built in ? If the above does not make sense, I have attempted to be more elaborate at http://www.ypl.com//build_windows_machines/install_applications/doc_book_to_ html/html_deep/ch08.html If I have violated some of the mailing list norms, please let me know so that I can correct them. - 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 ?
It was big help.
The generic explanation followed by the specific example of wanting to
change from yellow to blue really hit the point home.
To follow your example, what I really want is
emphasis role=key_wordssome text/emphasis
In Using CSS to style HTML in
http://www.sagehill.net/docbookxsl/UsingCSS.html
it states to create a CSS stylesheet entry
.sqlsyntax {font-variant: small-caps;}
How do I go about figuring out the magic words for the CSS stylesheet entry
?
I am totally new to this stuff. I Googled around and found
http://www.yourhtmlsource.com/stylesheets/introduction.html
selector {property: value; property: value; property: value; }
And now a worked example: p {color: blue; font-size: 120%; }
So, is it as easy as adding the following entry ?
.key_words {color: yellow}
I am attempting to be lazy and avoid working my way through
http://www.w3.org/Style/CSS
-Original Message-
From: Nathalie Sequeira [mailto:n...@n-faktor.net]
Sent: Wednesday, April 07, 2010 5:31 PM
To: Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?
Hi Robert,
Request help in figuring out how to highlight inline text.
It seems that the way to go is to use something like emphasis
role=yellowsome text/emphasis.
I think the way to go would rather be
emphasis role=semantic_function_of_the_emphasissome text/emphasis
while your example actually is going
emphasis role=how_the_emphasis_should_looksome text/emphasis
Pontification type of question: It seems like highlighting text w/ color
should be a standard feature ? Since its not, I am missing the mind set
associated w/ DocBook. What is the mind set w/ which to approach DocBook
and
its processing chain such that it makes sense that color highlighting is
not
built in ?
Yes, I'd say mind-set issue indeed :)
docBook handles information - the basic information plus the functions
single pieces of the information have within the whole (is this text a
title, for example, is it a list...or is it to be emphasized.).
Then come the docBook stylesheets, that will transform the docBook into
HTML for you (you can tweak how the result will be via customization layer).
And finally, colors and other aspects pertaining to styling are set in CSS.
The beauty of this is that (for example):
- in a few years, you may get tired of all those yellow texts and may
want to make them blue or orange or purple instead. If you defined the
specific color via CSS, all you need to change is one single class, and
you're set up (instead of having to go through your docBook file and
edit all the instances of, say, yellow -- It's the same principle as
in separating content and form in plain old HTML CSS).
- all texts you assign a certain role to (the name itself says it all -
role, what is the role these words play in the text?) will be styled
in the same way,
- you can output your docBook-Information for different media, and can
use the SAME source for them all, defining how they should look
individually and OUTSIDE the docBook information itself.
http://opensource.bureau-cornavin.com/crash-course/en/your-world-view.html
also discusses the issue :)
Hoping that helps a bit,
Nathalie Sequeira
-
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
