UNICODE Advantage: Any character in any language can be displayed.
UNICODE Disadvantage: Everyone using the structure needs to be UNICODE
aware. Are there systems and computer languages that can't handle it?
That's why I was wondering if there should be some type of switch passed to
the parser about whether to output UNICODE.
Actually, since the app passes the string with the tune to the parser, we
could have two functions, one that accepts a UNICODE string and outputs
UNICODE strings, and the other that accepts an ASCII string and outputs
ASCII strings.
(There's no point in returning UNICODE strings if the original was ASCII,
since no extra characters were used.)
Paul Rosen
--- Life is a musical, every once in a while
the plot stops and you start singing and dancing ---
http://home.earthlink.net/~catharsis.music/
http://home.earthlink.net/~theplums/
----- Original Message -----
From: Remo D. <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 11, 2004 5:26 AM
Subject: Re: [abcusers] ABCp output data structure
> > *Please* go for Unicode! TMHO, it is *the* way to go when it comes to
> encoding
> > plain text. For something like an international folk songbook (that
could
> > contain e.g. lyrics in latin, cyrillic *and* greek alphabet) the current
> > standard (and applications, for that matter) fall short.
>
> I do agree with you 100% on the needing. My problem is that I do not know
> enough Unicode to figure out how exacatly to do it! Any volunteer?
>
> Remo
>
> To subscribe/unsubscribe, point your browser to:
http://www.tullochgorm.com/lists.html
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
