From: ivan <ivan.brennan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24637@debbugs.gnu.org
Subject: bug#24637: 25.1; non-ascii chars fail to render in Info buffer
Date: Sat, 8 Oct 2016 08:31:33 -0400 [thread overview]
Message-ID: <CAOVAYztCmcgrXupxeo6-bBuC_07D5_25mJg99MP5GqK+Aw78PQ@mail.gmail.com> (raw)
In-Reply-To: <83eg3ridih.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
>
> It should be "utf-8", in lower case. How come it's in upper case on
> your system?
>
> Did you produce the Info files yourself, or did they come with some
> package built elsewhere?
>
I used homebrew to build Emacs, so I believe the info files were generated
locally during the build process, but I didn't do anything special in that
regard.
I've been trying out two different build formulas,
1. https://github.com/d12frosted/homebrew-emacs-plus
(just GNU Emacs with some build options)
2. https://github.com/railwaycat/homebrew-emacsmacport
(GNU Emacs with some source code modifications for OSX)
Both builds have the uppercase "UTF-8" local variable in their info files,
and both exhibit the behavior I described.
[-- Attachment #2: Type: text/html, Size: 1476 bytes --]
next prev parent reply other threads:[~2016-10-08 12:31 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 [this message]
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
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=CAOVAYztCmcgrXupxeo6-bBuC_07D5_25mJg99MP5GqK+Aw78PQ@mail.gmail.com \
--to=ivan.brennan@gmail.com \
--cc=24637@debbugs.gnu.org \
--cc=eliz@gnu.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 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).