In T432095#12135141, @Kengkong1 wrote:

Hello Team. I hope everyone is having a good day. As I work on the backend I realise that some words can have multiple classifications like fast- noun, adjective, adverb
so the front end will have to be able to display multiple options for words. To correct this we would need to do Natural Language Processing which is out of our scope.

@Kengkong1 , please check this prototype created by @Dagmawi-M . Please coordinate with each other to sync both of your workflow and codes.

In T432095#12134076, @Kengkong1 wrote:

Hello @Gnoeee. I hope you are doing well. I am currently working on the backend. Could you add me as a maintainer to the Toolforge project so I can have access. Thanks.

This is already done. If you change the interface language, all the category parameters will be changed to that language. Screenshot attached for your reference -

Tool name which is proposed to the team is Leximap or Wikisource leximap, since the tool intends to map lexicographical data from Wikisource corpora

Added fa to app repo too.

Persian is now in the API - https://wsindex.toolforge.org/books/?languages=fa

In T423460#11826527, @TheDJ wrote:

This to me seems like this would be used very selectively, only on very specific wikis. And i dont think this script has enough day to day use outside those wikis, to burden all editors of all wikis (wikimedia and 3rd parties) with this extra category and the extra bytes of pageload that go with it (or the door it would open for other less used scripts).

The final summary report is published - https://www.mediawiki.org/wiki/Outreachy/Past_projects#Improve_the_Wikisource_Reader_App

Breton added to the API and the app. Will show up in the next release.

https://codeberg.org/ph4ni/wsindex/pulls/22 by @Muguro merged for viewed books.

Related T417628

@Muguro , we need to implement this into the app in book details screen. (T417628)