Re: Displaying text and populating form fields

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61153
interpreted = N
texte = Rob Marquardt wrote: > [input] wouldn't make things harder for editing viewable text. Any > characters converted to HTML entities by [input] would (unlike when using > [url]) be presented onscreen as the original, single character. _Any_ HTML entity, whether it is hex, decimal, or character entity, will be rendered by the browser as the associated character. The only time you can detect whether [input] or [url] was used would be to View Source. As I keep harping on, since no one seems to be paying attention, is that [input] changes VTAB into a native linefeed, whereas [url] encodes that too. The fact that [input] returns & and [url] returns %38 is completely beside the point; the user see the ampersand character. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Displaying text and populating form fields (again) ( Kenneth Grome 2005)
  2. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  3. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  4. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  5. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  6. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  7. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  8. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  9. Displaying text and populating form fields (again) ( eLists 2005)
  10. Re: Displaying text and populating form fields (again) ( "eLists" 2005)
  11. Re: Displaying text and populating form fields ( eLists 2005)
  12. Re: Displaying text and populating form fields ( "eLists" 2005)
  13. Re: Displaying text and populating form fields ( John Peacock 2005)
  14. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  15. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  16. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  17. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  18. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  19. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  20. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  21. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  22. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  23. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  24. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  25. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  26. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  27. Re: Displaying text and populating form fields ( John Peacock 2005)
  28. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  29. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  30. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  31. Displaying text and populating form fields ... ( Kenneth Grome 2005)
Rob Marquardt wrote: > [input] wouldn't make things harder for editing viewable text. Any > characters converted to HTML entities by [input] would (unlike when using > [url]) be presented onscreen as the original, single character. _Any_ HTML entity, whether it is hex, decimal, or character entity, will be rendered by the browser as the associated character. The only time you can detect whether [input] or [url] was used would be to View Source. As I keep harping on, since no one seems to be paying attention, is that [input] changes VTAB into a native linefeed, whereas [url] encodes that too. The fact that [input] returns & and [url] returns %38 is completely beside the point; the user see the ampersand character. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ John Peacock

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:

Format question WC Mac f3 (1997) [WebDNA] Content-Type (2010) Multithreading of [replace] (1999) Support ?? (1997) More Applescript (1997) Simple way to create unique SKU (1997) F3 crashing server (1997) Sort Order on a page search (1997) Emailer connect failure definitions (2003) Shared conversion under WebTen (1998) Execute Applescript (1997) (slightly off) using menu and [search] (1998) problems with 2 tags (1997) Privacy Issue (Built in sniffer) (2003) Setheader question (1999) Code database (1998) WebCat for mass emailings (1997) Template not completely processed (1998) Not really WebCat- (1997) Am I going senile? (Price recalc based on quantity) (1997)