You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow Betty to be configured to use one or more locales.
Consider whether a default locale should be used.
Allow user-facing strings to be translated.
Allow dates to be formatted according the configured locale. Keep in mind while in practice Betty has only been used with Gregorian dates, date parts (days, months, years) may be missing, and in the future support for different calendars may be required.
Consider whether it is a good idea to avoid all-numeric date formats (YYYY-MM-DD, DD-MM-YYYY, or the American MM-DD-YYYY) altogether to avoid confusion.
For non-clean URLs, add the language to the URL.
For clean URLs, allow content negotiation by the web server.
For clean URLs, allow users to specifically request a particular language without using content negotiation as well.
Update the generated nginx configuration to reflect this functionality.
Update the <html> tag.
Ensure JavaScript uses the <html> tag to read the document's language, and displays strings in the correct one.
Allow plugins and sites to provide extra translations located in their resources directories.
Extend the sitemap with localized URLs.
Localize betty.webmanifest.
The text was updated successfully, but these errors were encountered:
Definition of done
<html>
tag.<html
> tag to read the document's language, and displays strings in the correct one.betty.webmanifest
.The text was updated successfully, but these errors were encountered: