Date: Fri Nov 12 2021 - 20:10:21 PST
Then the file D:\projects\client\2021\Dita2Pdf.client.aroslanovo.243209.1631212044375\test\temp\pdf\topic.fo
Does not call out the fonts you wish.
Post or examine that file.
Just a note … RenderX XEP has been producing millions of pages just last week in many languages.
The issue is not with the formatter, the issue is in your configuration.
If you do not know (through the toolkit) where of how XEP is actually being run, you need to.
This looks wrong: C:\Program Files\Oxygen XML Editor 24\frameworks\dita\DITA-OT3.x\plugins\org.dita.pdf2.xep\lib\xep>xep
What is “xep>xep” at the end of that line?
We cannot diagnose things we have no idea what or how you set up. We can only point to millions pf pages formatted with no issues.
Kevin Brown
Executive Vice President, Sales & Marketing RenderX, Inc.
(650) 327-1000 Direct
(650) 328-8008 Fax
(925) 395-1772 Mobile
skype:kbrown01
kevin@renderx.com <mailto:kevin@renderx.com>
sales@renderx.com <mailto:sales@renderx.com>
http://www.renderx.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.renderx.com_&d=DwMFAw&c=-5LgSL_TkF3nGRQI95ci6eeFVMQ5VESHPf5koMIAxOA&r=yVuryK9i5mTC1HwUhhk11jhcfoM_R79kcOemHB3wJKI&m=_pMuyWQwWjkweA_2ZgroeXdOPL47i9HXHONuCevGjNA&s=VFnYR1htDHu9RCll2WrcHORu2W57P6A8xvtq01n2caU&e=>
From: Eric Sirois <eric.sirois@ixiasoft.com>
Sent: Friday, November 12, 2021 8:37 AM
To: 'kevin@renderx.com' <kevin@renderx.com>; 'RenderX Community Support List' <xep-support@renderx.com>
Subject: RE: [xep-support] Re: multi-language support using XEP
Hi Kevin,
I made the changes you suggested for the options. Yes, the xep.xml and fonts folder are siblings. I changed the hardcoded path to just “fonts/”
Now I’m not getting the boxes anymore, but no messages via the OT. No messages regarding fonts from the command line either. I get the following:
C:\Program Files\Oxygen XML Editor 24\frameworks\dita\DITA-OT3.x\plugins\org.dita.pdf2.xep\lib\xep>xep -fo D:\projects\client\2021\Dita2Pdf.client.aroslanovo.243209.1631212044375\test\temp\pdf\topic.fo -pdf D:\projects\client\2021\Dita2Pdf.client.aroslanovo.243209.1631212044375\test\out\pdf\test.pdf
(document [system-id file:/D:/projects/client/2021/Dita2Pdf.client.aroslanovo.243209.1631212044375/test/temp/pdf/topic.fo]
(validate [validation OK])
(compile
(meta-info )
(masters
(sequence-master [master-name front-matter-first])
(sequence-master [master-name front-matter-last])
(sequence-master [master-name front-matter-odd])
(sequence-master [master-name toc-odd])
(sequence-master [master-name toc-last])
(sequence-master [master-name toc-first])
(sequence-master [master-name body-first])
(sequence-master [master-name body-odd])
(sequence-master [master-name body-last])
(sequence-master [master-name index-first])
(sequence-master [master-name index-odd])
(sequence-master [master-name glossary-first])
(sequence-master [master-name glossary-odd])
(sequence-master [master-name toc-sequence])
(sequence-master [master-name body-sequence])
(sequence-master [master-name ditamap-body-sequence])
(sequence-master [master-name index-sequence])
(sequence-master [master-name front-matter])
(sequence-master [master-name glossary-sequence]))
(outline )
(sequence [master-reference front-matter]
(static-content [flow-name xsl-footnote-separator])
(static-content [flow-name odd-frontmatter-footer])
(static-content [flow-name odd-frontmatter-header])
(flow [flow-name xsl-region-body]))
(sequence [master-reference toc-sequence]
(static-content [flow-name odd-toc-footer])
(static-content [flow-name odd-toc-header])
(flow [flow-name xsl-region-body]))
(sequence [master-reference ditamap-body-sequence]
(static-content [flow-name xsl-footnote-separator])
(static-content [flow-name odd-body-footer])
(static-content [flow-name odd-body-header])
(static-content [flow-name first-body-header])
(static-content [flow-name first-body-footer])
(static-content [flow-name last-body-header])
(static-content [flow-name last-body-footer])
(flow [flow-name xsl-region-body])))
(format
(sequence [master-reference front-matter]
(flow [1])
(static-content [1]))
(sequence [master-reference toc-sequence]
(flow [ii][ii])
(static-content [ii]))
(sequence [master-reference ditamap-body-sequence]
(flow [3])
(static-content [3]|odd-body-footer||odd-body-header|)))
(generate [output-format pdf][1][ii][3]))
Éric Sirois
DITA Toolsmith
IXIASOFT
45 Chemin Bates, Suite 220 • Montreal, QC H2V 1A6
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
<mailto:eric.sirois_AT_ixiasoft.com> eric.sirois_AT_ixiasoft.com / <http://www.ixiasoft.com/> www.ixiasoft.com
From: Kevin Brown <kevin@renderx.com <mailto:kevin@renderx.com> >
Sent: November 11, 2021 3:21 PM
To: 'RenderX Community Support List' <xep-support@renderx.com <mailto:xep-support@renderx.com> >; Eric Sirois <eric.sirois@ixiasoft.com <mailto:eric.sirois@ixiasoft.com> >
Subject: RE: [xep-support] Re: multi-language support using XEP
And just a note in modern Windows OSes like 10, 11 … do not simply right click and select install font.
This will not copy the font file to C:\windows\fonts.
It will actually put it in your user roaming directory.
The font will still be listed when you browse to the windows font directory but the actual path is not c:\Windows\Fonts.
Kevin
From: Xep-support <xep-support-bounces@renderx.com <mailto:xep-support-bounces@renderx.com> > On Behalf Of Kevin Brown
Sent: Thursday, November 11, 2021 12:12 PM
To: 'Eric Sirois' <eric.sirois@ixiasoft.com <mailto:eric.sirois@ixiasoft.com> >; 'RenderX Community Support List' <xep-support@renderx.com <mailto:xep-support@renderx.com> >
Subject: [xep-support] Re: multi-language support using XEP
There are some things wrong.
1. I assume this is the directory in the picture:
C:\Program Files\Oxygen XML Editor 24\frameworks\dita\DITA-OT3.x\plugins\org.dita.pdf2.xep\lib\xep\fonts
If not, that is your first problem. That font group says it is for all relatively referenced fonts in this absolute path.
2. Based on the fact that your first font group is this (relative) path:
fonts/
It means all the fonts in that group are found in a subdirectory /fonts from the location of the parent file (xep.xml).
Because your rendering is not failing completely and the fact that Helvetica is in the picture you sent, you sent a picture of the /fonts directory.
Now if C:\Program Files\Oxygen XML Editor 24\frameworks\dita\DITA-OT3.x\plugins\org.dita.pdf2.xep\lib\xep\fonts is the same as /fonts then you are still missing many of the referenced fonts. Like Artial.ttf, Times.ttf and such.
3. There are other issues like option VALIDATE is not a valid entry in the <generator-options format="PDF"> section. Whomever made these edits was incorrect.
The key here is that you should look at the log output from RenderX. If you are trying to reference a font and it is not found, then the log will tell you where it looked (per your xep.xml). Normally (since you are on Windows), one would copy the fonts to the c:\Windows\Fonts directory to install those TTF fonts in the Windows OS. Then that whole section where you are referencing fonts in some deep path under Oxygen should point to “c:/Windows/Fonts/”. In this case, fonts that are already install in Windows like Arial, Courier New, Tahoma and Verdana would just work. It may be that you actually did install the fonts like Noto and Arial Unicode and they are in Windows/Fonts but then you are telling XEP they are in C:\Program Files\Oxygen XML Editor 24\frameworks\dita\DITA-OT3.x\plugins\org.dita.pdf2.xep\lib\xep\fonts
As a side note, I would normally never use VALIDATE = false until I was sure I had a completely functional system. It is better to set:
VALIDATE=”true”
DISCARD_IF_NOT_VALID=”false”
This way you get all the warnings, errors and yet the formatter will still try and format the document.
Kevin Brown
RenderX
From: Eric Sirois <eric.sirois@ixiasoft.com <mailto:eric.sirois@ixiasoft.com> >
Sent: Thursday, November 11, 2021 11:30 AM
To: 'kevin@renderx.com' <kevin@renderx.com <mailto:kevin@renderx.com> >; 'RenderX Community Support List' <xep-support@renderx.com <mailto:xep-support@renderx.com> >
Subject: RE: [xep-support] Re: multi-language support using XEP
Apologies for the long delay.
Here is the info. I tried swapping out the reference to Arial MS Unicode in the xep.xml file from the actual licensed version to Noto Sans. The content has Hindi, Japanese, and Traditional Chinese. None are showing up. So I fully expect something missing or misconfigured in our xep.xml file. For the Hindi content though. The latest version of FOP in DITA OT 3.6.1 was able to render the content in the PDF.
Please let me know if you have any questions.
Éric Sirois
DITA Toolsmith
IXIASOFT
45 Chemin Bates, Suite 220 • Montreal, QC H2V 1A6
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
<mailto:eric.sirois_AT_ixiasoft.com> eric.sirois_AT_ixiasoft.com / <http://www.ixiasoft.com/> www.ixiasoft.com
From: Xep-support <xep-support-bounces@renderx.com <mailto:xep-support-bounces@renderx.com> > On Behalf Of Kevin Brown
Sent: September 29, 2021 1:35 PM
To: 'RenderX Community Support List' <xep-support@renderx.com <mailto:xep-support@renderx.com> >
Subject: [xep-support] Re: multi-language support using XEP
* We do have xep.xml configured to load the Arial MS Unicode font in which the glyph does exist in that font.
How do you know this is correct? Please send your xep.xml lines where you have included the font including all pathing. Also include a screen shot of your directory that the font is located in. And finally include the relative xsl fo showing you are specifying that font. Note: Arial Unicode MS is a font which requires a license to use. You should own this license if you intend to use it and even then it is not recommended. The copyright notice for the font is very large and legally required to be inserted into the output. RenderX respects this and will insert the copyright information *even if you are only using one character of that font*. We have had customers complain that using one smiley face increases the output PDF size by 100kb. This is because the copyright notice must be inserted into the PDF output (something other formatters may not do).
* I did find the following thread from 2015 where it was mentioned Hindi/Devanagari is not supported. Is that still the case or was support added in newer versions of Xep?
It takes more than just a font to support Indic languages. The formatter engine must support advanced ligatures and glyph reshaping to properly format those languages.
RenderX does not include support for Indic languages.
Kevin Brown
RenderX
From: Xep-support <xep-support-bounces@renderx.com <mailto:xep-support-bounces@renderx.com> > On Behalf Of Eric Sirois
Sent: Monday, September 20, 2021 7:43 AM
To: 'xep-support@renderx.com' <xep-support@renderx.com <mailto:xep-support@renderx.com> >
Subject: [xep-support] multi-language support using XEP
Hi,
A client of ours would like to have multi-language content show up in their PDFs, but they are getting blank boxes instead. We do have xep.xml configured to load the Arial MS Unicode font in which the glyph does exist in that font. I did find the following thread from 2015 where it was mentioned Hindi/Devanagari is not supported. Is that still the case or was support added in newer versions of Xep?
<http://services.renderx.com/lists/xep-support/7405.html> http://services.renderx.com/lists/xep-support/7405.html
Éric Sirois
DITA Toolsmith
IXIASOFT
45 Chemin Bates, Suite 220 • Montreal, QC H2V 1A6
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
<mailto:eric.sirois_AT_ixiasoft.com> eric.sirois_AT_ixiasoft.com / <http://www.ixiasoft.com/> www.ixiasoft.com
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
