[xep-support] General identifier in XEP configuration file for font paths

[Chris Ridd]

On 25/11/06 9:38, Thomas Schraitle <tom_schr at web.de> wrote:

> Hi,
> 
> On Saturday 25 November 2006 21:41, Chris Ridd wrote:
>> On 25/11/06 1:24, Thomas Schraitle <tom_schr at web.de> wrote:
>>> I am looking for a more general solution that I can use in my XEP
>>> configuration file. An option using on a command line that can switch
>>> from one font directory to the other would also help.
>>> 
>>> Any other ideas?
>> 
>> Look at the supplied xep shell script wrapper: it passes a path to
>> xep.xml to the processor via the command-line. Mine says:
>> 
>> "$JAVA_HOME/bin/java" \
>>         -classpath "$CP" \
>>         "-Dcom.renderx.xep.CONFIG=$XEP_HOME/xep.xml" \
>>         com.renderx.xep.XSLDriver "$@"
>> 
>> So what you /could/ do is support all your target OSes using one
>> package by installing *all* the platform-specific xep.xml files, and
>> then changing the script to select a different one depending on uname
>> or something.
> 
> Thanks for your solution, Chris! :-)
> 
> I believe it works. Unfortunatly, I have to use different configuration
> files that share a lot of duplicate font-group entries. The only
> difference is a different xml:base attribute, for example (omitted config
> root element):

The XEP reference documentation says that every "container" element can take
an href attribute to make it come from another file. So you could modularize
your configuration files by making the platform-specific xep.xml files look
like:

<config>
  <options href="xep-options.xml"/>
  <fonts...>
    <!-- platform specific fonts -->
  </fonts>
  <languages href="xep-langs.xml"/>
</config>

Cheers,

Chris


-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html