nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Double byte content displayed as question marks on page pre-view

PRK

Hi all,

We are using LSDS 7.2.1 on Windows 2008 server R2, IIS7.5,
and Teamsite 7.2.1 on the same machine.

When we enter double-byte content (Asian characters) into a SitePublisher page, it displays correctly in the editor, but not when previewing the page.
When the page is previewd these characters aredisplayed as questin marks.

The characters are replaced by question marks on the preview page.

Thanks and regards,
Pranav.

Find more posts tagged with

Comments

Rick Poulin

Make sure your browser is interpreting the page as UTF-8 and not CP1252 or some other single byte encoding. If your web server isn't serving pages as UTF-8 by default, you may need to add something like <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> to your html header. If you're producing XHTML, you also make sure that your XML declaration says encoding="UTF-8".

PRK

Hi ,

The previewed page does have a head section which declares UTF-8 as the character set. The page still shows question marks for the asian characters. However, when the component (this is the basic web page content OOTB component) is edited, the editor (TinyMCE) displays the characters just fine.

Thanks and regards,
Pranav

Rick Poulin

Oh, I thought you were saying they rendered fine in SitePub edit mode, not just TinyMCE. In that case, it's probably just a case where 1) make sure TinyMCE saves those characters as HTML/XML entities, and 2) make sure that your component disables the output escaping when you read the value, e.g.

<xsl:value-of select="/my/path/to/field" disable-output-escaping="yes" />

If that doesn't work, inspect the page using firebug or similar and post what the character looks like in the HTML source. Also, what does it look like in Firefox? If it's an unrecognized character, you'll see a box with the unicode character index value. If it's an actual problem passing the value around in your components and such, it'll still show up as a question mark.

PRK

Hi Rick,

This is the OOTB baic content component and its using $MODEL to fetch the textarea content directly into the Html . Should'nt this fetch the double byte characters in the textarea without the escaping?

Thanks and regards,
Pranav.

Rick Poulin

You might want to try converting the output to HTML entities, with $CONVERT or $EX_MODEL. Did you override the server_locale param in iw.cfg or is it still the default value? I'm thinking there must be a similar encoding/locale setting for sitepub/livesite, but I can't find it ATM.