Missing error translations #1497
Comments
Error handling has been reworked to always go through the new `error_template`, `error_json` and `error_atom` macros. They all accept a status code followed by a string message or an exception object. `error_json` accepts a hash with additional fields as third argument. If the second argument is an exception a backtrace will be printed, if it is a string only the string is printed. Since up till now only the exception message was printed a new `InfoException` class was added for situations where no backtrace is intended but a string cannot be used. `error_template` with a string message automatically localizes the message. Missing error translations have been collected in iv-org#1497 `error_json` with a string message does not localize the message. This is the same as previous behavior. If translations are desired for `error_json` they can be added easily but those error messages have not been collected yet. Uncaught exceptions previously only printed a generic message ("Looks like you've found a bug in Invidious. [...]"). They still print that message but now also include a backtrace.
TheFrenchGhosty
added
bug
Error handling has been reworked to always go through the new `error_template`, `error_json` and `error_atom` macros. They all accept a status code followed by a string message or an exception object. `error_json` accepts a hash with additional fields as third argument. If the second argument is an exception a backtrace will be printed, if it is a string only the string is printed. Since up till now only the exception message was printed a new `InfoException` class was added for situations where no backtrace is intended but a string cannot be used. `error_template` with a string message automatically localizes the message. Missing error translations have been collected in #1497 `error_json` with a string message does not localize the message. This is the same as previous behavior. If translations are desired for `error_json` they can be added easily but those error messages have not been collected yet. Uncaught exceptions previously only printed a generic message ("Looks like you've found a bug in Invidious. [...]"). They still print that message but now also include a backtrace.
|
They are all missing from the locale files. I don't know how those are handled and if they can be edited directly or if they need to be updated through Weblate. If they can be edited directly I'll do so. |
|
Blocked because of #1426 |
|
#1426 has been resolved. Shouldn't this issue be unblocked? |
|
This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked. |
SamantazFox
added
type:i18n/l10n
|
It would be great to have some documentation about how to add new translations in the code. |
|
Yes! Good idea! |
|
This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked. |
Missing translations:
Login has been disabled by administrator.Account has temporarily been disabledRegistration has been disabled by administrator.Administrator has disabled this endpoint.Title cannot be empty.Invalid privacy setting.User cannot have more than 100 playlists.Playlist cannot have more than 500 videosThis playlist is private.Video is unavailable.Invalid parameters.Could not extract continuation.Could not extract community tab.Could not extract channel info. Instance is likely blocked.Could not extract channel JSONCould not extract playlist info. Instance is likely blocked.Could not extract playlist infoCould not extract author infoInvalid scopeInvalid signatureThe text was updated successfully, but these errors were encountered: