Steven Bennett wrote:
Christian M. Cepel wrote:
It was my understanding that all unicode character sets contain English
characters mapped to the same values they're mapped to in other sets.
Close -- Unicode is a *single* character set. For convenience, you'll
frequently run into
Jack Campin writes:
|
| One problem: what if you want to mix character sets in a tune? -
| e.g. to have a Chinese song documented in English? (T: and w:
| fields in Chinese, N: and D: fields in English).
What I'd more likely want to do is: three T: fields (Chinese
characters, pinyin,
In message [EMAIL PROTECTED], Phil
Taylor [EMAIL PROTECTED] writes
On 29 Apr 2004, at 00:32, Steven Bennett wrote:
According to Apple docs (I'll take their word for it... ;):
0x2028 -- Unicode line separator
0x2029 -- Unicode paragraph separator
Thank you Steve,
Pardon my ignorance, but
Phil Taylor wrote:
On 29 Apr 2004, at 08:34, Stephen Kellett wrote:
In message [EMAIL PROTECTED],
Phil Taylor [EMAIL PROTECTED] writes
On 29 Apr 2004, at 00:32, Steven Bennett wrote:
According to Apple docs (I'll take their word for it... ;):
0x2028 -- Unicode line separator
0x2029 --
Perhaps this is a good time to bring up the idea of a central set of
parser test cases and test case fragments. In the past a number of
list members have mentioned the desire to have a corporate body of test
cases that could be used during testing and development of abc parsers.
Perhaps
Phil Taylor wrote:
OK, I understand that. What was bothering me though, is how Steven B's
parser is going to deal with regular ascii strings which include a
space followed by a bracket. It's no problem when everything is
unicode, or everything is ascii, but if we are to have ascii abc which
Christian M. Cepel wrote:
It was my understanding that all unicode character sets contain English
characters mapped to the same values they're mapped to in other sets.
Close -- Unicode is a *single* character set. For convenience, you'll
frequently run into references to Unicode code pages,
