Change Details

On English Wikisource, we have many tables of contents that span multiple pages. However, it's a bit tricky to construct it so that the `pagenum` spans (from `MediaWiki:Proofreadpage pagenum template`) are inserted at the right position. Imagine two Page-NS pages: Page 1: ``` {| | 1 | Chapter 1 ``` Page 2: ``` |- | 2 | Chapter 2 |} ``` In this case, the `pagenum` spans are inserted after Chapter 2, which is technically the wrong row, but it's a valid place for content to be (it's inside a td element) Also, when the table row is templated, this means that whitespace between rows is "sucked" into the end of the "Chapter 1" cell, and since `|-` has to start on a new line, it's easy to get extra row into the cell contents, even with a single-line gap in the wikitext: ``` {| {{foorow|1|Chapter 1}} {{foorow|2|Chapter 2}} ``` produces: ``` {| | 1 | Chapter 1 |- | 2 | Chapter 2 ``` The other way around, with `|-` on the first page Page 1: ``` {| | 1 | Chapter 1 |- ``` Page 2: ``` | 2 | Chapter 2 |} ``` In this case, the `pagenum` spans are inserted in the "dead" space between rows and therefore get "fostered". This doesn't set off the linter (I assume due to when the PP extension runs?). This means that all the table pagenum spans end up at the top of the table. On the other hand, extra whitespace between row templates is suppressed. So, the question is: Can the ProofreadPage extension be smarter about where the pagenum template is inserted to avoid putting it in "dead" table space? Or is this something that contributors are expected to need to be aware of, and just be very careful no to inject whitespace between rows? Background reading from when I looked into this at enWS last year: https://en.wikisource.org/wiki/Wikisource:Scriptorium/Help/Archives/2018#.7B.7BTOC_begin.7D.7D_and_family..

On English Wikisource, we have many tables of contents that span multiple pages. However, it's a bit tricky to construct it so that the `pagenum` spans (from `MediaWiki:Proofreadpage pagenum template`) are inserted at the right position. Imagine two Page-NS pages: Page 1: ``` {| | 1 | Chapter 1 ``` Page 2: ``` |- | 2 | Chapter 2 |} ``` In this case, the `pagenum` spans are inserted after Chapter 2, which is technically the wrong row, but it's a valid place for content to be (it's inside a td element) Also, when the table row is templated, this means that whitespace between rows is "sucked" into the end of the "Chapter 1" cell, and since `|-` has to start on a new line, it's easy to get extra row into the cell contents, even with a single-line gap in the wikitext: ``` {| {{foorow|1|Chapter 1}} {{foorow|2|Chapter 2}} ``` produces: ``` {| | 1 | Chapter 1 |- | 2 | Chapter 2 ``` The other way around, with `|-` on the first page: Page 1: ``` {| | 1 | Chapter 1 |- ``` Page 2: ``` | 2 | Chapter 2 |} ``` In this case, the `pagenum` spans are inserted in the "dead" space between rows and therefore get "fostered". This doesn't set off the linter (I assume due to when the PP extension runs?). This means that all the table pagenum spans end up at the top of the table. On the other hand, extra whitespace between row templates is suppressed. So, the question is: Can the ProofreadPage extension be smarter about where the pagenum template is inserted to avoid putting it in "dead" table space? Or is this something that contributors are expected to need to be aware of, and just be very careful no to inject whitespace between rows? Background reading from when I looked into this at enWS last year: https://en.wikisource.org/wiki/Wikisource:Scriptorium/Help/Archives/2018#.7B.7BTOC_begin.7D.7D_and_family..

On English Wikisource, we have many tables of contents that span multiple pages. However, it's a bit tricky to construct it so that the `pagenum` spans (from `MediaWiki:Proofreadpage pagenum template`) are inserted at the right position. Imagine two Page-NS pages: Page 1: ``` {| | 1 | Chapter 1 ``` Page 2: ``` |- | 2 | Chapter 2 |} ``` In this case, the `pagenum` spans are inserted after Chapter 2, which is technically the wrong row, but it's a valid place for content to be (it's inside a td element) Also, when the table row is templated, this means that whitespace between rows is "sucked" into the end of the "Chapter 1" cell, and since `|-` has to start on a new line, it's easy to get extra row into the cell contents, even with a single-line gap in the wikitext: ``` {| {{foorow|1|Chapter 1}} {{foorow|2|Chapter 2}} ``` produces: ``` {| | 1 | Chapter 1 |- | 2 | Chapter 2 ``` The other way around, with `|-` on the first page: Page 1: ``` {| | 1 | Chapter 1 |- ``` Page 2: ``` | 2 | Chapter 2 |} ``` In this case, the `pagenum` spans are inserted in the "dead" space between rows and therefore get "fostered". This doesn't set off the linter (I assume due to when the PP extension runs?). This means that all the table pagenum spans end up at the top of the table. On the other hand, extra whitespace between row templates is suppressed. So, the question is: Can the ProofreadPage extension be smarter about where the pagenum template is inserted to avoid putting it in "dead" table space? Or is this something that contributors are expected to need to be aware of, and just be very careful no to inject whitespace between rows? Background reading from when I looked into this at enWS last year: https://en.wikisource.org/wiki/Wikisource:Scriptorium/Help/Archives/2018#.7B.7BTOC_begin.7D.7D_and_family..