bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texi2any's equivalent for texi2html's option `--short-ref`


From: pertusus
Subject: Re: texi2any's equivalent for texi2html's option `--short-ref`
Date: Fri, 7 Jan 2022 12:21:04 +0100

On Fri, Jan 07, 2022 at 06:56:52AM +0000, Werner LEMBERG wrote:
> 
> Hello Gavin and Patrice,
> 
> >> `texi2html` had an option `--short-ref` [...]
> > 
> > I had a look at the history and this customization never made to
> > texi2any, however, previously if the reference was to a section,
> > there was 'section'.  This was removed in that commit
> > 
> > https://git.savannah.gnu.org/cgit/texinfo.git/commit/tp/Texinfo/Convert/HTML.pm?id=f97e44597dc6cda93c0bff607ce9599d6ea41069
> 
> Thanks a lot for your help and analysis.  This is excactly what we
> want for LilyPond.  Right now we are stuck with texi2html 1.82 because
> of a massive initialization file that doesn't translate easily to
> newer versions of texinfo.  The less stuff we have to adjust in a
> forthcoming transition to a current texinfo version the happier we
> areĀ :-)

At some point I looked at your bug to help you transition, but I could
not really find a way to help in practice...

If I recall well, one feature that is not in texi2any and that is hard
to achieve without changing the perl gettext implementation is to be
able to customize the translated strings.  What is missing is a way
to change messages based on new po/gmo file being read, and I do not
think that allowing that should be in Texinfo proper.  I discussed with
Guido, the perl gettext maintainer on that subject in the past, but I do
not think that this has moved on.

In any case, do not hesitate to bring issues here, I would really like
for lilypond to transition to texi2any, I believe it is the last project
to use texi2html...

-- 
Pat



reply via email to

[Prev in Thread] Current Thread [Next in Thread]