void-linux.github.io
void-linux.github.io copied to clipboard
void-linux
Request for translation approval
Hello, i was thinking about starting to translate the void linux page in Italian if possible. In order to organize foreign languages i was thinking about using subdirectories for each language (if somebody wants to translate it to another lang).
I'd like to investigate some kind of jekyll system to do the internationalization. That way we could ideally keep the pages and posts together, just switching them on the frontend.
Maybe i could do something similar to this, since this site uses jekyll: https://forestry.io/blog/creating-a-multilingual-blog-with-jekyll/
Maybe i could do something similar to this, since this site uses jekyll: https://forestry.io/blog/creating-a-multilingual-blog-with-jekyll/
It divides the same blog in different directories, one for each lang: if there is a better method i'm free to listen!
That looks like it could work. Since it requires changes to the site layout, I would sync with @gottox first. Some time ago there was an intent to re-design the site.
The design of the site is perfect: simple and coincise. It's a matter of re-organizing the directory structure and enable multi-lang support for it... We'll see what @Gottox wants to do
The site's may be good, but the underlying src is old and crud. We can do better :D
I'm a little concerned how we can keep the site up to date
Are you referring to the code in general or the source that drives it? Part of me would rather see the website redone in something that natively supports translations, though that would be a larger project.
The site's may be good, but the underlying src is old and crud. We can do better :D
I'm a little concerned how we can keep the site up to date
Maybe we could fork the website source and then do merge requests?
For example each "team" of translation could fork the void website's repo, do the modifications and then create a merge request?
Or it would be better to rewrite the site from scratch? @Gottox @the-maldridge
I have a WIP redesign of the page in my working copy. Nevertheless, I got some feedback and wanted to apply that first.
For the translation in general: I'm concerned that it's hard to maintain changes on the page when we have to apply them to languages we can't speak.
We'd want to make English the landing page, and I'm sure there is tooling for pointing out a translation has fallen behind in a specific place.
A menu could be added that lets the user display the page in their language: an idea for a menu would be to list the different languages with small icons of countries' flags so that it's more intuitive
I will reject any menu that does not also include text. Flag icons: OK. Only flag icons: Not OK. But a menu for language selection is not a terrible idea.
Maybe when the user hovers the cursor over a flag it specified the language: that could be intuitive enough to everybody
Possibly. "intuitive" is not the same as "accessible", I don't know what, for example, screen readers do with alt text. I also don't know how many country flags are indistinguishable for people who are red-green color blind.
Maybe a more "accessible" way (for example for color blind people) would be to integrate the page with a textual menu instead of a graphical one for choosing the language?
so, to summarize: I will reject any menu that does not also include text. Flag icons: OK. Only flag icons: Not OK.
That's perfect. So, should I start by forking the code of the website or not?
What is the current status of this issue, someone working on a solution? @Gottox @the-maldridge @Vaelatern
Re: the above, I refer you to http://www.flagsarenotlanguages.com/blog/best-practice-for-presenting-languages/
You shouldn't really have flags at all for many good reasons, but if you insist then you should have text next to them that is visible by default in the language's native name.
I personally am not working on a solution. Contributions probably welcome.
Is this still a thing? I'm ready to contribute with a spanish translation.
