Encoding settings

  • Input character encoding (cms): What input character encoding should we expect? Seldom needed to be changed – only if you experience encoding problems when entering data in InfoGlue’s standard GUI:s.
  • Input character encoding (deliver): What input character encoding should we expect when data is entered on pages on the site? Important when we use portlets etc and can depend on what encoding the site is written in, how the web server/tomcat is configured etc.
  • URI-encoding: What encoding should be used when InfoGlue deals with i18n strings when creating url’s inside cms?
  • Workflow encoding: What input character encoding should be used for the workflow definitions. Defaults to utf-8.
  • Property forms encoding: Not used at the moment.
  • Upload asset key from encoding: Just use this if asset keys(i18n chars) get scrambled. Should default to correct encoding since 2.5.0.
  • Upload asset key to encoding: Just use this if asset keys(i18n chars) get scrambled. Should default to correct encoding since 2.5.0.
  • Asset key from encoding in WYSIWYG asset dialog: Just use this if asset keys when using the wysiwyg with i18n chars in names get scrambled. Should default to correct encoding since 2.5.0.
  • Asset key to encoding in WYSIWYG asset dialog: Just use this if asset keys when using the wysiwyg with i18n chars in names get scrambled. Should default to correct encoding since 2.5.0.



comments powered by Disqus