> DocBook XML DTD (4.1.2). As editor I have tried using XML Spy
> 4.0 but have not been able to validate anything, not even simple
> sample documents.
You should give a try XML Spy 4.0.1 or 4.1 ... They had a bug
with validation engine in plain 4.0 ...
Martin
--
Martin Krumpolec <[EMAIL
Stayton-san wrote:
> I usually get that error reported when the processor cannot
> find the DTD. Without the DTD, it doesn't know which
> attributes are of type ID and IDREF, so the XSLT id()
> lookup function doesn't work.
Thank you! I'd been pondering why it worked on some documents and not
On Thu, 2001-10-25 at 21:29, Brendan Boyle wrote:
> Try Xmlmind xml editor.
>
> http://www.xmlmind.com
>
> Its a very good WYSIWYG xml editor with inbuilt support for Docbook.
> The current version is a free Java download and runs on pretty much
> anything. It is a beta product but I've foudn i
Try Xmlmind xml editor.
http://www.xmlmind.com
Its a very good WYSIWYG xml editor with inbuilt support for Docbook.
The current version is a free Java download and runs on pretty much
anything. It is a beta product but I've foudn it stable enough for
everyday use.
I've also written a very simp
/ "Kaiser Christian (SV SC RS T33)" <[EMAIL PROTECTED]> was heard to
say:
| > >But i've recognized that some bookmark items
| > >do have some appended characters. Looks like
| > >signs > 255. These signs are just rectangulars
| > >in this case.
| > >
|
| >
| > Is it possible that the weird char
Bradford, Denis wrote:
> As noted recently, I've got the Sun resolver classes working, but
> not sure it's set up optimally. Is there some way to avoid hard
> coding full catalog pathnames in the CatalogManager.properties file?
All the specs I've sifted through indicate a full pathname - sure
> From: Piet Seiden <[EMAIL PROTECTED]>
>
> I'm starting out with XML, trying to convert existing documents using the
> DocBook XML DTD (4.1.2). As editor I have tried using XML Spy 4.0 but have
> not been able to validate anything, not even simple sample documents. Before
> this drives me insane
I'm starting out with XML, trying to convert existing documents using the
DocBook XML DTD (4.1.2). As editor I have tried using XML Spy 4.0 but have
not been able to validate anything, not even simple sample documents. Before
this drives me insane, I would like to inquire here, if there is a
valid
As noted recently, I've got the Sun resolver classes working, but not sure
it's set up optimally.
Is there some way to avoid hard coding full catalog pathnames in the
CatalogManager.properties file?
All the specs I've sifted through indicate a full pathname - sure enough,
that's the only thing tha
At 14:09 25/10/2001 +0200, camille wrote:
>Hi all,
>
>I'm running through a strange behavior, on something so simple that I
>hesitated a lot before posting:
>$ java com.icl.saxon.StyleSheet -o test.html test.xml \
>/usr/share/sgml/docbook/xsl-stylesheets/html/docbook.xsl
>Error: no ID for con
Funny, your file looks valid to me. To be sure, I just processed your XML
file with Instant Saxon 6.4.3 + 1.45 xsl stylesheet and it generates the
HTML file correctly. Must be something with your Saxon setup on
Unix/Linux...
Gershon
On Thu, 25 Oct 2001, camille wrote:
> Hi all,
>
> I'm runnin
> From: camille <[EMAIL PROTECTED]>
>
> I'm running through a strange behavior, on something so simple that I
> hesitated a lot before posting:
>
> SAXON 6.4.3
> docbook-style-xsl-1.45
>
> Thanks for your help, Camille.
>
> -- shell interaction --
> $ java com.icl.saxon.StyleS
Yes, that may be true. Changing my XSL and source XML to iso-8859-1
encoding resolved all issues except for one. My source was using the
character entity → which evidently doesn't exist in iso-8859-1 and
caused the writing of the toc.hhc to exit with an error. Once I replaced
them with '->' all wa
Hi all,
I'm running through a strange behavior, on something so simple that I
hesitated a lot before posting:
SAXON 6.4.3
docbook-style-xsl-1.45
Thanks for your help, Camille.
-- shell interaction --
$ java com.icl.saxon.StyleSheet -o test.html test.xml \
/usr/share/sgml/docb
Would you mind looking at your documents in 'Plain Text' view in XMetaL and
report what your typographical characters look like?
Microsoft operating systems and products used to use variants of the ISO
8859 character sets; the one used in Western Europe and USA (1252,
http://www.microsoft.com/typ
15 matches
Mail list logo