FWIW, the $path has just what I hoped in it and works well.
Thanks!
Karl
On Tue, Jan 31, 2012 at 9:23 PM, Karl Wright daddy...@gmail.com wrote:
Then, inside your own document-to-fo.xsl you should have access
to a path parameter. You may add an additional condition to the
font of interest
On Wed, Feb 1, 2012 at 8:02 AM, Karl Wright daddy...@gmail.com wrote:
FWIW, the $path has just what I hoped in it and works well.
My apologies Karl, I got busy last night and didn't have a chance to
get back to this:( I haven't confirmed but path should be the request
path (of the URL) - so the
For the archives, it looks like this is the commit [
http://svn.apache.org/viewvc?view=revisionrevision=1239111 ]. If
this is a common need, perhaps a candidate to just get rolled into
Forrest itself, I dunno.
FWIW, I'm pretty sure the output.xmap is unnecessary and you could
have used a
Tim Williams wrote:
For the archives, it looks like this is the commit [
http://svn.apache.org/viewvc?view=revisionrevision=1239111 ]. If
this is a common need, perhaps a candidate to just get rolled into
Forrest itself, I dunno.
For the document-to-fo.xsl part.
FWIW, I'm pretty sure the
Hi Hitoshi,
plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/document-to-fo.xsl
does seem like the right place to conditionalize things, but I'm
unclear in your example where the language specifier comes from? In
other words, I'd like the path to the current file to determine
On Tue, Jan 31, 2012 at 3:16 AM, Karl Wright daddy...@gmail.com wrote:
Hi Hitoshi,
plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/document-to-fo.xsl
does seem like the right place to conditionalize things, but I'm
unclear in your example where the language specifier comes
On Tue, Jan 31, 2012 at 8:04 AM, Tim Williams william...@gmail.com wrote:
On Tue, Jan 31, 2012 at 3:16 AM, Karl Wright daddy...@gmail.com wrote:
Hi Hitoshi,
plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/document-to-fo.xsl
does seem like the right place to conditionalize
Then, inside your own document-to-fo.xsl you should have access
to a path parameter. You may add an additional condition to the
font of interest (e.g. rootFontFamily) that uses XSL string functions
against your $path parameter.
I've set things up so that my document path includes the
There are so many problems here that I now think the only way to
actually get this to work is to make a copy of Forrest via ant and
modify the Forrest files, also via ant. I've set this up for the
ManifoldCF site build now and we should be able to work our way
through it a problem at a time,
