Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

XML reserved characters

Featured Replies

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

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.

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 by Guest

  • Author

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

  • Author

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?

  • Author

I tried it and it doesnt seem to recognise it sigh.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.