The ns/encodings section was added with one of the 3.5.x releases. Unfortunately, the config documents were not updated. You can see an example of it's use in the sample-config.tcl file.
Mark Wei Shi wrote on 5/14/2004, 1:56 PM: > I can not find "ns/encodings" section in AOLServer 4.0 > documents. Do you mean "ns/mimetypes"? > > Thanks. > > Wei > > --- Mark Page <[EMAIL PROTECTED]> wrote: > > If you are using AOLserver 3.5 or 4.0, you can tell > > it, via > > configuration, what the character encoding of your > > source files are. > > This is described in the sample-config.tcl in top of > > the aolserver > > distribution tree. > > For example: > > > > ns_section "ns/encodings" > > ns_param .utf_html "utf-8" > > ns_param .sjis_html "shiftjis" > > ns_param .gb_html "gb2312" > > ns_param .big5_html "big5" > > ns_param .euc-cn_html "euc-cn" > > > > If all your .adp source files are GB-2312 encoded, > > you may just want to > > specify that like: > > > > ns_section "ns/encodings" > > ns_param .adp "gd2312" > > > > What's happening here, is that AOLserver, when it > > reads the specified > > file into memory in order to parse and interpret it, > > must first convert > > the text in the source file from it's native > > character encoding, into > > the internal text character encoding, e.g., UTF-8. > > If you don't > > specifically tell AOLserver what the native > > character encoding is, it > > will use Tcl's 'system' encoding. Depending upon > > your environment > > settings, this may not be what you want/expect. If > > your system is > > currently set to have system encoding == latin-1, > > for example, it would > > definitly get confused when encountering a > > multi-byte GB character. > > > > Wei Shi wrote on 5/14/2004, 11:32 AM: > > > > > Hi, Does anyone know how AOLServer handles 8-bit > > characters in .adp file? > > > For example, I have some Chinese characters in > > GB-2312 encoding. Each > > > word > > > is two bytes, and both bytes are 8-bit chars. > > From the HTML stream I got > > > for this .adp file, it looks like AOLServer > > altered these two bytes into > > > some other values. > > > > > > Is AOLServer supposed to pass through all chars > > without any altercation > > > even for 8-bit characters? If there's some > > parsing/altercation going on, > > > can we turn it off? > > > > > > Thanks. > > > > > > Wei > > > > > > > > > -- > > > AOLserver - http://www.aolserver.com/ > > > > > > To Remove yourself from this list, simply send an > > email to > > > <[EMAIL PROTECTED]> with the > > > body of "SIGNOFF AOLSERVER" in the email message. > > You can leave the > > > Subject: field of your email blank. > > > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an > > email to <[EMAIL PROTECTED]> with the > > body of "SIGNOFF AOLSERVER" in the email message. > > You can leave the Subject: field of your email > blank. > > > > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! - Internet access at a great low price. > http://promo.yahoo.com/sbc/ > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
