[xep-support] Re: String encoding issue

[Morley Tooke]

Thanks, I'll take a look. This is being run as part of an EasyDITA
integration, so it's a little bit hard to debug, but I have a similar setup
locally that I can test on.

RE: font/glyph issue - I don't think that is the problem. Those are regular
numeric characters in a fig title element. We have thousands of pages of
content with hundreds of similar equipment tag elements. For whatever
reason (this has happened twice now in three years) certain combinations of
those characters in the element tag are causing the text to disappear. It's
almost like an internal code or value that the rendering engine is picking
up.



On Tue, Jul 17, 2018 at 2:46 PM Kevin Brown <kevin at 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 at renderx.com] *On Behalf
> Of *Kevin Brown
> *Sent:* Tuesday, July 17, 2018 11:37 AM
> *To:* 'RenderX Community Support List' <xep-support at renderx.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 at renderx.com
> <xep-support-bounces at renderx.com>] *On Behalf Of *Morley Tooke
> *Sent:* Tuesday, July 17, 2018 11:32 AM
> *To:* RenderX Community Support List <xep-support at 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 customization 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20180717/9d4253db/attachment.html>