Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 84614 invoked by uid 500); 8 Aug 2002 19:42:17 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 84597 invoked from network); 8 Aug 2002 19:42:16 -0000 Message-ID: <3D52C94F.7080902@slive.ca> Date: Thu, 08 Aug 2002 15:41:03 -0400 From: Joshua Slive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721 X-Accept-Language: en-us, en, fr MIME-Version: 1.0 To: docs@httpd.apache.org Subject: Re: Japanese internationalized error messages; charset in typemap files References: <5.1.0.14.2.20020808115544.0314cab8@pop3.rowe-clan.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N William A. Rowe, Jr. wrote: > Perhaps the easest thing is to add the HTTP_ERROR_DOC.html.utf8 > or HTTP_ERROR_DOC.html.iso2022-jp or whatever, and reference it > by the uri: option from the .var file. Simply restrict the .var file to > 8 bit > sbcs encodings that won't be clobbered by editing the .var map file in > any 8 bit sbcs editor (e.g. all the iso8859's can stay in the var file.) > > Would this make sense to everyone? Sounds good to me. Then we just need a Japanese speaker to proofread the stuff. Joshua. --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org