Re: [WebDNA] special chars

This WebDNA talk-list message is from

2009

It keeps the original formatting. numero = 101925
interpreted = N
texte = --Apple-Mail-242--5398491Content-Type: text/plain;charset=WINDOWS-1252;format=flowed;delsp=yesContent-Transfer-Encoding: quoted-printableHiI've only seen some of this so I may be off subject but I have never =20managed to get the setmimeheader to make any difference on OSX. If I =20need a domain to be changed to utf I change the Apache config file for =20=that host. That's the only time that I have ever had it work.Cheers=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DSteve Craig - Asylum Interactive LtdTel +44 1330 860550 Fax +44 1330 860880=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3Dhttp://www.asylumweb.comEmail: steve@asylumweb.comSkype: s.craig - iChat: steve.craig=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DOn 5 Feb 2009, at 15:22, lawrence@authorsimage.com wrote:> Hello Michael and Tom> It looked easy, but it's not working...> I think it has some thing to do with the OS maybe not a WEBDNA =20> problem.> I'm used to Latin character but now it's when reading the filename =20> that I have the problem. [listfiles]> on my computer (OSX) I sent the file through Transmit to an (OSX =20> server) and once arrived on the server the file name isn't "r=E9union" ==20> but "R=C8union">> Lawrence>> Le 5 f=E9vr. 09 =E0 15:58, Michael A. DeLorenzo a =E9crit :>>> Gee Tom. I thought my more challenging and complicated approach =20>> would be more fun=85=85You went and made it easy.>>>> Mike>>>> From: Tom Duke [mailto:tom@revolutionaries.ie]>> Sent: Thursday, February 05, 2009 9:45 AM>> To: talk@webdna.us>> Subject: Re: [WebDNA] special chars>>>> Hi,>>>> Use Unicode (UTF-8) for your character set and you should be OK =20>> with all these characters. You can use>>>> [setmimeheader name=3DContent-Type&value=3Dtext/html; =charset=3Dutf-8]>>>> at the top of all your pages. If you have existing content / dbs =20>> which use other character sets then you can use BBedit to easily =20>> convert these. Just open the file using the correct character set =20=>> (File > Reopen using encoding >) and then at the bottom of the =20>> BBedit window you can change the character set to 'utf-8, no BOM' =20>> save and your done.>>>> - Tom>>>--Apple-Mail-242--5398491Content-Type: text/html;charset=WINDOWS-1252Content-Transfer-Encoding: quoted-printableHi

I've only =seen some of this so I may be off subject but I have never managed to =get the setmimeheader to make any difference on OSX. If I need a domain =to be changed to utf I change the Apache config file for that host. =That's the only time that I have ever had it =work.

Cheers