headers
Joachim Zobel | 17 Apr 20:41
Picon
Favicon

entity euro hurts

Hi.

I am using 2.05 I have got   to work by using 
	input        => 'HTML',
	output       => 'HTML',
but if I use € or € it turns to  Â, while € turns to
€.

What is going on here?

Sincerely,
Joachim

--

-- 
"... ein Geschlecht erfinderischer Zwerge, die fuer alles gemietet werden 
koennen."                            - Bertolt Brecht - Leben des Galilei
Permalink | Reply |
headers
Michele Beltrame | 18 Apr 21:48
Gravatar

Re: entity euro hurts


> I am using 2.05 I have got   to work by using 
> 	input        => 'HTML',
> 	output       => 'HTML',
> but if I use € or € it turns to  Â, while € turns to
> â???¬.

I have the same problem, that's why I have to avoid using "€" for
now. :-(

I'm just using output => 'XHTML' and leave the rest as per default.
" " works until I insert an "€", after which no entity
seems to work anymore until I remove it.

	Michele.

--

-- 
Michele Beltrame
http://www.italpro.net/mb/
ICQ# 76660101 - e-mail: mb-pzZ8rf8/VxTR7s880joybQ==@public.gmane.org
Permalink | Reply |
headers
Mark Holland | 19 Apr 01:41

Re: entity euro hurts

Michele Beltrame wrote:

>>I am using 2.05 I have got   to work by using 
>>	input        => 'HTML',
>>	output       => 'HTML',
>>but if I use € or € it turns to  Â, while € turns to
>>â???¬.
>>    
>>
>
>I have the same problem, that's why I have to avoid using "€" for
>now. :-(
>
>I'm just using output => 'XHTML' and leave the rest as per default.
>" " works until I insert an "€", after which no entity
>seems to work anymore until I remove it.
>  
>
Try making sure all your output is unicode and that your browser is 
aware of this by setting your http content-type header to:

Content-type: text/html; charset=utf-8

and adding the following meta tag to your html (as some browsers don't 
honour/recognise the charset portion of the content-type header)

<meta http-equiv="content-type" content="text/html" charset=utf-8"/>

 I tried the &euro; entity on my system with this set up and it produces 
the character with no problems.
(Continue reading)

Permalink | Reply |
headers
Michele Beltrame | 19 Apr 09:53
Gravatar

Re: entity euro hurts

Hi!

> Try making sure all your output is unicode and that your browser is 
> aware of this by setting your http content-type header to:
> 
> Content-type: text/html; charset=utf-8

Actually, all my templates are in 'latin1'. Is this a thing to be
avoided? If so, why?

	Thanks, Michele.

--

-- 
Michele Beltrame
http://www.italpro.net/mb/
ICQ# 76660101 - e-mail: mb-pzZ8rf8/VxTR7s880joybQ==@public.gmane.org
Permalink | Reply |
headers
Mark Holland | 20 Apr 01:42

Re: entity euro hurts

Michele Beltrame wrote:

>
>Actually, all my templates are in 'latin1'. Is this a thing to be
>avoided? If so, why?
>  
>
Well I've switched everything to unicode because I could never seem to 
successfully encode the output from Petal into latin1. I've never really 
had time to investigate, I just know unicode works for me.
Permalink | Reply |
headers
Mark Holland | 19 Apr 01:43

Re: entity euro hurts

Mark Holland wrote:

> and adding the following meta tag to your html (as some browsers don't 
> honour/recognise the charset portion of the content-type header)
>
> <meta http-equiv="content-type" content="text/html" charset=utf-8"/>

bah. that should be a semicolon, not a double quote, like so:

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

time for bed methinks.

~mark
Permalink | Reply |

Gmane