-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transformation en module de la traduction de l'app #703
Comments
Necessary for 1.11.44, custom translations are starting to break. |
@estellecomment je pense qu'il faut intégrer les traductions avec nos modules ensuite (avoir un module qui apporte notre comportement + les traductions associés). |
This breaks scalingo builds, because of the After talking to scalingo support, they don't really know why this happens, they suggest we use a custom buildpack in order to be able to see what's inside the container, and debug the problem. They don't know if it will be fixable. Options :
Option 2 is definitely the quickest to do. We'd need good arguments for the other two solutions. Thoughts ? |
Done the quick way. We can revisit later if it's too much work to maintain. |
Reopening because there's some weird build problems, i'm not very confident that release builds will really work, and the local builds are messed up. |
Should be good now ! |
Actuellement
Toutes les strings à remplacer sont dans /i18n/tchap_translations.json configurer dans "custom_translations_url".
Nouvelle méthode
Utilisation d'un module pour charger la traduction :
https://github.com/matrix-org/matrix-react-sdk-module-api#custom-translations--string-overrides
La traduction pourrait même être dynamique (par exemple, automatiquement remplacer "Element" par "Tchap").
Autre utilité, on peut faire des traductions par module, ça rends le code modulaire.
The text was updated successfully, but these errors were encountered: