[Top][All Lists]

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

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull

From: Eli Zaretskii
Subject: Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)
Date: Tue, 05 Jul 2016 19:23:25 +0300

> From: Robert Weiner <address@hidden>
> Date: Tue, 5 Jul 2016 11:04:35 -0400
> Cc: address@hidden
> On Tue, Jul 5, 2016 at 10:35 AM, Eli Zaretskii <address@hidden> wrote:
> >> On Sun, Jul 3, 2016 at 11:25 AM, Eli Zaretskii <address@hidden> wrote:
> >> > the result [of using braces around key sequences in Info manuals) will 
> >> > confuse the reader
> >>
> >> This is an assumption you are making that has not been borne out by the 
> >> experience of users of these manuals
> >> throughout the years.
> >
> > Does my experience of 30 years of reading Info manuals count?  We can
> > ask RMS to provide a second opinion.
> Of course I highly respect both of you and consider all of your
> feedback and will seek more.  On a topic like this, if you really care
> about it, we would ask that you look at and try out Hyperbole before
> finalizing your own judgement on this.

Sorry, what does that have to do with Hyperbole the program?  I can
get the impression from the docs without using the program itself,

> >> 1. The display is consistent across .pdf, .html and .info outputs. The 
> >> same markup can be used within any
> >> standard text as well (similar to what markdown does and we know how 
> >> popular that is).
> >
> > Texinfo explicitly doesn't attempt to do this, since the capabilities
> > of the various output formats are so different.
> There is the problem.  We have a solution for this particular area
> where there is no need to differentiate among the formats, so why
> continue to do so.  By using visible text delimiters in all formats
> you could solve a number of these issues.

Using the same notation in all formats necessarily means you aim at
the lowest common denominator, i.e. you lose some of the nice
capabilities of the more capable formats.

> > Any reasons Hyperbole couldn't be taught to recognize any other
> > format, including the standard Texinfo one?
> Because, as you said, it differs between different output formats.
> For any given output format, Hyperbole could recognize the delimiters
> and usage if they were specific enough but I would suggest that single
> quotes are not, i.e. 'C-x o', as the single quotes could generate too
> many false positives.  Surrounding this by braces does work, {'C-x o'}
> as of course does {C-x o}.

Key sequences are telltale enough to be able to distinguish them, I

> >  If not, does that mean
> > Hyperbole doesn't support key sequences documented by other GNU
> > packages?
> Yes, it means you cannot activate key bindings with a mouse click from
> other GNU documentation.  But lots of other Hyperbole functionality
> works for GNU packages and documentation.

That's a serious downside, IMO.  GNU packages should help each other.

reply via email to

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