[vorbis] Re: UTF8, vorbiscomment, oggenc, and 'vcedit.c'

[Nathan I. Sharfi]

On Sat, 12 Jan 2002, Glenn Maynard wrote:

> On Sat, Jan 12, 2002 at 12:37:24AM -0500, Glenn Maynard wrote:
> > On Fri, Jan 11, 2002 at 06:58:28PM -0500, Peter Harris wrote:
> > > > > umlaut-u in wchar_t *argv[] appears as superscript-n when wprintf()ed
> > > >
> > > > That seems to mean they're doing some weird conversion that we can't
> > > > really fix.  It might be worth adding a @file option (read arguments),
> > > > which is always in UTF-8, so that scripts that want to interface with
> > > > this always have at least one reliable way of getting these characters
> > > > through.  (Or perhaps in the locale/codepage encoding, I'm not sure.)
> > >
> > > We can detect UNICODE via the magic word 'FEFF' (looks like FFFE in
> > > little-endian files; looks like EFBBBF in UTF-8) and use that. In the
> >
> > Aack!  That's a Windowsism; requiring it in anything but Windows will
> > annoy a *lot* of people, myself included.
> >
> > How about this: read it in the current locale.  If a program (ie a
> > script) wants to call it with UTF-8 data, it can change the locale to
> > UTF-8 for that call.  That way, it works like every other modern locale-
> > sensitive package, and isn't an exception.
> >
> > For Windows, you could get away with using FEFF to change to Unicode,
> > but then you have fairly different behavior between Windows and Unix.
> > That might be inevitable, though.
>
> Actually, taking a look at vcomment, the @file notation isn't needed;
> that's what -c is for.  This applies to that option, however.
>

@file isn't available for oggenc, though.

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.