On Apr 25, 2006, at 12:40 AM, Thorsten Scherler wrote:
> El lun, 24-04-2006 a las 21:15 -0700, Clay Leeds escribió:
>> Updated Subject line. Sorry.
>> I meant to add, that OOo grabs the file name via an xsl:param, which
>> is passed through via a Cocoon pipeline. Will we want to do a similar
>> thing with this odt plugin?
> I reckon it is a nice enhancement. ;)
BTW, the filename doesn't appear to be stored anywhere in the
document, so if we want it, we'll have to pass it in. Then again, I
don't know if it really matters that much.
> Let us see how it is best (*IMO*) integrated.
> ...more inline...
>> On Apr 24, 2006, at 9:12 PM, Web Maestro Clay wrote:
>>> ODT uses a similar structure to OOo. I want to grab the document
>>> title element (stored in 'odt_file.odt/meta.xml' as /
>>> office:document-meta/office:meta/dc:title). But the ODT transformer
>>> currently only looks at /content.xml.
> Then we need to do an aggregate to as well pass this file into the
> and then we should create a forrest specific xsl and import the common
> one. IMO we should leave the common *as it* since one can import/
> xsl and override only specific matches (less code to maintain).
I like 'common' elements as much as the next guy. However, we'll need
to make modifications to that 'common' file, since it is missing
things like a more intelligent element. I would suspect that
Lenya would want an intelligent element as well.
In any case, I think we're in agreement that forrest-specific stuff
goes into forrest-specific xsl & lenya-specific stuff goes into lenya-
> You can see what I mean if you look at
Earlier today, I got a 404 when I went to that page (after removing
the 'and' below, which appended itself to the URL). Now when I see
it, this diff looks like a bunch of empty lines to me. What am I
supposed to see?
I can see those files fine.
My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet