Re: [chaperon] [patch] .cwiki improvements
Am Mi, den 28.04.2004 schrieb Dave Brondsema um 2:18:
> I'm a forrest developer and the attached patches fix the following for parsing
> .cwiki files:
>
> * handle nested bulletlists like nested numberedlists are
Can you also provide a snippet for selftest.txt to test the changes?
> * use the file name as the title of the page (most useful when copying wiki
> files over), unless the file parameter isn't passed, in which case it'll still
> use the first section's title
Okay.
> * change link that uses "view.do?page={$href}" to "${href}.html" This makes it
> work for standard forrest pages.
This will break the sample page for chaperon. Perhaps you able to make
this optional, for example using parameter.
BTW, the wiki2xdoc patch file wasn't created against the CVS HEAD. And
the patch file for the grammar produces a invalid grammar.
You should create a BUGZILLA entry, because email can get lost,
especially if get a spam rate of 80% :-/
Stephan.
RE: [chaperon] [patch] .cwiki improvements
Dave Brondsema wrote: > Note: the regex used in the 'spacify' template doesn't work. > How can I make the > replace() function work? Since it gives an error about the > function not being > found, I haven't tested the regex either: it's supposed to > put a space in before > capital letters (except for multiple sequential capital letters). Hi Dave I've attached a text file containing an xslt 1 template called "splitString" which could either just replace the "spacify" template or could be called from it: Cheers Con (ABCDEFGHIJKLMNOPQRSTUVWXYZ
RE: [chaperon] [patch] .cwiki improvements
Conal Tuohy <[EMAIL PROTECTED]> writes: > > Dave Brondsema wrote: > > > Note: the regex used in the 'spacify' template doesn't > work. How can I > > make the > > replace() function work? Since it gives an error about the > function > > not being found, I haven't tested the regex either: it's supposed to > > put a space in before > > capital letters (except for multiple sequential capital letters). > > D'oh! Of course replace() is an XPath 2 function. So still > best to avoid it. > :-) If you really need/want this you could Saxon 7.0 into Cocoon, implement your own XSLT that imports/includes the cforms templates and write your own version of the relevant template with a higher priority (or call the apply/apply-imports appropriately if using import)...
RE: [chaperon] [patch] .cwiki improvements
Dave Brondsema wrote: > Note: the regex used in the 'spacify' template doesn't work. > How can I make the > replace() function work? Since it gives an error about the > function not being > found, I haven't tested the regex either: it's supposed to > put a space in before > capital letters (except for multiple sequential capital letters). D'oh! Of course replace() is an XPath 2 function. So still best to avoid it. :-)
RE: [chaperon] [patch] .cwiki improvements
Dave Brondsema wrote: > Note: the regex used in the 'spacify' template doesn't work. > How can I make the > replace() function work? Since it gives an error about the > function not being > found, I haven't tested the regex either: it's supposed to > put a space in before > capital letters (except for multiple sequential capital letters). Dave, "replace" is not XSLT - I would guess it's some kind of extension function. But I have a recursive template (pure XSLT 1) which does exactly this job, that I wrote just a few weeks ago. I'll see if I can track it down at work tomorrow.
