unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean-Christophe Helary <brandelune@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Cc: texinfo-devel@gnu.org
Subject: Re: eshell manual: texinfo question
Date: Thu, 14 Feb 2019 08:00:50 +0900	[thread overview]
Message-ID: <960EDB66-A330-4EF6-A022-701B3DB6297B@gmail.com> (raw)
In-Reply-To: <87h8d74bbj.fsf@len.workgroup>

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>
> 
> I changed this paragraph with the help of texinfo-insert-dwim-@ref to:
> 
> 
> The command can be either an Elisp function or an external command.
> Eshell looks first for an alias (@pxref{Aliases}) with the same name as the
> command, then a built-in (@pxref{Built-ins}) or a function with the
> same name; if there is no match, it then tries to execute it as an
> external command.
> 
> 
> Now this renders nicely (if a bit heavy) in html:
> <eshell-patched.html.png>
> even heavier in pdf:
> <eshell-patched.pdf.png>
> but in info the second "see" is missing:
> <eshell-patched.info.png>
> 
> I also played with further with 'online-label' and
> 'printed-label' as described in the manual, but this did not hel
> either.  I'm mostly interested in the info output, but for files
> distributed with Emacs it should look good in all output formats.
> 
> 
> Any ideas, what to do in order to fix this issue?
> 
> 
> 
> Ciao; Gregor 

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune




  reply	other threads:[~2019-02-13 23:00 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 [this message]
2019-02-14 17:40   ` Gavin Smith
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

  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=960EDB66-A330-4EF6-A022-701B3DB6297B@gmail.com \
    --to=brandelune@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=texinfo-devel@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.
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).