From owner-freebsd-hackers  Mon Sep 18 05:44:21 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id FAA14590
          for hackers-outgoing; Mon, 18 Sep 1995 05:44:21 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA14572
          for <hackers@FreeBSD.org>; Mon, 18 Sep 1995 05:43:55 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA23935; Mon, 18 Sep 1995 22:36:33 +1000
Date: Mon, 18 Sep 1995 22:36:33 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199509181236.WAA23935@godzilla.zeta.org.au>
To: hackers@FreeBSD.org, terry@lambert.org
Subject: Re: Policy on printf format specifiers?
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

>I'd like to add a format specifier '%S' to the list of format specifiers
>accepted by printf.  Well, kernel printf, anyway.

I don't want wchar_t's in the kernel.

>I'd also like the wchar_t value to be 16 rather than 32 bits.  Other
>than page 0 (Unicode), no other code pages in ISO-10646 have yet been
>allocated.

I think wchar_t's were made 32 bits so that they are the same as rune_t's.
I don't know if this is important.

>This would affect constant ISO 8859-1 strings using the 'L' quailfier;
>for example:

>main()
>{
>	printf( "%S\n", L"Hello World");
>}

How are you supposed to print such strings in ANSI C?

Bruce