What is the correct content_type setting?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

What is the correct content_type setting?

jc-15
As Lasso 8 produce UTF encoded results, what is the correct
content-type setting for HTML pages produced with Lasso 8 content?

My template use
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">

but maybe this is better
<meta http-equiv="content-type" content="text/html; charset=utf-8">

Opinions?

HDB
JC


--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives: http://www.listsearch.com/lassotalk.lasso
Manage your list subscription:  
http://www.listsearch.com/lassotalk.lasso?manage
Reply | Threaded
Open this post in threaded view
|

Re: What is the correct content_type setting?

James Harvard
Whether you use the UTF-8 or ISO Latin 1 character set you choose to use you should ensure that the META tag on your page matches the content-type field from the HTTP response headers.

[encode_break: $__http_header__ ]

Others can probably advise on the most appropriate choice of character set for your application - I have to be honest and say that I've not really looked into the issue in depth.

James

>As Lasso 8 produce UTF encoded results, what is the correct content-type setting for HTML pages produced with Lasso 8 content?
>
>My template use
><meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
>
>but maybe this is better
><meta http-equiv="content-type" content="text/html; charset=utf-8">
>
>Opinions?
>
>HDB
>JC

--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives: http://www.listsearch.com/lassotalk.lasso
Manage your list subscription:  
http://www.listsearch.com/lassotalk.lasso?manage
Reply | Threaded
Open this post in threaded view
|

Re: What is the correct content_type setting?

Fletcher Sandbeck
In reply to this post by jc-15
On 5/19/05 at 6:58 AM by [hidden email] (JC):

>As Lasso 8 produce UTF encoded results, what is the correct
>content-type setting for HTML pages produced with Lasso 8 content?
>
>My template use
><meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
>
>but maybe this is better
><meta http-equiv="content-type" content="text/html; charset=utf-8">
>
>Opinions?

Since Lasso is reporting the content-type it is actually sending in the HTTP headers, there is no need to have a meta tag at all.

The http-equiv meta tags provide the HTML author a way of over-riding HTTP headers in static pages.  When you are using a dynamic tool like Lasso that can actually set HTTP headers directly, the http-equiv meta tags are unnecessary.  

Browsers will use the meta tag over that values set in the header so if the meta tag defines a
different charset than is actually being used the browser may render some characters wrong.

[fletcher]
--
Fletcher Sandbeck                         [hidden email]
Lasso Product Specialist              [hidden email]
OmniPilot, Software Inc.                http://www.omnipilot.com

--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives: http://www.listsearch.com/lassotalk.lasso
Manage your list subscription:  
http://www.listsearch.com/lassotalk.lasso?manage