That's the ASCII values. They show up in the raw file as < and > because a < and a > was typed in a rich-text processor like word and not in a plain text processor. -- Ryan E. Benson Access Technology Lab Consultant rbenson@xxxxxxxxxxxxxxxx On Wed, 3 May 2006 at 11:21, Chris Gray wrote: > > > Hello: > > In the raw XML files I'm working with, we run into some issues for > certain characters. For example, < and > show up in the raw file as > < and >. In bringing these files into XMetaL, the wordprocesor > we use, the characters resolve themselves properly. But, in Duxbury > they do not. Is there a parameter or technique of some sort to assist > with this? > > Thanks. > > Chris > > > * * * > * This message is via list duxuser at freelists.org. > * To unsubscribe, send a blank message with > * unsubscribe > * as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also > * subscribe, unsubscribe, and set vacation mode and other subscription > * options by visiting //www.freelists.org. The list archive > * is also located there. > * Duxbury Systems' web site is http://www.duxburysystems.com > * * * > * * * * This message is via list duxuser at freelists.org. * To unsubscribe, send a blank message with * unsubscribe * as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also * subscribe, unsubscribe, and set vacation mode and other subscription * options by visiting //www.freelists.org. The list archive * is also located there. * Duxbury Systems' web site is http://www.duxburysystems.com * * *