Re: DOCBOOK-APPS: Re: ignoring images width in HTML
Norman Walsh wrote: / Camille Bégnis [EMAIL PROTECTED] was heard to say: | I am using in my documents the same image format for both PDF and HTML | outputs (PNG). Though I want to specify the width for PDF output but | not for HTML. An option is to define two different imageobject but I | find much easier to change the XSL template for imageobject and ignore | the width. | | Can someone tell me the easier way to do so? Is it not possible to specify a width that would work in both places? unfortunately not. Especially for little paper formats. I suppose a stylesheet parameter to ignore image dimensions could be added... Probably yes. I have managed to ignore the width by heavily twicking the stylesheet, but this is not that clean :-) Camille.
Re: DOCBOOK-APPS: Ignoring image widths in HTML--a solution
Dennis Grace wrote: A couple weeks back, Camille posed this question: I am using in my documents the same image format for both PDF and HTML outputs (PNG). Though I want to specify the width for PDF output but not for HTML. An option is to define two different imageobject but I find much easier to change the XSL template for imageobject and ignore the width. Can someone tell me the easier way to do so? I've been working on solutions for the same problem. I, too, found the two-different-imageobjects solutions less than satisfactory (that whole dual source issue). the resolution trick is brilliant. Though it is not an option when you have more than one thousand images... So far, my best solution has been external to DocBook. In GIMP or PhotoShop, I can alter the resolution to find the optimum pixels/inch (pixels/mm) for a given size. An image that looks good in the browser at, say, 640 pixels wide will--at a resolution of 72 pixels/inch (2.8346 pixels/mm)--be too wide (8.9 in[225.8 mm]) for standard page outputs. Resetting the resolution to 110 pixels/inch (4.33 pixels/mm) reduces the print version to a printable width of 5.8 in ( 147.8 cm) while retaining the total pixel width unaffected for HTML output. Dennis Grace Information Developer IBM Linux Technology Center (512) 838-3937 T/L 678-3937 cell: (512)-296-7830 [EMAIL PROTECTED] There are only 10 kinds of people in the world: those who understand binary and those who don't.
DOCBOOK-APPS: Re: Ignoring image widths in HTML--a solution
On the dual resolution approach: We solved the problem of handling many images by creating high-but-welldefined resolution originals (PNGs) and rescale then via convert (belonging to ImageMagick) automatically, driven by a Makefile. Depending on the target (Web or Print) we use different scale factors. We put the formatted documents into seperate target directories and don't use any width specification at all. Sometimes not perfect and quite slow, but satisfactory. Jens Camille Bégnis [EMAIL PROTECTED] writes: Dennis Grace wrote: A couple weeks back, Camille posed this question: [...] the resolution trick is brilliant. Though it is not an option when you have more than one thousand images... So far, my best solution has been external to DocBook. In GIMP or PhotoShop, I can alter the resolution to find the optimum pixels/inch (pixels/mm) for a given size. An image that looks good in the browser at, say, 640 pixels wide will--at a resolution of 72 pixels/inch (2.8346 pixels/mm)--be too wide (8.9 in[225.8 mm]) for standard page outputs. Resetting the resolution to 110 pixels/inch (4.33 pixels/mm) reduces the print version to a printable width of 5.8 in ( 147.8 cm) while retaining the total pixel width unaffected for HTML output. Dennis Grace Information Developer IBM Linux Technology Center (512) 838-3937 T/L 678-3937 cell: (512)-296-7830 [EMAIL PROTECTED]
Re: DOCBOOK-APPS: default status (draft/final) for articles
Hi -- On Sun, 29 Sep 2002, Bob Stayton wrote: On Sun, Sep 29, 2002 at 04:32:50PM -0400, [EMAIL PROTECTED] wrote: Hello -- I've recently installed docbook-xsl-1.55, and found that the behavior seemed to have changed with regard to article documents, at some point since 1.48. Specifically, I'm now getting the -draft page-masters in my FO output, along with the draft watermark URL. This is curious. When I process your document with the 1.55.0 fo/docbook.xsl, I don't get draft output pages. Something is going on in your setup. I just deleted and reinstalled the 1.55.0 stylesheets, just in case, and I'm still getting the draft output. Strange. The only other variable I didn't mention is that I'm using Saxon, in case that plays a role (but I don't think it should). But the 1.48 run, which did not produce draft output, was also with Saxon. David -- David Alan Black | Register for RubyConf 2002! home: [EMAIL PROTECTED] | November 1-3 work: [EMAIL PROTECTED]| Seattle, WA, USA Web: http://pirate.shu.edu/~blackdav | http://www.rubyconf.com
DOCBOOK-APPS: Re: BUG: docbook-xsl-1.55.0/xhtml/chunk.xsl containsabsolute URL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Known bug. Fixed for the next release. / Mike Bresnahan [EMAIL PROTECTED] was heard to say: | I have found what appears to be a bug in the DocBook XSL stylesheets version | 1.55.0. The file docbook-xsl-1.55.0/xhtml/chunk.xsl contains the following | pair of xsl:import tags with absolute URLs. | |xsl:import | href=http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl; | / |xsl:import | href=http://docbook.sourceforge.net/release/xsl/current/html/chunk-common.x | sl / | | These URLs cause the XSLT engine (e.g. xsltproc) to download the referenced | files off the net. This results in a slow performance when a net connection | is present and a failure when no net connection exists. To fix the problem, | I replaced the above lines with: | |xsl:import href=docbook.xsl/ |xsl:import href=chunk-common.xsl/ | | Mike Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | One's never alone with a rubber http://www.oasis-open.org/docbook/ | duck. Chair, DocBook Technical Committee | -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE9mHQ0OyltUcwYWjsRAln1AKCOuX1ioIpvAfz8FiehVl+ziz/8ZQCfeZoV DMt589uCTyOf2Gkqy1VLvyI= =eZbj -END PGP SIGNATURE-
DOCBOOK-APPS: colwidth problem with instant saxon 6.5.2
hello, i have a problem concerning the colwidth attribute. when i set it, i get following error at transformation: No adjustColumnWidths function available. Processing terminated by xsl:message at line 337 i have set following parameters in my driver stylesheet: xsl:param name=saxon.extensions select=1/ xsl:param name=use.extensions select=1/ xsl:param name=tablecolumns.extension select=1/ i use instant_saxon 6.5.2 with docbook-xsl-1.55.0 (xml-4.2) on a win2k machine. has anybody encountered a similar problem (and solved it)? wbr, arno sosna p.s. i noticed, that xhtml/chunk.xsl contains following lines: xsl:import href=http://docbook.sourceforge.net/release/xsl/current/htm l/docbook.xsl/ xsl:import href=http://docbook.sourceforge.net/release/xsl/current/htm l/chunk-common.xsl/ why is it referencing to /html not /xhtml? i redirected it correctly in my catalog-file, but am still wondering, if it makes a difference.
DOCBOOK-APPS: [QUESTION] new head element for the website DTD
hello, i would like to use the following element within the header section of each HTM document. link href=/images/favicon.ico rel=SHORTCUT ICON/ that element changes the icon that appears beside a URL in the location bar of MS IE, Konqueror and Mozilla. is it possible to add that element to the next release of the website DTD? With best regards / Mit freundlichen Gruessen Daniel S. Haischt IT Consulting __ [revolutionary and alpha geek] Daniel S. Haischt Grabenstrasse 11 D-71083 Herrenberg G E R M A N Y FON: +49 -7032-992909 +49 -700-DHAISCHT FAX: +49 -7032-992910 CELLULAR: +49 -172-7668936 email: [EMAIL PROTECTED] web: http://www.daniel-s-haischt.biz -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS dx s:- a- C++ UB P+++ L E W+++ N+++ o-- K- w--- O++ M++ V- PS+ PE++ Y+ PGP++ t+++ 5+ X+++ R+ tv++ b+++ DI+ D+++ G e++ h-- r+ y+ --END GEEK CODE BLOCK--
Re: DOCBOOK-APPS: colwidth problem with instant saxon 6.5.2
Arno Sosna wrote: i use instant_saxon 6.5.2 with docbook-xsl-1.55.0 (xml-4.2) on a win2k machine. You must use full-fledged Saxon (no instant) and also add extensions/saxon651.jar file to your classpath. This JAR file contains code for extension used for column width adjusting. Jirka -- - Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz
DOCBOOK-APPS: [QUESTION] using the website stylesheets with the antstyle/xslt task
hello,
i tried to transform the website xml files using the
Xslt/Style that comes with ant. my task declaration
looks as follows.
--8---8---8
target name=website.postlayout depends=website.layout
style basedir=${src.dir}/documentation/website
destdir=${build.doc.website}
processor=trax
extension=.html
style=${website.chunk.driver}
includes=**/autolayout.xml
param name=xalan.extensions expression=1/
classpath refid=build.classpath/
/style
/target
--8---8---8
the classpath contains the xalan jars plus the jars
that contains the xsl and website extensions.
while executing this task, i am getting the error message
that the website-common.xsl stylesheet uses the exists()
extension method which couldn't be found.
my guessings are that the style task does not recognize
the param/ parameter.
is there anybody who was able to transform the website
xml files using the ant xslt task?
With best regards / Mit freundlichen Gruessen
Daniel S. Haischt IT Consulting
__
[revolutionary and alpha geek]
Daniel S. Haischt
Grabenstrasse 11
D-71083 Herrenberg
G E R M A N Y
FON: +49 -7032-992909
+49 -700-DHAISCHT
FAX: +49 -7032-992910
CELLULAR: +49 -172-7668936
email: [EMAIL PROTECTED]
web: http://www.daniel-s-haischt.biz
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS dx s:- a- C++ UB P+++ L E W+++ N+++ o-- K- w---
O++ M++ V- PS+ PE++ Y+ PGP++ t+++ 5+ X+++ R+ tv++ b+++ DI+ D+++
G e++ h-- r+ y+
--END GEEK CODE BLOCK--
