"mark lewis -> All" wrote in
news:332$fido.jamnntpd@JamNNTPd:
ml> in the subject line, i've placed the highbit characters alt-128 thru
ml> alt-157 and i'm going to duplicate them in this message's body with
ml> double quotes around them... let's see how it falls apart now ;)
ahhh!! i have it now... i commented out the utf-8 translations in xlat.cfg
and now it all looks fine...
ml> alt-128 - ""
ml> alt-129 - ""
ml> alt-130 - ""
ml> alt-131 - ""
ml> alt-132 - ""
ml> alt-133 - ""
ml> alt-134 - ""
ml> alt-135 - ""
ml> alt-136 - ""
ml> alt-137 - ""
ml> alt-138 - ""
ml> alt-139 - ""
ml> alt-140 - ""
ml> alt-141 - ""
ml> alt-142 - ""
ml> alt-143 - ""
ml> alt-144 - ""
ml> alt-145 - ""
ml> alt-146 - ""
ml> alt-147 - ""
ml> alt-148 - ""
ml> alt-149 - ""
ml> alt-150 - ""
ml> alt-151 - ""
ml> alt-152 - ""
ml> alt-153 - ""
ml> alt-154 - ""
ml> alt-155 - "" (cent)
ml> alt-156 - "" (british currency pound)
ml> alt-157 - "" (yen)
OH! i did also, before, have to go with the "noencode" option to avoind the
mime encoding of the subject and name fields when there were highbit
characters in them... i think i forgot to mention that before...
--
)\/(ark - remove .my.foot to email me, capiche?
* Origin: news://news.wpusa.dynip.com | acct reqd to post (1:3634/12)
|
