Hello, fellow Bat-lovers.
On Thursday, October 14, 1999, 12:50:18 PM, Thomas wrote:
> Hallo Syafril,
> On Friday, October 08, 1999, 1:14:28 PM, Syafril Hermansyah wrote:
[snip]
SH>> In the first time I run 1.36Beta/12, I found that I got new font :
SH>> Andele Mono, MS Hei (Chinese GB_2312), MingLiu (Chinese_BIG5), MS
SH>> Mincho (Japanese) and MS Song (Chinese_GB2312).
> GB2312 is used on the mainland, Big5 here in Taiwan.
Right. So what's Andele?
> I run C-Win98,
> and it's the Chinese version (meaning all the Windows stuff is written
> in Chinese, and I have to work a lot from memory). The bilingual
> version Chin/Engl is instable.
I didn't even know there was a Chinese/English version.
> If Win2000 supports Chinese characters,
> I will consider upgrading, I need it in the office.
I'm hopeful that it will. In beta testing Agent 1.6, we found that NT
displays CJK on its own, while 95/98 requires third-party CJK software
to be running concurrently. This is because NT fully supports Unicode.
I haven't looked into 2000, but am hopeful that it does the same. Does
anyone know?
> I also read&write
> Thai, so that would be really an advantage :-)
So you read and write Thai, but not Chinese? I'm envious. I never got very far with
the Thai writing system; it's so inconsistent it might as well be
logographic, like Chinese ;-).
> Any problems with
> Win2000 that I should be aware off? (Reply off-list OK).
Please copy me in, as well. I'm anxious to know, too.
SH>> If you have MS Office 2000, you can give a try.
SH>> I will update the character set with Korean Character set if time
SH>> permit, and see what happend then.
> Let us all now, that would be important for this part part of the
> world.
Absolutely.
KR>>> 2. Worse yet, if I compose and send a message using The Bat and
KR>>> Korean Partner, the message header identifies the charset as
KR>>> ISO-8851-1! (It should be sent as ISO-2022-KR.) I am afraid that
KR>>> this will make it unreadable to recipients.
SH>> What's character set you prefer ?
> A changeable one.
Yes, "changeable" is right. It should be determined by the encoding
used to create the message. I would like to be able to compose and
send Korean in at least two different encodings, maybe more.
> Actually, TB ignores the XLAT tables and "encoding"
> option when it comes to double-byte langauges.
Yes, that's what I've found, too.
[snip]
Thanks again!
Keith Russell
mailto:[EMAIL PROTECTED]
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, click below and send the generated message.
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
