On Wed, Mar 12, 2003 at 10:42:01AM -0500, Robert P. J. Day wrote:
currently, a key cap is written as keycapx/keycap. this
seems to suggest that a keycap is, by default, of type literal,
if i can call it that. and its content is x. so far, so good?
(one might even go as far as to suggest
--gxnQqCMJOKyxv5fW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Mar 12, 2003 at 10:53:53AM -0600, Jeff Biss wrote:
Here's my 2 cents:
=20
I see no reason that a procedure should be a child of a paragraph. The=20
On Tue, Mar 04, 2003 at 10:42:12AM -0500, Robert P. J. Day wrote:
the temporary stylesheet looks fine -- an xsl:import and some
xsl:includes. what's baffling me is that docbook markup that
rendered beautifully in HTML renders untelligibly or causes the
rendering to fail when trying to
With DocBook XSL 1.58.1, and $default.encoding set to 'UTF-8', chunked
HTML output comes out with its encoding set to 'ISO-8859-1'. Setting
$chunker.output.encoding to 'UTF-8' works around the problem, but why
is $default.encoding ignored?
Tim.
*/
msg03481/pgp0.pgp
Description: PGP
--KXBzRT9YWDEmI8VQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 18, 2002 at 10:31:11AM -0500, Dennis Grace wrote:
Hmmm, since you're messing with section.title.properties, I wonder if you
aren't having the same
On Thu, Oct 10, 2002 at 05:43:38PM -0400, Daniel Veillard wrote:
(1) You add support for ?if? and friends to xsltproc. Probably the
fastest route to a complete solution.
(2) You tell me you'll take a patch from me to implement them. I'd
have to learn the xsltproc code, so it
On Fri, Oct 11, 2002 at 04:22:50AM -0400, Daniel Veillard wrote:
Now if a number of people did voice in saying that's the kind of processing
they really need, that there is a clean and public description with
review of the suggested extension, then I would certainly be an early
implementor
--GTGEtWEe6jD60dxL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Is it intentional that xhtml/chunk.xsl spits out HTML not XHTML?
(xhtml/docbook.xsl outputs XHTML as expected.)
Tim.
*/
--GTGEtWEe6jD60dxL
Content-Type: application/pgp-signature
Content-Disposition:
On Mon, Jun 17, 2002 at 04:33:36PM -0400, Aravind Vinnakota wrote:
I am using docbook on a Solaris machine until now. I am wondering
whether there is any documentation on setting up docbook support on a
Redhat 7.3 machine. I am looking for documentation where the packages are
installed
--3BL0Ng5d1iPP6beU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Apr 29, 2002 at 05:53:22PM +0200, Peter Ring wrote:
For a while, Mandrake appeared to me to be most up-to-date. But I don't
think there's much difference now. Anyway, most of the DocBook and
On Fri, Apr 26, 2002 at 04:18:05AM +, Karif Battle wrote:
The Company has decided to use DocBooks and XML.
Problems:
The docbook2man utility does not handle XML properly.
Indeed: for nroff output from XML, better to use db2man, an improved
version of which is included in the xmlto
--JVTRtevMO87SusWP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Apr 25, 2002 at 01:25:00PM -0700, Carlos wrote:
Does anyone have step by step install instructions for PassiveTex. I've
tried following the instructions on the website but got confused by the
On Fri, Apr 26, 2002 at 09:25:25AM -0500, Dennis Grace wrote:
Trying to build man pages with docbook2man was (pace Steve Cheng)
something of a nightmare for us. It's incomplete. If you want to
build man pages from XML, I recommend processing with XSLTPROC via
Martin van Beers' db2man.xsl
(Oops, replied in private mail by accident; for the list, in summary:)
On Fri, Apr 26, 2002 at 11:44:06AM -0500, Dennis Grace wrote:
Does the PassiveTeX rpm include the upgrades to pdfTeX/teTeX (from
http://www.redhat.com/support/errata/RHEA-2001-166.html) and the
JadeTeX upgrade (from
--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Apr 05, 2002 at 10:24:37AM -0600, Dennis Grace wrote:
I am running Red Hat 7.2 on my IBM T21 ThinkPad. I installed Red Hat's
upgrades at http://www.w3.org/TR/2001/WD-xhtml1-20011004/
At
Is anyone on this list using free software DocBook tools that handle
Japanese?
Thanks,
Tim.
*/
--lQcP9vuZCkvmDKre
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Jan 28, 2002 at 05:44:51AM -0600, Michael Smith wrote:
* XSLT engine: xsltproc (outputs ISO-8859-1 with character references
for the Japanese characters)
How about for FO processing?
Tim.
--HNePlKHf6vuaTOUD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Jan 17, 2002 at 09:08:54AM -0500, Daniel Veillard wrote:
Usually you will need Iso Latin 1, but people start to switch to
Iso Latin 15 to get the Euro symbol support. Make sure you have
--gV1yUYniiDLxW66s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sun, Jan 13, 2002 at 09:11:01PM -0800, Carlos Araya wrote:
A couple days ago I asked about an RPM for Passivetex and even then
I'm having a hell of time trying to find if I have the correct
versions
--qp4W5+cUSnZs0RIF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Difficult to tell from the output, but perhaps it's because Absolute
dimensions always work, but proportional ones are often not
recognized (from the PassiveTeX page).
(Your informaltable example used
What version of pdfTeX do you have? I think this might be due to a
bug in an old version of pdfTeX (I'm using 0.14h here).
Tim.
*/
msg03402/pgp0.pgp
Description: PGP signature
--dUqh8vgUBVXHzm9w
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Dec 11, 2001 at 06:24:13PM -0600, G.L. Grobe wrote:
I've heard how to w/ docbook2html (newer version) which I havn't
found yet (really havn't look, as it took alot of work to install
docbook
--OZkY3AIuv2LYvjdk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Dec 11, 2001 at 01:03:11AM -0800, Alex Lancaster wrote:
On this very subject, I'm working through getting a working
XSL/FO/PassiveTex setup working on
--nDAeJifZeokOLf48
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Dec 10, 2001 at 09:31:22AM -0500, Norman Walsh wrote:
/ [EMAIL PROTECTED] (Michal Sanger) was heard to say:
| In PHP semantic I have declaration:
| string MyFunction(string param1, string
--BNK5cO+49IguOVQa
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Wed, Dec 05, 2001 at 05:16:47PM +0100, Jirka Kosek wrote:
does anyone of you tried new version of PassiveTeX and xmltex? I
grabbed them just now, and all fonts in formatted result are quite
large
--hiUvK+R7oewjwcXw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Wed, Dec 05, 2001 at 05:54:33PM +0100, Yann Dirson wrote:
You may want to have a look at sgml2x, which aims at simplifying
SGML/XML processing with jade (this is a beta release, I know of some
small
On Thu, Nov 15, 2001 at 12:29:13PM -0500, Tammy Fox wrote:
I have my stylesheet set to generate a link to a separate
HTML page for the legalnotice. My legalnotice has
an id set for it: legalnotice id=legalnotice,
but the HTML filename for it is still randomly generated.
Am I doing something
--8jcWiON1L7A8HfS7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Nov 12, 2001 at 11:22:02AM +0100, Ali Saffari wrote:
checking whether the C++ compiler (c++ -O2 ) is a cross-compiler... yes
This looks wrong for a start. You might want to take a look at
--Y+QtaVjtxOtr8cXH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Nov 12, 2001 at 02:39:50PM +0100, camille wrote:
- hyphenation problems on URLs and menu entries
I notice this particular customization is based on the '\url{...}'
LaTeX stuff. Have you found a
--i6jgfrJswdyoXnQp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Nov 12, 2001 at 01:46:35PM +, Tim Waugh wrote:
I notice this particular customization is based on the '\url{...}'
LaTeX stuff. Have you found a way around the magenta-URL-text problem
--MxYQAzdbOWKZB282
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Nov 12, 2001 at 02:55:59PM +0100, camille wrote:
I have followed coding only from far, but URLs appear in black in both
PDF and PS and the links work in PDF.
Huh. The PostScript output looks
On Fri, Nov 02, 2001 at 02:38:20PM +1030, David Lloyd wrote:
[ address ]
Does not render at all using the print modules. It renders when I use
the html modules.
A bug in the default stylesheet customization included in
docbook-utils, since fixed.
Also, when I attempted to use v1.73
--wuUGvGHayROCMC3J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 02, 2001 at 03:33:11PM -0500, Adam Di Carlo wrote:
(The Red Hat Linux openjade RPMs build without http support; should I
change this?)
=20
Yes,
--GEn4szYucjS2InE7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 12, 2001 at 06:02:20PM +0200, Jirka Kosek wrote:
PassiveTeX reads directly XML source so there is no preprocessing stage
as in JadeTeX which can
--RyB1I56Pcq42iZjE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Oct 25, 2001 at 12:43:28PM -0400, Adam Di Carlo wrote:
This isn't true. You probably just have a version which was built
with http support.
^out
(The Red Hat Linux openjade RPMs build
--5scqBHJkaHHnMcIt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sun, Oct 28, 2001 at 08:14:22PM +0100, Peter Eisentraut wrote:
Looks like a botched installation. I have tetex-1.0.7-7 as contained in
Red Hat 7.0.
The libpng ABI changed but the soname didn't, and
--3pZQ0wszfDg7ZRO+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 12, 2001 at 06:02:20PM +0200, Jirka Kosek wrote:
If you want quick workaround, you can insert zero-width joining space
character (?) between two
--nRwNdQxTdQ7rZk9A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Oct 12, 2001 at 09:03:25PM -0500, G.L. Grobe wrote:
So basically, I've got a *.dsl like below. Once I put in my own definitions,
how do I use this w/ 'db2html myDocbookFile.sgm' so that my
On Fri, Oct 12, 2001 at 07:55:23PM +0200, Juan R. Migoya wrote:
It seems that the pdfjadetex macro has been missed in db2pdf
when calling pdftex. I don't know anything about db2tex
but this is the message I get when I run pdftex without the
pdfjadetex option or when the pdfjadetex.fmt is not
--Dnvf+KcI+0MByPWJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sat, Oct 06, 2001 at 03:48:15PM +0200, Julio Merino wrote:
Well, I'm writing a chapter about the division of the hard disks, so I
explain what are the cylinders, the heads, the sectors, etc. I would
On Tue, Oct 02, 2001 at 12:39:12AM +0930, Richard Sharpe wrote:
Even though I have run 'fmtutil --all', I am still getting the above.
Try:
fmtutil --cnffile /usr/share/texmf/tex/jadetex/jadefmtutil.cnf --all
If you are using Red Hat based packages, the relevant bug report is
here:
--5UGlQXeG3ziZS81+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Jun 04, 2001 at 10:58:39AM +0930, David Lloyd wrote:
From default RedHat 7.1 distribution with no changes to dbparam.dsl or
any other settings. When I create my book using db2html which seems
On Sun, Apr 22, 2001 at 06:25:32PM -0500, David Cramer wrote:
Is there a way around this? For example, is there a way to let emacs or
XMetaL know that a document gets its document type declaration from
another document?
Put this at the end of the file:
!-- Local Variables: --
!--
On Fri, Apr 20, 2001 at 02:02:50PM -0400, Norman Walsh wrote:
| So the question is:
| - did Red Hat shipped a wrong (or old/buggy) version ?
Yes. I think so.
Yes, it's an old XML package. Hope to update it soon.
Tim.
*/
--FhKpTYimqQF2+bfE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Mar 22, 2001 at 04:37:19PM +0100, Rune Enggaard Jensen wrote:
Is there any way we can get this to work?
Yes, but it takes some doing. See
45 matches
Mail list logo
