@Samwilson Estimate for this ticket? Thanks in advance.

@dmaza Looks like this didn't get estimated yet. Any suggestion for the points it should be assigned? Thanks in advance.

Thanks for doing this, @Samwilson! How many points should we mark this as?

I have also tested http://wsexport.wmflabs.org/tool/book.php?format=mobi&lang=pl&page=Dziady%20cz%C4%99%C5%9B%C4%87%20III%2FScena%20V and it exports correctly. I am marking this as Done.

This change has been on production for a while now, and it seems to have resolved the issue. Users can now see valid expiry values in the dropdown. If there are invalid translations, they can still watch pages permanently. I'm marking this work as Done.

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.

I now see the invalid format message (see screenshot example below). Furthermore, if an invalid format is submitted, it defaults to epub. I'm marking this work as Done.

This is now on production. As noted by Dom, there are some minor formatting issues for us to analyze, as a result of this work. However, these issues can be addressed in separate tickets: T270367, T270372, T270373, T270395. For this reason, I am marking this work as Done.

This has been merged & has passed QA. It only impacts developers (not production), as noted by Dom. For this reason, I'm marking this work as Done.

Okay, thanks, @dmaza. I've added this information to the follow-up ticket (T271336), so it doesn't get lost. We'll discuss it in a future meeting.

@dom_walden Thank you for providing this information! It's a really great point.

As we are now recording the time it takes, which matches the data collected by Dom, I'm marking this as Done. There may be opportunities to chart this data with @jwang, but this can be explored in another ticket (placeholder ticket: T271336). Thanks!

@Samwilson Perhaps we already do have this data available! I wrote this placeholder ticket after talking with Jennifer, since she found she was able to create charts for Wikisource data, but she hadn't been able to create one for Wikisource downloads yet. So, the purpose of this ticket was to bring up the question of where/how to get this data, so @jwang could create such a Superset chart of ebook exports. As for the question of per user statistics, perhaps this could be useful? What do you think would be the main reason/use case for getting this data at a per user level? To see if certain users are increasing their activity over time?

Ah, thank you for clarifying, @dom_walden! In that case, we'll discuss it tomorrow during estimation.

Thanks for providing this potential explanation, @Billinghurst! Since this seems to just be on wsexport-test (and not on production), we'll monitor this & keep it open, but we won't prioritize it at the moment. However, if you or anyone do see this on production, please do let us know in this ticket & we can investigate further. Thank you!

@Samwilson Yes, great question about actually displaying the duration! Perhaps I can talk with @jwang (after our holiday break) about creating a table to display the calculated average time per download over a period of time. I think a statistics page would be great, but it can be handled in a separate ticket. I have created a placeholder ticket to separately explore this question: T270770. Thanks!

@Samwilson Thanks for bringing this up and apologies for the delay in response! While it seems like either Mobi or MOBI is acceptable, based on some quick research online, I think it probably makes sense to use MOBI (all caps). The other formats are capitalized in Wikisource, so it's better UX to have the same format. Also, I have found that some other online tools that deal with exporting or converting ebook file types use "MOBI" in all caps, so this would be a familiar user experience to many users.

Hello, @ValeJappo! Thank you for filing this request! Unfortunately, we can only display the data and analysis that we get from the WhoColor API. Currently, WhoColor is only available for English, German, Basque, Turkish, and Spanish Wikipedia. With that being said, we're would also love to see if WWT can be expanded to other wikis, which comes down to the WhoColor API. If the maintainers of the API expand to more languages, such as Italian, we would be happy to add that support to WWT, but it's not something we could do ourselves.

This is now on production. I have tested, and the issue has been fixed, as per the acceptance criteria. For this reason, I'm marking this ticket as Done.

The issues described above have been documented in separate tickets, and this work has been released to production. For this reason, I'm marking it as Done.

The release is complete, so I'm marking this as Done.

We have proceeded with the cache work in T265660, so I'm now marking this investigation as Done.

This has been released, and the font variant issue will be followed in another ticket. For this reason, I'm marking this work as Done.

The feature is now all wikis, so I'm marking this as Done.

Thanks for reporting this issue, @PerfektesChaos! When I tested on Brave/Chrome and Firefox, I wasn't able to reproduce the issue. However, as you report, it may be appearing on certain browsers, especially older browsers. I have created a separate ticket (T270197), so this issue can be tracked. Since it doesn't seem to happen on updated browsers, it's probably lower priority for us to fix now, but it's good for us to know & perhaps our team or a volunteer developer can fix it in the future. Thanks!

Thanks, @Esanders! I have updated the 2019 results page and the project page for the wish with this update.

@MusikAnimal Hello! How many points would you estimate this ticket to be?

Great, thanks, @Samwilson! I'll mark it as 5 :)

Fantastic, @Marostegui ! Thank you for your help & collaboration throughout the course of the release process. It's really appreciated :) I'll now mark this ticket as Resolved and we can keep track of the sizes in T268096.

Hello, @gh87! There are two more ways to edit the watch period. You can edit the page with the source editor & change the watch period upon saving. You don't need to actually make an edit to change the watch period. Additionally, you can access the action=watch version of a page, where you can also modify the watch period.