Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105706
interpreted = N
texte = --Apple-Mail-4-874880259 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Thanks Tom, and Chris (in the forum thread, same topic), for your =20 feedback. Chris, my question was not about re-populating a form input, but (for =20 example) about massaging (via Webdna) the formerly-*JS-massaged* data =20= so we can write it to db and have it accurately represent the data =20 that was originally input by the user. Anyway, let me assimilate the comments you two made about UTF-8, and =20 I'll set up some test pages we can use to better have any =20 discussion... before I get back to you with further questions. Thanks! -Govinda On Aug 16, 2010, at 4:54 AM, Tom Duke wrote: > Govinda, > > Hi - I switched to UTF-8 a good few years ago. Basic rule is to =20 > ensure that you use UTF-8 encoding for all your templates and dbs. > > Most web service APIs that I have come across expect UTF-8, so I'm =20 > not sure where your Javascript problem will kick in. You can also =20= > specify the charset within the HTML