In article <[EMAIL PROTECTED]>, Eli Zaretskii <[EMAIL PROTECTED]> writes:
> > Really, I think the only good way of solving this is to have a
> > `coding:' tag in the Info file. Handa-san, do you agree?
> I have now installed a change to use @documentencoding and the
> "--enable-encoding" switch,
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
> From: Zhang Wei <[EMAIL PROTECTED]>
> Date: Sat, 14 Jul 2007 19:23:50 +0800
>
> Eli Zaretskii <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > I have now installed a change to use @documentencoding and the
> > "--enable-encodin
Eli Zaretskii <[EMAIL PROTECTED]> writes:
[...]
> I have now installed a change to use @documentencoding and the
> "--enable-encoding" switch, so that the `coding:' tag is produced in
> info/emacs-mime. Please see if that solves the problem.
No problem now, thanks.
___
> Date: Sat, 07 Jul 2007 23:51:55 +0300
> From: Eli Zaretskii <[EMAIL PROTECTED]>
> Cc: emacs-pretest-bug@gnu.org, [EMAIL PROTECTED]
>
> > That is why I asked what it is that makes chinese-iso-8bit the default
> > on his system.
>
> His language environment is Chinese, so chinese-iso-8bit is high
> Date: Tue, 10 Jul 2007 13:10:17 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org, [EMAIL PROTECTED], [EMAIL
> PROTECTED]
>
> Anyway, back to the suggestion at hand: fine, I will make the
> --enable-encoding behavior the default when @documentencodi
Perhaps I'm confused: if Texinfo commands are not the recommended
way,
The Texinfo commands aren't unrecommended either. Both ways have their
advantages -- it depends on the document. That's why we support both.
then why do we have them? why not tell users to always use
literal
> Date: Mon, 9 Jul 2007 16:14:15 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org, [EMAIL PROTECTED], [EMAIL
> PROTECTED]
>
> source was written well,
>
> I can't agree that it is bad to use literal characters instead of
> Texinfo commands.
Pe
I agree that it should be the default.
Very well, I'll change that.
but still produce the Local Variables section, because without 8-bit
characters the result is a plain ASCII file.
As you know, if the input uses 8-bit characters, the output will also
use 8-bit characters, regardle
That is not a 100% solution for 100% of the problem, but it's a good
compromise that works well in practice. You often advise others to
shy away of purism and instead embrace practical compromises on the
Right side of the 80-20 divide. Why not go with this advice in this
case?
> Date: Sun, 8 Jul 2007 17:56:12 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: emacs-pretest-bug@gnu.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
>
> I could easily change things so that the Local Variables section was
> always output if a @documentencoding was present. I don't see any
> partic
> From: Richard Stallman <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
> emacs-pretest-bug@gnu.org
> Date: Sun, 08 Jul 2007 18:23:28 -0400
>
> It is pure luck if an Info file was generated for the same character
> set that your terminal supports.
That's
What happens if you do not specify --enable-encoding?
--enable-encoding principally affects two things.
1) whether the Local Variables section is output.
2) whether Texinfo constructs such @'e outputs an ASCII transliteration
of the accented character (e'), or a real 8-bit accented characte
If I'm understanding correctly, it can already be done. If you use the
@documentencoding command in the Texinfo source, and then specify
--enable-encoding to makeinfo, the resulting Info file(s) will contain a
Local Variables section setting the `coding' variable.
What happens if
> On the other hand, we might also want to fix a coding system
> for Info files, so that their handling will not depend on the locale.
How? Do you mean to encode Info files in UTF-8 or some such?
I mean, for some specific coding system. UTF-8 might be a good choice,
but not necessar
> Date: Sat, 7 Jul 2007 16:42:05 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: emacs-pretest-bug@gnu.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
>
> If you use the @documentencoding command in the Texinfo source, and
> then specify --enable-encoding to makeinfo, the resulting Info
> file(s) wil
On the other hand, we might also want to fix a coding system
for Info files, so that their handling will not depend on the locale.
Handa and Karl, what do you think?
If I'm understanding correctly, it can already be done. If you use the
@documentencoding command in the Texinfo source,
> From: Richard Stallman <[EMAIL PROTECTED]>
> Date: Sat, 07 Jul 2007 16:46:53 -0400
> Cc: emacs-pretest-bug@gnu.org
>
> On the other hand, we might also want to fix a coding system
> for Info files, so that their handling will not depend on the locale.
How? Do you mean to encode Info files in U
> From: Richard Stallman <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
> Date: Sat, 07 Jul 2007 09:06:32 -0400
>
> Richard, is it okay to assume Texinfo 4.6 for the CVS trunk?
>
> To support @documentencoding, when it appears in a .texi file, would
> not require anyon
The default coding system is determined by Locale settings, that is
`LC_ALL', `LC_CTYPE', or `LANG'.
Thanks.
I rechecked the first message and saw that the problem only affects a
few Info files that use non-ASCII characters. Maybe changing those
manuals to use @documentencoding is the ri
Richard, is it okay to assume Texinfo 4.6 for the CVS trunk?
To support @documentencoding, when it appears in a .texi file, would
not require anyone to move to Texinfo 4.6. There is no harm in
supporting it, so let's do so.
The problem is that that may not solve the whole problem.
Even peopl
Richard Stallman <[EMAIL PROTECTED]> writes:
[...]
> What is it on your system that makes the default coding system
> chinese-iso-8bit?
The default coding system is determined by Locale settings, that is
`LC_ALL', `LC_CTYPE', or `LANG'.
___
emacs-pr
This problem happens with "emacs -Q", I don't think my .emacs cause
this.
That is surely correct.
The comments in emacs-mime.texi specify which coding system should be
used to edit it:
--8<---cut here---start->8---
@c Local Variables:
> From: Zhang Wei <[EMAIL PROTECTED]>
> Date: Fri, 06 Jul 2007 09:56:08 +0800
>
> This problem happens with "emacs -Q", I don't think my .emacs cause
> this.
Right. I managed to reproduce this problem on my machine in "emacs -Q".
> The comments in emacs-mime.texi specify which coding system sho
Richard Stallman <[EMAIL PROTECTED]> writes:
> > Does the problem happen with "emacs -Q"? If it doesn't, then
> > something in your .emacs init file causes this.
>
> Yes, it does.
>
> Could you show us the code in your .emacs file which caused this?
>
> It is possible that your .emacs
> Does the problem happen with "emacs -Q"? If it doesn't, then
> something in your .emacs init file causes this.
Yes, it does.
Could you show us the code in your .emacs file which caused this?
It is possible that your .emacs file was incorrect. But it is also
possible that your cod
Eli Zaretskii <[EMAIL PROTECTED]> writes:
> Does the problem happen with "emacs -Q"? If it doesn't, then
> something in your .emacs init file causes this.
Yes, it does.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.or
When I enter Info, the info doc is allways opened with chinese-iso-8bit
coding system which is the default of my installation. If there are
non-ascii characters in the doc, it will be displayed incorrectly, such
as the emacs-mime page, there's a word `Naïve' in the page, and it
> From: Zhang Wei <[EMAIL PROTECTED]>
> Date: Wed, 04 Jul 2007 21:56:40 +0800
>
> When I enter Info, the info doc is allways opened with chinese-iso-8bit
> coding system which is the default of my installation.
Thank you for reporting this. Unfortunately, I seem to be unable to
reproduce this on
When I enter Info, the info doc is allways opened with chinese-iso-8bit
coding system which is the default of my installation. If there are
non-ascii characters in the doc, it will be displayed incorrectly, such
as the emacs-mime page, there's a word `Naïve' in the page, and it
should be opened wit
29 matches
Mail list logo
