You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on translating the Grist documentation to french, and were wondering what the best way to go about it was ?
Should we fork this repo and create a help_fr/ folder for now with all the translated Markdown content of help/ in it ? Any tool you would like us to use ?
Yes, forking and a help_fr/ folder seems the most practical. No-one on our team is familiar with tooling in maintenance of translations of technical documentation. I poked around and found gitlocalize usable, but have no particular reason to recommend it. We now use weblate for translation of the app, but it doesn't have particular support for documents. I see people doing po4a-based workflows with it, but it looks complicated. Some on your team used crowdin for translation of the app, and crowdin does apparently have some support for document translation. In short, no ideas here, we're ready to follow your lead on this.
Following up on this as we're preparing to really put some time and effort into this. Is forking + a help_fr/ folder still the best option at this stage ?
Would you like us to investigate what the best tool would be to handle multi-language documentation ?
Hey there 馃憢馃徏
We are working on translating the Grist documentation to french, and were wondering what the best way to go about it was ?
Should we fork this repo and create a
help_fr/
folder for now with all the translated Markdown content ofhelp/
in it ? Any tool you would like us to use ?Cheers !
cc @dsagal @paulfitz @anaisconce
The text was updated successfully, but these errors were encountered: