I translated not yet translated keys and fixed one case where we used informal speech, because everywhere else formal speech is being used.
closes#1230
Fixes#1326
This PR moves all json in side_menu.json to common.json. We have an issue with the side menu layout as it's a high level component and this causes hydration issues with SSR when global namespaces are not passed by default.
Removed language.json translation file as we don't really need it anymore, just moved the couple of remaining items into tasks.json
I also reverted the change where I created lang_mismatch_lang and lang_mismatch_lang.explanation because we don't actually need two different strings and it was causing an issue where it would show a mix of english and the users language rather than just show the existing "Wrong language" text that is probably a better intermediate until the translations are updated. Let me know if there is a better way to handle updating the source english text for translations.
* website: show language in text area
When the language hasn't been detected (too little text) the langauge that it will be submitted as is shown. When we detect the language is not what will be submitted we show the detected language in red. The tooltip informs the user that they don't appear to be writing in the correct language.
Note: this replaces the modal dialog that we use to popup if the language appeared to differ.
* website: Don't suggest the user change the language
also:
sort keys in json alphabetically
change the way files are printed to be grouped by language.
This will be spicy since we have many german speakers here.
- the translation for fails_task.question was confusing as the question
would require a different answer than yes or no
(the buttons available on the dashboard)
* add new apis to oasst client
* add tos handler
* Add ToS to Dashboard
* use Provider for ToS
* simplify provider
* fix error
* Inject into JWT
* primitive error handling
* update comment
* address review
Remove deleted property from Message
Add dedicated route for delete_message
Pre-commit
Revert change to promp_repository fetch_message
Remove blank line
Desciptions are shown both via tooltips, which are easier to read on desktop browsers, and via an explain (i) button so that mobile users can get the description (though in one larger list).
