Genx Posted July 4, 2006 Posted July 4, 2006 Hi, just trying to substitute out all the XML reserved characters but i'm having a really hard time doing it. There seem to be more than what is stated (e.g. ' vs ‘ vs ’ and different types of quotes etc.) Anyone know of a really long custom function that will make my field contents absolutley xml safe (or alternatively some way to specify to ignore these characters through xslt?). Any direction regarding this would be much appreciated. Cheers, ~Genx
Martin Brändle Posted July 4, 2006 Posted July 4, 2006 In which context? XML import/export, or custom web publishing? I don't quite understand what you mean with and why you want to substitute the XML reserved characters. There is no need to convert characters as long as they belong to the XML char set, which is the complete UTF-8 set minus the characters with ASCII code < 32, plus the white space characters tab, carriage return, or line feed. Just make sure that your XSLT uses UTF-8 as encoding.
Fenton Posted July 4, 2006 Posted July 4, 2006 (edited) There is an attribute: disable-output-escaping="yes" (which I've used to preserve html tags which are inside a FileMaker field when exporting to html text) There is: your content here Which says more or less, leave this alone. No processing takes place inside the tag. There is also just encoding it yourself, ie., < instead of < But it's hard to say what would be best, because we don't know what you're doing exactly; and because I don't always know which is best anyway :-] Edited July 4, 2006 by Guest
Genx Posted July 4, 2006 Author Posted July 4, 2006 I'm trying to export to another source and it's just not working out properly. I'll try the output escaping thing and or the !CDATA section. I'll also have a look at what all the chars are with ascii less than 32. Cheers guys, ~Genx
Genx Posted July 5, 2006 Author Posted July 5, 2006 Out of curiosity, if i did the following, would this work?: Create an extra calc field that basically has: Table::DataField Export that and then just use the following as the xsl: Would it actually recognise it as a proper CDATA entry?
Genx Posted July 5, 2006 Author Posted July 5, 2006 I tried it and it doesnt seem to recognise it sigh.
Recommended Posts
This topic is 6714 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now