2. Mobilizon
3. Mobilizon Glossaire
4. Galicien

Guidelines

• When in doubt, use the suggestion feature instead of changing the translation directly
• Post a comment to discuss about translations
• Feel free to ask clarification and context on a string

Components

Mobilizon has several modules that need to be translated:

• Frontend: mostly what you see in the web app in your browser

• Activity: every group activity log, that can be sent in emails

• Backend errors: errors returned by the backend (for instance if the event lacks a title)

• Backend: the rest of emails, server-side default configuration, push notifications, …

• Search index: the global search engine

  The Android app and Android app metadata components are not maintained.

Formating

Frontend (frontend + search index components) and backend (everything else) parts use different formats to hold translations so you may encounter different ways to format strings when translating:

• Frontend uses the Vue-I18N library
  • Formatting is based on the ICU Message Format syntax, with placeholders like this: {interpolation}. You must never translate what's between the brackets.
  • It handles pluralization manually by separating versions with pipes : https://vue-i18n.intlify.dev/guide/essentials/pluralization.html
  • Pluralization rules are included for the majority of languages but some may need to be added manually (example for Scottish Gaelic).
  • Special characters sometimes have to be escaped. For instance: {'@'}{username} would give, after interpolation : @thomas. See https://vue-i18n.intlify.dev/guide/essentials/syntax.html#special-characters
• Backend uses the classic Gettext library and Weblate should support this format much better
  • Placeholders look like this: This is user %{username}.