Skip to content
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

Closed
jdauphant opened this issue Sep 15, 2023 · 6 comments
Closed

Transformation en module de la traduction de l'app #703

jdauphant opened this issue Sep 15, 2023 · 6 comments

Comments

@jdauphant
Copy link
Contributor

jdauphant commented Sep 15, 2023

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.

@estellecomment
Copy link
Contributor

Necessary for 1.11.44, custom translations are starting to break.

@jdauphant
Copy link
Contributor Author

@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).
Et ne pas avoir un module unique pour toutes les traductions.

@estellecomment
Copy link
Contributor

estellecomment commented Oct 17, 2023

This breaks scalingo builds, because of the yarn add that is called by the module installer, during the build phase (not the install phase) .

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 :

  • debug using custom buildpack
  • remove the yarn add by modifying the installer code. If we add our modules as dependencies by hand, then they are still loaded ok. Done here : Migrate translations to module remove the yarn add to fix scalingo #776
  • stop using scalingo. We use scalingo for review apps and internal builds, so I think it's worth having, we would need to find another provider.

Option 2 is definitely the quickest to do. We'd need good arguments for the other two solutions. Thoughts ?

@estellecomment
Copy link
Contributor

Done the quick way. We can revisit later if it's too much work to maintain.

@estellecomment
Copy link
Contributor

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.

@estellecomment
Copy link
Contributor

Should be good now !

@github-project-automation github-project-automation bot moved this from sprint en cours - WIP to déployé en prod in Roadmap Produit Nov 7, 2023
@odelcroi odelcroi moved this from déployé en prod to done in Roadmap Produit Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants