From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24637@debbugs.gnu.org, ivan <ivan.brennan@gmail.com>
Subject: bug#24637: 25.1; non-ascii chars fail to render in Info buffer
Date: Mon, 19 Dec 2016 11:27:56 +0000 [thread overview]
Message-ID: <m2shpkyx8j.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <83bmyuhmj1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Oct 2016 18:45:54 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: ivan <ivan.brennan@gmail.com>
>> Date: Sat, 8 Oct 2016 11:36:02 -0400
>> Cc: 24637@debbugs.gnu.org
>>
>> Sorry, I should have mentioned in my last response -- I tried changing them to lowercase, but that didn't fix the
>> problem.
>
> Than I'm out of ideas.
>
> Does anyone else see this on OS X (or on any other OS)?
Just checked and I get the incorrect behaviour with the upper-case UTF-8
in emacs.info's "Local Variables:" section.
I built Emacs from git myself on OS X.
Now I think about it, I'm sure I've seen error messages regarding UTF-8
being invalid when building... Yup:
./../emacs/docstyle.texi:3: warning: unrecognized encoding name `UTF-8'.
GEN ../../info/eshell.info
./../emacs/docstyle.texi:3: warning: unrecognized encoding name `UTF-8'.
GEN ../../info/eudc.info
./../emacs/docstyle.texi:3: warning: unrecognized encoding name `UTF-8'.
GEN ../../info/efaq.info
./../emacs/docstyle.texi:3: warning: unrecognized encoding name `UTF-8'.
GEN ../../info/eww.info
./../emacs/docstyle.texi:3: warning: unrecognized encoding name `UTF-8'.
GEN ../../info/flymake.info
There are quite a lot of them. I guess one for each info file.
The only place I can think of right now that has this in upper case
that might affect the build is:
breton:/Users/alan/src/emacs/master>echo $LANG
en_GB.UTF-8
--
Alan Third
next prev parent reply other threads:[~2016-12-19 11:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 12:13 bug#24637: 25.1; non-ascii chars fail to render in Info buffer ivan
2016-10-07 12:44 ` Eli Zaretskii
[not found] ` <CAOVAYztVJLz7W0wo7an8p+wuw9cUS4TOXMaUvOtot0EZbondFw@mail.gmail.com>
2016-10-08 6:03 ` Eli Zaretskii
2016-10-08 12:31 ` ivan
2016-10-08 14:24 ` Eli Zaretskii
2016-10-08 15:36 ` ivan
2016-10-08 15:45 ` Eli Zaretskii
2016-10-08 19:40 ` John Mastro
2016-12-19 11:27 ` Alan Third [this message]
2016-12-19 16:18 ` Eli Zaretskii
2016-12-19 17:06 ` Alan Third
2016-12-19 18:06 ` Eli Zaretskii
2017-02-03 3:43 ` npostavs
2017-02-03 8:10 ` Eli Zaretskii
2019-11-08 2:50 ` Stefan Kangas
2019-12-15 20:18 ` Stefan Kangas
2016-10-09 9:44 ` Thien-Thi Nguyen
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=m2shpkyx8j.fsf@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=24637@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ivan.brennan@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).