You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by IAS <ia...@apache-korea.org> on 2002/11/21 04:51:37 UTC
[problem] xdocs validator doesn't support Korean characters
The problem is that Forrest xdocs validator doesn't work with Korean
(and possibly other non-Latin-1 languages). I tried to validate some
UTF8-encoded xdocs documents that have Korean characters by jEdit, and
the result was OK, i.e., 0 errors. I guess the current xdocs validator
uses English-oriented stuffs or read xdocs documents with some fixed
encoding that doesn't support non-Latin-1.
Thanks in advance for your great and kind guidance.
===========================================================
Changshin Lee (Korean name)
IAS (International name)
Company Web Site : http://www.tmax.co.kr
Personal Web Site : http://www.iasandcb.pe.kr
-----------------------------------------------------------
Senior Researcher & Java Technology Evangelist
R&D Institute
Tmax Soft
==========================================================
Re: [problem] xdocs validator doesn't support Korean characters
Posted by Jeff Turner <je...@apache.org>.
On Thu, Nov 28, 2002 at 07:13:28PM +0900, IAS wrote:
> Thanks. The patch exactly works for what I found. I'm expecting the
> (officially) updated ant soon. :-)
I have updated Ant in CVS.
> > However, it seems that the validator wants schema directory based on a
> > project with "Apache resolver library found, xml-commons resolver will
> > be used" message. For example, if a project doesn't explicitly put a
> > schema directory under src/documentation/resources, you can meet an
> > error message like this:
> >
> > BUILD FAILED
> > file://D:/apache/xml/forrest/forrest.build.xml:716:
> > D:\sites\appolo\src\documentation\resources\schema not found.
This should now be fixed.
--Jeff
RE: [problem] xdocs validator doesn't support Korean characters
Posted by IAS <ia...@apache-korea.org>.
Thanks. The patch exactly works for what I found. I'm expecting the
(officially) updated ant soon. :-)
--IAS
-----Original Message-----
From: Jeff Turner [mailto:jefft@apache.org]
Sent: Thursday, November 28, 2002 6:17 PM
To: forrest-dev@xml.apache.org
Subject: Re: [problem] xdocs validator doesn't support Korean characters
On Thu, Nov 28, 2002 at 04:45:56PM +0900, IAS wrote:
> I checked out the changes from CVS HEAD of Ant, and downloaded the
built
> jars(ant.jar, nodeps.jar, resolver.jar) at
> http://gump.covalent.net/jars/latest/jakarta-ant/ and
> http://gump.covalent.net/jars/latest/xml-commons/ . (2002-11-27)
>
> I'm very glad to tell you that now forrest (with the updated ant)
> validates Korean document very smoothly. I guess it's also the same in
> case of Japanese and all the other DBCS.
>
> However, it seems that the validator wants schema directory based on a
> project with "Apache resolver library found, xml-commons resolver will
> be used" message. For example, if a project doesn't explicitly put a
> schema directory under src/documentation/resources, you can meet an
> error message like this:
>
> BUILD FAILED
> file://D:/apache/xml/forrest/forrest.build.xml:716:
> D:\sites\appolo\src\documentation\resources\schema not found.
The patch I sent to Craeg [1] listed the following modifications in the
README:
"Some minor modifications have been made since that patch:
- If a <catalogfiles> fileset specifies a nonexistent base directory,
it is
silently ignored rather than throw a BuildException.
- Non-essential messages about which resolver is in use have been
degraded to
'DEBUG' status, so they don't appear in normal builds"
Now you've seen why I made them :)
--Jeff
[1] http://cvs.apache.org/~jefft/ant/ant-resolver-changes2.zip
Re: [problem] xdocs validator doesn't support Korean characters
Posted by Jeff Turner <je...@apache.org>.
On Thu, Nov 28, 2002 at 04:45:56PM +0900, IAS wrote:
> I checked out the changes from CVS HEAD of Ant, and downloaded the built
> jars(ant.jar, nodeps.jar, resolver.jar) at
> http://gump.covalent.net/jars/latest/jakarta-ant/ and
> http://gump.covalent.net/jars/latest/xml-commons/ . (2002-11-27)
>
> I'm very glad to tell you that now forrest (with the updated ant)
> validates Korean document very smoothly. I guess it's also the same in
> case of Japanese and all the other DBCS.
>
> However, it seems that the validator wants schema directory based on a
> project with "Apache resolver library found, xml-commons resolver will
> be used" message. For example, if a project doesn't explicitly put a
> schema directory under src/documentation/resources, you can meet an
> error message like this:
>
> BUILD FAILED
> file://D:/apache/xml/forrest/forrest.build.xml:716:
> D:\sites\appolo\src\documentation\resources\schema not found.
The patch I sent to Craeg [1] listed the following modifications in the README:
"Some minor modifications have been made since that patch:
- If a <catalogfiles> fileset specifies a nonexistent base directory, it is
silently ignored rather than throw a BuildException.
- Non-essential messages about which resolver is in use have been degraded to
'DEBUG' status, so they don't appear in normal builds"
Now you've seen why I made them :)
--Jeff
[1] http://cvs.apache.org/~jefft/ant/ant-resolver-changes2.zip
RE: [problem] xdocs validator doesn't support Korean characters
Posted by IAS <ia...@apache-korea.org>.
Instead of copying a schema from forrest, you can mmodify
forrest.propertiees to point out forrest default schema like
"project.schema-dir=d:/apache/xml/forrest/context/resources/schema" in
order to avoid validation failure.
Thanks.
IAS
-----Original Message-----
From: IAS [mailto:iasandcb@apache-korea.org]
Sent: Thursday, November 28, 2002 4:46 PM
To: forrest-dev@xml.apache.org
Subject: RE: [problem] xdocs validator doesn't support Korean characters
I checked out the changes from CVS HEAD of Ant, and downloaded the built
jars(ant.jar, nodeps.jar, resolver.jar) at
http://gump.covalent.net/jars/latest/jakarta-ant/ and
http://gump.covalent.net/jars/latest/xml-commons/ . (2002-11-27)
I'm very glad to tell you that now forrest (with the updated ant)
validates Korean document very smoothly. I guess it's also the same in
case of Japanese and all the other DBCS.
However, it seems that the validator wants schema directory based on a
project with "Apache resolver library found, xml-commons resolver will
be used" message. For example, if a project doesn't explicitly put a
schema directory under src/documentation/resources, you can meet an
error message like this:
BUILD FAILED
file://D:/apache/xml/forrest/forrest.build.xml:716:
D:\sites\appolo\src\documentation\resources\schema not found.
at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractF
ileSet.java:369)
at
org.apache.tools.ant.types.XMLCatalog$ApacheResolver.processExternalCata
logs(XMLCatalog.java:1083)
at
org.apache.tools.ant.types.XMLCatalog$ApacheResolver.resolveEntity(XMLCa
talog.java:921)
at
org.apache.tools.ant.types.XMLCatalog.resolveEntity(XMLCatalog.java:398)
at
org.apache.xerces.util.EntityResolverWrapper.resolveEntity(EntityResolve
rWrapper.java:148)
at
org.apache.xerces.impl.XMLEntityManager.resolveEntity(XMLEntityManager.j
ava:608)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XML
DocumentScannerImpl.java:839)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDo
cumentFragmentScannerImpl.java:329)
at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:5
25)
at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:5
81)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java
:1175)
at
org.apache.tools.ant.taskdefs.optional.XMLValidateTask.doValidate(XMLVal
idateTask.java:410)
at
org.apache.tools.ant.taskdefs.optional.XMLValidateTask.execute(XMLValida
teTask.java:298)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1331)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1275)
at org.apache.tools.ant.Main.runBuild(Main.java:614)
at org.apache.tools.ant.Main.start(Main.java:197)
at org.apache.tools.ant.Main.main(Main.java:235)
This failure can be resolved by just copying schema directory from
forrest main resources to your project.
In addition, I enjoy editing forrest xdocs with jEdit. In particular, if
you can add forrest/resources/schema/catalog.xcat to catalog of XML
plugin options, validation works very fine before forrest does.
Thanks a lot.
-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org]
Sent: Thursday, November 28, 2002 1:41 AM
To: forrest-dev@xml.apache.org
Subject: Re: [problem] xdocs validator doesn't support Korean characters
On 26 Nov 2002, Stefan Bodewig <bo...@apache.org> wrote:
> Looks easy to fix, I'll take a stab at it sometime this week.
This is supposed to be fixed in CVS HEAD of Ant now.
If you update forrest's version of Ant - so it can be tested here -
remember that you'll need a CVS version of resolver.jar as well.
Stefan
RE: [problem] xdocs validator doesn't support Korean characters
Posted by IAS <ia...@apache-korea.org>.
I checked out the changes from CVS HEAD of Ant, and downloaded the built
jars(ant.jar, nodeps.jar, resolver.jar) at
http://gump.covalent.net/jars/latest/jakarta-ant/ and
http://gump.covalent.net/jars/latest/xml-commons/ . (2002-11-27)
I'm very glad to tell you that now forrest (with the updated ant)
validates Korean document very smoothly. I guess it's also the same in
case of Japanese and all the other DBCS.
However, it seems that the validator wants schema directory based on a
project with "Apache resolver library found, xml-commons resolver will
be used" message. For example, if a project doesn't explicitly put a
schema directory under src/documentation/resources, you can meet an
error message like this:
BUILD FAILED
file://D:/apache/xml/forrest/forrest.build.xml:716:
D:\sites\appolo\src\documentation\resources\schema not found.
at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractF
ileSet.java:369)
at
org.apache.tools.ant.types.XMLCatalog$ApacheResolver.processExternalCata
logs(XMLCatalog.java:1083)
at
org.apache.tools.ant.types.XMLCatalog$ApacheResolver.resolveEntity(XMLCa
talog.java:921)
at
org.apache.tools.ant.types.XMLCatalog.resolveEntity(XMLCatalog.java:398)
at
org.apache.xerces.util.EntityResolverWrapper.resolveEntity(EntityResolve
rWrapper.java:148)
at
org.apache.xerces.impl.XMLEntityManager.resolveEntity(XMLEntityManager.j
ava:608)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XML
DocumentScannerImpl.java:839)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDo
cumentFragmentScannerImpl.java:329)
at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:5
25)
at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:5
81)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java
:1175)
at
org.apache.tools.ant.taskdefs.optional.XMLValidateTask.doValidate(XMLVal
idateTask.java:410)
at
org.apache.tools.ant.taskdefs.optional.XMLValidateTask.execute(XMLValida
teTask.java:298)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1331)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1275)
at org.apache.tools.ant.Main.runBuild(Main.java:614)
at org.apache.tools.ant.Main.start(Main.java:197)
at org.apache.tools.ant.Main.main(Main.java:235)
This failure can be resolved by just copying schema directory from
forrest main resources to your project.
In addition, I enjoy editing forrest xdocs with jEdit. In particular, if
you can add forrest/resources/schema/catalog.xcat to catalog of XML
plugin options, validation works very fine before forrest does.
Thanks a lot.
-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org]
Sent: Thursday, November 28, 2002 1:41 AM
To: forrest-dev@xml.apache.org
Subject: Re: [problem] xdocs validator doesn't support Korean characters
On 26 Nov 2002, Stefan Bodewig <bo...@apache.org> wrote:
> Looks easy to fix, I'll take a stab at it sometime this week.
This is supposed to be fixed in CVS HEAD of Ant now.
If you update forrest's version of Ant - so it can be tested here -
remember that you'll need a CVS version of resolver.jar as well.
Stefan
Re: [problem] xdocs validator doesn't support Korean characters
Posted by Stefan Bodewig <bo...@apache.org>.
On 26 Nov 2002, Stefan Bodewig <bo...@apache.org> wrote:
> Looks easy to fix, I'll take a stab at it sometime this week.
This is supposed to be fixed in CVS HEAD of Ant now.
If you update forrest's version of Ant - so it can be tested here -
remember that you'll need a CVS version of resolver.jar as well.
Stefan
RE: [problem] xdocs validator doesn't support Korean characters
Posted by IAS <ia...@apache-korea.org>.
Thanks, I'm looking forward to that.
IAS
-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org]
Sent: Tuesday, November 26, 2002 9:55 PM
To: forrest-dev@xml.apache.org
Subject: Re: [problem] xdocs validator doesn't support Korean characters
Probably this one
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11279>.
Looks easy to fix, I'll take a stab at it sometime this week.
Stefan
Re: [problem] xdocs validator doesn't support Korean characters
Posted by Stefan Bodewig <bo...@apache.org>.
Probably this one <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11279>.
Looks easy to fix, I'll take a stab at it sometime this week.
Stefan
RE: [problem] xdocs validator doesn't support Korean characters
Posted by IAS <ia...@apache-korea.org>.
First of all, I'd appreciate your effort on testing. I was surprised
that your Forrest validated my xdocs as "OK" because I've been still
going through validation problems with Forrest validator to my xdocs.
It's even stranger that your validator and mine made distinct results
based on the same xdocs. The only essential discrepancy between jEdit
(that says all my xdocs are valid) and Forrest (that says some of my
xdocs are invalid) ant task is the choice of Reader, i.e., StringReader
and FileReader. I just suspect that Sun's Korean-locale (and other DBCS)
JRE works slightly different from that of default English-locale in
terms of FileReader or some relevant to XML processing.
Notwithstanding this hard-to-understand situation, I resolved this
trouble with "enough" new lines at the (almost) every end of closing
tags in xdocs. Therefore, I can show Chinese, Japanese, and Korean
Forresters an alternative: Don't spare typing enters before closing a
tag. For example,
<li>An Item</li>
(Should be valid but invalid in Forrest on Korean JRE)
->
<li>An Item
</li>
(valid in Forrest on Korean JRE)
It's just a piece of recommendation for CJK Forresters (only). I wish it
could help out.
IAS
P.S. Another conclusion: it's not a fault of Forrest. :-)
> -----Original Message-----
> From: Jeff Turner [mailto:jefft@apache.org]
> Sent: Thursday, November 21, 2002 5:18 PM
> To: forrest-dev@xml.apache.org
> Subject: Re: [problem] xdocs validator doesn't support Korean
> characters
>
>
> On Thu, Nov 21, 2002 at 04:09:27PM +0900, IAS wrote:
> > I also tried my old site and the result was successful. However, my
> > current one (you can download it at
> > http://www.iasandcb.pe.kr/2g/ias-site2.zip) is different. In
> > particular,
> >
> /ias/src/documentation/content/xdocs/starbucks/2002-1101.xml is turn
> > out to be valid in jEdit but invalid in Forrest based on the latest
> > schema files from xml-forrest CVS repository.
>
> The file validates fine. Eg, run 'forrest validate -v':
>
> validate-xdocs:
> Using SAX2 reader org.apache.xerces.parsers.SAXParser
> Validating book.xml...
> Validating index.xml...
> Validating sample.xml.example...
> Validating tabs.xml...
> Validating book.xml...
> Validating chinese.xml...
> Validating index.xml...
> Validating apple.xml...
> Validating book.xml...
> Validating cactus-thorns.xml...
> Validating cocoon-encounter.xml...
> Validating homer.xml...
> Validating index.xml...
> Validating policenauts.xml...
> Validating 2002-1101.xml...
> Validating book.xml...
> Validating index.xml...
> 17 file(s) have been successfully validated.
> ...validated xdocs
>
>
> > (see /forrest-result.gif and
> > /jEdit-result.gif (status bar) snapshots.)
>
> The forrest-result.gif shows you have a bad link on line 40.
> The link is fine in ias-site2.zip
>
>
> --Jeff
>
> > Thanks.
> > --IAS
>
>
Re: [problem] xdocs validator doesn't support Korean characters
Posted by Jeff Turner <je...@apache.org>.
On Thu, Nov 21, 2002 at 04:09:27PM +0900, IAS wrote:
> I also tried my old site and the result was successful. However, my
> current one (you can download it at
> http://www.iasandcb.pe.kr/2g/ias-site2.zip) is different. In particular,
> /ias/src/documentation/content/xdocs/starbucks/2002-1101.xml is turn out
> to be valid in jEdit but invalid in Forrest based on the latest schema
> files from xml-forrest CVS repository.
The file validates fine. Eg, run 'forrest validate -v':
validate-xdocs:
Using SAX2 reader org.apache.xerces.parsers.SAXParser
Validating book.xml...
Validating index.xml...
Validating sample.xml.example...
Validating tabs.xml...
Validating book.xml...
Validating chinese.xml...
Validating index.xml...
Validating apple.xml...
Validating book.xml...
Validating cactus-thorns.xml...
Validating cocoon-encounter.xml...
Validating homer.xml...
Validating index.xml...
Validating policenauts.xml...
Validating 2002-1101.xml...
Validating book.xml...
Validating index.xml...
17 file(s) have been successfully validated.
...validated xdocs
> (see /forrest-result.gif and
> /jEdit-result.gif (status bar) snapshots.)
The forrest-result.gif shows you have a bad link on line 40. The link is fine
in ias-site2.zip
--Jeff
> Thanks.
> --IAS
RE: [problem] xdocs validator doesn't support Korean characters
Posted by IAS <ia...@apache-korea.org>.
I also tried my old site and the result was successful. However, my
current one (you can download it at
http://www.iasandcb.pe.kr/2g/ias-site2.zip) is different. In particular,
/ias/src/documentation/content/xdocs/starbucks/2002-1101.xml is turn out
to be valid in jEdit but invalid in Forrest based on the latest schema
files from xml-forrest CVS repository. (see /forrest-result.gif and
/jEdit-result.gif (status bar) snapshots.)
Thanks.
--IAS
> -----Original Message-----
> From: Jeff Turner [mailto:jefft@apache.org]
> Sent: Thursday, November 21, 2002 2:51 PM
> To: forrest-dev@xml.apache.org
> Subject: Re: [problem] xdocs validator doesn't support Korean
> characters
>
>
> On Thu, Nov 21, 2002 at 12:51:37PM +0900, IAS wrote:
> > The problem is that Forrest xdocs validator doesn't work
> with Korean
> > (and possibly other non-Latin-1 languages). I tried to
> validate some
> > UTF8-encoded xdocs documents that have Korean characters by
> jEdit, and
> > the result was OK, i.e., 0 errors. I guess the current
> xdocs validator
> > uses English-oriented stuffs or read xdocs documents with
> some fixed
> > encoding that doesn't support non-Latin-1.
>
> What is the error? After fixing the sitemap validation
> problem, I'm able to validate the docs in the ias-site.zip
> file you sent to the mailing list once:
>
> validate-xdocs:
> 6 file(s) have been successfully validated.
> ...validated xdocs
>
> validate-sitemap:
> ...validated sitemap
>
> Setup... done.
> Initializing... ready, let's go :-)
> * [25] index.html
> * [0] skin/page.css
> * [0] skin/images/spacer.gif
> * [0] skin/breadcrumbs.js
> * [0] images/group-logo.gif
> * [0] images/project-logo.gif
> * [0] skin/images/tabSel-left.gif
> * [0] skin/images/tabSel-right.gif
> * [0] skin/images/tab-left.gif
> * translate empty uri
> [20]
> -> [broken link] starbucks/index.html <-
> * [0] skin/images/tab-right.gif
> * [24] changes.html
> * [23] todo.html
> * [20] starbucks/index.html
> * [0] skin/images/menu-left.gif
> * [0] skin/images/menu-right.gif
> * [0] index.pdf
> * [0] skin/images/printer.gif
> * [0] skin/images/label.gif
> * [0] skin/images/page.gif
> * [0] skin/images/chapter.gif
> * [0] skin/images/chapter_open.gif
> * [0] skin/images/current.gif
> * [0] /favicon.ico
> * [0] skin/images/built-with-cocoon.gif
> * [0] skin/images/centipede-logo-small.gif
> * * [0] starbucks/index.pdf
> * [0] changes.pdf
> * [0] images/add.jpg
> * [0] todo.pdf
>
> disposing... done.
>
> ------------------------------
>
>
> --Jeff
>
Re: [problem] xdocs validator doesn't support Korean characters
Posted by Jeff Turner <je...@apache.org>.
On Thu, Nov 21, 2002 at 12:51:37PM +0900, IAS wrote:
> The problem is that Forrest xdocs validator doesn't work with Korean
> (and possibly other non-Latin-1 languages). I tried to validate some
> UTF8-encoded xdocs documents that have Korean characters by jEdit, and
> the result was OK, i.e., 0 errors. I guess the current xdocs validator
> uses English-oriented stuffs or read xdocs documents with some fixed
> encoding that doesn't support non-Latin-1.
What is the error? After fixing the sitemap validation problem, I'm able to
validate the docs in the ias-site.zip file you sent to the mailing list once:
validate-xdocs:
6 file(s) have been successfully validated.
...validated xdocs
validate-sitemap:
...validated sitemap
Setup... done.
Initializing... ready, let's go :-)
* [25] index.html
* [0] skin/page.css
* [0] skin/images/spacer.gif
* [0] skin/breadcrumbs.js
* [0] images/group-logo.gif
* [0] images/project-logo.gif
* [0] skin/images/tabSel-left.gif
* [0] skin/images/tabSel-right.gif
* [0] skin/images/tab-left.gif
* translate empty uri
[20]
-> [broken link] starbucks/index.html <-
* [0] skin/images/tab-right.gif
* [24] changes.html
* [23] todo.html
* [20] starbucks/index.html
* [0] skin/images/menu-left.gif
* [0] skin/images/menu-right.gif
* [0] index.pdf
* [0] skin/images/printer.gif
* [0] skin/images/label.gif
* [0] skin/images/page.gif
* [0] skin/images/chapter.gif
* [0] skin/images/chapter_open.gif
* [0] skin/images/current.gif
* [0] /favicon.ico
* [0] skin/images/built-with-cocoon.gif
* [0] skin/images/centipede-logo-small.gif
* * [0] starbucks/index.pdf
* [0] changes.pdf
* [0] images/add.jpg
* [0] todo.pdf
disposing... done.
------------------------------
--Jeff
>
> Thanks in advance for your great and kind guidance.
>
> ===========================================================
> Changshin Lee (Korean name)
> IAS (International name)
> Company Web Site : http://www.tmax.co.kr
> Personal Web Site : http://www.iasandcb.pe.kr
> -----------------------------------------------------------
> Senior Researcher & Java Technology Evangelist
> R&D Institute
> Tmax Soft
> ==========================================================
>
>