headers
Diane Larin | 1 Apr 2005 02:32
Picon

Re: Page X of Y in user.footer.navigation

I had a look at the 'process-chunk-element' template but I find
it quite cryptic (I don't have a lot of experience in writing/modifying
XSL stylesheets). I was expecting that I was not the first one to have 
this need and that a "recipe" would exist :-(

Diane Larin
INRO

On Wed, 30 Mar 2005, Bob Stayton wrote:

> I think this could be done by borrowing some of the chunkfast code.  
It
> precomputes a node-set of all the chunks.  Once you have that, you 
could
> count the nodes to get Y, and figure out the position of the current 
chunk
> in the node-set to get X.   Take a look at the first part of the 
template
> named 'process-chunk-element' in html/chunk-code.xsl.  It shows how to
> process nodes in the chunk node-set.
> 
> Bob Stayton
> Sagehill Enterprises
> DocBook Consulting
> bobs <at> sagehill.net
> 
> 
> ----- Original Message ----- 
> From: "Diane Larin" <diane <at> inro.ca>
> To: <bobs <at> sagehill.net>
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Austin | 1 Apr 2005 04:33

Vex is a DocBook Application in active development.

Does anyone here know of a good source for discussion on CSS as it
relates to DocBook ?

I am revising CSS stylesheets for Vex support for docbook.

Should I ask questions here ?

I am using the on-line version of DocBook TDG as a source of
info w.r.t. processing expectations and construction of selectors.

I am also using DocBook XSL as a reference implementation for
my stylesheets.

My first pass has been to review the DocBook testdocs for their support
in Vex. This has helped me improve 'tag coverage'.

I now use Cocoon & Fop to render these documents for comparison to
visual styling with Vex.

Anyone interested in checking out Vex with me ?

Tables and Images are coming in the next release (May ?)
Permalink | Reply | 0 comments |
headers
Michael Smith | 5 Apr 2005 06:44

Re: &uuml; and character number -> zvon.org

Sean Wheller <sean <at> enbaya.co.za> writes:

> What is the character code for &uuml; and can someone point to a reference so 
> I can figure this out by myself in future :-) The Unicode charts are endless.

  http://zvon.org/other/charSearch/PHP/search.php

Page for &uuml; (&#252; / &#xFC;) -

  http://zvon.org/other/charSearch/PHP/search.php?request=uuml&searchType=5

--

-- 
Michael Smith
http://logopoeia.com/  http://www.oreillynet.com/pub/au/890
Attachment (smime.p7s): application/x-pkcs7-signature, 2419 bytes
Permalink | Reply | 1 comment |
headers
Larry Garfield | 5 Apr 2005 07:24
Favicon

Re: Bug(?) in VERSION XSL file or in resolver?

Bob Stayton wrote:

> I don't believe the VERSION file is triggering access to the internet to
> read the DTD. If you are getting web accesses to the DTD instead of the
> stylesheet files, then the problem seems to be with the catalog resolution
> of the document's DOCTYPE identifiers.  I would be curious to see what the
> whole verbose output from the resolver looks like.

Hm, interesting syntactic trick.  So document('') is equivalent to /?

The following is a simplified version of the catalog file (mostly C&P 
from TCG), an excerpt from Ant, and the result of setting the verbosity 
level to 2.  (Anything more generated a lot more lines that didn't seem 
to have any relevant information, so I left it out to not abuse people's 
inboxes. <g>)

catalog.xml (simplified formatting)
-------------------------------

<?xml version="1.0"?>
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
<group  prefer="public"  xml:base="/usr/share/xml/docbook/schema/dtd/4.3/" >

<public publicId="-//OASIS//ELEMENTS DocBook XML HTML Tables V4.3//EN"
	uri="htmltblx.mod"/>
<public publicId="-//OASIS//DTD DocBook XML V4.3//EN"
	uri="docbookx.dtd"/>
<system
systemId="http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
uri="docbookx.dtd"/>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jens Barkvall | 5 Apr 2005 08:52
Picon

RE: Validate fails with customized profiling

I don't know what I do wrong because it doesn't work. The error I get is :

../book.xml:6: element para: validity error : No declaration for attribute
my_param of element para
Document ../book.xml does not validate
*** Error code 3
clearmake: Error: Build script failed for "validate"

Makefile:
------------
libxml2-2.6.7/bin/xmllint --nonet --catalogs --xinclude --postvalid --noout
$(BOOK)
--------------

XML:
----------
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE chapter SYSTEM "mydb.dtd">

<chapter>
  <title>My title</title>
  <para my_param="yes">
    bla bla
  </para>
</chapter>
---------------

DTD: (No I can't use version 4.2)
--------------
<!ENTITY % local.para.attrib "my_param CDATA #IMPLIED">
(Continue reading)

Permalink | Reply | 2 comments |
headers
Bob Stayton | 5 Apr 2005 10:12

Re: Bug(?) in VERSION XSL file or in resolver?

The stylesheet does not try to access the DTD, as far as I know.  It is
possible that the messages are buffered in memory, so the thing you think is
causing the delay is not those lines in the stylesheet file.  What do the
lines in the verbose output say when it is trying to resolve the DOCTYPE
identifier in the document?

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs <at> sagehill.net

----- Original Message ----- 
From: "Larry Garfield" <larry <at> garfieldtech.com>
To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
Sent: Monday, April 04, 2005 10:24 PM
Subject: Re: [docbook-apps] Bug(?) in VERSION XSL file or in resolver?

> Bob Stayton wrote:
>
> > I don't believe the VERSION file is triggering access to the internet to
> > read the DTD. If you are getting web accesses to the DTD instead of the
> > stylesheet files, then the problem seems to be with the catalog
resolution
> > of the document's DOCTYPE identifiers.  I would be curious to see what
the
> > whole verbose output from the resolver looks like.
>
> Hm, interesting syntactic trick.  So document('') is equivalent to /?
>
> The following is a simplified version of the catalog file (mostly C&P
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bob Stayton | 5 Apr 2005 10:14

Re: Validate fails with customized profiling

Hi Jens,
It works for me.  I notice that you are running clearmake, which means you
are using Clearcase, no?  Is it possible you are having a Clearcase view
problem?  Try running it on the command line without clearmake, which should
use the files in the current view.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs <at> sagehill.net

----- Original Message ----- 
From: "Jens Barkvall" <jens.barkvall <at> enea.se>
To: <docbook-apps <at> lists.oasis-open.org>
Sent: Monday, April 04, 2005 11:52 PM
Subject: RE: [docbook-apps] Validate fails with customized profiling

> I don't know what I do wrong because it doesn't work. The error I get is :
>
> ../book.xml:6: element para: validity error : No declaration for attribute
> my_param of element para
> Document ../book.xml does not validate
> *** Error code 3
> clearmake: Error: Build script failed for "validate"
>
> Makefile:
> ------------
>
libxml2-2.6.7/bin/xmllint --nonet --catalogs --xinclude --postvalid --noout
> $(BOOK)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Larry Garfield | 5 Apr 2005 12:16
Favicon

Re: Bug(?) in VERSION XSL file or in resolver?

I simplified the problem a bit by switching to a simple test document. 
The problem still appears, however.  Using the same catalog file before, 
and the following input file, it still hits the Oasis server but doesn't 
download as many files:

testbook.xml
----------------------------------------

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
	"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
<book>
	<bookinfo>
		<title>Test book</title>
		<author>
			<firstname>Some</firstname>
			<surname>Person</surname>
		</author>
	</bookinfo>
	<chapter>
		<title>Chain of command</title>
		<para>Moo.</para>
		<para>Meep.</para>
	</chapter>
</book>

--------------------------------

If, however, I change the Doctype declaration to read:

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bill Lawrence | 5 Apr 2005 17:36

Possible bug

I'm using the XEP formatter and using two-column output.  When I set 
pgwide="1" for either a table or informal table, I still get two-column 
tables.  I'm running the 1.68.1 stylesheets.

Thanks in advance,

Bill Lawrence
Permalink | Reply | 3 comments |
headers
Tristan Fiedler | 5 Apr 2005 18:03
Favicon

Symbols in HTML OK, PDF not OK

Hi All,

I am using
  	
	    <para>Here is alpha test 1 : <symbol 
role="symbolfont">&agr;</symbol> </para>
	    <para>Here is alpha test 2 : <symbol 
role="symbolfont">&alpha;</symbol> </para>
	    <para>Here is alpha test 3 :  <symbol 
role="symbolfont">&b.alpha;</symbol> </para>

	    <para>Here is beta test 1 :  <symbol 
role="symbolfont">&bgr;</symbol> </para>
	    <para>Here is beta test 2 :  <symbol 
role="symbolfont">&beta;</symbol> </para>
	    <para>Here is beta test 3 :  <symbol 
role="symbolfont">&b.beta;</symbol> </para>

But the resulting PDF is :

Here is alpha test 1 : α  -- correct
Here is alpha test 2 : α  -- correct
Here is alpha test 3 : ## -- incorrect **
Here is beta test 1 : β  -- correct
Here is beta test 2 : β  -- correct
Here is beta test 3 : ## -- incorrect **

And the resulting HTML is :

Here is alpha test 1 : α  -- correct
(Continue reading)

Permalink | Reply | 1 comment |

Gmane