>> you can still change default parser used by Saxon
>> to Xerces by setting system property
>> javax.xml.parsers.SAXParserFactory=
>> org.apache.xerces.jaxp.SAXParserFactoryImpl.
well... 8-(
I've tried swapping out to 1.49 version of the sheets, I've tried hardcoding
the file paths in the i18n.
At 21:58 04/05/2002 +0200, Jirka Kosek wrote:
>This is (was) bug in AElfred. Mike Kay said me that he fixed this bug in
>6.5.2, but I didn't test it yet. Same bug caused troubles with catalog
>files and AElfred when used within Saxon. You can try Saxon 6.5.2, and
>if this doesn't help, you can st
On Fri, May 03, 2002 at 02:56:12PM -0500, David Cramer wrote:
> Add: to Jeff's
Subtle ! I'd tried
:)
thanks
john
--
"ken kesey wrote 'one flew over the center of the cuckolded lizard man,
who strayed from his mistakes when he is a madeup word.'"
- Mega HAL
On Sat, May 04, 2002 at 11:41:42PM +0200, Steffen Maier wrote:
> > Works a treat, thanks /very/ much. Now the only problem I have
> > left is the xmlns thing, and I suppose a low-tech sed solution
> > will do for that.
>
> What does "the xmlns thing" look like? Is it introducing a wrong namespac
On Fri, 3 May 2002, John Levon wrote:
> On Fri, May 03, 2002 at 08:32:54AM -0400, Jeff Beal wrote:
>
> > However, you can write a customization template to handle this (note that I
> > didn't get the XHTML DOCTYPE - I'm too lazy to look it up, and I don't have
> > it memorized)
>
> Works a treat,
Sven Kitschke wrote:
> In the \webapps\cocoon\WEB-INF\logs\core.log you
> can find: "java.net.MalformedURLException: no protocol: af.xml"
> (adding "file:" doesn't fix the problem)
Aha.
> I know that's the wrong list, but: has anyone an idea
> where the bug resides? Is it a configuration probl
website, qandaentry processing is a simple apply-templates
for all websites (I'm using chunk-website)
The linking (local to page) down to page content is done
via generate-id().
I've had a request that these remain static as more
entries are added.
Although qandaentry has an id attribute in the
At 04:32 04/05/2002 -0500, Michael D. Crawford wrote:
>I saw a mention of a tool that converts WikiText pages to DocBook format.
It was the other way round that crossed my mind!
Then the faq could go on the wiki page.
Regards DaveP
>> What version of stylesheet you are using?
1.50.0
>> I think that these errors are produced by
>> some malicious version, try to get latest
>> release or 1.49 (latest version before
>> some major changes in stylesheets).
Right -- ok, I'll try 1.49 this afternoon and see if that helps
Hi,
Michael Cortez wrote:
[snip]
> Lots of:
>
> No localization exists for "en" or "". Using default "en".
> No "en" localization of "TableofContents" exists.
> No localization exists for "en" or "". Using default "en".
> No "en" localization exists.
>
I saw a mention of a tool that converts WikiText pages to DocBook format. It is
used by a project underway by the Linux Documentation Project to allow authors
to write Linux documentation (the HOWTOs I think are now standardized in
DocBook) in their web browsers;
Announcing the Lampadas Proje
Michael Cortez wrote:
>
> >> 7.0 and 7.1 are experimental releases. In order to use
> >> saxon:output the
> >> stylesheet has to have a version number different than 1.0.
> >>
> >> For compatibility's saxe I would stick to 6.5
> >>
>
> Running with 6.5.1 I appear to be having Localization proble
At 13:42 03/05/2002 -0700, Eric Richardson wrote:
>Dave Pawson wrote:
>
>>I've posted a new page, describing ant and .
>>I'd appreciate comments/improvements from 'seasoned' resolver class users
>>if you have the time please.
>>http://www.dpawson.co.uk/docbook/ant.html
>Hi Dave,
>
>
>It's nice
13 matches
Mail list logo
