← Retour aux issues

i18n : what's missing

publié le , mis à jour
Avatar Codeberg de laemlaem

Cover the most important sections

The first objective is to make the map usable by non-French speaking users. Not to make all the annex pages (like /boussole or /outils) or pseudo-technical documentation translated.

Other example : place edition is not something 90 % of users will do first, though it's important in the medium run

  • translate category names on place pages.

  • itinerary mode

    • car
    • transit
    • walk and bike
  • quick buttons, quick categories

  • review posting

  • Illustrate all this with a couple of pictures to be posted on Bluesky and as a news.yaml.

The rest

  • SEO

  • the place editor, v0

  • the place editor, complete translation

Only partly translated, we have to handle the schema.yaml file as we do for categories.yaml and other yaml files.

  • transit maps : not urgent, they are French-only (though english speakers could use them)

  • various other non translated portions

  • remove some French specific things

  • pages : /outils, etc.

  • content pages like /integration, and all that's linked from the Sidebar.tsx

  • /presentation (can be replaced by "about", already translated)

  • ...

Later

Give localised category keys to each local. So that ?cat=organic-grocery would be shared as an URL instead of cat=magasin-bio

Globally, all the searchParam keys that power this app and lets us use <a tags instead of stateless buttons would need to be translated.

Pathnames too could be translated : /boussole, /outils.


✏️ Participer à la discussion