Closed richfab closed 6 months ago
@richfab Cancel my previous comment... we need to use this structure:
.
├─ en/
│ └─ index.md
├─ fr/
│ └─ index.md
└─ mkdocs.yml
... to remove the confusion in managing files.
For future reference, these terms need to be manually replaced with gender inclusive language:
English | Find | Replace with |
---|---|---|
user | utilisateur | utilisateur·rice |
traveler | voyageur | voyageur·euse |
contributor | contributeur | contributeur·rice |
regulator | régulateur | régulateur·rice |
developer | développeur | développeur·euse |
researcher | chercheur | chercheur·euse |
And these terms need to be manually replaced:
English | Find | Replace with |
---|---|---|
repository | dépôt | répertoire |
form-factor | facteur de forme | type de véhicules |
geofencing | géo-clôturées | geofencing |
GBFS | GBFS | |
General Bikeshare Feed Specification | spécification générale des flux de vélos en libre-service | General Bikeshare Feed Specification |
consumer | consommateur | application réutilisatrice |
endpoint | point de terminaison | URL |
@richfab Looks great, just one little visual issue on the Specifications page, the left navigation section cuts off in french, I've seen this before, I'll try to find the issue.
For future reference, these terms need to be manually replaced with gender inclusive language:...
I'll make a script for this eventually, safest option. But I wonder at which step? When people commit markdown files and they get edited right then, or after generating the site maybe?
I'll make a script for this eventually
I think simpleen.io glossary should achieve this but it did not work when I tried it 🤷♂️
I'll make a script for this eventually
I think simpleen.io glossary should achieve this but it did not work when I tried it 🤷♂️
We want to move away from Simpleen, or at least not have it as the only option. At the very least using a script would be a second check just in case.
@richfab Can't find the reason for the visual bug, but it has no impact on UX, so let's leave it like that for now. Removed an extra return inside a paragraph in the english version, added to this PR.
https://github.com/MobilityData/gbfs.org/pull/78/commits/3655ad840fa91c6e501c51fadefd0a81b6810202
@richfab I'm about to go through the backlog of translations for the GTFS website, do you think these changes should be applied as well? Or is this only for GBFS?
For future reference, these terms need to be manually replaced with gender inclusive language:
English Find Replace with user utilisateur utilisateur·rice traveler voyageur voyageur·euse contributor contributeur contributeur·rice regulator régulateur régulateur·rice developer développeur développeur·euse researcher chercheur chercheur·euse And these terms need to be manually replaced:
English Find Replace with repository dépôt répertoire form-factor facteur de forme type de véhicules geofencing géo-clôturées geofencing GBFS GBFS General Bikeshare Feed Specification spécification générale des flux de vélos en libre-service General Bikeshare Feed Specification consumer consommateur application réutilisatrice endpoint point de terminaison URL
Gender neutral language should be used on all websites in my opinion, including gtfs.org. Thanks! cc @isabelle-dr
@richfab I've added the preferred translations to the EN > FR glossary of the translation tool. We could close this PR.
Thank you @fredericsimard! I believe this PR is already closed 👍
This PR adds French translations for all content on gbfs.org using gender inclusive language.
French was prioritized because gbfs.org will be referenced at conferences in France (and because it's the only language I speak fluently with English ^^). Other languages will follow.
Modules:
Note that I could not translate the banner at the top and the footer.