[xep-support] Re: String encoding issue

Maybe this was not posted on xep-support as several files went back and forth between Morley and myself.To close this out, the issue was the actual font file.
It has a broken Kern table in it.Since Kerning is on by default in RenderX, the Kern information in this font for the 'W' has a huge negative offset in it and sent the remaining content off the page.
We first formatted the document using Helvetica and all was there.We set back to the Agenda-Bold font and saw the content missing.We validated by formatting to XEP intermediate and examining where text was being placed (it was there, not removed).The text was being placed at an x location of -88907 units, way off the left side of the page.Then we formatted with Kern turned off and the text was there as expected in the correct location because it was not Kerned.Then we used the Agenda-Bold font in Word and set the Kerning on and showed that it was also broken (nothing to do with XEP).
The font itself is bad.
Kevin BrownRenderX
-----Original Message-----From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of Dave PawsonSent: Thursday, July 19, 2018 11:30 PMTo: RenderX Community Support List <xep-support@renderx.com>Subject: [xep-support] Re: String encoding issue
Wondering if it is an encoding issue?utf-8 all the way through? XML, XSLT and XSL-FO?
HTH
On 19 July 2018 at 17:51, Morley Tooke <morley.tooke@gmail.com> wrote:> Hi Kevin,>> I've done some more digging on this.>> To refresh you, this element:>> <fig id="fig_ddr_pvp_xdb" class="- topic/fig ">> <title class="- topic/title ">Injection Well W01I01: Process > Control</title> ...> fails to render the digits after the W and produces this output:>> Figure: Injection Well W>> whereas this element:>> <fig id="fig_ddr_pvp_xdb" class="- topic/fig ">> <title class="- topic/title ">Injection Well Y01I01: Process > Control</title> ...>> produces this output:>> Figure: Injection Well Y01I01: Process Control>> I can change that string to anything else and it works fine, but this > string seems to get picked up by some other process.>> This is what my FO looks like:>> <fo:block id="unique_11_Connect_42_fig_ddr_pvp_xdb"><fo:inline> id="unique_11_Connect_42_image_cxc_yvw_j2b"> margin-right="0.15in"><fo:external-graphic content-width="5.5in"> src="url(images/fc_all_field_common_injection_well_W01_pcd.png)"
/></fo> :inline><fo:block> font-size="10pt" font-weight="bold"> keep-with-previous.within-column="always"> keep-with-previous.within-page="always" space-after="10pt"> space-before="0pt" line-height-shift-adjustment="disregard-shifts"> font-family="agenda,helvetica,Symbol">Figure 7: Injection Well W01I01:> Process Control</fo:block></fo:block>>> <fo:block> id="unique_11_Connect_42_fig_ddr_pvp_xdb_d2e1293a1310"><fo:inline> id="unique_11_Connect_42_image_cxc_yvw_j2b_d2e1298a1310"> margin-right="0.15in"><fo:external-graphic content-width="5.5in"> src="url(images/fc_all_field_common_injection_well_W01_pcd.png)"/></fo> :inline><fo:block> font-size="10pt" font-weight="bold"> keep-with-previous.within-column="always"> keep-with-previous.within-page="always" space-after="10pt"> space-before="0pt" line-height-shift-adjustment="disregard-shifts"> font-family="agenda,helvetica,Symbol">Figure 8: Injection Well Y01I01:> Process Control</fo:block></fo:block>>> Other things:>> 1. The html output works as expected.> 2. The
 stock dita pdf2 output has the same error, so it doesn't seem > to be my custommization.> 3. I'm using Version 4.24.395>> I'm at a loss. I've tweaked my customization and found nothing (attrs > and> xslt) .Can you please create a fig.title element with that string in > it and see what happens?>> Thanks>>>> On Tue, Jul 17, 2018 at 2:46 PM Kevin Brown <kevin@renderx.com> wrote:>>>> Another debug test would be to run the document to FO (do not delete >> the final FO that is being sent).>>>> Examine that.>>>> 1) Are the characters there or not? If they are not … it is something>> in the DITA/XSL chain and has nothing to do with the PDF generation.>>>> 2) If they are … then post the two snippets of the FO so we can>> examine what fonts are used and what character selection strategy>>>>>>>> Kevin Brown>>>> RenderX>>>>>>>> From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf >> Of Kevin Brown>> Sent: Tuesday, July 17, 2018 11:37 AM>> To: 'RenderX Community Support List' <xep-support@r
enderx.com>>> Subject: [xep-support] Re: String encoding issue>>>>>>>> It is completely unclear how this relates to RenderX but one guess >> would be that you are using different fonts in each of the two representations.>>>> One font contains those glyphs, the other does not.>>>> Check what fonts are used in each of two cases.>>>>>>>> Kevin Brown>>>>>>>>>>>> From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf >> Of Morley Tooke>> Sent: Tuesday, July 17, 2018 11:32 AM>> To: RenderX Community Support List <xep-support@renderx.com>>> Subject: [xep-support] String encoding issue>>>>>>>> Hello,>>>>>>>> One of my writers has run into an issue where a string of numbers in >> a fig is being rendered out of his topic. I've seen this once before >> with a very similar string.This is his code:>>>>>>>> <title class="- topic/title ">Injection Well W01I01: Process >> Control</title>>>>>>>>> His output looks something like this:>>>>>>>> Injection Well W>>>>>>>> There is nothing special in the PDF customiza
tion code.>>>>>>>> This is the rest of his email to me:>>>>>>>> The basic gist is that I have a well that is labelled W010I01. And >> when I enter that label in body text, it renders fine in the PDF. >> However, when I enter it in a fig title tag, the W will render, but >> the rest of the text is left blank. EG:>>>>>>>> I have tried a few variations in the title text to see what happens.>> Adding a space between W and 0 works fine:>>>>>>>> As does replacing the first 0 with a capital O:>>>>>>>> But W01xxx is a no-go. So, far as I can gather, EasyDITA or Oxygen >> are interpreting that W01xxx as something other than plain text, and >> removing it from the document altogether.>>>>>>>> Thanks in advance,>>>>>>>> Morley>>>>>>>>>>>> _______________________________________________>> (*) 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>>> _____________________
__________________________> (*) 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

-- Dave PawsonXSLT XSL-FO FAQ.Docbook FAQ.
_______________________________________________(*) 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://www.renderx.com/terms-of-service.html
_______________________________________________(*) 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://www.renderx.com/terms-of-service.html
Received on Fri Jul 20 10:44:44 2018