docs/parse-support-md: Correctly process caveats in multi-status sections

When SUPPORT.md uses the syntax
  Status, <some thing>: <support status>
the caveats were lost (not footnoted) because they were attached
only to <some thing>.

Caveats occur in running text, so they are necessarily part of a real
section, not an individual status line like that.  So attach them to
the RealSectNode, and look there for them.

Reported-by: Lars Kurth <lars.kurth@citrix.com>
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
Acked-by: Lars Kurth <Lars.kurth@citrix.com>
Release-acked-by: Juergen Gross <jgross@suse.com>
This commit is contained in:
Ian Jackson authored and Ian Jackson committed 2018-05-15 16:41:45 +01:00
1 parent 42a5581404
commit bd9f5f7c66
1 file changed
+3 -3
+3 -3
View File
@@ -34,7 +34,7 @@ our $toplevel_sectlist = new_sectlist();
# $sectlist->{KEY}{Children} = a further $sectlist
# $sectlist->{KEY}{Key} = KEY
# $sectlist->{KEY}{RealSectNode} = us, or our parent
# $sectlist->{KEY}{HasCaveat}[VI] = trueish iff other in a Para
# $sectlist->{KEY}{RealSectNode}{HasCaveat}[VI] = trueish iff other in a Para
# $sectlist->{KEY}{RealInSect} = containing real section in @insections, so
# $sectlist->{KEY}{RealInSect}{HasDescription} = VI for some Emph in Para
# $sectlist->{KEY}{RealInSect}{Anchor} = value for < id="" > in the pandoc html
@@ -123,7 +123,7 @@ sub ri_Para {
if ($had_feature) {
my $sectnode = find_current_sectnode();
$sectnode->{HasCaveat}[$version_index] = 1;
$sectnode->{RealSectNode}{HasCaveat}[$version_index] = 1;
} else {
$insection->{HasDescription} //= $version_index;
}
@@ -402,7 +402,7 @@ sub write_output_row ($) {
my $nextcell = '';
if (!defined $colspan) { # first row of this RealInSect
$colspan= ' colspan="2"';
if ($sectnode->{HasCaveat}[$i] && $st
if ($sectnode->{RealSectNode}{HasCaveat}[$i] && $st
&& $sectnode->{RealInSect}{Anchor}) {
my $rows = $sectnode->{RealInSect}{OwnRows};
$nextcell = '<td';
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.