Hi Peter, You are right. There was a bug in the XML writer, the FEATURE_ENCODING value that is set by the user was not being fetch correctly and so it took no effect.
The XML writer fix should be available in the next FME beta; there should be some sort of message in the whatsnew.txt file looking something like: "XML Writer: Fix the FEATURE_ENCODING keyword such that the value set by the user is actually propagated." Also, if you only set the writer's SYSTEM_ENCODING then the FEATURE_ENCODING and MAPPING_FILE_ENCODING will inherit the encoding you set for system. Sorry about this, Juan > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > gravepmsms > Sent: November 2, 2005 1:36 AM > To: [email protected] > Subject: [fme] Re: MicroStation character set > > I've successfully managed to change the Output Dataset Encoding, to > Unicode, ISO 8859-2 and ISO-8859-1. But I have had no luck with the > other settings you suggested (the system encoding, FME Feature > ENcoding and FME Mapping FIle Encoding); whatever the setting, the > input still seems to be interpreted as CP1252. So I'm unable to > output in XML any character that does not have an equivalent in > CP1252. > > Peter > --- In [email protected], "Juan Chu Chow" <[EMAIL PROTECTED]> wrote: > > > > Hi Peter, > > > > The "XML (Generic)" writer will assume by default that the features > it > > gets from the FME are in the system's encoding, in your case the > system > > encoding could be CP1252. In the FME Workbench you can set the "FME > > Feature Encoding" and "FME Mapping File Encoding" parameters > to "UTF-8" > > because the igds reader seems to be giving its features to FME in > UTF-8. > > > > > > Likewise the encoding for the output XML files can be controlled > with > > the "Output Dataset Encoding" parameter, you may set this to > > "ISO-8859-1", leaving this blank defaults to UTF-8. > > > > Hope this helps, > > > > Juan > > > > > -----Original Message----- > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > Of > > > gravepmsms > > > Sent: October 25, 2005 7:00 AM > > > To: [email protected] > > > Subject: [fme] MicroStation character set > > > > > > I'm trying to get text in UTF-8 from MicroStation (igds) to > generic > > > XML. It seems that FME assumes the input is in CP1252 and that it > > needs > > > to be translated into UTF-8. How do I stop the unwanted > translation > > > from happening? > > > > > > For example, the two byte sequence 0xc480 is intended to be UTF-8 > for > > A > > > macron but it is interpreted as A dieresis followed by Euro sign > (ie > > > cp1252). I can tell its not ISO 8859/1 because 0x8a is > interpreted as > > S > > > hacek; it would be a non-printing character in ISO 8859/1. > > > > > > Peter Grave > > > > > > > > > > > > > > > > > > > > > > > > Get the maximum benefit from your FME, FME Objects, or > SpatialDirect > > via > > > our Professional Services team. Visit www.safe.com/services for > > details. > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > Get the maximum benefit from your FME, FME Objects, or SpatialDirect via > our Professional Services team. Visit www.safe.com/services for details. > Yahoo! Groups Links > > > > > Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
