FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.


Sep 25, 2016, 3:33 PM
324 Posts

Setting Domino HTTP character set to UTF-8

  • Category: Domino Server
  • Platform: IBM i
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags:
  • Replies: 0

Having issues with setting the charset of webpages. Currently at 9.0.1FP6, but this really hasn't changed since 8.5.x...

Current settings are: Internet Sites document -> Domino Web Engine -> Character Set -> 'Use UTF-8 for output:' "YES" - but many pages are rendered using US-ASCII. Character set is set as 'Default' on the forms (in Designer).

It appears that forms that are opened with 'OpenForm' generally specify 'UTF-8', while forms being opened via 'ReadForm' as well as $$ViewTemplates specify 'US-ASCII'.

Additionally, took me a while to find it, but in order to have the Content Type shown automatically on a webpage, one must set 'Meta content type' to 'Enabled' - but found that this option is hidden when 'Use UTF-8 for output:' is set to "YES". Setting the option to 'No' allows the 'Meta content type' to be changed, then setting UTF-8 Output back to 'Yes'. Don't know if this is an accident or by design, also not sure if this works through a server restart yet.

So, a couple questions - First of all, does anyone know why UTF-8 isn't being used - as the implication is that it should be...

Second - would it be recommended to set 'Use UTF-8 for Output' to 'No', then set the character sets individually?

Third - it appears that I can override what is being displayed via a setting on each Form in Designer, I just didn't want to have to do that thinking that the default should be.... UTF-8!

Thanks!


FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.