W3C home > Mailing lists > Public > xproc-dev@w3.org > May 2009

Re: Thoughts on cx:zip

From: Dave Pawson <dave.pawson@gmail.com>
Date: Wed, 27 May 2009 13:38:46 +0100
Message-ID: <711a73df0905270538u1903de86r28658a0269703953@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: XProc Dev <xproc-dev@w3.org>
2009/5/27 Norman Walsh <ndw@nwalsh.com>:
> Dave Pawson <dave.pawson@gmail.com> writes:
>> If the manifest is an external XML document, I couldn't use
>>  variables within that manifest since they wouldn't be 'expanded'?
> I never said the manifest had to be an *external* document. XProc is
> all about XML processing, I expect to construct the manifest in the
> pipeline.

Sorry, the example painted the picture (to me) that it was
an external document.

>> E.g. my ant list (in build.properties) reads
>> zip_file_list="${html_stylesheet}  ${my_schema_rng}  ${main_fo_stylesheet}  \
>> ${listimages_stylesheet} ${listimages_sh_stylesheet}  ${css_stylesheet}  \
>> ${xmlcatalog}  ${build_properties}  ${build_properties_sh}  ${build_sh}  \
>> ${build_xml}  ${cp_images_sh} ${test_docbook_xml} ${testprops_xsl} \
>> ${antvars_sh_py}  ${example_catalog} ${catalog_manager}"
> ... leaves open the question: what can we do to make it easiest for you
> to construct zip manifests like that one.

Some xml structure such that either the 'variables' are CDATA  element
content or individual content within elements?

<items>${html_stylesheet}   ${my_schema_rng}  ${main_fo_stylesheet} </

<item> ${example_catalog}</



Dave Pawson
Docbook FAQ.
Received on Wednesday, 27 May 2009 12:39:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:05 UTC