From: Kenichi Handa <handa@m17n.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: docs for insert-file-contents use 'bytes'
Date: Thu, 02 Oct 2008 10:33:49 +0900 [thread overview]
Message-ID: <E1KlD4f-0002xS-U9@etlken.m17n.org> (raw)
In-Reply-To: <868wt845op.fsf@lifelogs.com> (message from Ted Zlatanov on Wed, 01 Oct 2008 11:54:14 -0500)
In article <868wt845op.fsf@lifelogs.com>, Ted Zlatanov <tzz@lifelogs.com> writes:
KH> It's not that easy. Some encoding requires to seek back an
KH> escape sequence to get the next character. And, for UTF-16
KH> with BOM, we have to check the first 2-byte.
> OK. Does it ever require going more than N*2 (where N = max sequence
> length for the encoding) bytes back? Is N ever bigger than 10? If not,
> it may be complicated code but at least it will be fairly fast.
N can be much much longer than 10. For instance, the
following is the byte sequence of iso-2022-jp for a Japanese
sentence (ESC code is represented by "^[").
^[$BA0$N2hLL$H<!$N2hLL$H$G$O!I=<($5$l$kFbMF$K2?9T$+$N=E$J$j$,$$j$^$9!#$3^[(B
^[$B$l$O!I=<($5$l$F$$$kFbMF$,OB3$7$F$$$k$3$H$,$9$0H=$k$h$&$K$9$k$?$a$G$9!#^[(B
We must search back the sequence ^[$B or ^[(B for
iso-2022-jp. Which pattern to search depends on the
coding-system.
> The semantics could be (given N as above):
> 1) jump to character number C: scan from beginning of file and count
> characters up to C if the encoding has a variable length. Otherwise the
> offset is obvious.
> 2) jump to character around/at byte B: jump to B-N*2 and scan characters
> forward until you find the one that straddles or begins at B. Also
> should have a way to report that character's actual starting byte
> position.
> 3) jump to byte: operate as now, just a fseek
> For my purposes (2) is most useful, but I can use (3) and bypass
> encodings. (1) is not good for me, since the application is to view
> large files, but (1) is OK for small files.
As you now see from the above example, implementing (2) is
very difficult. And, for small files, we don't need (1).
We can just read the whole file.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-10-02 1:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 19:58 docs for insert-file-contents use 'bytes' Ted Zlatanov
2008-09-29 20:12 ` Eli Zaretskii
2008-09-29 21:04 ` Ted Zlatanov
2008-09-30 6:06 ` Miles Bader
2008-09-30 7:19 ` Eli Zaretskii
2008-09-30 13:48 ` Ted Zlatanov
2008-09-30 15:58 ` Stefan Monnier
2008-09-30 16:29 ` Eli Zaretskii
2008-10-01 0:44 ` Kenichi Handa
2008-10-01 16:54 ` Ted Zlatanov
2008-10-02 1:33 ` Kenichi Handa [this message]
2008-10-02 13:42 ` Ted Zlatanov
2008-10-02 18:55 ` Stefan Monnier
2008-10-03 13:55 ` Ted Zlatanov
2008-10-02 1:58 ` Kenichi Handa
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=E1KlD4f-0002xS-U9@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.