First of all, really sorry for the inconvenience and the extra work
caused by the complexity of the design and documentation of XXE.
Yuriko N. wrote:
After reading your response, I am not quite clear of the logic of
when to use parameterGroup/parameters of customize.xxe and when to use options
of command-line.
So, let me ask a related question.
Last time when I questioned about how to set eastAsiaFonts for word
document, I understood that it can also be written into Cusomize.xxe instead of
using
command line option -eastAsiaFontFamilies=map.
(By the way, we've purchased a copy of XSL-FO Converter since then.)
Command line option "-eastAsiaFontFamilies=map" is for the fo2docx
command-line, not for the XXE command-line.
Command line fo2docx is found in XFC_install_dir/bin/.
Because the XMLmind XSL-FO Converter engine is embedded in XXE in the
form of a add-on, it's certainlypossible to specify:
eastAsiaFontFamilies = <a custom font map> here too, but *not* using
command line options.
--> Note that you don't need to have XMLmind XSL-FO Converter installed
on your computer to be able to use this converter in the context of XXE.
The "XMLmind FO Converter XSL-FO processor plug-in" XXE add-on contains
its own copy of the the XMLmind XSL-FO Converter engine.
I would recommend to *uninstall* the copy of the XMLmind XSL-FO
Converter product you have purchased and this way, focus on your
"XMLmind FO Converter XSL-FO processor plug-in" XXE add-on.
See "XMLmind FO Converter XSL-FO processor plug-in",
http://www.xmlmind.com/xmleditor/addons_doc.html#xfc_foprocessor
#####Your response for eastAsiaFonts question#########
Rather than directly modifying "C:\Program
Files\XMLmind_XML_Editor\addon\config\dita\xslMenu.incl", it's simpler
to add this parameter group:
---
<parameterGroup name="dita.toRTF.XFCParameters">
<parameter name="genericFontFamilies">serif=MS Mincho,sans-serif=MS
PGothic,monospace=MS Gothic</parameter>
<parameter name="eastAsiaFontFamilies">MS Mincho=Times New Roman,MS
PGothic=Arial,MS Gothic=Courier New</parameter>
</parameterGroup>
---
to your customize.xxe.
#######################################################
So I was guessing that your basic software design is so that user customized
settings
can be put into customize.xxe in the form of parameterGroup and parameters,
as well as using command Line options.
This is not the case.
Customization of configurations and user preferences are completely
different, unrelated concepts. It does not make sense to specify
different, unrelated, concepts in the same place.
Is it only for XSL-FO Converter that same customization can be done by both
command line options and customize.xxe parameterGroup/parameters ?
No, in the context of XXE, the parametrization of the XMLmind XSL-FO
Converter engine, must be specified in configuration files by the means
of configuration elements parameterGroup/parameters.
See "21. parameterGroup",
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/parameterGroup.html.
If it is the same concept for XXE as well,
then I thought it would be nice to put to customize.xxe and make it into an
add-on
for all company members to have.
And this is currently the case, *except* for user preferences.
I'm not sure that it's technically feasible to add to customize.xxe a
way to force user preferences. If you are interested and if it's not too
late for your deployment, I can look into that and get back to you.
Please confirm that you are still interested in having that feature for
the next release.
If there is a clear line between, what can be taken to customize.xxe as
ParameterGroup/Parameter
and what can be only be set in CommandLine option, can you please explain the
way of thinking
for this ?
Sorry but I'm not sure to understand. Do you mean: "please explain the
rationale of the separation between customization of configurations and
user preferences"?
Rationale
---------
Customization of configurations and user preferences are completely
different, unrelated, concepts. It does not make sense to specify
different, unrelated, concepts in the same place.
Where to specify what?
----------------------
To make it simple, the answer is:
1) Customizations common to several configurations (like parameter
"dita.toRTF.XFCParameters"; common to DITA Topic, Map, BookMap) go to
"customize.xxe".
2) Customizations of a specific configuration (e.g. DocBook v5+) go to
something like "custom_docbook5.xxe".
See "5. Customizing an existing configuration",
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/customizing.html
3) XXE user preferences (like "-putpref activeInputMethodClient true")
must be passed to the XXE command-line.
Please list *all* your customization requirements (attach files if
needed to) and I'll explain precisely --by the means of directly usable
files ("customize.xxe", user preferences, etc)-- how to implement them
in XXE.
--> Your corporate deployment problem is solved simply and elegantly by
using Java Web Start.
In a nutshell,
a) configure XXE on a computer,
b) run command-line deployxxe,
c) add command-line parameters to the generated "xxe.jnlp",
<application-desc main-class="com.xmlmind.xmleditapp.app.WebStart">
<argument>-putpref</argument>
<argument>activeInputMethodClient</argument>
<argument>true</argument>
</application-desc>
(This cannot be done automatically by deployxxe.)
d) copy all generated files to a intranet HTTP server.
Demo (without any add-on) here:
http://www.xmlmind.com/xmleditor/web_deployment.html
Yes, I insist, the right way to solve your corporate deployment is to
use Java Web Start. See "8. Deploying XXE using Java™ Web Start",
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/deploy_webstart.html
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
