Re: eshell manual: texinfo question

[Gavin Smith <gavinsmith0123@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.