First, jaxme.properties.sample doesn't contain docbook.home key-value pair.
Here's what I made up for that:
#########################################################
#
# Location of the DocBook XML DTDs (docbook-xml 4.2)
# DocBook XML is available from http://www.oasis-open.org/docbook/xml
# and required to build the documentation of the manual.
#
#docbook.home=d:/java/tool/docbook-xml-4.2
#docbook.home=/usr/local/docbook-xml-4.2
#
Next, it's quite strange though, src/documentation/manual/faq.xml has a
character, of which code is 146 (heximally x92) hence illegal against
US-ASCII. Here's an error message from ant:
docbook.html:
[delete] Deleting directory
D:\java\tools\eclipse3.0-m3\workspace\JaxMe2\src\documentation\content\manua
l
[mkdir] Created dir:
D:\java\tools\eclipse3.0-m3\workspace\JaxMe2\src\documentation\content\manua
l
[style] Processing
D:\java\tools\eclipse3.0-m3\workspace\JaxMe2\src\documentation\manual\jaxme2
.xml to D:\java\tools\eclipse3.0-m3\workspace\JaxMe
2\src\documentation\content\manual\index.html
[style] Loading stylesheet
D:\java\tools\docbook-xsl-1.61.3\html\chunk.xsl
[style] : Fatal Error! java.io.IOException: Byte "146" is not a member
of the (7-bit) ASCII character set. Cause: java.io.IOException: Byte "146"
is not a member of the (7-bit) ASCII character set.
[style] Failed to process
D:\java\tools\eclipse3.0-m3\workspace\JaxMe2\src\documentation\manual\jaxme2
.xml
The attached patch is for resolving this situation. I guess 146 may be '
(apostrophe) and hope you can make sure of it.
Thanks for the great documentation,
Ias
=========================================================
Lee, Changshin (Korean name)
Ias (International name)
Company Web Site: http://www.tmax.co.kr
Personal Web Site: http://www.iasandcb.pe.kr
---------------------------------------------------------
Senior Researcher, Emerging Technology Evangelist
JCP member - http://jcp.org/en/participation/members/L
R&D Institute
Tmax Soft, Inc.
JCP member - http://jcp.org/en/participation/members/T
=========================================================
Index: faq.xml
===================================================================
RCS file: /cvsroot/jaxme/JaxMe2/src/documentation/manual/faq.xml,v
retrieving revision 1.1
diff -u -r1.1 faq.xml
--- faq.xml 29 Aug 2003 18:03:49 -0000 1.1
+++ faq.xml 11 Sep 2003 03:38:55 -0000
@@ -142,12 +142,12 @@
</qandaentry>
<qandaentry>
- <question><para>What are JaxMe�s "find methods" and "list
methods"?</para></question>
+ <question><para>What are JaxMe's "find methods" and "list
methods"?</para></question>
<answer>
<para>As of this writing, the following applies for JaxMe 1 only.
EJB support is not yet included in JaxMe 2. This will hopefully change
soon.</para>
<para>You know what an SQL view is? Forgetting updateable views, one could
describe them as a
- stored query, that returns some data in a fixed format. In essence this
is what JaxMe�s find
+ stored query, that returns some data in a fixed format. In essence this
is what JaxMe's find
and list methods are: You specify a query that is compiled by the source
code generator. The
result are Java sources that can perform the specified query, possibly
configured with some
parameters that you specify as well.</para>
@@ -174,7 +174,7 @@
<qandaentry>
<question><para>How is Tamino supported?</para></question>
<answer>
- <para>Software AG, the vendor of Tamino, is the employer of Jochen Wiedmann
(JaxMe�s head
+ <para>Software AG, the vendor of Tamino, is the employer of Jochen Wiedmann
(JaxMe's head
developer). Jochen uses Tamino in his daily work, so support for Tamino
is essential. He
considers work with Tamino as definitely much more fun than using DB2,
Oracle, or
whatsoever.</para>
