bug-texinfo
[Top][All Lists]
Advanced

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

Re: texinfo-6.8.90 pretest


From: Robert Pluim
Subject: Re: texinfo-6.8.90 pretest
Date: Thu, 20 Oct 2022 17:15:41 +0200

>>>>> On Thu, 20 Oct 2022 16:42:45 +0200, Patrice Dumas <pertusus@free.fr> said:
    Patrice> Previously there were no check at all on @w content.  I assumed 
that @w
    Patrice> could only contain "simple text" which meant all the inline 
@-commands
    Patrice> except for 'titlefont', 'anchor', 'footnote', 'verb', 'xref', 
'ref',
    Patrice> 'pxref', 'inforef'.

    Patrice> Actually, for this specific example it seems to me that the code 
put on
    Patrice> @w is too long to allow for correct display.  I checked in HTML, 
and
    Patrice> indeed, the non breakable part seems to me to be too long to allow 
for
    Patrice> good rendering, unless the browser width is within a specific 
range.
    Patrice> Wouldn't you obtain the effect you want or even something better by
    Patrice> simply using @w for the arguments of the @pxref instead, possible 
adding
    Patrice> a third argument in @w?

@pxref often 'expands', if that is the right word, to something that
is considerably shorter that the source, in this case in info it
produces:

    (*note (elisp)Yanking Media::).

so putting @w on the arguments wouldnʼt help. In html it produces

    (see Yanking Media in The Emacs Lisp Reference Manual)

which, whilst longer, fits within the width of any reasonable browser
window. I guess we could use @w for "The Emacs Lisp Reference Manual"
there (but I never read emacs docs in html, so Iʼm the wrong person to
offer an opinion).

Robert
-- 



reply via email to

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