Page MenuHomePhabricator

List-defined ref only linked from another ref in the <reference> block supposedly does not exist
Open, LowPublic

Description

Test case:

=== Article text ===
Lorem ipsum<ref name="expl_A" group="n" />
===Explanatory notes section===
<references group="n">
{{#tag:ref
|BBBB
|group="n"|name="expl_B"}}
{{#tag:ref
|AAAA link to B<ref name="expl_B" group="n" />
|group="n"|name="expl_A"}}
</references>
===References section===
<references />

Result: Failure. For one, it will twice generate an inappropriate <ref> tag with name "expl_B" defined in <references> is not used in prior text. (changing the order of the two #tag:refs makes no difference) Secondly, the <ref name="expl_B" group="n" /> is ignored. If however the "expl_A" is moved into the article text, everything is just fine.

Event Timeline

Izno raised the priority of this task from to Low.
Izno updated the task description. (Show Details)
Izno added a project: Cite.
Izno added subscribers: Meno25, Jackmcbarn, matmarex and 4 others.
Izno set Security to None.

This can apparently be partially worked around by using the #tag form for <references>:

{{#tag:references|
...
|group="n"}}

(You only get one error this way, "Invalid <ref> tag; name "expl_B" defined multiple times with different content".)

thiemowmde renamed this task from LDR only linked from another ref in the <reference> block supposedly does not exist to List-defined ref only linked from another ref in the <reference> block supposedly does not exist.Feb 21 2023, 1:58 PM