I can't find where to the pipeline to do this. I looked at all the
sitemaps in the Lenya delivery:
lenya/lenya/lucene.xmap
lenya/lenya/xopus.xmap
lenya/lenya/resources.xmap
lenya/lenya/lenya.xmap
lenya/lenya/info.xmap
lenya/lenya/i18n.xmap
lenya/lenya/import.xmap
lenya/lenya/pubs/blog/usecase-create.xmap
lenya/lenya/pubs/blog/atomapi.xmap
lenya/lenya/pubs/blog/webdav.xmap
lenya/lenya/pubs/blog/parameter-doctype.xmap
lenya/lenya/pubs/blog/menus.xmap
lenya/lenya/pubs/blog/sitemap.xmap
lenya/lenya/pubs/default/usecase-bxeng.xmap
lenya/lenya/pubs/default/parameter-doctype.xmap
lenya/lenya/pubs/default/publication-sitemap.xmap
lenya/lenya/pubs/default/menus.xmap
lenya/lenya/pubs/default/usecase-search.xmap
lenya/lenya/pubs/default/sitemap.xmap
lenya/lenya/pubs/default/doctypes.xmap
lenya/lenya/resources-shared.xmap
lenya/lenya/admin.xmap
lenya/lenya/navigation.xmap
lenya/lenya/usecase.xmap
lenya/lenya/usecases/edit/usecase-edit.xmap
lenya/lenya/usecases/1formedit/usecase-1formedit.xmap
lenya/lenya/usecases/kupu/usecase-kupu.xmap
lenya/lenya/scheduler.xmap
lenya/._sitemap.xmap
lenya/global-sitemap.xmap
lenya/test-suite/sitemap.xmap
lenya/sitemap.xmap
I understood that if I were to put my pipeline into one of the
sitemaps in lenya/lenya/pubs/default
it should work. I created the following pipeline:
<map:match pattern="vimia/css/*-*-*-*.css">
<!--
! {1} file name
! {2} language (de|en)
! {3} topic ([1..6])
! {4} browser (1=standards compliant, 2=minimal
PC, 3=text, 4=PDA, 5=cell phone)
-->
<map:generate type="file" src="resources/shared/css/
{1}.xcss" />
<map:transform type="i18n">
<map:parameter name="locale" value="{2}" />
</map:transform>
<map:transform src="resources/shared/css/{1}.xslt">
<map:parameter name="topic" value="{3}" />
<map:parameter name="browser" value="{4}" />
</map:transform>
<map:serialize mime-type="text/css" />
</map:match>
I have tried it in
lenya/lenya/pubs/default/publication-sitemap.xmap
lenya/lenya/pubs/default/sitemap.xmap
and also in a sub-sitemap I mounted under lenya/lenya/pubs/default.
However I can't get Lenya to acknowledge its existence. Calls like
http://public/lenya/default/live/css/vimia-de-1-1.css
result in the following response:
The requested document does not exist
The requested document '/css/vimia-de-1-1.css' with document-id '/
css/vimia-de-1-1' does not exist.
I get the impression that my <map:match pattern="vimia/css/*-*-*-
*.css"> is being masked by something
higher up the tree.
I thought I understood Cocoon, but I realise now that writing your
own and using someone else's stuff
are rather different :-)
Can anyone give me a bit of guidance please?
Steve
On 20 Jan 2006, at 14:14, Andreas Hartmann wrote:
Stephen Winnall wrote:
I am trying to implement my company website using Lenya 1.2.4 on
Linux. I would claim to
understand Cocoon, but I don't know my way around Lenya yet.
I would like to create a different presentation depending on
language (graphics
with language text), browser (non-compliance with standards),
subject (different
colours) etc. My approach in Cocoon would be to create a pipeline:
match **/css/company-*-*-*.css
// {2} = language
// {3} = subject
// {4} = browser
generate .../company.xml
transform with i18n using parameter {2}
transform for subject using parameter {3}
transform for browser if needed using parameter {4}
serialize as text/css
What I don't understand is where to embed this in Lenya. I assume
that it needs
to be part of my publication.
Yes, certainly.
Should I put it into resources/shared/css?
That's what I usually do. I add a pipeline to the main sitemap (or
create
an extra sitemap for such resources), and put the XSLT and the
CSS XML in the resources/shared/css directory.
IMO Lenya should provide a sophisticated mechanism to support this
functionality. There is already a pipeline for dynamic CSS generation
in resources.xmap and resources-shared.xmap, but it doesn't allow
custom parameters yet.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
