From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] tcs bug
Date: Wed, 31 Aug 2005 14:54:37 +0900 [thread overview]
Message-ID: <BE150F4C-09E2-4701-B422-63143BAB69E1@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <ee9e417a050830104657bed5bc@mail.gmail.com>
Hello,
tcs both for plan 9 and for unix has a bug in reading utf text.
that comes from:
utf_in(int fd, long *notused, struct convert *out){
char buf[N];
...
while((n = read(fd, buf+tot, N-tot)) >= 0){
...
}
in utf.c
N is assigned to be 10000 in hdr.h
if you set N to 10, you will find the problem more clearly:
tcs cannot handle correctly utf character boundary.
for example, assume a.txt have the content:
aaaaaaaこの
term% xd -c a.txt
0000000 a a a a a a a e3 81 93 e3 81 ae \n
000000e
tcs can handle this text because N=10 is just uft boundary
but tcs fails if 'a' are 6 or 8 ...
tcs is very important for me.
Who maintains tcs ?
I might help debugging.
Kenji Arisawa
next prev parent reply other threads:[~2005-08-31 5:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 23:23 [9fans] some Plan9 related ideas Bhanu Nagendra Pisupati
2005-08-30 12:27 ` Sape Mullender
2005-08-30 15:21 ` Francisco Ballesteros
2005-08-30 15:25 ` Francisco Ballesteros
2005-08-30 17:07 ` [9fans] " Dave Eckhardt
2005-08-30 17:33 ` Francisco Ballesteros
2005-08-30 17:46 ` Russ Cox
2005-08-31 5:54 ` arisawa [this message]
2005-08-31 5:57 ` [9fans] tcs bug Rob Pike
2005-10-17 7:14 ` [9fans] Re: some Plan9 related ideas Uriel
2005-10-17 11:23 ` Russ Cox
2005-10-17 12:45 ` Uriel
2005-10-17 13:03 ` Russ Cox
2005-10-17 13:22 ` Uriel
2005-10-17 15:14 ` Russ Cox
2005-08-31 6:07 [9fans] tcs bug arisawa
2005-08-31 9:11 ` arisawa
2005-08-31 9:17 ` Rob Pike
2005-08-31 10:48 ` arisawa
2005-08-31 11:22 ` arisawa
2005-08-31 10:51 quanstro
2005-08-31 21:36 ` Russ Cox
2005-09-01 0:36 quanstro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BE150F4C-09E2-4701-B422-63143BAB69E1@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).