-
Notifications
You must be signed in to change notification settings - Fork 296
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
Documentation in French #1319
Comments
Non, il n'y a aucun travail en ce sens à ma connaissance. However having a documentation in multiple languages seems hard to maintain. |
It will be hard to keep the localized documentation up to date. I suggested something similar in go-gitea/gitea#6552 and it seems there is no simple way to maintain docs in multiple languages (note that gitea uses Hugo for their documentation, which has built-in i18n/l10n features, but even then, keeping multiple languages in sync is painful) |
OK, I understand. You're both right! I might make one unofficial documentation though one day because we are using Shaarli at work and it would be nice to have a documentation in French. If I do, I'll let you know :) |
@Llune I assume you would want to only translate end-user documentation? Eg. not the entire setup/admin/dev documentation, but only the If that's the case, that would be more manageable. since these pages don't change so often, and are the only pages of direct value to non-technical end users:
What could be done:
Does this make sense? Please let us know if you're interested, feel free to re-close if not. |
Hi, Documentation in multiple languages can be managed using the Sphinx documentation engine, which provides internationalization features:
The translation files use the Gettext format and can be edited with Poedit or sphinx-intl As Sphinx is ReadTheDocs' canonical engine, internationalization is supported there as well:
This would require porting the documentation to Sphinx (which we already use for the Python API client) and either switching to CommonMark (Markdown with batteries included) or reStructuredText. IMO this would be interesting as Sphinx has a number of advantages over MkDocs:
|
Hi! I've not forgotten you but had no time to work on it. If I do work on the documentation, I'll let you now before I start! |
The switch to recommonmark + sphinx can easily be done, here is a sample working config:
Edit: issue about switching doc generation system in #1451 |
J'envisage de commencer à traduire la documentation de Shaarli en français parce que je n'ai pas trouvé.
Avant de le faire, je préfère demander s'il y a un déjà un travail qui a commencé là dessus.
The text was updated successfully, but these errors were encountered: