| HMonroy | |
| Oct 6 2020, 7:28 PM |
| F33984291: alignment_after.png | |
| Jan 4 2021, 10:20 AM |
| F33984297: size_after.png | |
| Jan 4 2021, 10:20 AM |
| F33984289: alignment_before.png | |
| Jan 4 2021, 10:20 AM |
| F33984295: size_before.png | |
| Jan 4 2021, 10:20 AM |
Background: After the investigation T257902, it was concluded that the current MediaWiki parser HTML needs to be replaced with the new Parsoid's API so that reliability can be improved and simplify some of the HTML transformations.
Acceptance Criteria:
*WSexport uses Parsoid's API to get the HTML pages and convert them to an epub.
*Parse API's response according to new retrieved data.
I compared the appearance of ebooks generated on test and production for a number of different ebooks, including those in the recently popular list.
I found a number of differences before and after this change. Many of these are not likely to be troubling to users. For example, margins between paragraphs sometimes differ, some text is aligned differently, some text is of different size.
| Before | After |
 |  |
 |  |
There are a few I think are worth fixing, and I raised those separately below:
There are probably more bugs which we will hopefully find in due course.
I mostly tested epub and pdf formats, but I briefly tested mobi and rtf as well.
I compared the appearance of ebooks generated on test and production for a number of different ebooks, including those in the recently popular list.
I found a number of differences before and after this change. Many of these are not likely to be troubling to users. For example, margins between paragraphs sometimes differ, some text is aligned differently, some text is of different size.
Before After
For these two works it would be useful to know the urls of the original works. The Thai language work, I cannot tell whether it is a block center gone wrong or what.
Correction: This is on the test server, but not on production yet. While it appeared to be released, as per https://github.com/wsexport/tool/releases, this wasn't the case when we actually logged into the prod server to check. So I'll move it back to sign-off & mark it as Done when it's released to prod.
It looks like we've either never set up autodeployment on prod, or we removed it at some point. I think we should set it up again. Or were we purposefully sticking at 2.0.0 for a reason (sorry, I know I should remember…)?
This is now on production, so I am marking this ticket as Done. There are some bugs associated with this work, but they will be resolved in separate tickets. The team is already working on some of these tickets and further tickets will be discussed in our next estimation meeting.