From dave at badgers-in-foil.co.uk Thu Oct 14 10:01:20 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 14 Oct 2004 10:01:20 +0000 Subject: [docbook-css] The docbook-css docbook-css Message-ID: <20041014100119.GA11810@vhost.badgers-in-foil.co.uk> This list is for discussion of the Docbook CSS stylesheets found at http://www.badgers-in-foil.co.uk/projects/docbook-css/ If you would like to request a change, or report a bug, please post a message to the members of this mailing list. thanks, David Holroyd From dave at badgers-in-foil.co.uk Thu Oct 14 10:01:20 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 14 Oct 2004 10:01:20 +0000 Subject: [docbook-css] The docbook-css docbook-css Message-ID: <20041014100119.GA11810@vhost.badgers-in-foil.co.uk> This list is for discussion of the Docbook CSS stylesheets found at http://www.badgers-in-foil.co.uk/projects/docbook-css/ If you would like to request a change, or report a bug, please post a message to the members of this mailing list. thanks, David Holroyd _______________________________________________ docbook-css mailing list docbook-css@lists.badgers-in-foil.co.uk http://lists.badgers-in-foil.co.uk/mailman/listinfo/docbook-css From dave at badgers-in-foil.co.uk Thu Oct 14 11:14:34 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 14 Oct 2004 11:14:34 +0000 Subject: [docbook-css] Customisation layers Message-ID: <20041014111434.GB11810@vhost.badgers-in-foil.co.uk> I was going to allow for customisations be adding an extra @import to driver.css, like this: @import "core.css"; @import "tables.css"; @import "styles.css"; @import "mozilla.css"; @import "opera.css"; /* Local customisations to docbook-css should be added in local.css */ @import "local.css"; An example local.css would appear in the distribution files. Problem is, this means that someone unpacking a new set of distribution files would overwrite any changes to local.css in addition to updating the core stylesheets. I was thinking it would be better to just create a custom .css file for local changes, and have that @import "driver.css". This would make it a bit simpler to implement multiple customisation layers all sharing the same copy of docbook-css, too. Seems sensible? dave From martin.gautier at myrnham.co.uk Thu Oct 14 12:42:23 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Thu, 14 Oct 2004 13:42:23 +0100 Subject: [docbook-css] Customisation layers In-Reply-To: <20041014111434.GB11810@vhost.badgers-in-foil.co.uk> Message-ID: >> I was thinking it would be better to just create a custom .css file for local changes, and have that @import "driver.css". This would make it a bit simpler to implement multiple customisation layers all sharing the same copy of docbook-css, too. That would certainly be the most flexible method I can think of Mart From martin.gautier at myrnham.co.uk Thu Oct 14 12:45:41 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Thu, 14 Oct 2004 13:45:41 +0100 Subject: [docbook-css] List Config - Reply too Message-ID: When replying to list messages, the sender's email address is entered in the To: field of the email client. Would it be possible to adjust the list settings to have "docbook-css@lists.badgers-in-foil.co.uk" as the Reply-To field? Mart From dave at badgers-in-foil.co.uk Thu Oct 14 15:05:52 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 14 Oct 2004 15:05:52 +0000 Subject: [docbook-css] List Config - Reply too In-Reply-To: References: Message-ID: <20041014150551.GA14104@vhost.badgers-in-foil.co.uk> On Thu, Oct 14, 2004 at 01:45:41PM +0100, martin.gautier@myrnham.co.uk wrote: > When replying to list messages, the sender's email address is entered in > the To: field of the email client. > > Would it be possible to adjust the list settings to have > "docbook-css@lists.badgers-in-foil.co.uk" as the Reply-To field? I've see the 'Reply-To Munging Considered Harmful' / 'Reply-To Munging Considered Useful' debates out there, and my preference is for keeping things as they are. I hope Notes doesn't make it too much trouble to use the list this way (?). I'm blessed with a mailer that supports a 'reply to list' function, in addition to 'reply to sender' and 'reply to all'. The current list config lets me keep all of these options. dave From dave at badgers-in-foil.co.uk Thu Oct 14 15:12:46 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 14 Oct 2004 15:12:46 +0000 Subject: [docbook-css] Nicer Message-ID: <20041014151246.GB14104@vhost.badgers-in-foil.co.uk> This makes look a bit more like a key on a standard issue beige keyboard: keycap { padding-left: .2em; padding-right: .2em; border-style: solid; border-top-width: 2px; border-left-width: 3px; border-right-width: 3px; border-bottom-width: 5px; border-top-color: #eeeecc; border-left-color: #eeeecc; border-right-color: #999977; border-bottom-color: #999977; background-color: #ddddbb; } Might need to adjust the colour, as I've only checked in on my laptop (LCD). dave From dave at badgers-in-foil.co.uk Fri Oct 15 14:16:59 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Fri, 15 Oct 2004 14:16:59 +0000 Subject: [docbook-css] Internationalisation Message-ID: <20041015141658.GA3123@vhost.badgers-in-foil.co.uk> I just saw an example of someone rendering a Serbian document with the stylesheet: http://gnom-uzivo.prevod.org/dokumentacija/uputstvo/uputstvo2.xml This reminds me: there's lots of language specific generated content in the styleseet; this needs to be seperated out into locale-specific fragments. I also need to investigate the possibility of automatically selecting the correct content based on the document language (i.e. the :lang 'pseudo class' [1]) dave [1] http://www.w3.org/TR/CSS21/selector.html#lang From dave at badgers-in-foil.co.uk Sun Oct 17 23:34:17 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Sun, 17 Oct 2004 23:34:17 +0000 Subject: [docbook-css] [ANN] Docbook CSS 0.3 Released Message-ID: <20041017233417.GA16384@vhost.badgers-in-foil.co.uk> Version 0.3 of the Docbook CSS stylesheet is now available from the project page: http://www.badgers-in-foil.co.uk/projects/docbook-css/ Changes in this release: * Make work again in mozilla.org browsers. Invalid XBL will simply crash Mozilla in some cases; I spotted where I'd made a syntax error. * Make work in Opera. Opera has an '-o-link:' CSS attribute that is given a value from 'attr(url)'. * Stop the numbers on s within always being '0' in Mozilla (using a special mozilla hack). The html.css included with mozilla browsers includes a magic CSS attribute, '-moz-counter-reset: -html-counter 0;'. This seems to be required for correct list numbering. (Nested lists are untested.) * Add formatting for ; to match other admonitions. * Factor language-specific generated content into a 'localisation framework': There is now a file, 'l10n.css' that imports further, locale-specific stylesheet files. * Add some support for 'pl', 'de' and 'es' locales (in addition to 'en'). Some friends helped me with translation. * Nicer ; beige background, and borders to look more 'key-like'. * Give grey background and raised borders. * Avoids arrows in front of and , except when children of . * Make italic. * Extra 5% on left/right margins for admonitions, to set them off better from the main text. * Explicitly alter formatting of nested tags (mozilla seems not to support CSS for nested quoting). Specifying an attribute like, 'quotes: '"' '"' "'" "'";', mozilla picks up the first level quote characters, but doesn't use the second pair for nested quotes. Added a rule with selector 'quote quote { .. }' instead. Also, I've added further test cases, linked from the project page, and have tried to list some of the limitations inherent in using CSS with Docbook documents. David Holroyd From martin.gautier at myrnham.co.uk Mon Oct 18 20:14:48 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Mon, 18 Oct 2004 21:14:48 +0100 Subject: [docbook-css] [ANN] Docbook CSS 0.3 Released Message-ID: 0.3 looks good. The ulink stuff will be really helpful. Haven't got around to testing it yet... Getting s to work with proper numbering is a major tick off the to-do list too. Excellent work. Testing the s on my Windows box throws up an issue for me. important:before { /* way too dark to read text with purple background */ /* background-color: purple; */ /* plum seems to work better */ background-color: plum; } I pulled "plum" the table listed here: http://www.webcolors.freeserve.co.uk/names140.htm I like the enhancements to . I think the colours work quite well to give that "keyboard" look. The only issue for me is the fact that my customisation layer specifies "font-family=verdana" for the element which seems to reduce the line spacing such that the bottom of the keycap interferes with the top of the text in the next line. Setting " border-bottom-width: 3px;" and "font-size:smaller;" for keycap in my customisation layer fixes this though. I guess this comment would be a FAQ rather than a bug issue ;o) BTW. I've used "font-size:smaller;" for my guibutton too. I noticed the website mentions that CSS can't do TOCs. Having a TOC has been an issue for me and I've done some work on it recently. I can get a pop-up TOC to appear in Mozilla quite nicely. Unfortunately, at this stage, it interferes with the main text (ie. it pops up down the left hand side of the page) and needs code in the XML doc which works for the browser but makes the XML invalid. I have some ideas on fixing this and I'll get back to the list when I start looking at the problem again... Cheers Mart From martin.gautier at myrnham.co.uk Mon Oct 18 20:22:25 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Mon, 18 Oct 2004 21:22:25 +0100 Subject: [docbook-css] Different image resources for HTML & FO output Message-ID: Hiya The DocBook stylesheets have hard-coded support for the "role" attribute in the element such that authors can include multiple s with their own roles of "html" or "fo". This allows different image resolutions depending on the target. The stylesheets are built to support this. Here's an example: When viewing the XML through a browser with docbook-css you might not want to see both images. My customisation layer now includes: imageobject[role="fo"] { display: none; } which avoids the problem. Mart From dave at badgers-in-foil.co.uk Tue Oct 19 18:57:54 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Tue, 19 Oct 2004 18:57:54 +0000 Subject: [docbook-css] [ANN] Docbook CSS 0.3 Released In-Reply-To: References: Message-ID: <20041019185753.GA20944@vhost.badgers-in-foil.co.uk> On Mon, Oct 18, 2004 at 09:14:48PM +0100, martin.gautier@myrnham.co.uk wrote: > Testing the s on my Windows box throws up an issue for me. > > important:before { > /* way too dark to read text with purple background */ > /* background-color: purple; */ > /* plum seems to work better */ > background-color: plum; > } You're right. I've changed the stylesheet. > I like the enhancements to . I think the colours work quite well > to give that "keyboard" look. The only issue for me is the fact that my > customisation layer specifies "font-family=verdana" for the element > which seems to reduce the line spacing such that the bottom of the keycap > interferes with the top of the text in the next line. Setting " > border-bottom-width: 3px;" and "font-size:smaller;" for keycap in my > customisation layer fixes this though. I guess this comment would be a FAQ > rather than a bug issue ;o) BTW. I've used "font-size:smaller;" for my > guibutton too. I've added font-size:smaller, and, splitting the difference, reduced the bottom border of keycap 4px. > I noticed the website mentions that CSS can't do TOCs. Having a TOC has > been an issue for me and I've done some work on it recently. I can get a > pop-up TOC to appear in Mozilla quite nicely. Unfortunately, at this > stage, it interferes with the main text (ie. it pops up down the left hand > side of the page) and needs code in the XML doc which works for the > browser but makes the XML invalid. I have some ideas on fixing this and > I'll get back to the list when I start looking at the problem again... I recall seeing an 'Outline' mozilla extension for HTML pages (I assume that this wouldn't require changes to the document to make it work). Maybe I'll have a poke at that, to see how it does its magic. dave From dave at badgers-in-foil.co.uk Tue Oct 19 20:08:00 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Tue, 19 Oct 2004 20:08:00 +0000 Subject: [docbook-css] Different image resources for HTML & FO output In-Reply-To: References: Message-ID: <20041019200800.GB20944@vhost.badgers-in-foil.co.uk> On Mon, Oct 18, 2004 at 09:22:25PM +0100, martin.gautier@myrnham.co.uk wrote: > The DocBook stylesheets have hard-coded support for the "role" attribute > in the element such that authors can include multiple > s with their own roles of "html" or "fo". This allows > different image resolutions depending on the target. The stylesheets are > built to support this. Here's an example: > > > fileref="figure\dialog_100.png"/> > fileref="figure\dialog_300.png"/> > > > When viewing the XML through a browser with docbook-css you might not want > to see both images. My customisation layer now includes: > > imageobject[role="fo"] { > display: none; > } This is a fair solution to the problem. However, I'm not sure that the possible values for 'role' are well-defined enough to blacklist all those that don't apply. Also, I think that some stylesheets are quite happy to just inspect the files and pick the media that tastes good, so it would be nice to try and cope with documents written assuming that behaviour. I was thinking about changing the XBL such that, rather than simply binding to all the elements, a binding is made to the containing . That binding would then, somehow, make a reasonable selection from the children. I was thinking it might be possible to implement a suck-it-and-see strategy, where the browser tries to load every , in order, until if finds one that loads successfully. Any solution that involves me writing vast amounts of mozilla-specific javascript is a solution I want to avoid, though. dave From martin.gautier at myrnham.co.uk Tue Oct 19 23:38:02 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Wed, 20 Oct 2004 00:38:02 +0100 Subject: [docbook-css] Different image resources for HTML & FO output In-Reply-To: <20041019200800.GB20944@vhost.badgers-in-foil.co.uk> Message-ID: >> I'm not sure that the possible values for 'role' are well-defined enough to blacklist all those that don't apply. In general I would agree. However do recall seeing comments in Bob Stayton's DocBook XSL book regarding the built-in support of "fo" and "html" for the specific use of . >> where the browser tries to load every I think specific javascript will always be a superior (technically) solution however, I agree that you'll probably want to avoid the overhead of maintaining large amounts of code. If people want an accurate representation in their borwser then I guess they can always run their XML through the HTML XSL stylesheets ;o) Mart From dave at badgers-in-foil.co.uk Wed Oct 20 00:37:37 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Wed, 20 Oct 2004 00:37:37 +0000 Subject: [docbook-css] Different image resources for HTML & FO output In-Reply-To: References: <20041019200800.GB20944@vhost.badgers-in-foil.co.uk> Message-ID: <20041020003731.GA23785@vhost.badgers-in-foil.co.uk> On Wed, Oct 20, 2004 at 12:38:02AM +0100, martin.gautier@myrnham.co.uk wrote: > > I'm not sure that the possible values for 'role' are well-defined > > enough to blacklist all those that don't apply. > > In general I would agree. However do recall seeing comments in Bob > Stayton's DocBook XSL book regarding the built-in support of "fo" and > "html" for the specific use of . Yeah, I spotted that here, http://www.sagehill.net/docbookxsl/GraphicSelection.html > > where the browser tries to load every > I think specific javascript will always be a superior (technically) > solution however, I agree that you'll probably want to avoid the overhead > of maintaining large amounts of code. If people want an accurate > representation in their borwser then I guess they can always run their XML > through the HTML XSL stylesheets ;o) I suppose that any image marked as suitable for [X]HTML output will do, so we could just turn the logic in your previous suggestion on its head: imageobject { display: none; } imageobject[role$=html] { display: block; } I've not tested that. Also, attr$=val is crazy-CSS3-syntax, and we currently claim (lie) that this is a CSS2 stylesheet. Soooo, maybe replace that last rule with: imageobject[role=html], imageobject[role=xhtml] { display: block; } Lets hope that authors don't include multiple s that match those rules just foil naive stylesheet implementors. dave From martin.gautier at myrnham.co.uk Wed Oct 20 20:29:27 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Wed, 20 Oct 2004 21:29:27 +0100 Subject: [docbook-css] Minor Table problem Message-ID:
When viewed in Mozilla, the following table doesn't render row 2 correctly.

I would have expected both the text and image to be aligned to the top of the row however, the image is rendered bottom aligned with the top of the text column aligned to the bottom of the image.

I haven't had a chance to look into this as yet so nothing else to report at this stage...

<table id="id1087516753703" frame="all">
                           <title></title>
                        <tgroup cols="3" colsep="0" rowsep="0" align="left">
                      <colspec colnum="1" colwidth="1.00cm" colname="col1"/>
                      <colspec colnum="2" colwidth="7.00cm" colname="col2"/>
                      <colspec colnum="3" colwidth="7.00cm" colname="col3"/>
                          <thead><row><entry colname="col1" valign="top" align="center"><para></para></entry><entry colname="col2" valign="top" align="center"><para>Steps</para></entry><entry colname="col3" valign="top" align="center"><para>Results</para></entry></row></thead>
                        <tbody>
                                <row>
                                <entry colname="col1" valign="top"><para>1</para></entry>
                                <entry colname="col2" valign="top">
                                        <para>Blah Blah Blah.</para>
                                </entry>
                                <entry colname="col3" valign="top">
                                        <para>Blah Blah Blah.<inlinemediaobject>
                                        <imageobject><imagedata fileref = "cc2-ug-100\dialog_splash.png" format = "PNG"/></imageobject>
                                        </inlinemediaobject></para>
                                </entry>
                                </row>
                                <row>
                                <entry colname="col1" valign="top"><para>2</para></entry>
                                <entry colname="col2" valign="top">
                                        <para><para>Blah Blah Blah.</para>
                                </entry>
                                <entry colname="col3" valign="top">
                                        <mediaobject><imageobject><imagedata format="PNG" fileref="cc2-ug-100\dialog_register.png"/></imageobject></mediaobject>
                                </entry>
                                </row>
                                <row>
                                <entry colname="col1" valign="top"><para>3</para></entry>
                                <entry colname="col2" valign="top">
                                        <para>Blah Blah Blah.</para>
                                </entry>
                                <entry colname="col3" valign="top">
                                        <para></para>
                                </entry>
                                </row>      
                        </tbody>
                        </tgroup>
                        </table> From martin.gautier at myrnham.co.uk Thu Oct 21 11:50:16 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Thu, 21 Oct 2004 12:50:16 +0100 Subject: [docbook-css] Minor Table problem In-Reply-To: <20041020232923.GB12124@vhost.badgers-in-foil.co.uk> Message-ID: --=_mixed 003D707980256F34_= Content-Type: text/plain; charset="US-ASCII" I noticed that by putting a   in front of my offending in the XML, I was able to get the valign="top" behaviour that was desired. Obviously, I didn't want to sully my XML with fixes for a presetation issue so I added the following to my customisation layer instead. inlinemediaobject:before { content:"\00A0"; } The image is now aligned as expected though it is slightly offset because of the  . the overall effect is acceptable. The solution feels a bit of a cludge but it works... Mart David Holroyd 21/10/2004 00:29 To: martin.gautier@myrnham.co.uk cc: Subject: Re: [docbook-css] Minor Table problem On Wed, Oct 20, 2004 at 09:29:27PM +0100, martin.gautier@myrnham.co.uk wrote: > When viewed in Mozilla, the following table doesn't render row 2 > correctly. > > I would have expected both the text and image to be aligned to the top > of the row however, the image is rendered bottom aligned with the top of > the text column aligned to the bottom of the image. Hmm, not sure I'm seeing exactly the same thing; maybe the proportions of images to the rest of the elements matters. I can see roughly the same thing -- text aligning to the bottom of the cell -- and I observe that I can produce a similar layout in Opera, if I add the following CSS: imagedata { border: 2px solid red; height: 50px; width: 50px; display: inline-block; } [Note that I also added a 1px border to , and removed the extra from the code you posted.] I attached the screenshot of Opera. I notice that the stylesheet currently lacks any display: property for , though setting this explicity to 'block' didn't seem to change the layout. Hmmm... dave --=_mixed 003D707980256F34_= Content-Type: application/octet-stream; name="table_valign_shot.png" Content-Disposition: attachment; filename="table_valign_shot.png" Content-Transfer-Encoding: base64 iVBORw0KGgoAAAANSUhEUgAAAPsAAADOCAIAAAB3p+PvAAAABmJLR0QA/wD/AP+gvaeTAAAACXBI WXMAABBfAAAQcgFxTIhMAAAAB3RJTUUH1AoUFxUtu7MjZAAAEC1JREFUeJzt3XtYVGUeB/DfmRsg 4BXBC3kFsXUz80KoZWxeMiUvK2pqmqtIkYqXrNwsL7VpuZpmImbqapvmKukmq+1juVvb7rNoGIli 3moNFENCBGYGmMt5948j4+EMM0AyzHDe7+fxjzmXOe/hd768886Z4VVgjBEANzTePgGARoXEA1+Q eOCLTr4gCIK3zgPAc+RvVnVuttVK+g3Be98GhJI2OEU/jlEN8AWJB74g8cAXJB7uKLlRUCF6+yQ8 rPESz+xlGRkZN21qr2gTxOzGl5+fOyI6omVYuyM3y6tWqvN6NXDibaYLKxLGdAttodX6den9yDNP dQ//zV+kTWV5mwYOHPjPW5UN26K6/XRitCCj0WiDWrUbNHrm8XxzQzbDbKczPv3s6+/l61R7vZiM YrFWzkdIurcVET367Iodf9q+atG0tnqtzi/8lk20VeS/MDCMiNIKzfVqgjeKktrMuUe3T5FWbt6T dujAh0lDOxBR8y5zG7Zd0VYmtSJdIDVdL2XI3Wyry7HkT6m49YW05uPT16U1xef2dvTTv/LdpdCA ajf+i60iY/b09Qvu69RGpzHc02vwG/uypackTBn7QI+OWkF4aERM6wCdX/MO4+atv2UTGWMVN79O jo9t1zzAcZxF39/6BSXwZc6diLkwTb7SmJ9KRIImoGp7zWWssVaTx4z4dfeOekFIKzQXZa8ZGRvT OayF48iOxNstN5yvV9MtvgcTb6/MDzNopZWtwnuOfnLOH9/b903Oz0y0ZmVlSevX/TMjKyvLxlhO yhNENPr1HYc+2qAVBEHQpuSVMcYef6irtOf9kxa9v3Pb9P5tiShy2n7G2PzIlkQ0bvX29E/+snT6 ICIamn7ll1fCJ7lJfGFh4fXc8+8m9SaiFl0XSFtdlbHGWi1JHO6I9a1Lu2bFdZM3d6ePr+l6Nd3i ezDxjLEfDr/Zt1Nzefeg0TZLSM1m8oIyxhgb2dqfqhu09TvGmGgrke9ZXnSEiARtwNVKW2u9hoja 3Bc7J/mljVt3b3j7zxd/rqh/BXyam8Q7hPWNO5JbJm11VcaaayVWymtrvrGn5sTXtNh0i+/BxNst BWtX7GLMnpuTsfe99c9NH9ethYGI9M2imFMF/TUCEf3hq2++q3KlqEJ+2Nt7ihXSYnpR+WfLxxs0 1T4xHpiUVu8C+DY3iT9z6mB7g5aIuozb6tjqqoyualUt8dXHS+4T33SL78HEM9ESGaAf9frfHCtK c9cRkS4gwrHz/kJzZcnZSpGNaRNARKP2f88YY8y++XeJ+04Uyg8r1bosdysRafSti6zi1jdf3Xn8 v8fS095PWZ8U35uINLoW9Tph3+cm8YyxC7unSo/npf8obXVVRle1kr5ksu+GmTFmKvhIOpooa1qR eMf1arrF92TiGfswOoyIuj8yac2mbbu2vzs1JpSIhiz7N6t6WewzbXa/Nv6PrMu+sGMSEen8wp99 Ydmsx6MEjWH96SL5YQdMWbjh7dXDOgUR0X1JnzLGpoUGavVtJj/3+w3vbFg8rR8RhfZf+QtK4MsU JbVbijI+niOt3HvifIUorh3WkYj0zXqmnbhoZ8xVGV3Vql+wgYgin5gx5+kJPdrcHhHNW5v6n79v kx7P/OBYiU1kTter6Rbfs4n/38HhLSMWJI59qG2QQdAYOvUa/PuUT+2MMcb+mjxUJwiCxv/B8Qsu mKyMseNbXnyga4hG0IRFxqw+cE5x2L4xv2qm0wS0Cp+0OMVkFxlj6bEdHS+pQSGdx8xZ9X25rV4n 7PsUJb2eMUo+kDhSVG4xnukTZJAWfyi3MRdldFWry2krenVoLgja0O59n1maQDXZft3InK5X0y2+ IqICk30xVRCqLdaqvl9ttZnLLPrAZnr3H3sxQdAQ0YFCc3xIgNs9Vcinvi1ct+vl6xSpbtQfRtcs uNby/fndF6QHqevfyzZZPX9S4FJdrleT06h9fF307NnT8XjqsZPLq9/rVD2f6uPVQZFqn0s851DS BufNUQ2A1yHxwBckHviCxANflO9cvXgqAB6Cd67ALyQe+II5yXwLStrgMCcZcA2JB74g8cAXJB74 0qiJZ7bSrw4r/07ZWV52JhrytRNQT0Nu/lqEMXZy4/KJI4fc08qvxpl6FEe4mbN7Rmx7IooYOiFp 3vy5SYmTx414+InZx6+ZGGPGa/vi+4c4NyFX+uOeiQ+Gu99HlQ05oKSeKGm1RTfbJOYbX5CLuamc f2eM+VuISPpDSUn2rrHBnRKkx2XXNtV6oiVXVtflh1FfQxKU1BMllS/WPqoJaPtInV8wSKMPJaLm 2jt3QLs9NtqUv196rDV0qPUI+sBIPhvy+gmor6EaKT+BakC2SlPuhVOpS1/r8/R2562XPlm35vP8 FmS8mHU2cuLqjQtiq7YIRPRTxt5lW46aK0wXMs/1n7tz2/ODuWrI6yegvobucNP/y9fXcVTjPIFW SJ8p541W+VbGmNV0NkirLbczxlhl6UlB0HxrtMj3Sd6QXikyxlhRzlKtIcy5afU1hJJ6rqTyRY/c q2GMMVG0lBvzzp+YpP98UPQSxQ5av85vp6T7a4iIDMEDGBMvl9vkO7yzMM4gEBEFhPa3Wwr4acjr J6C+hhQ8NqoRBL1/YHhU9JoDC7Z0eSWjbG1MsOHORm3QrBm9drz50ql8W0jrYDTkWyegvoZkPDiO l2h0gUSkrf5tHmY3junR675N/92y9NdE9PqqVWjIB09AfQ1RXT6BYqKJiExinb7NJ1pvENF1S9V/ pcJse5dsbtN76YAgveNQ5SJZjJlHrxqfHB5FRKWXjxGRuer4TCyX9pEvOv/nROpoKPfwWwmLU9xX Vh0/qQ+V1M0YnzF2amfK4qeiiShy0qJNqX91fk8gf0pxzgczH21PRGH9RsxKfGb2jCnDBvcZ+dSL OWUWxpgxP23u2K5EFPvsy9kma2risHYRMROnTp+/andybES76Lg1e84Y8w4uio8gotjnXj1WXFF0 et/CCd2JaOj8lZllFvU1dGhouNYQVmS1o6QeLak8tJivxptEa9GlAv+o8EDHGpT0LtVY0mohR+J9 Ckra4DBDE3ANiQe+ePzuJNwV359PpakNwNDHA1/QxzcFvtmP+v7rT03QxwNfkHjgCxIPfEHigS9I PPAFiQe+IPHAFyQe+ILEA1+QeOALEg98QeKBL0g88AWJB74g8cAXJB74gsQDX5B44AsSD3xB4oEv SDzwBYkHviDxwBckHviCxANfkHjgCxIPfEHigS9IPPAFiQe+IPHAFyQe+ILEA1+QeOALEg98QeKB L0g88AWJB74g8cAXJB74gsQDX5B44AsSD3xB4oEvSDzwBYkHviDxwBckHviCxANfdN4+AagDQfD2 GagH+njgC/p438aYt89AbdDHA1+QeOALEg98QeKBL0g88AWJB74ITHb/S8AnHaBG8pCjjwe+KD+B YvX5yEN6TajXU8A9lLTBKUYu6OOBL0g88AXfq/Ftvn8voakNwNDHA1/QxzcFvtmP+v7rT03QxwNf kHjgCxIPfEHigS9IPPAFiQe+IPHAFyQe+ILEA1+QeOALEg98QeKBL0g88AWJB74g8cAXJB74gsQD X5B44AsSD3xB4oEvSDzwBYkHviDxwBckHviCxANfkHjgCxIPfEHigS9IPPAFiQe+IPHAFyQe+ILE A1+QeOALEg98QeKBL0g88AWJB74g8cAXJB740qiJZ7bSrw6n1bpbXnYmGgJPYTKKxcqSbxdOGv5Y 3Ji4kb95/Hcr8iptrDrFEW7m7J4R256IIoZOSJo3f25S4uRxIx5+YvbxaybGmPHavvj+IYomFEp/ 3DPxwXD3+6iyIQflRSFidX5uY/Plc5NRhtz1NnFOZMvNJwukhS//ENNp1E7nYykOZ8zfQkQlNtGx JnvX2OBOCdLjsmubar32JVdW1yUf6mtIgsQ3OEXxXY5qKku+fP/SrZbtm0mL/eckXf1sSa2vGBp9 KBE11wqONd0eG23K3y891ho61HoEfWBkrfuosiFoHDpXGwyB94+M6nz6qnlaeBARVRSd0vndU69D 2ypNuRdOpS59rc/T2523Xvpk3ZrP81uQ8WLW2ciJqzcuiK3aIhDRTxl7l205aq4wXcg813/uzm3P D+aqIfAgN/2/3PZh4fcm/cP59ULxFHOh8m1cSJ8p541W+VbGmNV0NkirLbczxlhl6UlB0HxrtMj3 Sd6QXikyxlhRzlKtIcz5fNTXUM0l9eWRgy+fmwzVcVQjd/3LlcmnexzdMKQev0WiaCk35p0/MUn/ +aBo5XBI69f57ZR0fw0RkSF4AGPi5XKbfId3FsYZBCKigND+dksBPw2Bp7kc1TiUXflk2KS/Hfjm yy5+2nocWBD0/oHhUdFrDizY0uWVjLK1McGGOxu1QbNm9Nrx5kun8m0hrYN/wXmruSHwpFr6+MJT H46K/yDl23+NCg+0GrOmbP6u3g3oAolIKwjylcxuHNOj16Wo6Vs2rX9t5cr6HpOThsATXCeeWQ/9 MXFw8rEVqctaFlzMyvzPWzN/6zc4xP3hROsNIrpuEasOYtu7ZHOb3ksHBOmJiIkmIioXyWLMPHrV +OTwKCIqvXyMiMxi1RBWLJf2kS9WiKSgjoZyD7+VsDiFua8pEQmCL/5rolyN8Z3fsQmCJsdkVewv f0pxzgczH21PRGH9RsxKfGb2jCnDBvcZ+dSLOWUWxpgxP23u2K5EFPvsy9kma2risHYRMROnTp+/ andybES76Lg1e84Y8w4uio8gotjnXj1WXFF0et/CCd2JaOj8lZllFvU1dGhouNYQVmS1uyrp7XeH vvzP5ylCLrCqKhORIFRbrJUgCNLh6vlbBreJ1qJLBf5R4YGONShpg1OkGon3LShpg1OkGt+dBL4g 8cAXJB74gsQDX5B44IvyXo0XTwXAQ3CvBvil/CYZ7sd7F0ra4BQjF/TxwBckHviCxANfkHjgC2Zo ahoNQYNx801ic8FXc8aOHh8/MX583JARUz8+W+z8zWP5U9Q3cZL3Z2iCu6YMuZttMzsFrzl3U3pc cPItfWCvn2V/u8AwQ1MjzNAEd01RT3ejmqxiNqTj7T9WCLl/htWUc85sc7M/qXHiJMzQpDLu5jLI Ki4RtBoisfB/Z3a98XT3Mesebm5ws7+C+iZOwgxNauCm/2eMXc8YJe3W7dGkvIpaZlplapw4ycsz NMFdo7qPaoio3YCDVrvtxg+npjQ70m/Iynr8Fqlr4qRGawg8zeWoRrTYNAYdafx0RG279l2+56M3 Wgw+WbY8OlhfpwOrb+IkzNCkCi77+Oi2rTLKLI5FXUAEEenrf/tefRMnYYamJs1lhO9tIRw+V+xY /GLj9E6j33kgsJYOXh0TJzVaQ3WdoQkakKsxfvnPJxc+GTdm/ITJkydPGDc64ZVt8nvSjv3lT1HN xEmN1lDtMzTBXVPUE/PVeBNmaGoEmKHJp6GkDQ4zNAHXkHjgCxIPfEHigS9IPPAFMzSB+lUL+T/+ 9bUXTwWgkek0osnb5wDQeP4P1eoc2jkvp30AAAAASUVORK5CYII= --=_mixed 003D707980256F34_=-- From martin.gautier at myrnham.co.uk Thu Oct 21 11:35:27 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Thu, 21 Oct 2004 12:35:27 +0100 Subject: Fw: [docbook-css] Minor Table problem Message-ID: Looks like the reply only came in to me. As the example stands, the XML is properly processed by XSLT for HTML and PDF output. The images are aligned as one would expect. The problem is for XML viewed with CSS only. The troublesome images _are_ larger than the column width I've set - I've not tried smaller images but David's earlier work implies that they work OK? Adding the valign="top" to the imagedata makes no difference to the CSS output unfortunately. My impression is that the problem is related to CSS and the Browser technology rather than the XML itself... Hmmm... Mart _______________________________________________ I just read in DocBook TDG that you can give the attribute valign='top' to the imagepath. Grtz Epco -----Oorspronkelijk bericht----- Van: docbook-css-admin@lists.badgers-in-foil.co.uk [mailto:docbook-css-admin@lists.badgers-in-foil.co.uk]Namens martin.gautier@myrnham.co.uk Verzonden: woensdag 20 oktober 2004 22:29 Aan: docbook-css@lists.badgers-in-foil.co.uk Onderwerp: [docbook-css] Minor Table problem When viewed in Mozilla, the following table doesn't render row 2 correctly. I would have expected both the text and image to be aligned to the top of the row however, the image is rendered bottom aligned with the top of the text column aligned to the bottom of the image. I haven't had a chance to look into this as yet so nothing else to report at this stage... From dave at badgers-in-foil.co.uk Thu Oct 21 12:24:37 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 21 Oct 2004 12:24:37 +0000 Subject: Fw: [docbook-css] Minor Table problem In-Reply-To: References: Message-ID: <20041021122436.GB23206@vhost.badgers-in-foil.co.uk> On Thu, Oct 21, 2004 at 12:35:27PM +0100, martin.gautier@myrnham.co.uk wrote: > The problem is for XML viewed with CSS only. The troublesome images _are_ > larger than the column width I've set - I've not tried smaller images but > David's earlier work implies that they work OK? > > Adding the valign="top" to the imagedata makes no difference to the CSS > output unfortunately. The CSS currently makes no use of any attributes on table-related elements, though it's probably possible to make use of 'valign', at least. You could try the following (I've no time to test): entry[valign=top] { vertical-align: top; } entry[valign=bottom] { vertical-align: bottom; } I didn't really spend any effort on doing tables 'right', I just tried to give the correct values for the display: property, so that the content wouldn't all just appear inline. > My impression is that the problem is related to CSS and the Browser > technology rather than the XML itself... My hunch is that; in the absence of any other instructions on how to vertically align things, it's trying to align cell content to some row-wide 'baseline'. That being the case, adding a newline before the image will mean that this cell contains two line-boxes, and probably other elements in the row are then vertically aligned to the baseline of the (empty) line-box above the image. Does any of that help? dave From martin.gautier at myrnham.co.uk Thu Oct 21 23:06:23 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Fri, 22 Oct 2004 00:06:23 +0100 Subject: [docbook-css] Support for sgmltag Message-ID: To support the element, I have added "sgmltag" to the following line entry in styles.css cmdsynopsis, code, command, computeroutput, envar, filename, keycode, keysym, literal, option, parameter, systemitem, sgmltag { font-family: monospace; } From martin.gautier at myrnham.co.uk Thu Oct 21 23:11:38 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Fri, 22 Oct 2004 00:11:38 +0100 Subject: Fw: [docbook-css] Minor Table problem In-Reply-To: <20041021122436.GB23206@vhost.badgers-in-foil.co.uk> Message-ID: Those entry styles seem to work well for me. Way better than my quick cludge... elements that contain text as well as images are aligned correctly as a elements with just images (which were the problematic ones). Thanks for that... Mart David Holroyd Sent by: docbook-css-admin@lists.badgers-in-foil.co.uk 21/10/2004 13:24 To: docbook-css@lists.badgers-in-foil.co.uk cc: Subject: Re: Fw: [docbook-css] Minor Table problem On Thu, Oct 21, 2004 at 12:35:27PM +0100, martin.gautier@myrnham.co.uk wrote: > The problem is for XML viewed with CSS only. The troublesome images _are_ > larger than the column width I've set - I've not tried smaller images but > David's earlier work implies that they work OK? > > Adding the valign="top" to the imagedata makes no difference to the CSS > output unfortunately. The CSS currently makes no use of any attributes on table-related elements, though it's probably possible to make use of 'valign', at least. You could try the following (I've no time to test): entry[valign=top] { vertical-align: top; } entry[valign=bottom] { vertical-align: bottom; } I didn't really spend any effort on doing tables 'right', I just tried to give the correct values for the display: property, so that the content wouldn't all just appear inline. > My impression is that the problem is related to CSS and the Browser > technology rather than the XML itself... My hunch is that; in the absence of any other instructions on how to vertically align things, it's trying to align cell content to some row-wide 'baseline'. That being the case, adding a newline before the image will mean that this cell contains two line-boxes, and probably other elements in the row are then vertically aligned to the baseline of the (empty) line-box above the image. Does any of that help? dave _______________________________________________ docbook-css mailing list docbook-css@lists.badgers-in-foil.co.uk http://lists.badgers-in-foil.co.uk/mailman/listinfo/docbook-css From dave at badgers-in-foil.co.uk Fri Oct 22 00:44:34 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Fri, 22 Oct 2004 00:44:34 +0000 Subject: [docbook-css] Support for sgmltag In-Reply-To: References: Message-ID: <20041022004433.GA759@vhost.badgers-in-foil.co.uk> On Fri, Oct 22, 2004 at 12:06:23AM +0100, martin.gautier@myrnham.co.uk wrote: > To support the element, I have added "sgmltag" to the following > line entry in styles.css > > cmdsynopsis, code, command, computeroutput, envar, filename, keycode, > keysym, > literal, option, parameter, systemitem, sgmltag { > font-family: monospace; > } Ok, I've added that in, and this reminded me that there are a bunch of possible 'class' attribute values going unhandled for . I've expanded the set to now look like this: sgmltag[class="starttag"]:before, sgmltag[class="emptytag"]:before { content: "<"; } sgmltag[class="starttag"]:after, sgmltag[class="endtag"]:after { content: ">"; } sgmltag[class="endtag"]:before { content: ""; } sgmltag[class="attvalue"]:before { content: '"'; } sgmltag[class="attvalue"]:after { content: '"'; } sgmltag[class="genentity"]:before { content: "&"; } sgmltag[class="genentity"]:after { content: ";"; } sgmltag[class="sgmlcomment"]:before { content: ""; } sgmltag[class="xmlpi"]:before { content: ""; } There's a few other values that I'd need to look up the punctuation for, like "paramentity", "pi" vs. "xmlpi". dave From martin.gautier at myrnham.co.uk Thu Oct 28 09:45:18 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Thu, 28 Oct 2004 10:45:18 +0100 Subject: [docbook-css] Heads up - Orderedlist numbering Message-ID: The following code is rendered such that listitem 3 of the orderedlist continues at 13 rather than 3. Mozilla seems to include the listitems from the itemizedlist when calculating the item number... Mart Create a partition occupying 2 GB of hard-disk space. Leave the remaining free space. Install Windows 2000 Server on the C drive in the default installation location. To start the Windows 2000 Server Setup program, you can either boot the computer from the Windows 2000 Server installation CD-ROM, create Setup Boot disks by using the appropriate command (Makeboot.exe or Makebt32.exe) and then boot from the Setup boot floppies, or create a network book disk and install from a network share. Use the following installation parameters: Convert or format the C drive to NTFS. Set the appropriate regional settings for your country. Enter the appropriate user name and organization for your environment. Specify the appropriate number of per-server licenses for all classroom computers to connect to this server. Use a computer name of ADDC#. (Start with 0, zero, for the instructor's computer.) Set the Administrator's password to password. Install the Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) networking services and the Remote Installation Services Windows 2000 components. Configure the date and time settings that are appropriate for your locale. Select Custom networking settings. Assign a static IP address that is unique on your network and an appropriate subnet mask. (We recommend using a dummy IP addressing scheme such as 200.200.200.#.) Leave the DNS server address blank. We'll be assigning it during class. Accept the default workgroup name. Finish the wizard. After the Setup program restarts the computer, log on to Windows 2000 Server as Administrator. Close the Windows 2000 Configure Your Server window. In the unpartitioned space, create one NTFS partition. Assign it the drive letter R. Create a local printer called Printer# on each computer, but don't share the printer! Extract the data files from the CD-ROM shipped with this book. From dave at badgers-in-foil.co.uk Thu Oct 28 10:07:53 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 28 Oct 2004 10:07:53 +0000 Subject: [docbook-css] Heads up - Orderedlist numbering In-Reply-To: References: Message-ID: <20041028100746.GA29022@vhost.badgers-in-foil.co.uk> On Thu, Oct 28, 2004 at 10:45:18AM +0100, martin.gautier@myrnham.co.uk wrote: > The following code is rendered such that listitem 3 of the orderedlist > continues at 13 rather than 3. Mozilla seems to include the listitems from > the itemizedlist when calculating the item number... It looks like the Mozilla CSS hack I added for needs to appear for any list-like element. I've extended the entry in mozilla.css to look like this: orderedlist, itemizedlist { /* this seems to be required to make auto-numbering work */ -moz-counter-reset: -html-counter 0; } Probably this should also be added to other things that are declaired to be list-like, using the proper CSS in styles.css. I've not spent the time to confirm this though. dave From martin.gautier at myrnham.co.uk Thu Oct 28 10:50:16 2004 From: martin.gautier at myrnham.co.uk (martin.gautier@myrnham.co.uk) Date: Thu, 28 Oct 2004 11:50:16 +0100 Subject: [docbook-css] TIFF Support Message-ID:
Browsers, by default, don't support TIFF images.

http://www.alternatiff.com seems to be the free cross-platform Browser plugin of choice that enables support for TIFF images within a HTML page.

Using the <html:img> tag however does not work.

http://www.alternatiff.com/howtoembed.html explains how to setup an HTML page that includes TIFFs. It looks to me like the following is the most generic:

<object width=200 height=200
  data="placeholder.tif" type="image/tiff">
 <param name="src" value="placeholder.tif">
 <param name="toolbar" value="none">
</object>

... where placeholder.tif is the image.

Is it possible to edit db-bindings.xml to include specific support for different image types?

I come across a lot of XML/DocBook documents that come with a pile of TIFFs (which are really good for creating PDFs for quality printing) and would love to be able to view them through CSS too.

Cheers

mart From dave at badgers-in-foil.co.uk Thu Oct 28 12:42:37 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Thu, 28 Oct 2004 12:42:37 +0000 Subject: [docbook-css] TIFF Support In-Reply-To: References: Message-ID: <20041028124236.GA31248@vhost.badgers-in-foil.co.uk> On Thu, Oct 28, 2004 at 11:50:16AM +0100, martin.gautier@myrnham.co.uk wrote: > Browsers, by default, don't support TIFF images. > > http://www.alternatiff.com seems to be the free cross-platform Browser > plugin of choice that enables support for TIFF images within a HTML page. > > Using the tag however does not work. > > http://www.alternatiff.com/howtoembed.html explains how to setup an HTML > page that includes TIFFs. It looks to me like the following is the most > generic: > > data="placeholder.tif" type="image/tiff"> > > > > > ... where placeholder.tif is the image. > > Is it possible to edit db-bindings.xml to include specific support for > different image types? > > I come across a lot of XML/DocBook documents that come with a pile of > TIFFs (which are really good for creating PDFs for quality printing) and > would love to be able to view them through CSS too. That should be possible, yes. I was thinking, along sililar lines, that it would be cool to try and detect if the browser suports SVG, and then add an html:iframe to inline the graphic file. There are special mozilla builds available that display SVG (even mixed inline with HTML). This will probably be one of the areas I'll hack on soon, but I'm currently in the process of writing a CSS parser (partly as a validation/documentation tool for this project), so it wont happen for a bit. dave From dave at badgers-in-foil.co.uk Fri Oct 29 11:06:33 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Fri, 29 Oct 2004 11:06:33 +0000 Subject: [docbook-css] CSS Reference Message-ID: <20041029110633.GA16952@vhost.badgers-in-foil.co.uk> On Thu, Oct 28, 2004 at 12:42:37PM +0000, David Holroyd wrote: > [...] I'm > currently in the process of writing a CSS parser (partly as a > validation/documentation tool for this project) [...] As evidence of the 'documentation' aspect, I've got the CSS grammar mostly done, and hacked up a quick syntax-highlighter script based on it last night. Output looks like this at the moment: http://www.badgers-in-foil.co.uk/projects/docbook-css/cssref/styles.html It links to DB:TDG and the W3 CSS2.1 spec, which may aid people trying to understand the stylesheets. I know there are two bugs in the output: - '(' incorrectly inserted after colours, like "#ffffff(" - '*' is missing from selectors The script still needs work to have it make cross-references for @import, etc. The other thing I want to do with the parser is compare a list of all docbook elements with the list of elements that docbook-css actually has styling for. We can use this to help compile a 'todo list' for the stylesheet. dave From dave at badgers-in-foil.co.uk Sat Oct 30 15:47:28 2004 From: dave at badgers-in-foil.co.uk (David Holroyd) Date: Sat, 30 Oct 2004 15:47:28 +0000 Subject: [docbook-css] CSS Reference In-Reply-To: <20041029110633.GA16952@vhost.badgers-in-foil.co.uk> References: <20041029110633.GA16952@vhost.badgers-in-foil.co.uk> Message-ID: <20041030154728.GA25849@vhost.badgers-in-foil.co.uk> On Fri, Oct 29, 2004 at 11:06:33AM +0000, David Holroyd wrote: > As evidence of the 'documentation' aspect, I've got the CSS grammar > mostly done, and hacked up a quick syntax-highlighter script based on > it last night. [...] > The script still needs work to have it make cross-references for > @import, etc. Now implemented: http://www.badgers-in-foil.co.uk/projects/docbook-css/cssref/stylesheet-driver.css.html dave