Wim, I would take a look at the XSLT 2.0 'character-map' statement. See http://www.w3.org/TR/xslt20/#dt-character-map for details. It was designed to handle this sort of problem.
You will need to run the XSLT transform using an XSLT 2.0-compliant processor. Note that FrameMaker 7.2 provides an XSLT 1.0-compliant processor. This is reasonable, since XSLT 2.0 has not yet been finalized by the W3C. Using xsl:choose to test for the presence of multiple Unicode characters is problematic. When any single xsl:choose test evaluates to 'true', subsequent tests are not invoked. Also, you are likely to want to translate Unicode characters to character entities (e.g., č), and the translate() function will only map to single replacement characters. Javascript should not cause any problems, as long as XML special characters in the Javascript are escaped in the result of the transformation. (e.g., '<' must be represented as '<'). -Alan Wim Hooghwinkel (Scriptware) wrote: > Hello all, > > I am trying to create a XSLT template to transform uncode characters to ansii > on import of XML in FM. This concerns the unicode characters for CE/EE > languages that can not be read by FM. > > As I don't have any experience with XSLT, could anyone point me in the right > direction? Probably need a kind of if-else construction or variables to use > the 'transate' function. > > How does FM react when an XSLT refers to Javascript? > > > Met vriendelijke groet / kind regards, > > Wim Hooghwinkel wimh at scriptware.nl > DTP and XML Management > -- Alan Houser, President Group Wellesley, Inc. 412-363-3481 www.groupwellesley.com