Re: Updating fields from different platforms

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 18979
interpreted = N
texte = >Another solution I am trying now is to asume everyone is a PC, and let >the Mac try to be compatible. I have placed: > >on all my pages, and I have stored the data in the databases as PC native >accented characters.This is IMO the best approach. Assume everyone is using ISO-8859-1, which is the most used charset on the net.But. Force the use of it by WebCat [SETMIMEHEADER] tag instead of the tag, it's cleaner and you avoid the page being loaded twice.Use the follwing tags on your templates and you should be able to have both new and old browsers use the correct charset:[SETMIMEHEADER name=Content-Type&value=text/html; charset=iso-8859-1] [SETMIMEHEADER name=charset&value=iso-8859-1]Use them both for max compability. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Art director S-211 37 Malmoe Fax +46 40 97 99 77 Ljusa Ideer AB Sweden http://www.ljusaideer.se Associated Messages, from the most recent to the oldest:

    
  1. Re: Updating fields from different platforms (Charles Kefauver 1998)
  2. Re: Updating fields from different platforms (Christer Olsson 1998)
  3. Re: Updating fields from different platforms (Charles Kefauver 1998)
  4. Re: Updating fields from different platforms (Charles Kefauver 1998)
  5. Re: Updating fields from different platforms (Peter Ostry 1998)
  6. Re: Updating fields from different platforms (Christer Olsson 1998)
  7. Re: Updating fields from different platforms (Charles Kefauver 1998)
  8. Re: Updating fields from different platforms (Peter Ostry 1998)
  9. Re: Updating fields from different platforms (Charles Kefauver 1998)
  10. Re: Updating fields from different platforms (Peter Ostry 1998)
  11. Updating fields from different platforms (Charles Kefauver 1998)
>Another solution I am trying now is to asume everyone is a PC, and let >the Mac try to be compatible. I have placed: > >on all my pages, and I have stored the data in the databases as PC native >accented characters.This is IMO the best approach. Assume everyone is using ISO-8859-1, which is the most used charset on the net.But. Force the use of it by WebCat [setmimeheader] tag instead of the tag, it's cleaner and you avoid the page being loaded twice.Use the follwing tags on your templates and you should be able to have both new and old browsers use the correct charset:[SETMIMEHEADER name=Content-Type&value=text/html; charset=iso-8859-1] [SETMIMEHEADER name=charset&value=iso-8859-1]Use them both for max compability. ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Art director S-211 37 Malmoe Fax +46 40 97 99 77 Ljusa Ideer AB Sweden http://www.ljusaideer.se Christer Olsson

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:

WebCatalog2 Feature Feedback (1996) Potential Conflicts? (1997) Country & Ship-to address & other fields ? (1997) displaying New products (using [date]) (1997) Strange ShowIf behaviour (2001) Ampersand (1997) (OT) SERVER FREEZES ALL AT SAME TIME (2004) [setcookie] (2001) Show your support (2002) creating writefile data from a nested search (1997) limitation found on group searching (1997) won't serve .tpl (2000) New Guestbook Source (1997) [WebDNA] XML Help please (2009) test (2000) [WebDNA] OT: what is the "right" platform ? (2009) Crashing Server (2000) javascript problem copying values (2000) politeness (was searches with dash...) Please Read (2000) WebCat2final1 crashes (1997)