[docbook-apps] Side-by-side images
Hello, What is the proper way to display two images side-by-side? The way I do this now is to put two into a . The HTML output is two images side-by-side aligned to the left. Playing with the align attribute in the tags results in text for the proceeding paragraphs to creep up in the space between them, since they are inline. Using the would separate the images onto two different lines. I feel like I'm tagging these images wrong. doesn't really describe the content here since they're not *really* inline. Is there a "right" way to accomplish this (other than combining two images into one)? My goal is to get two images side-by-side, center aligned, though a solution that would work for more than 2 images side-by-side would be ideal. Thanks, DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] Side-by-side images
This does get the desired result, though this is similar to my current solution. The content isn't *really* a table, so doesn't accurately describe what it is. Logically, I would think that with 2 s would make the most sense, but when I transformed that into HTML, only the 1st image displayed. The description of in TDG5 does state that it can contain "one or more..." for objects, but perhaps that means one or more different objects, not two objects that are the same. See http://docbook.org/tdg5/en/html/mediaobject.html -David From: Roland Burda [mailto:burda.rol...@gmail.com] Sent: Wednesday, February 22, 2012 1:25 PM To: David Goss Cc: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Side-by-side images David! I use tables to get two images side-by-side. This is my workaround for the issue: Cheers, Roland 2012/2/22 David Goss Hello, What is the proper way to display two images side-by-side? The way I do this now is to put two into a . The HTML output is two images side-by-side aligned to the left. Playing with the align attribute in the tags results in text for the proceeding paragraphs to creep up in the space between them, since they are inline. Using the would separate the images onto two different lines. I feel like I'm tagging these images wrong. doesn't really describe the content here since they're not *really* inline. Is there a "right" way to accomplish this (other than combining two images into one)? My goal is to get two images side-by-side, center aligned, though a solution that would work for more than 2 images side-by-side would be ideal. Thanks, DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] Assigning an ID and a class to HTML output
I would like to use a Javascript fancyzoom() with images in a Docbook HTML output. Basically, all the images would float right and be of equal width, and could be clicked to zoom. My problem is that setting xml:id='theimagename' and role='thumbnail' in mediaobject (or imageobject and imagedata) doesn't seem to add an id or a class to the HTML output. Is there some way I can explicitly tell the transformation sheet that I want the id and class in the output? DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] xsltproc, glossary.collection, and xinclude - glossary is not found
Hello, I'm having a bit of a problem using the glossary.collection parameter with xincluded files. My project directory looks something like this: / /doc/glossary.docbook /doc/article1.docbook /doc/article1/sect1.docbook /xsl/stylesheet.xsl Doc/Article1.docbook contains an xinclude element for doc/article1/sect1.docbook. At the bottom of doc/article1.docbook is ; within doc/article1/sect1.docbook I have http://www.MuellerReports.com - 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] xsltproc, glossary.collection, and xinclude - glossary is not found
Bob, Thank you very much for the information! I could see that it was taking the path relative to the included files, but ../glossary.docbook still results in the file not being found (same problem with the full path--I blame path issues on using cygwin). Setting glossterm.auto.link to 0, however, builds the HTML successfully, though albeit without links. -Original Message- From: Bob Stayton [mailto:b...@sagehill.net] Sent: Saturday, March 17, 2012 5:11 PM To: David Goss; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] xsltproc, glossary.collection, and xinclude - glossary is not found Hi David, It seems the documentation about glossary.collection fails to mention how a relative path to the collection file is interpreted. The short answer is: a. If you have glossterm.auto.link set to zero, the path is taken as relative to the file containing the empty element. b. If you have glossterm.auto.link set to non-zero, the path is taken as relative to the file containing the *first* inline glossterm or firstterm in the document, in document order. In your case, I think you must have glossterm.auto.link set to 1, and the firstterm in your xincluded file is the first instance. So for your particular case, setting the param this way should work: --stringparam glossary.collection ../glossary.docbook If you want to see why it works this way, read on. Note that the XSL stylesheet does not know from what directory you issued your processing command. Your shell interpreter resolves the path to only the document and stylesheet files, but has no effect on parameter settings. The XSL processor itself does not normally have your location information, and so does not know that "doc/docbook.glossary" means relative to CWD. In the stylesheet, the instruction that opens the glossary collection looks like this: The first argument of the document() function specifies the file to open, but the second argument can specify a base URI that is prepended to the filename. Here, the second argument of the document() function is . which represents the current node in the document (not the stylesheet). In this function, the XSL processor interprets that . to mean the base dir for the file containing the current document element. If the second argument is omitted, then the first argument path is interpreted as relative to the stylesheet file. Since most people keep their collection file with the doc files, using . usually makes sense. So what is the current document element? In the case where $glossterm.auto.link is set to zero, the collection file is not opened until the element is processed. In that case, the collection path is relative to the file containing that empty glossary element. In the case where $glossterm.auto.link is non-zero, the first instance of an inline glossterm or firstterm will trigger opening the collection file. That's because it must have the information from the database to form the link. Once the collection has been opened, the processor keeps it in memory and does not need to open it again. So any subsequent references, and the glossary element itself, will reuse that already opened collection. Obviously this arrangement may not suit everyone. In your case, the first instance happens to be in an Xincluded file in a subdirectory, so the glossary.collection path would have to be relative to that subdirectory. In other cases, you might have a collection file shared by documents in many locations, which requires setting the glossary.collection parameter according to where the glossary element resides, which can be inconvenient. In such cases, you could specify a full path in the glossary.collection param, or you could specify a phony path and reinterpret it with an XML catalog file. See this reference for details on the latter option: http://www.sagehill.net/docbookxsl/GlossDatabase.html#GlossaryCatalogEnt ry Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message ----- From: "David Goss" To: Sent: Friday, March 16, 2012 12:14 PM Subject: [docbook-apps] xsltproc, glossary.collection, and xinclude - glossary is not found Hello, I'm having a bit of a problem using the glossary.collection parameter with xincluded files. My project directory looks something like this: / /doc/glossary.docbook /doc/article1.docbook /doc/article1/sect1.docbook /xsl/stylesheet.xsl Doc/Article1.docbook contains an xinclude element for doc/article1/sect1.docbook. At the bottom of doc/article1.docbook is ; within doc/article1/sect1.docbook I have http://www.MuellerReports.com - 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-unsubs
[docbook-apps] Applying a processing instruction by default in a stylesheet
Per the instructions in Bob Stayton's excellent XSL Guide for [http://www.sagehill.net/docbookxsl/Variablelists.html], I've found that I want to use a number of processing instructions in every variablelist in a set of documents. Something along the lines of: Rather than copying/pasting these into every , it would make sense to make this the default behavior for each instance. Is there a way to activate the applicable instructions in my customization layers for print and html for all variablelists? I've searched through the stylesheets, but with my limited understanding of XSL, I'm not sure how exactly the instruction is set during processing and how I can set it manually in the stylesheet instead of the document. DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] Assigning an ID and a class to HTML output
Sorry for the slow response time. I never quite got this working using
fancyzoom(), so I just used a bit of Jquery. Not being a programmer myself, I'm
sure this could be greatly improved.
$("body").append('');
$("#zoomed").hide();
$("div.thumbnail").click(function(){
$("#zoomed").empty();
$("#zoomed").html($(this).html());
var newtop = $(window).scrollTop() +
($(window).height()/2 -$("#zoomed").height()/2);
$("#zoomed").css("top", newtop);
$("#zoomed").fadeIn("fast");
});
$("#zoomed").click(function(){
$(this).fadeOut("fast");
});
Bob's Stayton's method for matching with role='thumbnail' works
perfectly.
Everything else is done by tweaking the CSS for #zoomed and div.thumbnail. I
have the thumbnails all sized about 200px and floating to the right. This has
really helped clean up some HTML docs that are very image heavy.
-----Original Message-
From: Fekete Robert [mailto:frob...@balabit.hu]
Sent: Tuesday, March 13, 2012 8:43 AM
To: docbook-apps@lists.oasis-open.org; David Goss
Subject: Re: [docbook-apps] Assigning an ID and a class to HTML
output
Hi David, in case you managed to get it working, would you share your
results/experiences with us? I'd love to try something similar on our docs.
Regards,
Robert
On 03/06/2012 07:35 PM, David Goss wrote:
> I would like to use a Javascript fancyzoom() with images in a Docbook
> HTML output. Basically, all the images would float right and be of
> equal width, and could be clicked to zoom.
>
> My problem is that setting xml:id='theimagename' and role='thumbnail'
> in mediaobject (or imageobject and imagedata) doesn't seem to add an
> id or a class to the HTML output. Is there some way I can explicitly
> tell the transformation sheet that I want the id and class in the output?
>
>
> DAVID GOSS | Technical Writer
> P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com
> http://www.MuellerReports.com
>
>
>
> -
> 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] Setting a fixed height for within
I'm having difficulty setting the default height for images that appear in . The source for these images is not always the same size, so I just want to scale them to the line height in my customization layer (instead of doing this in every image in the XML source). I've tried something like this (and probably a hundred variables): Which is at least preventing the image from pushing the text up, but the image itself is not scaling. DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] Making PDFs in Windows
Take a look at this chapter from the Docbook XSL Guide: http://www.sagehill.net/docbookxsl/InstallingAnFO.html That guide, along with the Docbook Definitive Guide are indispensible. 98% of problems I've had are addressed in one of those these two books. http://docbook.org/tdg5/en/html/docbook.html Personally, I use Cygwin, xsltproc, FOP, and a makefile for processing. (I'd kill to have a Unixy box at work instead of XP, but that's really another matter). -David From: deannel...@aol.com [mailto:deannel...@aol.com] Sent: Wednesday, April 18, 2012 9:59 AM To: yoursurrogate...@gmail.com; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Making PDFs in Windows Its not necessary to use Cygwin or MinGW. I use a batch file that calls XSLTPROC and FOP to generate PDFs under Windows. Check our Bob Stayton's book for more info. Regards, Dean Nelson In a message dated 4/18/2012 6:51:52 A.M. Pacific Daylight Time, yoursurrogate...@gmail.com writes: Hi guys, have you ever used Docbook to generate PDFs in Windows? Did you use Cygwin? If not, would you recommend anything else?
RE: [docbook-apps] nested lists being displayed incorrectly
Hi, The nested list needs to have a as a parent, not the top level list, like this: It declares the document to be XML by indicating a version and an encoding. It defines the root element for our document (book) and the following additional elements The default namespace; the default type of document we are using (docbook) along with its namespace address The namespace for xlink (used to create hyperlinks) with its namespace address The version of Docbook we are using The default language for the document The structure for the rest of the document: title for the book, author information and a sample chapter for us to work with I just tested and it works fine fine. (Yay! I was finally able to *give* help on this list! :) ) -David -Original Message- From: Carlos Araya [mailto:carlos.ar...@gmail.com] Sent: Tuesday, April 24, 2012 4:15 PM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] nested lists being displayed incorrectly I am working with the following nested lists It declares the document to be XML by indicating a version and an encoding. It defines the root element for our document (book) and the following additional elements The default namespace; the default type of document we are using (docbook) along with its namespace address The namespace for xlink (used to create hyperlinks) with its namespace address The version of Docbook we are using The default language for the document The structure for the rest of the document: title for the book, author information and a sample chapter for us to work with Is the syntax correct? When transforming the file to XHTML and FO it is swapping the order of the lists in the resulting document. Below is the result in HTML using the 1.76 styelsheets downloaded late last week The skeleton of the file does a few things for us: The default namespace; the default type of document we are using (docbook) along with its namespace address The namespace for xlink (used to create hyperlinks) with its namespace address The version of Docbook we are using The default language for the document It declares the document to be XML by indicating a version and an encoding. It defines the root element for our document (book) and the following additional elements The structure for the rest of the document: title for the book, author information and a sample chapter for us to work with I get the same result if I use the snapshot stylesheets when building epub3 and if I change the orderedlist to an itemizedlist. . - 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] output in PDF
In your customization layer, try something like this: For more information, see the section on customization layers in Bob Sayton's Docbook XSL Guide: http://www.sagehill.net/docbookxsl/CustomMethods.html#WriteCustomization -David -Original Message- From: Lars Vogel [mailto:lars.vo...@googlemail.com] Sent: Tuesday, May 08, 2012 3:37 PM To: DocBook Apps Subject: [docbook-apps] output in PDF Hi, I started using in my Docbook sources but it seems that the PDF output is just normal text. Is their a way to change it, e.g. to Italic? Best regards, Lars -- Lars http://www.vogella.com - Eclipse, Android and Java Tutorials http://www.twitter.com/vogella - Lars on Twitter - 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] Problems customizing an article titlepage
I'm trying to create a PDF title page for my docbooks and I'm running into two issues. I'm having difficult figuring out what is wrong, partly because I'm using the article class instead of the book class for my documents. I'm also using a 2 column layout 1.) Despite having column.count.titlepage set to 1, I'm still getting 2 columns on the titlepage. 2.) I want to remove the headers and footers (and corresponding rulers) from the titlepage. From what I've read, the titlepage is supposed to have blank headers/footers already, so I'm not sure how to remove them. I suspect both of these are part of the behavior of the article class. Any advice that could point me in the write direction would be greatly appreciated (mostly likely it's in Bob's book and I just haven't spotted the solutions yet). Thank you, DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] Automatic glossaries and seealso
I'm using to generate a glossary for multiple documents from the same source. This works great, unless I use a glossterm in the document that contains a element. When this happens, I get the "See also" reference in the generated glossary, but if the glossterm was not used in the document, the reference term isn't in the glossary. Example: My document contains: heating My glossary has cooling So when I run the stylesheets, I get "See also, cooling" under the entry for heating, even though "cooling" isn't in the generated glossary. I would either like to automatically add the term to the generated glossary or remove the seealso reference for terms that are not used. (Could this also be a bug? It doesn't seem like expected behavior.) DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com <http://www.muellerreports.com/>
[docbook-apps] Customizing the process.image template
Hi,
I'm using the [Lazy Load](http://www.appelsiini.net/projects/lazyload)
JQuery plugin to help out on some image-heavy docbook articles. I
basically just copy/pasted the process.image template to my
customization later and made these changes ("data-original" was "src"
and the last two attributes are my additions):
../img/common/placeholder.png
lazy
It works just fine, that's not the problem. I want to make it degrade
gracefully (without JavaScript, only the placeholder image is
displayed). The way the plugin author recommends to do so is the place
an alternative in a tag after the image, like this:
My question is where/how in the process.image template should this
redundant image be added? (Perhaps I need to call process.image twice in
the imagedata template, then have some sort of condition in
process.image to determine whether to swap "src" and "data-original"?)
DAVID GOSS | Technical Writer
P 1.800.876.9218 x 345 | F 1.800.588.9866
dg...@mueller-inc.com
http://www.MuellerReports.com
-
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] Customizing the process.image template
Thank you Bob, that was the exact place I need to add the code I wanted.
It works perfectly now.
-David
-Original Message-
From: Bob Stayton [mailto:b...@sagehill.net]
Sent: Friday, June 08, 2012 1:00 PM
To: David Goss; DocBook Apps
Subject: Re: [docbook-apps] Customizing the process.image template
Hi David,
No need to call 'process.image' again. Since you have already copied it
to your customization layer, you can just add the extra element there.
Put it after these
lines:
which is just before the element would be output for an imagemap,
or at the very end of the template.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message -----
From: "David Goss"
To: "DocBook Apps"
Sent: Friday, June 08, 2012 8:42 AM
Subject: [docbook-apps] Customizing the process.image template
Hi,
I'm using the [Lazy Load](http://www.appelsiini.net/projects/lazyload)
JQuery plugin to help out on some image-heavy docbook articles. I
basically just copy/pasted the process.image template to my
customization later and made these changes ("data-original" was "src"
and the last two attributes are my additions):
../img/common/placeholder.png
lazy
It works just fine, that's not the problem. I want to make it degrade
gracefully (without JavaScript, only the placeholder image is
displayed). The way the plugin author recommends to do so is the place
an alternative in a tag after the image, like this:
My question is where/how in the process.image template should this
redundant image be added? (Perhaps I need to call process.image twice in
the imagedata template, then have some sort of condition in
process.image to determine whether to swap "src" and "data-original"?)
DAVID GOSS | Technical Writer
P 1.800.876.9218 x 345 | F 1.800.588.9866
dg...@mueller-inc.com
http://www.MuellerReports.com
-
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] Using DiffMk with Docbook
Hi, I hope this question is within the scope of this list. I'm trying to use [DiffMk](http://sourceforge.net/projects/diffmk/) to compare two version of a file checked out from SVN, and I'm having all sorts of problems getting it to work in Cygwin. I'm following [Bob's directions in the XSL Guide](http://www.sagehill.net/docbookxsl/Changebars.html#d0e50355), but there are a few problems + I'm plagued by "Could not find or load main class" errors + There is no diffmk.xml (or config/) in the DiffMk distribution Does anyone have this program working in Cygwin and might be able to offer some advice, or know of an alternative that might work better? Being able to generate revisionflags between versions would be more useful than sliced bread is for sandwich making. DAVID GOSS | Technical Writer P 1.800.876.9218 x 345 | F 1.800.588.9866 dg...@mueller-inc.com http://www.MuellerReports.com - 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] Possible (brief?) {www.}docbook.org and wiki.docbook.org downtime
Hi,
I'm encountering an error, "Element caption in namespace
'http://docbook.org/ns/docbook' encountered in figure, but no template
matches" whenever I try to build documents that previously built without
a hitch. Could this problem be caused by docbook.org server changes?
-David
-Original Message-
From: Norman Walsh [mailto:n...@nwalsh.com]
Sent: Thursday, July 26, 2012 9:10 AM
To: docb...@lists.oasis-open.org; docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] Possible (brief?) {www.}docbook.org and
wiki.docbook.org downtime
Hi folks,
I'm moving the DNS for {www.}docbook.org and wiki.docbook.org around
today.
There may be some short period of downtime. Or not. Hard for me to say.
In theory, if you get the current DNS entries, you'll go to the current
sites and as the new DNS entries propagate, you'll go to the new sites.
So, with luck, you'll never notice.
But if you do, well, it's me again :-)
Be seeing you,
norm
--
Norman Walsh | Nothing ever gets anywhere. The
http://www.oasis-open.org/docbook/ | earth keeps turning round and gets
Chair, DocBook Technical Committee | nowhere. The moment is the only
| thing that counts.--Jean Cocteau
-
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] Possible (brief?) {www.}docbook.org and wiki.docbook.org downtime
No, I haven't changed my customizations in awhile.
I've been using the stock sheets that come with Cygwin. I looked and
notice that those files had been modified in the past few days (must
have been updated and I didn't notice). I downloaded the stylesheets
from the Sourceforge site.
It looks like I'm encountering this problem with the 1.77.x sheets but
1.76.1 works fine. I tried pull out all of my customizations out and
just using the stock 1.77.1 sheets and still encountered this error. I
have figure/caption/para, which looks to be valid, so maybe this is a
stylesheet bug?
-David
-Original Message-
From: Norman Walsh [mailto:n...@nwalsh.com]
Sent: Thursday, July 26, 2012 8:21 PM
To: David Goss
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Possible (brief?) {www.}docbook.org and
wiki.docbook.org downtime
"David Goss" writes:
> I'm encountering an error, "Element caption in namespace
> 'http://docbook.org/ns/docbook' encountered in figure, but no template
> matches" whenever I try to build documents that previously built
> without a hitch. Could this problem be caused by docbook.org server
changes?
I *really* don't think so. That sounds like a stylesheet problem. Did
you change your stylesheets recently?
Be seeing you,
norm
--
Norman Walsh | He who will not reason is a bigot;
http://www.oasis-open.org/docbook/ | he who cannot is a fool; and he
Chair, DocBook Technical Committee | who dares not is a slave.--Sir
| William Drummond
-
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] export from MS Excel to DocBook?
I did something like this recently to take some spreadsheets (or rather
tab-delimited data from them) and format it in LaTeX. I'm not a programmer, so
my skills doing something like this are pretty crude. I used this bit of Lua
code to pull data from a tab-delimited text file produced by Excel and read it
into a Lua table. In your case, you could use the LuaXML library to write data
from the table to a Docbook file as you see fit.
function string:split( inSplitPattern, outResults )
if not outResults then
outResults = { }
end
local theStart = 1
local theSplitStart, theSplitEnd = string.find( self,
inSplitPattern, theStart )
while theSplitStart do
table.insert( outResults, string.sub( self, theStart,
theSplitStart-1 ) )
theStart = theSplitEnd + 1
theSplitStart, theSplitEnd = string.find( self,
inSplitPattern, theStart )
end
table.insert( outResults, string.sub( self, theStart ) )
return outResults
end
-- table to hold data
local data = {}
local file = assert(io.open(arg[2], "r"), "Error error reading file")
line = file:read("*line")
repeat
table.insert(data, line:split("\t"))
line = file:read("*line")
until line==nil
file:flush()
file:close()
Again, not elegant, but it worked out for me.
-David
-Original Message-
From: robert.buer...@bmw.de [mailto:robert.buer...@bmw.de]
Sent: Thursday, August 16, 2012 3:24 AM
To: docbook-apps@lists.oasis-open.org
Subject: [docbook-apps] export from MS Excel to DocBook?
Hi all,
I've got a large number of text paragraphs in a Excel spreadsheet.
I think about to convert the entries of the spreadsheet cells to a docbook file
using the XML capabilities of the newer Excel versions.
My Excel looks like this:
Heading 1 | | | |
| Text a| | |
| Text b| | |
| | Heading 2 | |
| | | Text c|
| | | Text d|
This should go in something like this:
Heading 1
Text a
Text b
Heading 2
Text a
Text b
Has anybody any experience with this? Any pointers?
Best regards
Robert Bürgel
-
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] Custom css with webhelp
I want to use a custom CSS file with webhelp output. I'm using Oxygen. I set the html.stylesheet parameter and pointed it to a custom CSS file. In my output, however, the CSS is not linked. I only see one for css in the output, which is for tocWDiv.css. Does the html.stylesheet parameter not work the way I'm expecting it to with webhelp? --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - 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] Ajax HTML format wanted
Personally, I think docbook's HTML output can be very aesthetically pleasing, and so well designed that the sky is the limit with CSS. It's also technologically pleasing, displaying well in my browser of choice (elinks). In my antiquated opinion, web pages are documents, not applications. For our audiences, functionality is more important. Some of the clients we work with are in developing countries and are using very old hardware and slow, unreliable internet access. Even on a fast internet connection, a user can still hit CTRL+F faster than they can scroll around, clicking menus and pecking around to find the "hidden" text they're looking for. That said, I have experimented specifically with some of the things you're talking about. We tried working in things like thumbnails that float off to the side and expand when clicked, glossary entries that open in fancy-pants popups, etc. One of the most useful things we worked out was implementing the JQuery Lazy Load plugin, which waits to load images until you scroll down to them. It's possible to implement some of these things while still keeping pages accessible, sitting on top of docbook's output and degrading gracefully when the user doesn't want it. We don't have anything like that in our production documentation though because it breaks the accessibility and easy-of-use. I can dig around and see what I can pull up. There are a lot of possibilities with CSS and JQuery using Docbook, because the DOM in Docbook's output is so well structured. -David --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "Edwin Aldridge" To: docbook-apps@lists.oasis-open.org Sent: Thursday, April 25, 2013 5:56:31 AM Subject: [docbook-apps] Ajax HTML format wanted I am writing a set of docbook articles which I would like presented on the web but I find the HTML and XHTML formats really clunky. Aesthetics asice, they certainly do not take advantage of the medium's capabilities and am looking for something a bit smarter. Does anyone know of, or would anyone be interested in developing, stylesheet variant which does something like the following: * present chapters down one side - just one level, definitely no tree structures dancing before your eyes * present first level sections as tabs across the top * present lower level sections as headings (writing to a limit of two levels is a useful discipline) * present sidebars on the side (like the FO transforms) but say as accordians * present foot notes and glossary terms as pinable popups onclick or mouseover This could also make use of the much wider screens now commonly available, e.g. giving lots of display room for sidebars. It would make better use of internal links and non-serial reading approaches (which readers often don#'t do with dead tree media and never do with the web). There are a few practical challenges - like making the doc display correctly when someone links to an internal URL, but I am sure this is not beyond the wit of someone with good JQuery skills (or similar). Does anyone know if there is anything out there like that? Or would anyone be interested enough to do something like this? Regards Edwin Aldridge - 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] Problem with "\" in WebHelp Search
Hi Morgan, What browser does this happen in? I'm not able to reproduce this issue using the 1.78.1 stylesheets. I tried in IE9 and FireFox 18. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "Morgan Hayward" To: docbook-apps@lists.oasis-open.org Sent: Wednesday, June 5, 2013 12:30:33 PM Subject: [docbook-apps] Problem with "\" in WebHelp Search Hi all, We recently started using the DocBook WebHelp templates to create an HTML version of our manuals that includes a search function. So far, the search function works great, but we noticed the sidebar disappears if your search query includes a backslash (\). You also can’t get the sidebar back unless you clear your browser cache completely and restart the browser. Has anyone encountered this problem before and, hopefully, fixed the issue? We’re using DocBook 1.78.0. Please let me know if you need any more information. Regards, Morgan
[docbook-apps] body.start.indent with mixed one and two column layout
Hi, I'm using the column.count.back property to change the layout for the index, glossary, etc for our manual to 2 columns. The problem is, this is inheriting the indent (body.start.indent, I assume) from the rest of the document. This creates a weird look where the back matter columns are intented. I know I can just do body.start.intent=0 to fix that, but I want to keep the indent elsewhere. I'm not sure what sure what template and/or parameters to customize so that body.start.indent=0 only if the current section is 2 columns, otherwise it is 4pc. Regards, David --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218
Re: [docbook-apps] body.start.indent with mixed one and two column layout
Thank you so much, Bob. That's exactly what I was looking for. In going back to my original output, you were right about the index. I was just seeing my other appendixes being indented awkwardly. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "Bob Stayton" To: "David Goss" , docbook-apps@lists.oasis-open.org Sent: Friday, June 7, 2013 11:52:29 AM Subject: Re: [docbook-apps] body.start.indent with mixed one and two column layout Hi David, You will need to customize the template named 'set.flow.properties' from fo/pagesetup.xsl. There is an xsl:choose statement in there that decides how to add that property to the fo:flow of each page-sequence. You can modify it to handle the elements or pageclasses you want to control. You'll notice that pageclass="index" is omitted, so you should not be getting indents in the index already. Bob Stayton Sagehill Enterprises b...@sagehill.net From: David Goss Sent: Friday, June 07, 2013 8:14 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] body.start.indent with mixed one and two column layout Hi, I'm using the column.count.back property to change the layout for the index, glossary, etc for our manual to 2 columns. The problem is, this is inheriting the indent (body.start.indent, I assume) from the rest of the document. This creates a weird look where the back matter columns are intented. I know I can just do body.start.intent=0 to fix that, but I want to keep the indent elsewhere. I'm not sure what sure what template and/or parameters to customize so that body.start.indent=0 only if the current section is 2 columns, otherwise it is 4pc. Regards, David --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218
[docbook-apps] Formatting section titles in an appendix
I'm running into a bit of difficulty formatting section titles within an appendix, without breaking titles in chapters. I'm attempting to format and children of an appendix to be different than those in chapters. Specifically + Section titles in an appendix shouldn't be numbered (but the Appendix itself *should* be numbered; basically, appendixes need a different numbering depth) + Section titles in an appendix need different font sizes and margins than those in chapters (i.e. different attribute set). I'm not sure where to actually customize these things in my customization and/or titlepage spec. Assistance pointing me in the right direction (or the applicable section in the XSL guide) would be greatly appreciated. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218
Re: [docbook-apps] Formatting section titles in an appendix
I hadn't thought of that approach, but simplesect actually should meet our needs. That's probably a lot easier than working out the necessary customizations. Simpleset is living up to its name! -David --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "Pc Thoms" To: "David Goss" , docbook-apps@lists.oasis-open.org Sent: Monday, August 19, 2013 2:24:04 PM Subject: Re: [docbook-apps] Formatting section titles in an appendix Hi David Would meet your requirements? http://docbook.org/tdg51/en/html/simplesect.html On Mon, Aug 19, 2013 at 3:16 PM, David Goss < g...@fstrf.org > wrote: I'm running into a bit of difficulty formatting section titles within an appendix, without breaking titles in chapters. I'm attempting to format and children of an appendix to be different than those in chapters. Specifically + Section titles in an appendix shouldn't be numbered (but the Appendix itself *should* be numbered; basically, appendixes need a different numbering depth) + Section titles in an appendix need different font sizes and margins than those in chapters (i.e. different attribute set). I'm not sure where to actually customize these things in my customization and/or titlepage spec. Assistance pointing me in the right direction (or the applicable section in the XSL guide) would be greatly appreciated. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218
[docbook-apps] Info element & title
I've noticed that the title element, when present in an info element does not always appear. For example: My Title Is fine, but the same scenario with a procedure instead of a chapter will not display the title in FO output. Moving the title to be a direct child of the procedure will display the title in the output as expected. I'm more or less curious if this behavior is intentional in docbook's design, and how, for elements where d:info/d:title is not displayed, is the appropriate way to display it in output. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218
[docbook-apps] Alt text not appearing in inlinemediaobject
I have the the following docbook 5 markup: Click the Execute button. It is outputting the following HTML : Click the button. I'm not sure why the alt text is not carrying over. Am I using the alt tag incorrectly or is this a bug? I'm using webhelp docbook-xsl-ns-1.78.1 . I did see this page in the XSL Guide: http://www.sagehill.net/docbookxsl/AltText.html But it looks to be for Docbook4. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218
Re: [docbook-apps] Alt text not appearing in inlinemediaobject
Thanks Thomas. I tried that solution, but I'm still not seeing the alt attribute in the output. Below is what I added to my customization (I marked the change from the original stylesheet--it's just 3 additional lines). http://www.w3.org/1998/Math/MathML";> http://www.w3.org/2000/svg";> No insertfile extension available. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "Thomas Schraitle" To: docbook-apps@lists.oasis-open.org Sent: Tuesday, October 29, 2013 12:20:08 PM Subject: Re: [docbook-apps] Alt text not appearing in inlinemediaobject Hi David, Am Dienstag, 29. Oktober 2013, 11:52:20 schrieb David Goss: > I have the the following docbook 5 markup: > Click the > Execute fileref="img/ldms/ldms_button_execute.png" > depth="1em"/> button. > > It is outputting the following HTML : > Click the src="img/ldms/ldms_button_execute.png" height="13"> > button. > > I'm not sure why the alt text is not carrying over. Am I using the alt tag > incorrectly or is this a bug? I'm using webhelp docbook-xsl-ns-1.78.1 . Your DocBook markup is perfectly correct. But it seems, there is a deficiancy about the handling of inlinemediaobject in the DocBook stylesheets. I suspect the html/graphics.xsl file in the "imagedata" template (lines 1250 - 1331). In this template rule, the "process.image" template is called and the "alt" parameter is passed. However, it is not checked against an inlinemediaobject with a possible alt element. I would propose this change: If you would like to give it a try, do the following: 1. Create a customization layer if you haven't done yet. If you don't know how, read one of the following URLs: http://www.sagehill.net/docbookxsl/CustomMethods.html#CustomizationLayer http://doccookbook.sf.net/html/en/dbc.common.dbcustomize.html 2. Copy the "imagedata" template from the original html/graphics.xsl template into your customization layer. 3. Search for the xsl:call-template line and apply the above "patch" (add the 2nd xsl:when test). 4. Transform your DocBook document and use your customization layer. > I did see this page in the XSL Guide: > http://www.sagehill.net/docbookxsl/AltText.html > But it looks to be for Docbook4. You can use this also in DocBook 5 as long as it is valid. -- Gruß/Regards Thomas Schraitle - 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] Alt text not appearing in inlinemediaobject
It looks like xsl/graphics.xsl was also missing this: Adding this, along with Thomas's suggestion fixed this problem. Thanks again for your help! --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "David Goss" To: "Thomas Schraitle" Cc: docbook-apps@lists.oasis-open.org Sent: Tuesday, October 29, 2013 12:47:41 PM Subject: Re: [docbook-apps] Alt text not appearing in inlinemediaobject Thanks Thomas. I tried that solution, but I'm still not seeing the alt attribute in the output. Below is what I added to my customization (I marked the change from the original stylesheet--it's just 3 additional lines). http://www.w3.org/1998/Math/MathML";> http://www.w3.org/2000/svg";> No insertfile extension available. --- David Goss, M.A. Technical Writer, Laboratory Division Frontier Science & Technology Research Foundation 4033 Maple Road Amherst, NY 14226 (716) 834-0900 x7218 - Original Message - From: "Thomas Schraitle" To: docbook-apps@lists.oasis-open.org Sent: Tuesday, October 29, 2013 12:20:08 PM Subject: Re: [docbook-apps] Alt text not appearing in inlinemediaobject Hi David, Am Dienstag, 29. Oktober 2013, 11:52:20 schrieb David Goss: > I have the the following docbook 5 markup: > Click the > Execute fileref="img/ldms/ldms_button_execute.png" > depth="1em"/> button. > > It is outputting the following HTML : > Click the src="img/ldms/ldms_button_execute.png" height="13"> > button. > > I'm not sure why the alt text is not carrying over. Am I using the alt tag > incorrectly or is this a bug? I'm using webhelp docbook-xsl-ns-1.78.1 . Your DocBook markup is perfectly correct. But it seems, there is a deficiancy about the handling of inlinemediaobject in the DocBook stylesheets. I suspect the html/graphics.xsl file in the "imagedata" template (lines 1250 - 1331). In this template rule, the "process.image" template is called and the "alt" parameter is passed. However, it is not checked against an inlinemediaobject with a possible alt element. I would propose this change: If you would like to give it a try, do the following: 1. Create a customization layer if you haven't done yet. If you don't know how, read one of the following URLs: http://www.sagehill.net/docbookxsl/CustomMethods.html#CustomizationLayer http://doccookbook.sf.net/html/en/dbc.common.dbcustomize.html 2. Copy the "imagedata" template from the original html/graphics.xsl template into your customization layer. 3. Search for the xsl:call-template line and apply the above "patch" (add the 2nd xsl:when test). 4. Transform your DocBook document and use your customization layer. > I did see this page in the XSL Guide: > http://www.sagehill.net/docbookxsl/AltText.html > But it looks to be for Docbook4. You can use this also in DocBook 5 as long as it is valid. -- Gruß/Regards Thomas Schraitle - 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] Adding an additional "section" between a sect1 and a sect2
I just wanted to point out the renderas ("render as") attribute, which actually
might be closer to what you're looking for. This would let you use section
levels correctly, but you could select individual ones to be formatted
differently, e.g.
Application Basics
Setting Up a Project
How to Setup a Project
...
See http://www.sagehill.net/docbookxsl/Typography.html#UsingRenderas
---
David Goss, M.A.
Technical Writer, Laboratory Division
Frontier Science & Technology Research Foundation
4033 Maple Road
Amherst, NY 14226
(716) 834-0900 x7218
- Original Message -
From: "Jen"
To: docbook-apps@lists.oasis-open.org
Sent: Thursday, November 28, 2013 5:32:43 AM
Subject: [docbook-apps] Adding an additional "section" between a sect1 and a
sect2
Hi,
I'm trying to convert an existing document to DocBook and I'm struggling with a
structure that is not (I think!) supported in DocBook (H3 between H1 and H2).
Right now, the layout of this section is (in HTML) something like:
Application Basics -> chapter name
Description of application.
Setting Up a Project
Short description of project setup, plus links to relevant topics.
Setting Up A Task
Short description of task setup, plus links to relevant topics.
How to Set Up a Project -> first "true" section
Procedure for setting up a project.
Now, I don't think this can work in DocBook, since you can't have
sect1>sect3>sect2... but I'd like to maintain the smaller headings in the
chapter introduction. Is there a tag that I can use for this? Worst case
scenario, I'll just have an , but I'd prefer to use a
dedicated tag so I could also change the font size and so on.
Thanks in advance,
Jen
[docbook-apps] Turning off admonition graphics
I would like for admonition graphics to not be displayed in both HTML and PDF output. Based on the documentation, this seems to be a trivial thing to accomplish. I simply set the following in my customization layers: And yet, the admonition graphics are still appearing in both HTML and FO output. Is this a bug in the 1.78.1 stylesheets? I actually thought the stylesheets were supposed to default to *not* displaying the admonition graphics? -- David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7218
[docbook-apps] Re: Turning off admonition graphics
Silly me, I've answered my own question. The issue was not with the stylesheets or my customization layer, but rather with oXygen. Apparently oXygen set up some parameters in the transformation scenarios that were overriding my own stylesheets. After removing those parameters, this problem (and a few other oddities) were fixed. ------ David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7218 - Original Message - From: "David Goss" To: docbook-apps@lists.oasis-open.org Sent: Wednesday, February 26, 2014 11:48:51 AM Subject: Turning off admonition graphics I would like for admonition graphics to not be displayed in both HTML and PDF output. Based on the documentation, this seems to be a trivial thing to accomplish. I simply set the following in my customization layers: And yet, the admonition graphics are still appearing in both HTML and FO output. Is this a bug in the 1.78.1 stylesheets? I actually thought the stylesheets were supposed to default to *not* displaying the admonition graphics? ------ David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7218
Re: [docbook-apps] FO index title formatting
I think what you want is this: all For any sections that are multiple columns, this will put the span all property in the outer fo:block, causing the title to span all columns. I think this is what you want. For more, see http://www.sagehill.net/docbookxsl/MultiColumns.html -- David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7218 - Original Message - From: "Gábor Kövesdán" To: docbook-apps@lists.oasis-open.org Sent: Wednesday, February 26, 2014 12:08:08 PM Subject: [docbook-apps] FO index title formatting Hi, I'm using a two-column setup but I want the second column to start below the title, in line with the first column. In other words, I want to typeset the title in a single column and have a two-column section below. As far as I see, the column count can only be set up by region in the page master and both the title and the actual index is part of region-body. Is there any way to render it in this way? Thanks, Gabor Kovesdan - 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] Redundant end tags been removed
Hi Barton, For an explanation of why self-closing tags can be an issue with browsers see this question on stack exchange: http://stackoverflow.com/questions/69913/why-dont-self-closing-script-tags-work -- David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7204 - Original Message - From: "Barton Wright" To: "Peter Fleck" Cc: "apps docbook" Sent: Wednesday, July 23, 2014 2:22:08 PM Subject: Re: [docbook-apps] Redundant end tags been removed Hello Peter, I’m confused why the version without the closing is a problem on any modern OS or browser. It’s a completely valid construction. Nevertheless, perhaps the addthis.com site is expecting some content inside the pair. You could place a space or even a non-breaking space character ( or its Unicode equivalent) just before the to see if that preserves the closing . Let us know what worked when you figure it out! > Hi guys, > > I'm trying to add the below to each chunked html page. > > src="//s7.addthis.com/js/300/addthis_widget.js#pubid=XXX"> > > > What happens is that the
Re: [docbook-apps] fop and embedding fonts
Do you have your conf file to set to look for system fonts: C:\Windows\Fonts If so, and if you have DroidSans available as a system font, it might be trying to pull the system version (which might an open type font, which FOP wouldn't support). I've always had bad luck with FOP's font configuration. The only success I've ever had is just installing the ttf version of the font on the system. -- David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7204 From: "Tim Arnold" To: "docbook-apps" Sent: Friday, December 12, 2014 10:44:42 AM Subject: [docbook-apps] fop and embedding fonts Hi, I'm attempting font-embedding with Apache FOP 1.1 with difficulties. Is there a tutorial on setting this up? In my xsl customization layer I set "body.font.family" to 'Droid'. Droid In my fo configuration file, I specify the TrueType font: specified in the renderer for application/pdf. When I compile the document, I don't see any errors or warnings, but Droid is not listed in the fonts, let alone being embedded. But the settings have some effect though, since the body text in the pdf has '#' for each character that is supposed to be in the body font. I am reading the fop fonts doc (with 1.1 the metrics are optional it says). http://xmlgraphics.apache.org/fop/1.1/fonts.html and the DocBook XSL Guide on fonts: http://www.sagehill.net/docbookxsl/AddFont.html Anyone see what I'm doing wrong? thanks, --Tim
Re: [docbook-apps] docbook -> docx
There is also the roundtrip stylesheets in the Docbook XSL distribution. These require that you use a subset of docbook elements. http://www.sagehill.net/docbookxsl/MSWord.html I haven't personally tried the roundtrip stuff. Whenever a non-technical person has asked for an "editable" version of a docbook file, I usually just copy/paste the HTML into Word, and explain the caveat that they should just ignore the formatting. ------ David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7204 From: "Peter Lavin" To: "Fredrik Unger" Cc: "docbook-apps" Sent: Friday, January 23, 2015 9:03:12 AM Subject: Re: [docbook-apps] docbook -> docx Hi Fredrik, pandoc does a decent job of converting DocBook to .docx. See: http://johnmacfarlane.net/pandoc/ and for a detailed review, http://www.objectorientedphp.com/articles/pandoc.html Peter On 23 January 2015 at 08:45, Fredrik Unger < f...@tree.se > wrote: Hi, I am looking into generating reports that has to be Word 2010. Now I am able to get reasonable results with a simple test file using python-docx, currently just writing the report in python. My plan would be : - Generate/write docbook file - Create docx file with styles as template in Word 2010 - Translate docbook -> docx using python-docx building a small python library This gives me the freedom to generate the reports in docbook xml using the tools in python, xml, templates etc. My current document contains, text, tables, images which all are supported in python-docx. Are there any better alternatives to this approach ? Thanks, Fredrik Unger -- -- - To unsubscribe, e-mail: docbook-apps-unsubscribe@ lists.oasis-open.org For additional commands, e-mail: docbook-apps-help@lists.oasis- open.org
Re: [docbook-apps] Note Box
Hi,
Docbook's default output is plain HTML, without styling. To add borders to
notes (and other style changes) for HTML output, you need to use a CSS
stylesheet. For notes, for example, you'd want to do something like:
div.note {
border: 1px solid black;
}
For more, see:
http://www.sagehill.net/docbookxsl/UsingCSS.html
------
David Goss , Technical Writer
Frontier Science | www.fstrf.org
4033 Maple Rd, Amherst, NY 14226
(716) 834-0900 extension 7204
- Original Message -
From: "Joydeep Chakrabarty"
To: "docbook-apps"
Sent: Sunday, January 25, 2015 10:29:58 AM
Subject: [docbook-apps] Note Box
Hello all,
I have been trying to write a docbook file. I am using element.
But I cannot see the note box (or borders) in my output html file. What
am I missing here? Here
is my code.
http://www.oasis-open.org/docbook/xml/4.5/
docbookx.dtd">
My first DocBook document
TEST DOCBOOK
This is Note
This is test.
Thanks.
-
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] ANNOUNCE: new solar book produced using Docbook
Hi Bob, Where there any elements in particular in the InDesign mock-ups that your designer provided that were difficult to implement in XSL for the PDF? Was there anything in particular that required some "creative" stylesheet workarounds? ------ David Goss , Technical Writer Frontier Science | www.fstrf.org 4033 Maple Rd, Amherst, NY 14226 (716) 834-0900 extension 7204 From: "Bob Stayton" To: "docbook-apps" Sent: Tuesday, July 7, 2015 5:16:46 PM Subject: [docbook-apps] ANNOUNCE: new solar book produced using Docbook You know me as the author of DocBook XSL: The Complete Guide . Now I have written another book on a completely different topic: solar energy. Since I produced my new book using DocBook, I'm taking this opportunity to tell the DocBook community about it, and I describe how I produced it at the end of this message. Replies about the DocBook process can go to the whole list if you think it's appropriate. If you want to reply about the book's content, please reply just to me so we don't burden the mailing list. I'm pleased to announce that my book Power Shift: From Fossil Energy to Dynamic Solar Power has been unleashed from its long development and is now available to the world. If you have any interest in solar energy, then you should read this book. Climate change researchers sometimes paint a bleak picture of our current global-warming crisis, but rarely explain how we got into this predicament in the first place and how we get out of it. Now, for the first time, my new book does just that. Power Shift retells human history through the lens of energy, explains the science behind the crisis--in clear, succinct language that anyone can understand—and provides a detailed blueprint for the future, from governmental, commercial, and individual perspectives. Wondering if the book is any good? Here is what others are saying: "Solar is surging all of a sudden, and if you read this comprehensive book you’ll understand why!" -- Bill McKibben, author of The End of Nature "An energy book that is a pleasure to read" -- Kirkus Reviews "visionary and brilliant" -- NASA Researcher Joe Jordan "Exceptionally well written" -- Midwest Book Review "lucid, convincing" -- Denis Hayes, organizer of the first Earth Day "points the way to a clean energy future" -- California Secretary of Natural Resources John Laird or check out the reader reviews on Amazon After teaching solar energy for many years, I spent over 15 years researching and writing this book, all while living the life in the off-grid solar home we built. This is my lifework. It has been a long road to publication. I handed out the first draft in January 2000, and many things have changed since then. Now I get to report on solar energy's success instead of just wishing for it. I'm self publishing the book, because as an unknown author I could not interest a publishing company, and because they don't offer much in the way of marketing for new authors anyway. So I started my own publishing company, Sandstone Publishing ( www.sandstonepublishing.com ) , whose catalog contains exactly one book. Now I get to market my book, an activity for which I am totally unsuited. My low-budget marketing plan consists of getting good reviews, and word of mouth. So if you read the book and like it, please write a review on Amazon or Goodreads, and tell your friends and family about it. Even climate skeptics can get something out of this book. The book is available in paperback and Kindle at Amazon , in paperback and Nook Book at Barnes & Noble , in iBooks at the Apple iTunes Store and in Kobo from Kobo Books . And if you can't afford one, convince me and I'll give you an Ebook copy. 8^) By the way, although you know me as Bob Stayton, I'm publishing the book under my full name Robert Arthur Stayton as a gesture to honor my father Chester Arthur Stayton, Jr. and my grandfather Chester Arthur Stayton, Sr., with whom I share my middle name. Producing Power Shift with DocBook I wrote the book in DocBook 5 using XMetal 7. I started off writing it in modular fashion, but found that it got in the way of continuity. This isn't technical documentation, after all. 8^) So I merged all the files into one big book file and finished the book that way. That allowed me to easily find something for cross referencing and to keep the narrative flow moving. Searches for indexterms were much easier in a single file, and I used XMetal macros to assist with inserting indexterms. I hired a book designer for the interior and implemented the specs from the InDesign file she gave me in DocBook XSL. From that I could generate the PDF for the book's interior. I had hoped to be able to show you the page design by referring to the Look Inside
Re: [docbook-apps] Pure JS WebHelp
It'd be great if you added this to Github. I'm especially interested to see if this could be adapted to provide features (search, side navigation, etc) to other tools that can only output HTML out of box. -------- David Goss, Business Analyst Frontier Science (www.frontierscience.org) LDMS (www.ldms.org) - Original Message - From: "Barton Wright" To: "Jan Tosovsky" Cc: "docbook-apps" Sent: Sunday, April 16, 2017 11:47:50 AM Subject: Re: [docbook-apps] Pure JS WebHelp Hi Jan, Thank you a thousand times for posting this work. I vote for an initial upload to GitHub. I notice you're using . Have you tried your XSL with structuring? Thanks! On Apr 16, 2017, at 10:46 AM, Jan Tosovsky wrote: Dear All, as promised, I've published a demo output https://www.bilyujezd.cz/beta/strucna-historie.html Core changes against the current WebHelp: - responsive design (Mobile First) - breadcrumb - improved ToC processing (ToC is linked, not embedded in every HTML file) - enhanced search related code (cleaning up the code for better maintenance) - enhanced translation support (all messages are stored in standard l10n XML files) - storing client state even on file system or localhost (utilizing HTML5 Local Storage) - removing jQuery and jQueryUI dependency Further features: - ability to enlarge downsized images (aka lightbox, especially useful for SVG images) - ability to copy links to specific anchors - SASS styling (interpreted into CSS) Weaknesses: - only modern browsers are supported (Chrome, FF, Edge, IE10+) - no custom params to override current bahavior - no out-of-the-box scripts for copying dependencies to the target destination Should I put related XSL files and resources to my GitHub account or directly to some DocBook sandbox? Thanks, Jan - 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
