Re: isolat2.rw

[Dan Emory <danemory@xxxxxxxxxxxx>]

In my earlier post on this thread I stated:
================================================================
Finally, there is a bug in FM+SGML 5.5.x that compounds the problem.
According to the developers guide, the order in which the #include
statements for the .rw files appear in the main r/w rules file determines
the precedence. But this is not true. There are a number of code points in
the isolatin2 character set that correspond to the same code points in
isolatin1. In those cases, FM+SGML chooses the isolatin1 entity rather than
the isolatin2 entity, even though the #include statement for isolatin2
appears before isolatin2. FM+SGML appears to have the order of precedence of
these entities "hard wired". The only way to make it work is to comment out
in isolat1.ent and isolat1.rw both the entity declarations and the
read/write rules for the conflicting entities.
================================================================
What I forgot to mention is that there are also code points that conflict with
isolatin2 in other .ent and .rw files (e.g., isonum and isodia) The entities
in those files also must be commented out before the right entity references
are produced on export, or before the correct character is produced on import.

     ====================
     | Nullius in Verba |
     ====================
Dan Emory, Dan Emory & Associates
FrameMaker/FrameMaker+SGML Document Design & Database Publishing
Voice/Fax: 949-722-8971 E-Mail: danemory@primenet.com
10044 Adams Ave. #208, Huntington Beach, CA 92646
---Subscribe to the "Free Framers" list by sending a message to
   majordomo@omsys.com with "subscribe framers" (no quotes) in the body.


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **