Does anyone have any information on when the unparsed-entity-uri
function is likely to be supported in distributions of Cocoon (eg
in whatever parser is distributed by default)?
///Peter
-
To unsubscribe, e-mail: [EMAIL
Does anyone have any information on when the unparsed-entity-uri()
function is likely to be supported in distributions of Cocoon (eg
in whatever parser is distributed by default)? Its absence is a
significant problem for text document publishing applications,
where it offers a solution to
Does anyone know when or if the unparsed-entity-uri() function will be
implemented in distributions of Cocoon? It's becoming very hard to do
serious document publishing without proper entity resolution.
///Peter
---
Could someone in the know please post the status of this
function in Cocoon? Searching turns up numerous posts about
it not being available because some parser feature is not
implemented, but no information about when or if this is
likely to be fixed.
Currently it's a major factor in preventing Co
On Jan 5, 2007, at 11:38 AM, Peter Flynn wrote:
Does anyone know when or if the unparsed-entity-uri() function will
be implemented in distributions of Cocoon? It's becoming very hard
to do
serious document publishing without proper entity resolution.
I don't know but this is
Hi all,
Another user reported this problem back in April 2002:
http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=101908975415672&w=2
Given XML source like this:
]
...
...
and XSLT like this:
...
I should see this in output (this works with xalan command line):
But instead, I get a
Thanks to both Grzegorz Kossakowski and Andrew Stevens
who both pointed me to RequestParameterExistsAction.
This does exactly what I want:
uri="cocoon://vivaead/entity-resolver?document=published/{../1}/{../
2}.xml&entity=unparsed-e
