Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
Date: Sun, 7 Sep 2003 21:43:59 +0200
Subject: Re: Character References for Japanese translations
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Erik Abele <erik@codefaktor.de>
To: docs@httpd.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <20030908010354.F42A.TETSUYA@apache.org>
Message-Id: <A03CE5A8-E16B-11D7-9367-000A95882BE0@codefaktor.de>

On 07/09/2003, at 06:34, Tetsuya Kitahata wrote:

>   Yoshiki Hayashi <yoshiki@xemacs.org> wrote:
>
>> The funny things may happen if we insert characters encoded
>> in iso-2022-jp directly to typemap file but we are going to
>> use URI keyword to refer to separate file for Japanese
>> translation, I don't see any need to use character
>
> If this (separation of the files) is true, I will put
> my plus one (and just my 2 YEN :-), too.

Yes, I'd also say the best way is to simply store 'special' languages
in separate files and then refer to these files from the typemap itself.

btw, the attached materials already contained separate files and
the corresponding patches to the typemap files, so there shouldn't
be a problem ;)

Cheers,
Erik

> Sincerely,
>
> -- Tetsuya. (tetsuya@apache.org)


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org