Alex Milowski wrote:
>
> On Friday, November 21, 2003, at 06:58 AM, Vitaly Harisov wrote:
>
>> Hussein Shafie wrote:
>>
>>> For now, we recommend what follows:
>>> [1] Create your own custom CSS style sheet (example:
>>> literate_docbook.css) in the user configuration directory or in a
>>> system wide configuration directory different from XXE configuration
>>> directory.
>>> [2] First line of literate_docbook.css should be:
>>> ---
>>> @import url(<XXE_install_dir>/config/docbook/css/docbook.css);
>>> ---
>>> (Yes, you explicitly need to know where XXE has been installed.
>>> That's why this solution is not clean.)
>>
>>
>> It would be nice to have an ability write @import
>> url(%XXE_HOME%/config/docbook/css/docbook.css);
>> or
>> @import url($XXE_HOME/config/docbook/css/docbook.css);
>>
>
> In addition, it would be nice to be able to have access to certain base
> URI's throughout
> the configuration files. For example, a lot of my schemas/etc. come out
> of CVS and
> I'd love to be able to configure the base URI for where they live so I
> can check in
> the configuration to CVS and distributed they to users via CVS.
>
> An alternative to the environment variable above would be to have a
> function-like
> syntax similar to XPath:
>
> @import url(base-uri('xxe-home')/config/docbook/css/docbook.css);
>
> and then somehow keywords would be associated with URI values.
Due to the layered architecture of XXE, what you suggest for @import is
not easy to implement:
* Our CSS parser is a generic CSS parser. It ignores what is XXE.
* An @import is a standard CSS at-rule.
* url() is a standard CSS data type which, in our implementation,
contains an URL supported by Java.
* The CSS parser does not delegate to the application the processing of
@import.
But we agree on the fact that we'll have to find a clean solution to
this problem.
