httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From traw...@locus.apache.org
Subject cvs commit: apache-2.0/src/modules/experimental mod_charset_lite.c
Date Wed, 25 Oct 2000 17:32:56 GMT
trawick     00/10/25 10:32:54

  Modified:    src/modules/experimental mod_charset_lite.c
  Log:
  On an EBCDIC machine, be willing to translate mod_autoindex-
  generated output.  Otherwise, it doesn't look too cool.
  
  XXX This isn't a perfect fix because this doesn't trigger us
  to convert from the charset of the source code to ASCII.  The
  general solution seems to be to allow a generator to set an
  indicator in the r specifying that the body is coded in the
  implementation character set (i.e., the charset of the source
  code).  This would get several different types of documents
  translated properly: mod_autoindex output, mod_status output,
  mod_info output, hard-coded error documents, etc.
  
  Problem reported by: Martin Kraemer
  
  Revision  Changes    Path
  1.30      +15 -0     apache-2.0/src/modules/experimental/mod_charset_lite.c
  
  Index: mod_charset_lite.c
  ===================================================================
  RCS file: /home/cvs/apache-2.0/src/modules/experimental/mod_charset_lite.c,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- mod_charset_lite.c	2000/10/25 16:49:14	1.29
  +++ mod_charset_lite.c	2000/10/25 17:32:52	1.30
  @@ -291,6 +291,21 @@
    */
                
       if (strncasecmp(mime_type, "text/", 5) &&
  +#ifdef CHARSET_EBCDIC
  +        /* On an EBCDIC machine, be willing to translate mod_autoindex-
  +         * generated output.  Otherwise, it doesn't look too cool.
  +         *
  +         * XXX This isn't a perfect fix because this doesn't trigger us
  +         * to convert from the charset of the source code to ASCII.  The
  +         * general solution seems to be to allow a generator to set an
  +         * indicator in the r specifying that the body is coded in the
  +         * implementation character set (i.e., the charset of the source
  +         * code).  This would get several different types of documents
  +         * translated properly: mod_autoindex output, mod_status output,
  +         * mod_info output, hard-coded error documents, etc.
  +         */
  +        strcmp(mime_type, DIR_MAGIC_TYPE) &&
  +#endif
           strncasecmp(mime_type, "message/", 8)) {
           if (dc->debug >= DBGLVL_GORY) {
               ap_log_rerror(APLOG_MARK, APLOG_DEBUG|APLOG_NOERRNO, 0, r,
  
  
  

Mime
View raw message