Subramanya Sastry 23b9c314e1 Take #2: (Bug 49555): Support all nested ref scenarios ... * This patch now supports any template that generates nested refs where the top-level token is just a single-ref. Ex: {{efn|New timetable{{sfn|Vallance|1991|p=31}}}} * The solution in this patch removes the hack from the previous version (53bbcbb3). As documented in the bug report, this solution essentially "trusts" template authors and lets nested refs through when they come from templates. But, top-level nested refs are still not allowed. <ref>foo<ref>bar</ref>baz</ref> in the toplevel page will still generate a single reference with content "foo<ref>bar</ref>baz" * Updated the nested ref test output - Regenerated selser changes because of the changed output. - Regenerated blacklist because of the changed selser changes. * This now handles: - https://en.wikipedia.org/wiki/User:Edgepedia/VE/GNoSR - https://en.wikipedia.org/wiki/Phellinus ellipsoideus Change-Id: I627955f0be1c5e2bafc49647c94c2be68ce711a8		2013-07-18 15:35:21 -05:00
..
ext.Cite.js	Take #2: (Bug 49555): Support all nested ref scenarios	2013-07-18 15:35:21 -05:00