On Sun, Feb 16, 2025 at 04:56:37PM +0100, pertu...@free.fr wrote:
> What should we do for @*heading not at the top level, like
>
> @node node
>
> @quotation
> @heading in quitation
> Quote
> @end quotation
>
> @heading at top-level
This is actually a problem for an implementation in texinfo.tex
Hello,
There are new HTML 5 base entities (dot, breve...) for accented letters,
and more accented letters:
https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
I think that it is better if the new base entities are considered to be
available anyway, as they only will be
On Sun, Feb 16, 2025 at 03:36:07PM +, Gavin Smith wrote:
> > Actually, I was proposing the opposite, so I was probably unclear.
> >
> > For @node, the association is with the next sectioning command, even if
> > there are @*heading commands in-between. This is also quite
> > theoretical, as t
> A target is an anchor, where it is placed. Maybe @identifier could
> be better than @label?
If this is what people like most then I suggest to use `@id`, which is
shorter. (I'm not really happy with the name, though, but I can't
explain why this is so :-)
Werner
>> > So, this is not different if a @node is before an @XXXheading, it
>> > may appear in an explicit node direction and in another @node
>> > menu.
>>
>> Well, the behaviour of `@node` in a split HTML document is to start
>> a new file. However, this is exactly what I would like to avoid.
>
> O
On Sun, Feb 16, 2025 at 02:53:05PM +0100, pertu...@free.fr wrote:
> > What would be the advantage to a user of setting USE_NODES=0?
>
> If there are lone nodes, they are associated to the preceding section.
> It allows to have HTML more book like, while Info could have more @node
> units. I am no
>> Ah, ok. Then `@label` should be indeed avoided. I would still
>> like to have a snappy command name, maybe `@mark` or `@tag`?
>
> 2. "Label" as the anchor name:
>
> @label Bows
> @heading Bögen
>
> Here there would be an anchor created called "Bows". @xref{Bows}
> would
On Sun, Feb 16, 2025 at 12:24:23PM +, Gavin Smith wrote:
> On Sun, Feb 16, 2025 at 12:57:21PM +0100, pertu...@free.fr wrote:
> > This is only true if USE_NODES=1. For HTML, if USE_NODES=0, the
> > sectioning commands define units of output and @node are only
> > used ase targets of cross-refe
On Sun, Feb 16, 2025 at 12:35:11PM +, Gavin Smith wrote:
> On Sun, Feb 16, 2025 at 01:00:24PM +0100, pertu...@free.fr wrote:
> > On Sat, Feb 15, 2025 at 02:26:11PM +, Gavin Smith wrote:
> > > @label could be ok for the command, but it could be confusing as there
> >
> > Even without a conf
On Sun, Feb 16, 2025 at 01:00:24PM +0100, pertu...@free.fr wrote:
> On Sat, Feb 15, 2025 at 02:26:11PM +, Gavin Smith wrote:
> > @label could be ok for the command, but it could be confusing as there
>
> Even without a confusion with LaTeX command, @label is confusing to be
> used as a target
On Sun, Feb 16, 2025 at 12:57:21PM +0100, pertu...@free.fr wrote:
> On Sat, Feb 15, 2025 at 04:38:34PM +, Gavin Smith wrote:
> > On Sat, Feb 15, 2025 at 01:16:13PM +, Werner LEMBERG wrote:
> > >
> > > [folding answers to two e-mails into one]
> > >
> > > >> Because in Info a `@node` alway
On Sat, Feb 15, 2025 at 02:01:13PM +, Gavin Smith wrote:
> I don't see the purpose of this as documents should use a sectioning
> command, not a @*heading command after a node.
I disagree, I think that @*heading command after a node is a natural
setting for a manual organized in topics that do
On Sat, Feb 15, 2025 at 02:26:11PM +, Gavin Smith wrote:
> @label could be ok for the command, but it could be confusing as there
Even without a confusion with LaTeX command, @label is confusing to be
used as a target to cross references, because it is exactly the opposite
of what seems to me
On Sat, Feb 15, 2025 at 04:38:34PM +, Gavin Smith wrote:
> On Sat, Feb 15, 2025 at 01:16:13PM +, Werner LEMBERG wrote:
> >
> > [folding answers to two e-mails into one]
> >
> > >> Because in Info a `@node` always needs a `@menu` entry, AFAIK,
> > >> which is inconsistent with the `@XXXhea
On Sat, Feb 15, 2025 at 01:16:13PM +, Werner LEMBERG wrote:
>
> > So, this is not different if a @node is before an @XXXheading, it
> > may appear in an explicit node direction and in another @node menu.
>
> Well, the behaviour of `@node` in a split HTML document is to start a
> new file. Ho
On Wed, Feb 12, 2025 at 10:12:15PM +0100, pertu...@free.fr wrote:
> Note that having separate anchor and label most likely requires changing
> diverse things, because the anchor part always need to be 'hidden'. For
> instance cross references should be like @ref{Bows, Bögen, Bögen,
> manual}, whic
On Sat, Feb 15, 2025 at 09:51:41PM +, Werner LEMBERG wrote:
> >> Yes, exactly – in HTML split mode, `@anchorlabel` (or `@label`,
> >> which I won't stop advertising :-) plus `@XXXheading` should be on
> >> the same page as the last `@node` command.
> >
> > @label could be ok for the command, b
17 matches
Mail list logo
