From: Kenichi Handa <handa@m17n.org>
Cc: mule-ja@m17n.org
Subject: problem with system_eol_type
Date: Mon, 31 Jul 2006 15:04:59 +0900 [thread overview]
Message-ID: <E1G7Qtf-0006YS-00@etlken> (raw)
I've got several complaints about the change I made a few
months ago regarding the handling of the default eol-type.
Previously, when a coding system without explicit eol-type
(e.g. iso-latin-1) was specified for encoding, Unix-like
eol-type is selected on any platform.
The change I made was to use an eol-type set to
system_eol_type (CRLF on Windows, LF otherwise) in such a
case. To me, that change was just a bug fix.
But, the bug-reports say that there are many codes that
assumes the previous behaviour, and some of them now don't
work well on Windows.
I think that it is cleaner to ask a program to specify the
eol-type explicitly if it requires a specific eol-type on
encoding. But, as long as the behavior is clearly
documented, it seems that the previous behaviour is also not
that bad.
What do people think?
---
Kenichi Handa
handa@m17n.org
PS. I included mule-ja maining list in CC:. Mule-ja
subscribers please write in English if you want to reply to
this mail.
next reply other threads:[~2006-07-31 6:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 6:04 Kenichi Handa [this message]
2006-07-31 9:46 ` problem with system_eol_type Reiner Steib
2006-07-31 16:30 ` Stefan Monnier
2006-07-31 17:00 ` Jason Rumney
2006-07-31 17:28 ` Eli Zaretskii
2006-07-31 17:28 ` Eli Zaretskii
2006-07-31 17:52 ` Stefan Monnier
2006-07-31 17:27 ` Eli Zaretskii
2006-07-31 22:16 ` Richard Stallman
2006-08-01 2:03 ` Katsumi Yamaoka
2006-08-01 3:19 ` Stefan Monnier
2006-08-01 6:10 ` Katsumi Yamaoka
2006-08-09 10:35 ` Katsumi Yamaoka
2006-08-09 12:27 ` Stefan Monnier
2006-08-09 22:07 ` Katsumi Yamaoka
2006-08-10 1:13 ` Richard Stallman
2006-08-10 7:35 ` Reiner Steib
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=E1G7Qtf-0006YS-00@etlken \
--to=handa@m17n.org \
--cc=mule-ja@m17n.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.