From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: utf-16le vs utf-16-le
Date: Tue, 15 Apr 2008 00:26:52 +0200 [thread overview]
Message-ID: <85od8cgjir.fsf@lola.goethe.zz> (raw)
In-Reply-To: <jwviqykm69j.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 14 Apr 2008 18:19:13 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>>> For what it's worth, I do think it would make sense to try and move
>>> the BOM-processing outside of the coding-system proper. For me a good
>>> test for coding-system-worthiness is "what if I use it for a process
>>> rather than a file". Based on this test, I'm not sure if BOMs really
>>> fit in (other than for auto-detection and automatically stripping
>>> them, maybe).
>
>> Hm? I don't see why starting communication with a BOM or not would
>> _not_ fit in.
>
> I don't think the notion of "start" is quite the same for process data
> as for files.
>
>>>> What I proposed was a more generic concept where use of signatures
>>>> and the EOL convention would (at least to the user) appear as
>>>> buffer-local variables.
>>>
>>> Here, I disagree: EOL processing definitely need to take place when
>>> talking to subprocesses, so EOL-handling doesn't belong in
>>> buffer-local vars but in the coding-system.
>
>> I don't quite see the difference to BOM processing, even though the BOM
>> processing has to happen only once at the start.
>
> You mean, it's almost exactly the same, except it's completely
> different? Then I agree,
"Start/end of line" and "Start of buffer/communication" is not
"completely different". Likewise, "\\`" and "^" are not "completely
different" regular expressions. They are different, yes, but less
different than a lot of other things.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-04-14 22:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 14:54 utf-16le vs utf-16-le Eli Zaretskii
2008-04-13 19:32 ` Stefan Monnier
2008-04-14 5:17 ` Kenichi Handa
2008-04-14 6:10 ` David Kastrup
2008-04-14 18:54 ` Eli Zaretskii
2008-04-14 19:04 ` David Kastrup
2008-04-14 17:38 ` Eli Zaretskii
2008-04-14 18:57 ` Eli Zaretskii
2008-04-13 22:23 ` Stephen J. Turnbull
2008-04-14 3:19 ` Eli Zaretskii
2008-04-14 7:32 ` Stephen J. Turnbull
2008-04-14 8:20 ` David Kastrup
2008-04-14 18:25 ` Stephen J. Turnbull
2008-04-14 18:46 ` Eli Zaretskii
2008-04-14 21:01 ` Stephen J. Turnbull
2008-04-14 21:15 ` Andreas Schwab
2008-04-15 0:22 ` Stephen J. Turnbull
2008-04-15 3:25 ` Eli Zaretskii
2008-04-15 16:51 ` Stephen J. Turnbull
2008-04-15 20:09 ` Eli Zaretskii
2008-04-15 20:31 ` Eli Zaretskii
2008-04-15 20:35 ` David Kastrup
2008-04-16 20:15 ` Stephen J. Turnbull
2008-04-16 20:32 ` David Kastrup
2008-04-17 3:23 ` Stephen J. Turnbull
2008-04-17 3:26 ` Eli Zaretskii
2008-04-17 7:44 ` Stephen J. Turnbull
2008-04-17 8:19 ` Jan Djärv
2008-04-17 12:41 ` Eli Zaretskii
2008-04-17 17:20 ` Stephen J. Turnbull
2008-04-17 18:03 ` Eli Zaretskii
2008-04-16 22:09 ` Eli Zaretskii
2008-04-17 1:14 ` Stefan Monnier
2008-04-14 20:20 ` Stefan Monnier
2008-04-14 20:58 ` David Kastrup
2008-04-14 22:19 ` Stefan Monnier
2008-04-14 22:26 ` David Kastrup [this message]
2008-04-14 22:33 ` Stefan Monnier
2008-04-15 5:44 ` David Kastrup
2008-04-15 15:35 ` Stefan Monnier
2008-04-14 21:35 ` Stephen J. Turnbull
2008-04-14 5:17 ` Kenichi Handa
2008-04-14 13:57 ` Stefan Monnier
2008-04-14 7:02 ` tomas
2008-04-14 17:45 ` Eli Zaretskii
2008-04-15 7:38 ` tomas
2008-04-15 22:30 ` Juri Linkov
2008-04-16 3:20 ` Eli Zaretskii
2008-04-16 8:12 ` Jason Rumney
2008-04-16 13:35 ` Stefan Monnier
2008-04-16 14:45 ` Jason Rumney
2008-04-16 17:05 ` Stefan Monnier
2008-04-16 20:09 ` Stephen J. Turnbull
2008-04-16 23:17 ` Juri Linkov
2008-04-16 23:42 ` Jason Rumney
2008-04-17 1:03 ` 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=85od8cgjir.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=stephen@xemacs.org \
/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.