Currently translators have no way of knowing when something happens on Bilara that they need to know about. We should have one simple system for notifying translators.
overall UI
On the Home page, when a translator logs in, there is a notice at the top of the page:
any remarks by proofreaders (I am not sure if we have a separate field for this. Anyway, just work with whatever is there.)
The translator has three options:
Click "accept" to replace the old string with the proofreader’s suggestion.
Edit the string in place.
Click to open the text at the segment.
changes to underlying texts
Translators typically work from both a root text (eg. Pali) and a translation (eg. English) into their language (eg. German). In such cases they will usually want to receive notifications to:
the Pali root text
the English translation
Note that this is notification per text. You only get a notification if you have made a translation of that specific sutta, not if there any change to the collection as a whole.
choose underlying notifications
There are no underlying texts by default.
Let us give each translator the option of choosing whatever they want to be notified of.
On the Home page, we can put a setting icon ⚙️ next to the notifications notice.
⚙️ Notifications: you have XYZ notifications
Click it, it gives a list of all projects. You can choose to be notified of changes to whatever you want.
background
Currently translators have no way of knowing when something happens on Bilara that they need to know about. We should have one simple system for notifying translators.
overall UI
On the Home page, when a translator logs in, there is a notice at the top of the page:
Click on that, it takes you to
/notifications
.There you have a list of all notifications, similar to https://github.com/notifications
Notifications may be of several types. Each type should be visually distinct. For now, we can just put
class='remark'
class='underlying'
class='split'
class='merge'
for every notification, include the segment number
Each notification should display the segment number. This is similar to the current search results in Bilara:
The segment number is linked to the appropriate page:
This is used for all kinds of notifications, because sometimes the translator needs to see the text in the context of the whole page.
remarks
Remarks (or suggestions) are recommendations made by a proofreader. They are stored in the DB and are not committed to Github.
The original issue for this is here:
https://github.com/suttacentral/bilara/issues/14
This has a fairly detailed UI for remarks.
UI
Each remarked segment presents:
The translator has three options:
changes to underlying texts
Translators typically work from both a root text (eg. Pali) and a translation (eg. English) into their language (eg. German). In such cases they will usually want to receive notifications to:
choose underlying notifications
There are no underlying texts by default.
Let us give each translator the option of choosing whatever they want to be notified of.
On the Home page, we can put a setting icon ⚙️ next to the notifications notice.
Click it, it gives a list of all projects. You can choose to be notified of changes to whatever you want.
UI
Each segment with underlying changes presents:
oldunderlying translation (mark with<del>
)<ins>
)The translator has two options:
Here there is no option to "accept" changes.
split/merge
Any split or merged segments should be notified.
UI
Each split or merged segment presents:
The only difference is that:
The translator has three options: