From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: "lu@luxdo.jp" <lu@luxdo.jp>
Cc: help-gnu-emacs@gnu.org
Subject: Re: about nxhtml-mode encoding problem
Date: Wed, 11 Jul 2007 15:18:55 +0200 [thread overview]
Message-ID: <4694D8BF.8030808@gmail.com> (raw)
In-Reply-To: <4694D17E.2000203@luxdo.jp>
Could you then please provide more information? (You did not answer my
previous mail.)
Especially I would like to know how the xml header look.
lu@luxdo.jp wrote:
> Hi,
>
> I sovle the nxhtml encoding problem by add the following code.
>
> ;; Fix nhxtml save bug(error encoding)
> (add-hook 'before-save-hook
> (lambda ()
> (setq coding-system-for-write buffer-file-coding-system)))
>
> I think it is a bug in nxhtml.
>
> lu@luxdo.jp wrote:
>> I'm very sorry,I made a mistake.
>> The problem is only on *nxhtml-mode*.
>> so The title is confusing.I correct it.
>>
>> Peter Dyballa wrote:
>>>
>>> Am 09.07.2007 um 18:07 schrieb lu:
>>>
>>>> But I'm sorry to say all of them doesn't work.
>>>> when I save the file it become utf-8.
>>>
>>> What is the definition of file-coding-system-alist before you try to
>>> save the buffer? Have you checked that your file does not contain
>>> characters outside the allowed ascii, katakana-jisx0201, and
>>> japanese-jisx0208 sets? What happens when you open the file in sjis,
>>> i.e. C-x RET c sjis RET C-x C-f <your file name>? Do you see strange
>>> or inappropriate glyphs?
>>>
>>> --
>>> Greetings
>>>
>>> Pete
>>>
>>> Atheism is a non prophet organization.
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> help-gnu-emacs mailing list
>> help-gnu-emacs@gnu.org
>> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>>
>> lu@luxdo.jp wrote:
>>> I use xhtml-mode to edit jsp file which is encoded by sjis.
>>> while I save the file it become utf-8 even when I (Coding system for
>>> saving file (default nil): sjis
>>> I want to know How to solve this problem.
>>>
>>>
>>> _______________________________________________
>>> help-gnu-emacs mailing list
>>> help-gnu-emacs@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>>>
>
>
>
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>
next prev parent reply other threads:[~2007-07-11 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 14:44 about xhtml-mode encoding problem lu
2007-07-09 15:31 ` Peter Dyballa
2007-07-09 16:07 ` lu
2007-07-09 17:08 ` Lennart Borgman (gmail)
2007-07-09 18:00 ` Peter Dyballa
2007-07-09 23:26 ` lu
2007-07-09 23:37 ` about nxhtml-mode " lu
2007-07-11 12:47 ` lu
2007-07-11 13:18 ` Lennart Borgman (gmail) [this message]
2007-07-11 14:07 ` lu
2007-07-12 13:56 ` lu
2007-11-25 22:56 ` Lennart Borgman (gmail)
2007-11-26 4:53 ` Ke Lu
2007-11-26 8:03 ` Lennart Borgman (gmail)
2007-07-09 16:12 ` about xhtml-mode " 呂 克
2007-07-09 17:59 ` Lennart Borgman (gmail)
2007-07-11 14:02 ` lu
2007-07-11 14:41 ` Lennart Borgman (gmail)
[not found] ` <mailman.3225.1183997250.32220.help-gnu-emacs@gnu.org>
2007-07-09 16:41 ` B. T. Raven
2007-07-09 23:29 ` lu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4694D8BF.8030808@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lu@luxdo.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).