I've already answered your questions. In a nutshell, my answers were:
Step 1) You want "Letter Gothic Standard" instead of "Symbol" for the menucascade separator, then use our XSL customizer to add attribute font-family="Letter Gothic Standard" to attribute-set "menucascade-separator".
Once you have done this, please generate a .docx file and open it in MS-Word. You'll see by yourself that the font of the menucascade separator is "Letter Gothic Standard" (assuming that you actually have this font on your computer).
Now step 1) is not sufficient for the PDF output, as the PDF format does not support font "Letter Gothic Standard". For the PDF output, you need to instruct FOP to embed parts or all of font "Letter Gothic Standard" in the PDF file.
For the PDF output, you must additionally perform step 2).Step 2) Select Options|Preferences. Select Add-on|FOP. Drop the .ttf or .ttc file containing "Letter Gothic Standard" (NOT the whole C:\Windows\Fonts\ directory) to the list. Click OK and restart XXE.
Yes, that's it. From now, FOP knows what is font "Letter Gothic Standard".I did that (using font "Impact" because I have no "Letter Gothic Standard" font on my computer). It took me just 5 minutes to create all the files attached to this email. It worked flawlessly.
References:* The "Customize Document Conversion Stylesheets" dialog box -- http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.kit.part.ConversionStylesheetsEditor.html
* Apache FOP options -- http://www.xmlmind.com/xmleditor/_distrib/doc/help/addonOptions.html#fopOptions
Attachments: * Sample document: Test.dita.* .xsl file containing customized attribute-set "menucascade-separator" (created using XMLmind XSL Customizer, not by hand): fo_custom.xsl.
* After specifying fo_custom.xsl for the "RTF, WML and .docx" output formats, generated: Test.docx (the font of the separator is indeed seen as Impact by MS-Word).
* After specifying fo_custom.xsl for the "PDF and PostScript" output formats, generated incorrect Test_before_2.pdf.
* After dropping C:\Windows\Fonts\impact.ttf onto FOP preferences sheet and restarting XXE, generated correct Test.pdf (Looks OK and Acrobat Reader says that font "Impact" is embedded in the file).
On 04/17/2014 02:15 PM, Niels Grundtvig Nielsen wrote:
Since I'm lucky enough to have Acrobat X, I can just open the .pdf
output and touch up the font property of the problem character. Takes
the urgency off the question, but I would still like to know how to
achieve the required result by making more informed use of XXE … and for
the time being, I'm still very confused :-{
*what I've seen happen*
the default .pdf conversion does not render a glyph I select from the
XXE symbols pallette correctly, even though it is displayed on screen
*what you've explained*
this is what we can expect, because by default the .pdf conversion uses
the Symbol font that does not contain this glyph
*what I need to do*
I imagine, from your explanation and from other experiments, this is a
two-step procedure:
1. include a font (for example, Letter Gothic Standard) in the "embed
fonts" list in the FOP options
2. edit the attribute set in the custom XSLT stylesheet to make .pdf
conversion use this font – for example, <uicontrol
font-family="Letter Gothic Standard">
*what the FAQ say*
*A:* By default, PDF uses its 14 built-in fonts: Times, Helvetica,
Courier, Symbol and ZapfDingbats. These fonts have glyphs only for the
western (AKA Latin1) languages. Therefore you need to substitute to
these built-in fonts truly multilingual fonts [...] This can be done
from within XMLmind XML Editor. More information in XMLmind XML Editor -
Online Help, Apache FOP options and RenderX XEP options
The link to Apache FOP options takes me to /6.13. Add-on options >
6.13.1. Apache FOP options > Procedure 9.2. How to choose specific fonts
(for example, you want to replace Times fonts by Georgia fonts)/
I have read, re-read and experimented – complete lack of success :-{
* the procedure says nothing about /replacing /or /substituting/ – it
just talks about adding a TTF font to the list
* the list looks as though it's related to the 14 standard PS fonts …
but does not include Symbol or ZapfDingbats
* alerted by the warning about Windows, I've tried drag and drop from
C:\windows\fonts to the list … no luck on this Windows 7 PC; I've
also tried typing in the path and filename, and that doesn't work either
Following your advice to read the help topics on
editConversionStylesheetsAction and xslcustom.Customizer has improved my
general understanding, but I'm no nearer being able to carry out the one
piece of customisation I'm aiming for: telling FOP to use Letter Gothic
Standard instead of Symbol when rendering a UIcontrol element.
Any chance you can come up with a new way of guiding my idiot footsteps
through this task? unfortunately, I'm not managing to interpret either
the interface or the helps in a way that solves my problem. As I said,
it is less urgent now I've worked out how to adjust the final .pdf myself.
Thanks in advance!
Niels Grundtvig Nielsen
Technical Communicator
/you know what you're talking about – I can help you say it/
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
"task.dtd">
<task id="Test">
<title>Test</title>
<taskbody>
<steps>
<step>
<cmd>Select menu item <menucascade>
<uicontrol>Options</uicontrol>
<uicontrol>Preferences</uicontrol>
</menucascade>.</cmd>
</step>
<step>
<cmd>Select section <menucascade>
<uicontrol>Add-on</uicontrol>
<uicontrol>FOP</uicontrol>
</menucascade>.</cmd>
</step>
</steps>
</taskbody>
</task>
Test.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Test.pdf
Description: Adobe PDF document
Test_before_2.pdf
Description: Adobe PDF document
fo_custom.xsl
Description: application/xslt
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
