Another thing I noticed is that it is impossible to have _javascript_ and
css ressources for a particular area in your publication . The error
comes from the following lines in ressources.xmap
<!-- matches pub-id/area/css/*.css -->
<map:match pattern="*/*/css/*.css">
<map:read src="" mime-type="text/css"
/>
</map:match>
<!-- matches pub-id/area/_javascript_/**.js -->
<map:match pattern="*/*/_javascript_/**.js">
<map:read src=""
mime-type="application/x-_javascript_" />
</map:match>
Those 2 lines don't respect the standard pattern used for other ressources. It's seems akward. I think it should be like that :
<map:match pattern="*/*/**.css">
<map:read src="" mime-type="text/css"
/>
</map:match>
<map:match pattern="*/*/**.js">
<map:read src=""
mime-type="application/x-_javascript_" />
</map:match>
I haven't filled a bug for it because it's kind of technical so maybe I'm wrong.
--
Alexandre Poitras
Québec, Canada
- Ressources Bug in 1.2.4 ?? Alexandre Poitras
- Re: Ressources Bug in 1.2.4 ?? Alexandre Poitras