bug-texinfo
[Top][All Lists]
Advanced

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

Re: <link rel="next"> element does not match Next hyperlink


From: Patrice Dumas
Subject: Re: <link rel="next"> element does not match Next hyperlink
Date: Thu, 7 Nov 2019 15:07:46 +0100
User-agent: Mutt/1.12.2 (2019-09-21)

On Thu, Nov 07, 2019 at 11:36:28AM +0000, Gavin Smith wrote:
> If I have the input:
> 
> \input texinfo
> 
> @node One
> @chapter One
> 
> @node Section
> @section Section
> 
> @node Two
> @chapter Two
> 
> @bye
> 
> in test.texi and run "texi2any --html test.texi", then in the output
> file One.html, in the <head> there is
> 
> <link href="Section.html" rel="next" title="Section">
> 
> showing the Next node is "Section", whereas in the <body>, there is
> 
> Next: <a href="Two.html" accesskey="n" rel="next">Two</a>
> 
> showing the next node is "Two". Is this discrepancy deliberate?

I think that it is indeed deliberate, based on my interepretation of
some description of the links in head specification.  Based on that
description (I don't remember where it was), I used the following 
directions for the links:

  'LINKS_BUTTONS'        => ['Top', 'Index', 'Contents', 'About',
                              'NodeUp', 'NextFile', 'PrevFile'],

'NextFile' will be associated to 'next' in rel.

In the nodes directions hrefs, the directions are different, typically 

  'SECTION_BUTTONS'      => [[ 'NodeNext', \&_default_node_direction ],
                             [ 'NodePrev', \&_default_node_direction ],
                             [ 'NodeUp', \&_default_node_direction ], ' ',
                             'Contents', 'Index'],

and in that case it is 'NodeNext' that will be associated to 'next' in
rel. 

The association is in %BUTTONS_REL, and you can see that diverse
directions map to the same rel attribut as there are many directions
possible in Texinfo HTML and not many possibilities for rel.  For
instance there are four directions assocaited to rel 'next: 
 'Next' (next section on the same level), 
 'NodeNext' (next node), 
 'Forward' (following node in reading order)
 'NextFile' (next file)

So it is on purpose, but it is unclear if it is correct.  Based on 
https://www.w3schools.com/tags/att_a_rel.asp
it seems that start, contents and up disappeared.  Both next and prev
are defined too imprecisely to really conclude, I think.  I don't know
what they mean by document and by series, and I guess that they are
vague on purpose.

-- 
Pat



reply via email to

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