That makes beautiful source code! Thank you!
- Original Message -From: Radu Coravu To:
docbook-apps@lists.oasis-open.orgSent: Mon, 20 Feb 2017 07:25:59 -
(UTC)Subject: Re: [docbook-apps] Color In Syntax Highlighting
Hi,
There is a "highlight.xsl" specific for
Hi,
I downloaded again, and in comparison, you are right they differ. The original
has windows style EOL, the one I have has UNIX style EOL, so it must have been
saved in an editor on my system. That is strange to say the least, but I'm
going to unpack a pristine copy and see what happens.
Hi,
This gets me a step further, but it looks like the docbook-xsl-ns-1.79.1 is
missing part of what it needs. In "fo/highlight.xsl", line 21, there is this
import:
This file is missing and not part of the docbook 1.79.1 source
code..."ini-hl.xsl" does not exist (the ".xml" version exists,
Hi,
I do not currently customize other than param.xsl and fop.xconf, and have never
created a customization layer. So I currently have no xsl:import of docbook.xsl
other than where it would occur in the non-customized DocBook 5.1. Is this URL
the correct information for the customization
Hi,
I see by default in fo/highlighting.xsl (I'm using fo):
My XSL knowledge is minimal, but if for example I'm using bourne as the
language, do I need to import something specific to bourne? The README has a
note about importing, but it isn't clear what the intended import file is.
Hi,
I thought I would summarize my progress on syntax highlighting and then ask
about the sourceforge.net version of Saxon.
My DocBook is "docbook-xsl-ns-1.79.1". My install of xslthl is "xslthl-2.1.3".
When using the jar files which came with DocBook 5.1, and from xslthl 2.1.3, I
can
work, so I
must still be missing some detail about how I am using Saxon for highlighting.
Thanks!
- Original Message -From: Dave Pawson <dave.paw...@gmail.com>To:
stimits@comcast.netCc: Docbook <docbook-apps@lists.oasis-open.org>Sent: Sun, 12
Feb 2017 19:06:52 - (UTC
ecified? Syntax
highlighting would be a valuable tool, but it just feels like I'll end up
skipping actual content writing if I have to debug at the source code
level...and the issue is probably just something simple I've overlooked, but I
do not have the experience to know what to look at.
T
ve URL on syntax highlighting?
Thanks!
- Original Message -From: Richard Hamilton <hamil...@xmlpress.net>To:
stimits@comcast.netCc: Docbook <docbook-apps@lists.oasis-open.org>Sent: Sat, 11
Feb 2017 00:50:21 - (UTC)Subject: Re: [docbook-apps] does not number...
Hi,
Hi,
I was going by this reference as to requirements, and have not read the whole
book (thus I did not yet see the Java requirement):
http://tdg.docbook.org/tdg/5.1/programlisting.html
Admittedly I'm trying to do something quicker than I should and not reading
everything (I've been through a
Hi,
Under DocBook 5.1 I've been able to list programs, but line numbering has no
effect (and there is no error under xmllint or jing). Is there some ENTITY or
other precondition required for line numbering under 5.1?
Thanks!
Hi,
I've been trying to use the "fo/highlight.xsl" which comes with the Docbook 5.1
code for a "" project (Linux host) and requires listing source code in
multiple programming languages. Current source code listing without syntax
highlighting just looks like ordinary text and is hard to
Hi,
Thank you everyone! With the info on that fop configuration for custom setup I
was able to get fop to actually use the xconf fileso much trouble because I
had thought fop had been using the standard system configuration file by
default, but it does not. Edits to use the required font
This is turning out to be odd...I have to conclude that fop is not reading any
configuration files...especially none named "fop.xconf". The short story is
that I can intentionally introduce errors in fop.xconf (all occurrences on the
computer as verified by updatedb and locate .xconf),
x for my
addition of DejaVuSans?
Thanks!
- Original Message -----From: Richard Hamilton <hamil...@xmlpress.net>To:
stimits@comcast.netCc: Docbook <docbook-apps@lists.oasis-open.org>Sent: Wed, 01
Feb 2017 20:36:59 - (UTC)Subject: Re: [docbook-apps] Odd Characters in
UTF-8,
Hi,
I tested this by changing body.font.family to sans-serif. The document did
successfully switch, and used Helvetica. Unfortunately, Helvetica also lacks
the box drawing characters. Is there a configuration file used for a given
Docbook 5.1 installation which maps "Times Roman" to serif,
k
configuration from a system administrator's point of view...if anyone has a URL
for information on specifics of tuning Docbook defaults under Linux I'd be very
happy!
Thanks!
- Original Message -From: stimits@comcast.netTo:
docbook-apps@lists.oasis-open.orgSent: Tue, 31 Jan 2017 23:20:24
Hi,
I'm working on a Linux machine which has UTF-8 encoding. The docbook 5.1 I'm
working with is declared:
]>
Entities changed a while back (relaxng changed things), but so far as I know I
should still be able to work with numeric entities when using odd characters
which are part of UTF-8.
to not be dropped. Rephrased, I moved mediaobject out of
book->info->mediaobject->imageobject->imagedata and into
book->info->legalnotice->figure->mediaobject->imageobject->imagedata (svg).
This works as expected.
----- Original Message -From: Richard H
Hi,
I'm struggling to embed SVG into a docbook5 document. I don't know if this is
an issue of how I'm coding, or if this is an issue with the tools being
used...any advice on solving this is welcomed.
I am using xsltproc with docbook5 docbook.xsl to produce a ".fo" file (Linux
o/s), with
Hi,
With previous help I was able to get a Makefile working for complete validation
and publishing to xhtml, rtf, pdf, and ps.
Now I'm at a point where I can actually author in docbook 5. I'm hoping someone
here can suggest an available docbook 5 example document which contains a large
Hi,
I am trying to find a suitable combination of tools under Linux (currently
Fedora 23) for validating and publishing from Docbook 5 to PDF, PostScript,
RTF, and some variant of HTML (preferably xhtml strict, but most any variant
will work). Some of my testing "almost" works via xsltproc
22 matches
Mail list logo