From: Gavin Smith <gavinsmith0123@gmail.com>
To: Jean-Christophe Helary <brandelune@gmail.com>,
Gregor Zattler <telegraph@gmx.net>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>, bug-texinfo@gnu.org
Subject: Re: eshell manual: texinfo question
Date: Thu, 14 Feb 2019 17:40:59 +0000 [thread overview]
Message-ID: <CAKPWYQ085OD3jwrrkuY=1Fx4=ALU-2x66nCSyD+yTh0dw4xxng@mail.gmail.com> (raw)
In-Reply-To: <960EDB66-A330-4EF6-A022-701B3DB6297B@gmail.com>
On 2/13/19, Jean-Christophe Helary <brandelune@gmail.com> wrote:
> Gregor,
>
> You need to send this to the texinfo dev list. It is not an emacs issue.
>
> The best way to deal with that is to change texinfo so that the output does
> not add arbitrary English strings to the links/references. Those should be
> added by the author (it's also l10n best practice).
>
> Jean-Christophe
>
>> On Feb 14, 2019, at 6:40, Gregor Zattler <telegraph@gmx.net> wrote:
>>
>> Hi emacs users,
>>
>> the eshell.text file as of current emacs master contains the
>> following paragraph:
>>
>>
>> The command can be either an Elisp function or an external command.
>> Eshell looks first for an @ref{Aliases, alias} with the same name as the
>> command, then a @ref{Built-ins, built-in command} or a function with the
>> same name; if there is no match, it then tries to execute it as an
>> external command.
>>
>>
>> With makeinfo version 6.3 this renders nicely in html:
>> <eshell.html.png>
>> but not so nice in pdf:
>> <eshell.pdf.png>
>> and not in info:
>> <eshell.info.png>
In the forwarded email, these images were not present, so we can't see
what the problem is. (I changing the mailing list to one which is more
read.)
The pdf output is the Texinfo project's problem, but how the output
appears in Emacs Info is very likely the Emacs project's problem.
next prev parent reply other threads:[~2019-02-14 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 21:40 eshell manual: texinfo question Gregor Zattler
2019-02-13 23:00 ` Jean-Christophe Helary
2019-02-14 17:40 ` Gavin Smith [this message]
2019-02-14 17:53 ` Gavin Smith
2019-02-14 3:56 ` Glenn Morris
2019-02-14 18:29 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKPWYQ085OD3jwrrkuY=1Fx4=ALU-2x66nCSyD+yTh0dw4xxng@mail.gmail.com' \
--to=gavinsmith0123@gmail.com \
--cc=brandelune@gmail.com \
--cc=bug-texinfo@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=telegraph@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.