Skip to content
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

Open
luce-carevic opened this issue Jul 12, 2019 · 8 comments
Open

Documentation in French #1319

luce-carevic opened this issue Jul 12, 2019 · 8 comments

Comments

@luce-carevic
Copy link

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.

@ArthurHoaro
Copy link
Member

Non, il n'y a aucun travail en ce sens à ma connaissance.

However having a documentation in multiple languages seems hard to maintain.

@nodiscc
Copy link
Member

nodiscc commented Jul 13, 2019

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)

@luce-carevic
Copy link
Author

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 :)

@nodiscc
Copy link
Member

nodiscc commented Jul 13, 2019

@Llune I assume you would want to only translate end-user documentation? Eg. not the entire setup/admin/dev documentation, but only the Usage part?

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:

| 💥 | La documentation en français peut avoir un léger retard sur la [documentation officielle en anglais]($pagename.md). |
|---------|---------|

Does this make sense? Please let us know if you're interested, feel free to re-close if not.

@virtualtam
Copy link
Member

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:

  • syntax checks (typos, dead internal links/references)
  • tooling (Makefile, Tox)
  • flexible table of contents management
  • integrations with diagramming tools like Graphviz/dot and PlantUML
  • builders for HTML, LaTeX, PDF, EPUB, etc.

@nodiscc nodiscc self-assigned this Jul 30, 2019
@luce-carevic
Copy link
Author

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!

@nodiscc
Copy link
Member

nodiscc commented Apr 12, 2020

The switch to recommonmark + sphinx can easily be done, here is a sample working config:

Edit: issue about switching doc generation system in #1451

@nodiscc
Copy link
Member

nodiscc commented Oct 5, 2023

Documentation in multiple languages can be managed using the Sphinx documentation engine, which provides internationalization features:

PR to switch from MkDocs to Sphinx at #2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants