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 = 105778
interpreted = N
texte = --Apple-Mail-6-819600994 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable *** Please, anyone who knows Javascript (JS) and WebDNA, take a look! =20= *** OK, I finally made a little time to put together a page where we can =20 tinker/talk about the issue I mentioned in a previous post, if there =20 is one. (Note that some of what I wrote before in that older post =20 was based on a greater degree of ignorance than I have now, so focus =20 mostly on this post.) I am still new at handling chars that need utf-8, let alone in JS =20 (where I am still somewhat green).. but as far as I can tell, there is =20= an issue that needs to be addressed when/where any Webdna programmer =20 gets serious with UTF and JS/AJAX. I hope I am wrong about that. Can =20= anyone help me see that I am wrong, or confirm that we have an issue? The page at the following link explains everything, but ask here if =20 needed, and I will certainly clarify/modify any code anyone (who takes =20= a good look) might suggest. http://www.sleeperhouse.com/admin/govTestDump/webdnaJStest_utf8.html Thanks so much! -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