Character Encoding: CMS integration / browser display

Managed by | Updated .

The Modern UI can only produce UTF-8. This means that:

  • The web browser should interpret the page as being encoded in UTF-8. That's guaranteed by setting the right charset in a META tag
  • Any CMS slurping the results should read the content as UTF-8 as well.

Some CMS don't support rendering UTF-8. There is no possible workaround for that on the Funnelback side. The CMS (or something sitting between the CMS and Funnelback) needs to read the content as UTF-8, and then do its own charsets conversion.

That's also true for the XML / JSON endpoint. Those endpoint will produce UTF-8 and only UTF-8, so the consumer needs to work with that or do its own conversion.

Was this artcle helpful?

Comments