charset and utf

A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.

This thread is closed to new posts. You must sign in to post in the forums.
2/12/2013 11:01:54 AM
Gravatar
Total Posts 21

charset and utf

Here is what they asked..

accented characters problem, can you change the charset randy?
http://158.255.45.230

-------
I just looked at the worldbridge.org site
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
the layout.master we are using has
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US" xml:lang="en">

 

-----  Can we use both together?

Latest mojoportal .net 4.0 MSSql
 

2/13/2013 3:02:47 AM
Gravatar
Total Posts 21

Re: charset and utf


http://devel.worldbridge.org/zonelist.aspx?qzone=1

has some strange characters in for example Monaco or Swiss  in IE

 
Source code has
<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

as well as from the layout.master

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US" xml:lang="en">

 

I cant seem to find ...CodeBehind="~/App_MasterPages/layout.Master.cs"

 
 

2/13/2013 9:36:46 AM
Gravatar
Total Posts 18439

Re: charset and utf

Hi,

That page looks to me like you have developed a custom feature without following recommended guidelines. I don't think those character problems are related to the charset or language declared in the page. I would review how that data is generated, ie if it is stored in an ascii file or in a database table that doesn't support utf or uses varchar instead of nvarchar. Included features in mojoPortal don't exhibit problems with non ascii characters so it is something about your implementation.

But aside from that I do not recommend implementing features in such a way that you pass extra parameters to a CMS page, none of the included features do that. You should use a supporting page instead just like all features that we ship in mojoPortal such as the blog, forums, webstore that need extra params we do not use the CMS page for that, we link to detail pages. The CMS page is just the entry point to the feature it contains the module control which is the entry point of the feature and does not expect additional parameters. The module control should link to the supporting page and pass any needed extra params in addition to pageid and module id (mid). Note that the CMS page has a cannonical url that does not include the extras paramter you are passing which means search indexes will not see the different content from different params. You can get away with developing like that if SEO is not a concern for your feature but it is not the way I recommend doing things.

Hope that helps,

Joe

2/13/2013 9:40:38 AM
Gravatar
Total Posts 18439

Re: charset and utf

You can edit the language and charset directly in your own layout.master file but I don't think that is the problem as mentioned.

You cannot modify the code behind for layout.master.cs because that is compiled into mojoPortal.Web.dll but it is not setting the charset or language, that is just text in your layout.master file.

2/13/2013 11:39:13 AM
Gravatar
Total Posts 9

Re: charset and utf

Joe, our apologies for getting a custom module written but we have hundreds of pages on an old site pulling from a database and this was what we needed in order to use your wonderful CMS So we got a content scraper module developed to display the database stuff in mojo Probably best if we convert all the weird characters in the database. The scraped page on its own looks fine when using the ISO charset it uses but when it is changed to UFT8 it gets those question marks so we know that the meta charset is the issue.
You must sign in to post in the forums. This thread is closed to new posts.