Re: [WebDNA] special chars
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 101926
interpreted = N
texte = Any user with any OS using special caracters (accents..) in his files =20= has the very same problem. It depends on your file encoding, your ftp =20= user and the browser preferences. If you specify charset=3Diso-8859-1 or = =20 charset=3DUTF-8 in your file, then another encoding in your ftp client, =20= this one will try to modify the encoding and the browser will show =20 strange caracters.... the same problem will appear in a form with a =20 text area read with a specific encoding, stored in a webdna database, =20= then read with another encoding. This never happens for users working =20= without special caracters (english) or if you know how to deal with it. chris On Feb 5, 2009, at 14:34, lawrence@authorsimage.com wrote: > Hi Tom, > > it's one thing I thought about, I can select it in Cyberduck. > I think there is no issue to this problem, when I will have clients =20= > uploading folders I wont be able to set their FTPclient... > > Lawrence > > > Le 5 f=E9vr. 09 =E0 17:26, Tom Duke a =E9crit : > >> Lawrence, >> >> My understanding is that OSX does not have a default character set =20= >> - it depends on the application that creates the file/folder. So =20= >> as Christophe says there should be a preference somewhere in =20 >> transmit for default encoding - I use Fetch and this can be set in =20= >> the preferences. >> >> - Tom >> >> >
Associated Messages, from the most recent to the oldest:
Any user with any OS using special caracters (accents..) in his files =20= has the very same problem. It depends on your file encoding, your ftp =20= user and the browser preferences. If you specify charset=3Diso-8859-1 or = =20 charset=3DUTF-8 in your file, then another encoding in your ftp client, =20= this one will try to modify the encoding and the browser will show =20 strange caracters.... the same problem will appear in a form with a =20 text area read with a specific encoding, stored in a webdna database, =20= then read with another encoding. This never happens for users working =20= without special caracters (english) or if you know how to deal with it. chris On Feb 5, 2009, at 14:34, lawrence@authorsimage.com wrote: > Hi Tom, > > it's one thing I thought about, I can select it in Cyberduck. > I think there is no issue to this problem, when I will have clients =20= > uploading folders I wont be able to set their FTPclient... > > Lawrence > > > Le 5 f=E9vr. 09 =E0 17:26, Tom Duke a =E9crit : > >> Lawrence, >> >> My understanding is that OSX does not have a default character set =20= >> - it depends on the application that creates the file/folder. So =20= >> as Christophe says there should be a preference somewhere in =20 >> transmit for default encoding - I use Fetch and this can be set in =20= >> the preferences. >> >> - Tom >> >> >
christophe.billiottet@webdna.us
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:
Mime Headers for Mail (1998)
& not allowed in db by definition? (1999)
[BULK] [WebDNA] Happy St. Patricks Day WEBDNA (2018)
RE: Template not found error messages (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
[WebDNA] Sorry, WebCatalog server not running. (2008)
I have troubles to send message out (1998)
Setting up shop (1997)
Duplicate Messages (1998)
Potential Conflicts? (1997)
Bug or syntax error on my part? (1997)
PROBLEM (1997)
Running _every_ page through WebCat ? (1997)
Windows-based Code Editor (2002)
Delete problem (2005)
WebCommerce: Folder organization ? (1997)
PSC recommends what date format yr 2000??? (1997)
Running 2 two WebCatalog.acgi's (1996)
WebCatalog can't find database (1997)
[OT] Ecommerce Insurance (2000)