Re: [WebDNA] special chars

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 101917
interpreted = N
texte = --Apple-Mail-2--10385540 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed 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 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-2--10385540 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=WINDOWS-1252 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 problem.
I'm used to Latin character but now it's = when reading the filename that I have the problem. = [listfiles]
on my computer (OSX) I sent the file through = Transmit to an (OSX server) and once arrived on the server the file name = isn't "r=E9union" 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 would be more fun=85=85You went and = made it easy.
=A0
Mike
=A0
From:=A0Tom Duke = [mailto:tom@revolutionaries.ie]=A0
Sent:=A0Thursday, February 05, 2009 = 9:45 AM
To:=A0talk@webdna.us
<= span style=3D"font-weight: bold; ">Subject:=A0Re: [WebDNA] special = chars
=A0
Hi,
=A0
Use Unicode = (UTF-8) for your character set and you should be OK with all these = characters. =A0You can use
=A0
=A0=A0 = [setmimeheader name=3DContent-Type&value=3Dtext/html; = charset=3Dutf-8]
=A0
at the top of = all your pages. =A0If you have existing content / dbs which use other = character sets then you can use BBedit to easily convert these. =A0Just = open the file using the correct character set (File > Reopen using = encoding >) =A0and then at the bottom of the BBedit window you can = change the character set to 'utf-8, no BOM' save and your = done.
=A0
- = Tom
=A0

= --Apple-Mail-2--10385540-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] special chars --> WebDNA file upload (Brian Fries 2009)
  2. [WebDNA] special chars --> WebDNA file upload (Lawrence Banahan 2009)
  3. Re: [WebDNA] special chars --> WebDNA file upload (christophe.billiottet@webdna.us 2009)
  4. Re: [WebDNA] special chars --> WebDNA file upload (Tom Duke 2009)
  5. Re: [WebDNA] special chars --> WebDNA file upload (Govinda 2009)
  6. Re: [WebDNA] special chars (lawrence@authorsimage.com 2009)
  7. Re: [WebDNA] special chars (Tom Duke 2009)
  8. Re: [WebDNA] special chars (Tom Duke 2009)
  9. Re: [WebDNA] special chars (christophe.billiottet@webdna.us 2009)
  10. Re: [WebDNA] special chars (Steve Craig 2009)
  11. Re: [WebDNA] special chars (lawrence@authorsimage.com 2009)
  12. Re: [WebDNA] special chars (Tom Duke 2009)
  13. Re: [WebDNA] special chars (christophe.billiottet@webdna.us 2009)
  14. Re: [WebDNA] special chars (lawrence@authorsimage.com 2009)
  15. Re: [WebDNA] special chars (Tom Duke 2009)
  16. Fwd: [WebDNA] special chars (Lawrence Banahan 2009)
  17. Re: [WebDNA] special chars (lawrence@authorsimage.com 2009)
  18. Re: [WebDNA] special chars (Tom Duke 2009)
  19. RE: [WebDNA] special chars ("Michael A. DeLorenzo" 2009)
  20. RE: [WebDNA] special chars ("Michael A. DeLorenzo" 2009)
  21. Re: [WebDNA] special chars (Tom Duke 2009)
  22. Re: [WebDNA] special chars (William DeVaul 2009)
  23. [WebDNA] special chars (lawrence@authorsimage.com 2009)
--Apple-Mail-2--10385540 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed 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 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-2--10385540 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=WINDOWS-1252 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 problem.
I'm used to Latin character but now it's = when reading the filename that I have the problem. = [listfiles]
on my computer (OSX) I sent the file through = Transmit to an (OSX server) and once arrived on the server the file name = isn't "r=E9union" 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 would be more fun=85=85You went and = made it easy.
=A0
Mike
=A0
From:=A0Tom Duke = [mailto:tom@revolutionaries.ie]=A0
Sent:=A0Thursday, February 05, 2009 = 9:45 AM
To:=A0talk@webdna.us
<= span style=3D"font-weight: bold; ">Subject:=A0Re: [WebDNA] special = chars
=A0
Hi,
=A0
Use Unicode = (UTF-8) for your character set and you should be OK with all these = characters. =A0You can use
=A0
=A0=A0 = [setmimeheader name=3DContent-Type&value=3Dtext/html; = charset=3Dutf-8]
=A0
at the top of = all your pages. =A0If you have existing content / dbs which use other = character sets then you can use BBedit to easily convert these. =A0Just = open the file using the correct character set (File > Reopen using = encoding >) =A0and then at the bottom of the BBedit window you can = change the character set to 'utf-8, no BOM' save and your = done.
=A0
- = Tom
=A0

= --Apple-Mail-2--10385540-- lawrence@authorsimage.com

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Converting spaces to + in results list (2000) WebCat2b12 - nesting [tags] (1997) I hate talking to myself on this list (2004) Secure server question (1997) Thanks for tips, more quest (1997) Initiating NewCart (1997) BUG REPORT: numeric ge, le, gr & ls comparisons don't work ... (1999) Quit revisited (1997) SMSI FTP - calander system (2002) Creating main- and sub-category search (1997) Unexpected error (1997) Redirect frame targets (1998) Site Builder & IE Mac (2004) [WebDNA] trouble with memory (2014) Separate SSL Server (1997) [protect] and identification (2008) Country & Ship-to address & other fields ? (1997) F3 crashing server (1997) OT: 128 bit Encryption (2003) A little syntax help (1997)