[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 = 105704
interpreted = N
texte = Hi WSC, Chris, et al :-) I am mostly new at playing with characters out of the range of things =20= we see on our keyboard.. but in light of needing to go back and forth =20= between JS and Webdna sometimes.. like when making ajax calls to pages =20= that need to pass form data via JS (and so be escaped via JS).. and =20 then write that data to disk *via webdna*... it would sure be nice to have a webdna version of javascript's: escape(str) unescape(str) To see what I mean, look at this example: If we take the British pound symbol: =A3 (option-3 on a mac) If we have the file's encoding set to UTF-8, then that char, [url]'ed =20= becomes: %C2%A3 but in JS, and here: http://www.w3schools.com/tags/ref_urlencode.asp it becomes: %A3 If we change the file's encoding to Mac OS Roman, then webdna does =20 [url] the british pound symbol into: %A3 but then the JS (FF3/mac) turns the british pound symbol into: %uFFFD ..so again we do not have consistency between the 2 languages. Furthermore, whatever the file's encoding, webdna's [unUrl] only =20 produces the british pound symbol when wrapped around: %C2%A3 (I.e. there does not seem to be any way to get webdna's [unUrl] to =20 change: %A3 into the british pound symbol. As I said I am rather newbie when working with projects that =20 definitely need to be using UTF-8.. but my understanding is that that =20= is the current standard. In light of this.. does it seem reasonable =20 to request a couple new webdna contexts that encode/decode just like =20 javascript's escape/unescape? Or put another way, can we have a =20 couple contexts that turn all characters into what is listed here http://www.w3schools.com/tags/ref_urlencode.asp when file is UTF-8. Or someone please explain to me what I need to understand more deeply =20= before I make (uneducated?) requests like the above. Thanks! ------------ Govinda govinda.webdnatalk@gmail.com Associated Messages, from the most recent to the oldest:

    
  1. Re: -- SOLVED -- [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  2. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Christer Olsson 2010)
  3. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  4. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Tom Duke 2010)
  5. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  6. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Tom Duke 2010)
  7. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  8. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  9. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Tom Duke 2010)
  10. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  11. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  12. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Tom Duke 2010)
  13. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  14. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
  15. Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Tom Duke 2010)
  16. [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets (Govinda 2010)
Hi WSC, Chris, et al :-) I am mostly new at playing with characters out of the range of things =20= we see on our keyboard.. but in light of needing to go back and forth =20= between JS and Webdna sometimes.. like when making ajax calls to pages =20= that need to pass form data via JS (and so be escaped via JS).. and =20 then write that data to disk *via webdna*... it would sure be nice to have a webdna version of javascript's: escape(str) unescape(str) To see what I mean, look at this example: If we take the British pound symbol: =A3 (option-3 on a mac) If we have the file's encoding set to UTF-8, then that char, [url]'ed =20= becomes: %C2%A3 but in JS, and here: http://www.w3schools.com/tags/ref_urlencode.asp it becomes: %A3 If we change the file's encoding to Mac OS Roman, then webdna does =20 [url] the british pound symbol into: %A3 but then the JS (FF3/mac) turns the british pound symbol into: %uFFFD ..so again we do not have consistency between the 2 languages. Furthermore, whatever the file's encoding, webdna's [unurl] only =20 produces the british pound symbol when wrapped around: %C2%A3 (I.e. there does not seem to be any way to get webdna's [unurl] to =20 change: %A3 into the british pound symbol. As I said I am rather newbie when working with projects that =20 definitely need to be using UTF-8.. but my understanding is that that =20= is the current standard. In light of this.. does it seem reasonable =20 to request a couple new webdna contexts that encode/decode just like =20 javascript's escape/unescape? Or put another way, can we have a =20 couple contexts that turn all characters into what is listed here http://www.w3schools.com/tags/ref_urlencode.asp when file is UTF-8. Or someone please explain to me what I need to understand more deeply =20= before I make (uneducated?) requests like the above. Thanks! ------------ Govinda govinda.webdnatalk@gmail.com Govinda

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:

[ShowNext] feature in 2.0 (1997) Notepad problems (1998) [GROUPS] followup (1997) WebCatalog Upgrade Pricing? (1997) Listserver problem (1997) [WebDNA] A universal version of WebDNA ... (2008) Rhapsody? (1997) Template not found error messages (1997) Webcat interfering with Webstar? (1998) Possible Bug in 2.0b15.acgi (1997) Re:F*** you (1998) Lookup Notfound (1998) building / customizing stores (2000) emailer w/F2 (1997) Bad File: DeleteCommand.html (1998) Next X hits (1996) [lookup] speed sales pitch (2003) New Plug-in and Type 11 errors (1997) Set Line Item (1999) payment processors (2005)