[vorbis-dev] vorbis-tools reorganziation and UTF-8 stuff

[volsung at asu.edu]

On Tue, 25 Sep 2001, Edmund GRIMLEY EVANS wrote:

> Stan Seibert:
> 
> > I have already fixed vorbiscomment to encode comments in UTF-8 (like oggenc
> > already did), but I have not fixed ogg123 or oggenc to display UTF-8 comments
> > in the native charset yet. This is because utf8.c does not have any decode
> > functions, since they weren't needed. Since I would rather debug the
> > kcarnold_branch ogg123 than figure out UTF-8, I'm throwing out this list of
> > requests to the more motivated and/or knowledgable people out there:
>  
> Bruno Haible wrote a portable libiconv library that probably runs on
> anything vorbis-tools runs on. You could just make people install
> libiconv if their system doesn't provide an adequate version of iconv.
> 
> I know it's tempting to think "let's just include some simple charset
> conversion functions so we have fewer dependencies", but you also have
> to think about the duplication of effort, bloat and maintenance burden
> that occurs when each program on a system includes its own set of
> simple charset conversion functions.
> 
> So, I think you should seriously consider throwing out all the charset
> conversion stuff from vorbis-tools and simply requiring iconv.

Um, we already use iconv.  :)  We actually have three implementations in
utf8.c: win32 (totally different), iconv (for UNIX), and a very simple
converter for those cases where we don't have iconv.  If the platform has
iconv, we use it.


---
Stan Seibert

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