From erik@sran8.sra.co.jp Wed Jul 24 12:29:42 1991
Received: from mcsun.EU.net by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA01359; Wed, 24 Jul 91 12:29:42 +0200
Received: from srawgw.sra.co.jp by mcsun.EU.net with SMTP;
	id AA23919 (5.65a/CWI-2.100); Wed, 24 Jul 91 12:29:42 +0200
Received: from srava.sra.co.jp by srawgw.sra.co.jp (5.64WH/1.4)
	id AA10721; Wed, 24 Jul 91 19:28:52 +0859
Received: from sran8.sra.co.jp by srava.sra.co.jp (5.64b/6.4J.6-BJW)
	id AA16337; Wed, 24 Jul 91 19:29:17 +0900
Received: from localhost by sran8.sra.co.jp (5.65/6.4J.6-SJ)
	id AA12768; Wed, 24 Jul 91 19:27:00 +0900
Return-Path: <erik@sran8.sra.co.jp>
Message-Id: <9107241027.AA12768@sran8.sra.co.jp>
Reply-To: erik@sra.co.jp
From: erik@sra.co.jp (Erik M. van der Poel)
To: i18n@dkuug.dk
Subject: locale category for sound
Date: Wed, 24 Jul 91 19:26:40 +0900
Sender: erik@sran8.sra.co.jp
X-Charset: ASCII
X-Char-Esc: 29

Dear i18n Subscribers:

Do any of you know (or have ideas) about locale categories for sound
(as in voice, or some other kind of sound)?

We could just lump this together with LC_MESSAGES, but then users
wouldn't be able to have screen messages in one language with voice
messages in another language.

One might also argue that sound input and output should be able to be
set separately, but maybe this is going too far.

Applications might generate messages (1) on the screen only, (2)
through the speaker only, or (3) in both text and sound, depending on
the user's preference.

Comments? Ideas? Existing implementations?


Regards,
EvdP