From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jason Rumney <jasonr@gnu.org>
Cc: "Tomasz Zbrożek" <scianagoryczy@wp.pl>, 5235@debbugs.gnu.org
Subject: bug#5235: 23.1; Unibyte keyboard input problem
Date: Tue, 29 Dec 2009 13:43:01 -0200 [thread overview]
Message-ID: <m2my11bxn5.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <4B338705.5090508@gnu.org> (Jason Rumney's message of "Thu, 24 Dec 2009 23:21:41 +0800")
>>> I'll try to explain why I need unibyte mode. I'm maintener of a C/C++
>>> source code which has comments coded in cp1250 (polish language) but
>>> strings in code are coded in cp852. So I have two different code
>>> pages in source code file. This is old source code and it was
>>> developed in Windows (that's why comments are in cp1250) but is
>>> compiled to work on MS-DOS (that's why strings are coded in cp852).
>> So what happens if you read those files as binary (i.e. C-x RET
>> r binary RET)?
> At best, he'd end up silently screwing up his files even further, with
> cp1250, cp852 and now utf-8 encoded characters in them. More likely he
> would still get prompted when saving, just as if he'd used cp1250 or cp852
> to read them.
That would be a bug: a file visited as `binary' (or as `raw-text')
should be placed in a unibyte buffer, so it should not screw anything up
more than was already the case to start with.
> The problem here is the files, not Emacs. Basically the reason for using
> unibyte is that it allows the user to bury their head in the sand and
> pretend the problem does not exist.
Of course, but if you start with such files and can't (or don't want to)
recode the parts consistently, we can't do much better.
> I work on similar files in my day job, with Japanese comments in ShiftJIS
> and Chinese comments in GB2312. An easy method of fixing such files would be
> nice, but the best I can think of would be to provide a recode-region
> function, which would still be too much manual work to be worth it to me
> given that I can barely make sense of the Japanese comments and can't make
> any sense of the Chinese ones. The original poster might be more motivated
> to make use of such a function if it existed though.
I'm not sure what would be the best approach in general or in particular
cases, but we could certainly provide a command that recodes comments.
Or another one that looks for invalid byte sequences (i.e. decoded as
eight-bit-bytes) and tries to re-decode them with a secondary coding system.
Stefan
next prev parent reply other threads:[~2009-12-29 15:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 21:17 bug#5235: 23.1; Unibyte keyboard input problem Tomasz Zbrożek
2009-12-17 16:47 ` Jason Rumney
2009-12-17 19:25 ` Tomasz Zbrożek
2009-12-24 3:40 ` Stefan Monnier
2009-12-24 15:21 ` Jason Rumney
2009-12-24 19:27 ` Eli Zaretskii
2009-12-25 11:03 ` Tomasz Zbrożek
2009-12-25 11:23 ` Jason Rumney
2009-12-25 11:43 ` Tomasz Zbrożek
2009-12-26 12:45 ` Tomasz Zbrożek
2009-12-26 14:30 ` Eli Zaretskii
2009-12-25 20:42 ` Eli Zaretskii
2009-12-29 15:43 ` Stefan Monnier [this message]
2010-02-26 20:42 ` Tomasz Zbrożek
2010-02-26 23:42 ` Eli Zaretskii
2020-09-14 13:59 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2009-12-26 17:03 Tomasz Zbrożek
2009-12-26 17:52 ` Eli Zaretskii
2009-12-26 19:19 Tomasz Zbrożek
2009-12-26 21:24 ` Eli Zaretskii
2009-12-27 13:30 Tomasz Zbrożek
2009-12-27 20:07 ` Eli Zaretskii
2009-12-29 15:48 ` Stefan Monnier
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=m2my11bxn5.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=5235@debbugs.gnu.org \
--cc=jasonr@gnu.org \
--cc=scianagoryczy@wp.pl \
/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.