Re: Unusual characters in the db ...

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 42500
interpreted = N
texte = >>>I suspect that you want UNICODE characters, though. >>> >>> >>Are you sure WebCat can handle/search/sort unicode? > >I don't think it can, and I know for a fact that some browsers cannot handle unicode ... >I know for a fact that some browsers cannot handle images. Mosaic 1.0 is one. I don't spend any time worrying about such antiques, though. WebTV's browser can't handle tables, but that's not a major concern, either. >From http://www.unicode.org/unicode/faq/unicode_web.html#0 --Q: My web page is in Latin-1 (ISO-8859-1). So I don't need a charset declaration, right?A: Wrong. You always need a charset declaration, even when you are using Latin-1. To quote from the HTML specification:The HTTP protocol ([RFC2616], section 3.7.1) mentions ISO-8859-1 as a default character encoding when the charset parameter is absent from the Content-Type header field. In practice, this recommendation has proved useless because some servers don't allow a charset parameter to be sent, and others may not be configured to send the parameter. Therefore, user agents must not assume any default value for the charset parameter. - HTML 4.01Thus you should always include a charset declaration of the form in the element:Q: We are setting up a database for use with our web server. I understand that if I want to store data into a database, I need to use a consistent character encoding scheme. Does Unicode cover all the character sets we need, for a web server ?A: Yes, Unicode works perfectly on the backend for keeping all of your data in a consistent format. [MD]------------------------------------------------------------- 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://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Unusual characters in the db ... (Christer Olsson 2002)
  2. Re: Unusual characters in the db ... (Glenn Busbin 2002)
  3. Re: Unusual characters in the db ... (Kenneth Grome 2002)
  4. Re: Unusual characters in the db ... (Glenn Busbin 2002)
  5. Re: Unusual characters in the db ... (Glenn Busbin 2002)
  6. Re: Unusual characters in the db ... (Glenn Busbin 2002)
  7. Re: Unusual characters in the db ... (Kenneth Grome 2002)
  8. Re: Unusual characters in the db ... (Christer Olsson 2002)
  9. Re: Unusual characters in the db ... (Christer Olsson 2002)
  10. Re: Unusual characters in the db ... (Glenn Busbin 2002)
  11. Re: Unusual characters in the db ... (Kenneth Grome 2002)
  12. Re: Unusual characters in the db ... (Glenn Busbin 2002)
  13. Re: Unusual characters in the db ... (Kenneth Grome 2002)
  14. Re: Unusual characters in the db ... (Kenneth Grome 2002)
  15. Re: Unusual characters in the db ... (Christer Olsson 2002)
  16. Unusual characters in the db ... (Kenneth Grome 2002)
>>>I suspect that you want UNICODE characters, though. >>> >>> >>Are you sure WebCat can handle/search/sort unicode? > >I don't think it can, and I know for a fact that some browsers cannot handle unicode ... >I know for a fact that some browsers cannot handle images. Mosaic 1.0 is one. I don't spend any time worrying about such antiques, though. WebTV's browser can't handle tables, but that's not a major concern, either. >From http://www.unicode.org/unicode/faq/unicode_web.html#0 --Q: My web page is in Latin-1 (ISO-8859-1). So I don't need a charset declaration, right?A: Wrong. You always need a charset declaration, even when you are using Latin-1. To quote from the HTML specification:The HTTP protocol ([RFC2616], section 3.7.1) mentions ISO-8859-1 as a default character encoding when the charset parameter is absent from the Content-Type header field. In practice, this recommendation has proved useless because some servers don't allow a charset parameter to be sent, and others may not be configured to send the parameter. Therefore, user agents must not assume any default value for the charset parameter. - HTML 4.01Thus you should always include a charset declaration of the form in the element:Q: We are setting up a database for use with our web server. I understand that if I want to store data into a database, I need to use a consistent character encoding scheme. Does Unicode cover all the character sets we need, for a web server ?A: Yes, Unicode works perfectly on the backend for keeping all of your data in a consistent format. [MD]------------------------------------------------------------- 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://search.smithmicro.com/ Glenn Busbin

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 max=?] armed (1997) WebCat2.0 acgi vs plugin (1997) RE: 2nd WebCatalog2 Feature Request (1996) Frames (1997) No Access warning when caching HTML files (1997) Platform differences Commitdatabases (2000) Snippet for finding unused Header Fields in the Orders.db (2003) webcatalog plugin bug - webstar refusing connections (1999) WebCatalog NT beta 18 problem (1997) Nesting format tags (1997) Password Generator (2004) Help name our technology! (1997) Unusual characters in the db ... (2002) NY taxRates.db? (1997) Size limit for tmpl editor ? (1997) Live hits (2003) Text data with spaces in them... (1997) Credit card types (1997) Webcat causing crashes left and right! (1997) simple answer? [hideif] (1997)