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 "“"> <!-- --> should be <!ENTITY rdquor "”"> <!-- -->
<!ENTITY rsquor "‘"> <!-- --> should be <!ENTITY rsquor "’"> <!-- -->
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