From: Sam S. <sd...@gn...> - 2002-05-21 15:12:19
|
> * In message <155...@ho...> > * On the subject of "Re: encoding issues" > * Sent on Tue, 21 May 2002 14:42:32 +0200 (CEST) > * Honorable Bruno Haible <ha...@il...> writes: > > > > 2) Joerg needs a function MIME-ENCODING-NAME, because not all clisp > > > encoding names are valid for transmission across the internet. Those > > > which are are mentioned in libcharset/lib/config.charset (rightmost > > > column). > > > > so could you please add a function > > > > char * mime_name(const char* charset); > > > > to libcharset? > > It has no place in libcharset, because it's specific to Internet > protocols and not general use. so? is this a "no"? :-) this function is nice to have - and not just in CLISP. > Also for interoperability it's usually best to choose an encoding name > depending on the contents to be sent. It is annoying if you send a > mail labelled as being ISO-8859-15 but in fact it is plain ASCII. So I > would propose that INSPECT chooses the charset using a heuristic that > makes it likely that the browser can nicely display the result: > > (let ((contents <precomputed text to be sent via http)) > (cond ((every #'(lambda (ch) (typep ch charset:ascii))) charset:ascii) > ((every #'(lambda (ch) (typep ch charset:iso-8859-1))) charset:iso-8859-1) > (t charset:utf-8))) we send the contents using a specific encoding. yes, usually it's all ASCII, but suppose these is a koi8-r char there - then you would send it as an iso-8859-1 char. we need a way to get the right mime name for the encoding. until then (string (encoding-charset encoding)) is the best approximation (well, it's no worse than what you proposed :-) -- Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html> Perl: all stupidities of UNIX in one. |