Change Details

The following page https://en.wikisource.org/w/index.php?title=Page:A_biographical_dictionary_of_eminent_Scotsmen,_vol_1.djvu/337&action=edit&lintid=1080094 was being detected as having a "fostered content" concern. The only fostered content that could be located was a <section /> tag, which is used by LST to mark the start of a 'section'. Removing the <section /> tag from the markup caused the fostered content concern to vanish. The presence of the section tag is not however an error, as Wikisource uses <section /> tags extensively. Having Linter erroneously report a 'fostered' content concern. Linter mis-reporting these where no fostered content actually exists is tiresome. What should have happened is that the <Section /> tag should once noted for the purposes of building a transcluded section have been stripped from the output, and from the markup supplied to the Linter analyser. Of course if Mediawiki had a more sensible way of splitting table sections (the current markup and handling having been designed for single page use....) then concerns like this would be less important... (Aside: The use of section tgas for LST possibly conflicts with HTML5)

The following page https://en.wikisource.org/w/index.php?title=Page:A_biographical_dictionary_of_eminent_Scotsmen,_vol_1.djvu/337&action=edit&lintid=1080094 was being detected as having a "fostered content" concern. The only fostered content that could be located was a <section /> tag, which is used by LST to mark the start of a 'section'. Removing the <section /> tag from the markup caused the fostered content concern to vanish. The presence of the section tag is not however an error, as Wikisource uses <section /> tags extensively. Having Linter erroneously report a 'fostered' content concern. Linter mis-reporting these where no fostered content actually exists is tiresome. What should have happened is that the <Section /> tag should once noted for the purposes of building a transcluded section have been stripped from the output, and from the markup supplied to the Linter analyser. Of course if Mediawiki had a more sensible way of splitting table sections (the current markup and handling having been designed for single page use....) then concerns like this would be less important... (Aside: The use of section tags for LST possibly conflicts with HTML5)

The following page https://en.wikisource.org/w/index.php?title=Page:A_biographical_dictionary_of_eminent_Scotsmen,_vol_1.djvu/337&action=edit&lintid=1080094 was being detected as having a "fostered content" concern. The only fostered content that could be located was a <section /> tag, which is used by LST to mark the start of a 'section'. Removing the <section /> tag from the markup caused the fostered content concern to vanish. The presence of the section tag is not however an error, as Wikisource uses <section /> tags extensively. Having Linter erroneously report a 'fostered' content concern. Linter mis-reporting these where no fostered content actually exists is tiresome. What should have happened is that the <Section /> tag should once noted for the purposes of building a transcluded section have been stripped from the output, and from the markup supplied to the Linter analyser. Of course if Mediawiki had a more sensible way of splitting table sections (the current markup and handling having been designed for single page use....) then concerns like this would be less important... (Aside: The use of section tgastags for LST possibly conflicts with HTML5)