Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 26302 invoked by uid 6000); 2 Sep 1999 17:53:54 -0000 Received: (qmail 26186 invoked from network); 2 Sep 1999 17:53:48 -0000 Received: from fwns2d.raleigh.ibm.com (HELO fwns2.raleigh.ibm.com) (204.146.167.236) by taz.hyperreal.org with SMTP; 2 Sep 1999 17:53:48 -0000 Received: from rtpmail01.raleigh.ibm.com (rtpmail01.raleigh.ibm.com [9.37.172.24]) by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id NAA16654 for ; Thu, 2 Sep 1999 13:52:58 -0400 Received: from raleigh.ibm.com (wgs.raleigh.ibm.com [9.37.74.19]) by rtpmail01.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id NAA18766 for ; Thu, 2 Sep 1999 13:53:00 -0400 Message-ID: <37CEB9A2.AA8CF092@raleigh.ibm.com> Date: Thu, 02 Sep 1999 13:53:38 -0400 From: Bill Stoddard X-Mailer: Mozilla 4.5 [en] (X11; U; AIX 4.2) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Unicode and double byte character sets in Apache Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org How do Apache users in Japan accomodate single byte Apache running on a double byte OS? Are URIs, which use the 8859-1 charset, translated to filenames valid in a DBCS file system? Or are Japanese users forced into using single byte charsets when they are using Apache? -- Bill Stoddard stoddard@raleigh.ibm.com