- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Provide localised title/description ZIM metadata #148
Comments
I'd advise the scraper handles this (best effort) ; keeping in mind we have the CMS. Scraper could have a limited map of Title/Description for languages and fallback to what we have now. In any way, we'd need an Erik-provided Title and Description for English that we can translate in major languages. As the number of languages is already important, we could imagine attempting translations using an online service but most require an API key, Libretranslate doesn't support much languages (and it's only the major ones we could get translations for) and even Google or Microsoft wouldn't support them all. |
@rgaudin OK, it would be good that these two strings are besides the others. |
No, but I think the community could generate such a list in a few weeks. |
so the strings to be translates would be Title: "Project Gutenberg Library - Books in " and Description: "The first producer of Free Ebooks" (or something better). ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
Best handled with Translatewiki I guess. |
We just need here to have the strings in the translation files. Trivial. |
Currently the Gutenberg ZIM we produce share the exact same ZIM title/description metadata (in English)
This, although:
I think we should either introduce translated versions of these metadata or split the recipe in Zimfarm https://farm.openzim.org/recipes/gutenberg_mul_all.
@rgaudin Not sure what is the best approach
The text was updated successfully, but these errors were encountered: