unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: Typesetting non-ASCII names in Emacs manuals
Date: Wed, 09 Mar 2011 23:21:45 +0800	[thread overview]
Message-ID: <87zkp4wc8m.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTin4XitSdgptLQcmeWamkqsjL6FHAeibi4G8dajM@mail.gmail.com> (Juanma Barranquero's message of "Wed, 9 Mar 2011 16:15:09 +0100")

Juanma Barranquero <lekktu@gmail.com> writes:

> On Wed, Mar 9, 2011 at 15:19, Jason Rumney <jasonr@gnu.org> wrote:
>
>> Surely the cost of an extra warning for old versions of makeinfo is
>> worth it if users of newer versions of makeinfo can have the "odd
>> character" problem fixed.
>
> Well, it's not just an extra warning. Non-ASCII latin names are
> garbled right now on Windows, at least if you use makeinfo 4.8.

Right, but without the change you and Eli are objecting to, they're
garbled for everyone, aren't they?




  parent reply	other threads:[~2011-03-09 15:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Pwt3K-0000qp-1y@eggs.gnu.org>
2011-03-08  9:36 ` Emacs-diffs Digest, Vol 100, Issue 28 Eli Zaretskii
2011-03-08 17:43   ` Glenn Morris
2011-03-08 23:14     ` Karl Berry
2011-03-09  6:12       ` Typesetting non-ASCII names in Emacs manuals (was: Emacs-diffs Digest, Vol 100, Issue 28) Eli Zaretskii
2011-03-09  7:57       ` Emacs-diffs Digest, Vol 100, Issue 28 Glenn Morris
2011-03-09  8:56         ` Typesetting non-ASCII names in Emacs manuals Eli Zaretskii
2011-03-09 18:24           ` Stefan Monnier
2011-03-08 18:50   ` Emacs-diffs Digest, Vol 100, Issue 28 Glenn Morris
2011-03-08 19:09     ` Eli Zaretskii
2011-03-08 19:19       ` Glenn Morris
2011-03-08 19:39         ` Eli Zaretskii
2011-03-09  8:03           ` Glenn Morris
2011-03-09  8:45             ` Typesetting non-ASCII names in Emacs manuals Eli Zaretskii
2011-03-09 10:19               ` Andreas Schwab
2011-03-09 10:32                 ` Eli Zaretskii
2011-03-09 10:34                   ` Andreas Schwab
2011-03-09 10:50                     ` Eli Zaretskii
2011-03-09 14:19               ` Jason Rumney
2011-03-09 14:32                 ` Eli Zaretskii
2011-03-09 18:26                   ` Stefan Monnier
2011-03-09 15:15                 ` Juanma Barranquero
2011-03-09 15:15                   ` Juanma Barranquero
2011-03-09 15:21                   ` Jason Rumney [this message]
2011-03-09 15:28                     ` Juanma Barranquero
2011-03-09 15:49                     ` Eli Zaretskii
2011-03-09 17:02               ` Eli Zaretskii
2011-03-09 19:43                 ` Glenn Morris
2011-03-09 20:07                   ` Eli Zaretskii
2011-03-09 20:19                     ` Glenn Morris
2011-03-09 20:44                       ` Eli Zaretskii
2011-03-09 21:02                         ` Glenn Morris
2011-03-10  5:52                           ` Eli Zaretskii
2011-03-09 11:49             ` Emacs-diffs Digest, Vol 100, Issue 28 Juanma Barranquero
2011-03-09 19:35               ` Glenn Morris
2011-03-09 19:48                 ` Juanma Barranquero
2011-03-08 23:32         ` Juanma Barranquero
2011-03-10  3:40           ` Jason Rumney
2011-03-10  4:04             ` Juanma Barranquero
2011-03-10  4:07             ` Eli Zaretskii

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=87zkp4wc8m.fsf@gnu.org \
    --to=jasonr@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.org \
    --cc=lekktu@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).