Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Incorrect entity mapping in FrameMaker 11 and 12 - A FYI!

Contributor ,
Feb 11, 2015 Feb 11, 2015

Copy link to clipboard

Copied

In testing round tripping of XML to FrameMaker to XML I came across a particular ISO character 'lsquo' (Unicode x2018) which FrameMaker happily converted to the equivalent internal character xd4, and then promptly converted it to the entity 'rsquor' when saving as XML.  I have traced the cause to incorrect mappings in the entity files as shown below.  The same entity mapping error exists in FrameMaker 12.  I am guessing that the mapping may have been in the early version of the standard, however the latest version has the correct mappings (http://www.w3.org/2003/entities/iso8879doc/isopub.html).

In the file isopub.rw in folder %ProgramFiles(x86)%\Adobe\AdobeFrameMaker11\Structure\xml\isoents the following entries are incorrect, and should be set as shown:

entity "rsquor" is fm char 0x2018; should be entity "rsquor" is fm char 0x2019;
entity "rdquor" is fm char 0x201C; should be entity "rdquor" is fm char 0x201D;

In the file iso-pub.ent in folder %ProgramFiles(x86)%\Adobe\AdobeFrameMaker11\Structure\xml\isoents the following entries are incorrect, and should be set as shown:

<!ENTITY rdquor "&#x201C;"> <!--  --> should be <!ENTITY rdquor "&#x201D;"> <!--  -->
<!ENTITY rsquor "&#x2018;"> <!--  --> should be <!ENTITY rsquor "&#x2019;"> <!--  -->

You can choose to correct the entries in the folder locations above, however I like to keep changes there to a minimum so I added a RulesSearchPaths entry for each structured application to point to a folder controlled by logon scripts, which includes the complete isoent folder with both files updated.

 

You can also place the correct entity declarations before the include of isopub.rw however this does not work around the incorrect entries in iso-pub.ent.

Jon

TOPICS
Structured

Views

1.1K
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
LEGEND ,
Feb 11, 2015 Feb 11, 2015

Copy link to clipboard

Copied

Thanks for letting us userknow about this Jon.

Have you also reported this to the Bugbase (https://bugbase.adobe.com/index.cfm) for a formal record of this incorret mappng?

Votes

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
Contributor ,
Feb 11, 2015 Feb 11, 2015

Copy link to clipboard

Copied

Arnis,

I have notified Adobe through a direct email link however I will also report it to the bugbase as you suggest.

Thanks!

Jon

Votes

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
Contributor ,
Feb 22, 2015 Feb 22, 2015

Copy link to clipboard

Copied

LATEST

An additional incorrect mapping!

In the file isoamsr.rw in folder %ProgramFiles(x86)%\Adobe\AdobeFrameMaker[11|12]\Structure\xml\isoents the following entry is incorrect, and should be set as shown:

entity "ges" is fm char 0x2265; should be entity "ges" is fm char 0x2A7E;

In the file iso-amsr.ent in folder %ProgramFiles(x86)%\Adobe\AdobeFrameMaker[11|12]\Structure\xml\isoents the following entry is incorrect, and should be set as shown:

<!ENTITY ges "&#x2265;"> <!-- GREATER-THAN OR EQUAL TO --> should be <!ENTITY ges "&#x2A7E;"> <!-- GREATER-THAN OR SLANTED EQUAL TO -->

Given this is the third incorrect mapping so far, I am, given time, going to check all files for duplicates.  It is a completely separate, and time consuming task, to check that all entries map to the correct Unicode character unless they duplicate a correct entry, like the one here.  I only found this entry because I was looking for instances of 0x2265.

Jon

Votes

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