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

[Beni Cherniavksy]

On 2002-01-12, Nathan I. Sharfi wrote:

> On Fri, 11 Jan 2002, Glenn Maynard wrote:
>
> > On Fri, Jan 11, 2002 at 12:27:36PM -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.)
>
> I'd love having that around...
>
Working around the normal option-passing of the brain-dead OS...  That's
the route DJGPP took on DOS (all apps support response files (@file)
and also a some other way, system() automatically uses them if the
called app is a DJGPP program too).

I guess cygwin did something like this around windows too.  They surely
have better posix support than winNT ;) and probably they support
unix-styled locale interfaces sanely.  Does anybody know how they support
it?  Compiling for cygwin will probably let it work transparently with
other cygwin apps.  Maybe that would be less pain (at least for oggenc /
vorbiscomment)?


-- 
Beni Cherniavsky <cben at tx.technion.ac.il>
                 (also scben at t2 in Technion)

<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.