Random characters are not correctly displayed

Explorer ,
Aug 19, 2021 Aug 19, 2021

Copy link to clipboard

Copied

Hi,

 

one FrameMaker instance (technical writer located in India) cannot correctly render some characters in a MIF file. I don't recognize any systematical logic.

 

StefanEike_0-1629384947715.jpeg

What is really strange is, that the ciphered chars "ņ" and "ā" are correctly displayed in the same file at a different position. The problem is reproducible, but only on one specific computer/FrameMaker instance.

 

Do you have an idea? I've already tried setting the Windows locale to UTF-8, but this did not help.

https://superuser.com/questions/1033088/is-it-possible-to-set-locale-of-a-windows-application-to-utf...

 

Adobe does not allow me to upload the original MIF file, therefore I've renamed the MIF to TXT and upload it here. If you want to open the file, please rename the file extension from TXT to MIF first.

TOPICS
Error

Views

99

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Correct answers

Adobe Community Professional , Aug 20, 2021 Aug 20, 2021
All I'd suggest is contacting the FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

Likes

Translate

Translate
Explorer , Aug 29, 2021 Aug 29, 2021
Hi,the problem has been solved now. The reason is still a mystery but it has helped to upgrade FM from 2019 to 2020.BRStefan

Likes

Translate

Translate
Explorer ,
Aug 19, 2021 Aug 19, 2021

Copy link to clipboard

Copied

I'm also not allowed to upload a MIF file renamed to TXT. This link guides you to the MIF file: https://wetransfer.com/downloads/8603c98c3eb2be93a7b55f4d7b35b5b620210819150238/9c350c01b26f8697088d...

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Aug 19, 2021 Aug 19, 2021

Copy link to clipboard

Copied

Have you looked at the FM file at the spot where those two characters are giving you problems? Does replacing them fix anything in the MIF?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Aug 19, 2021 Aug 19, 2021

Copy link to clipboard

Copied

I'm not really sure what you mean. When I save the MIF to FM on this computer, the problem remains. The affected content snippet is:

<Para 
  <Unique 1050907>
  <PgfTag `BodyText'>
  <PgfReferenced Yes>
  <ParaLine 
<Unconditional > 
<String `Sildītājs ir paredzēts lietošanai motorizētajos un nemotorizētajos tūrisma furgonos un citos transportlīdzekļos, kuros ir tikai dzīvojamās telpas, ja gāzes sistēma ir ierīkota saskaņā ar EN'>
<Char HardSpace>
<String `1949. '>
  > # end of ParaLine
 > # end of Para

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Aug 19, 2021 Aug 19, 2021

Copy link to clipboard

Copied

Normally, an unexpected "?" means one of two things:
1. The currently applied font does not populate the Unicode BMP codepoint. FM does not do fallback.
2. It's a Unicode SMP codepoint (above U+FFFF, and thus not supported yet by FM at all).

 

In this case, these are both BMP codepoints, which rules out the SMP limitation.

ņ U+0146 LATIN SMALL LETTER N WITH CEDILLA
ā U+0101 LATIN SMALL LETTER A WITH MACRON
and this would still be the case even if these are composed characters using the
Unicode combining cedilla (U+0327) and macron (U+0304).

 

This suggests something peculiar with the fonts on the machine exhibiting the artifact.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Aug 19, 2021 Aug 19, 2021

Copy link to clipboard

Copied

Hi Bob,

 

Thanks a lot for digging into this. Unfortunately that cannot be the problem. We have compared the installed fonts on the affected computer with the fonts we use on other tech writer machines. The fonts are exactly the same.

This is really confusing to me, as the issue seems to be absolutely random.

 

Any other ideas?

 

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Aug 20, 2021 Aug 20, 2021

Copy link to clipboard

Copied

All I'd suggest is contacting the FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Aug 29, 2021 Aug 29, 2021

Copy link to clipboard

Copied

LATEST

Hi,

the problem has been solved now. The reason is still a mystery but it has helped to upgrade FM from 2019 to 2020.

BR

Stefan

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines