--ytoMbUMiTKPMT3hY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 30, 2004 at 09:34:51AM +0000, Valeriy E. Ushakov wrote:
> Thomas Klausner <wiz@netbsd.org> wrote:
>=20
> >> Note that this patch doesn't handle -B and -b options, because I'm
> >> not sure how strvis() should be i18n'ized.
> >=20
> > Does someone else have comments on this?
>=20
> What about
>=20
> \xHHHH or for double byte encodings
> \uHHHH or \UHHHHHHHH for unicode (or whatever java and c99 syntax is).

I'm confused as to why we would want both. Is there prior art we're=20
following?

I ask as my initial read on your comments is that one syntax would=20
generate UTF-16 output, and the other would generate UTF-8. However it=20
strikes me that we either are dealing with a routine that works with only=
=20
one or the other (it is passed wchar or char strings explicitly) or we are=
=20
dealing with an output routine that learns what to do based on ENV=20
settings. In either case, there is enough context that I don't see why=20
we'd need both.

Take care,

Bill

--ytoMbUMiTKPMT3hY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFBXdBAWz+3JHUci9cRAnI4AJ40ykmLA7dUBdPUE/H0HLtQPpj5bwCdG/TP
RILq8z1mbOnA6CcJ8PyIsts=
=v3sS
-----END PGP SIGNATURE-----

--ytoMbUMiTKPMT3hY--