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

Request for translation approval #53

Open
rc-05-zz opened this issue May 9, 2019 · 22 comments
Open

Request for translation approval #53

rc-05-zz opened this issue May 9, 2019 · 22 comments

Comments

@rc-05-zz
Copy link

rc-05-zz commented May 9, 2019

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

@the-maldridge
Copy link
Member

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.

@rc-05-zz
Copy link
Author

rc-05-zz commented May 9, 2019

Maybe i could do something similar to this, since this site uses jekyll:
https://forestry.io/blog/creating-a-multilingual-blog-with-jekyll/

@rc-05-zz
Copy link
Author

rc-05-zz commented May 9, 2019

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!

@the-maldridge
Copy link
Member

Edited your comment to fix the link.

@the-maldridge
Copy link
Member

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.

@rc-05-zz
Copy link
Author

rc-05-zz commented May 9, 2019

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

@Gottox
Copy link
Member

Gottox commented May 10, 2019

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

@the-maldridge
Copy link
Member

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.

@rc-05-zz
Copy link
Author

rc-05-zz commented May 11, 2019

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

@Gottox
Copy link
Member

Gottox commented May 13, 2019

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.

@Vaelatern
Copy link
Member

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.

@rc-05-zz
Copy link
Author

rc-05-zz commented May 19, 2019

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

@Vaelatern
Copy link
Member

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.

@rc-05-zz
Copy link
Author

rc-05-zz commented May 20, 2019

Maybe when the user hovers the cursor over a flag it specified the language: that could be intuitive enough to everybody

@Vaelatern
Copy link
Member

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.

@rc-05-zz
Copy link
Author

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?

@Vaelatern
Copy link
Member

so, to summarize: I will reject any menu that does not also include text. Flag icons: OK. Only flag icons: Not OK.

@rc-05-zz
Copy link
Author

rc-05-zz commented Jun 5, 2019

That's perfect. So, should I start by forking the code of the website or not?

@ghost
Copy link

ghost commented Oct 28, 2019

What is the current status of this issue, someone working on a solution? @Gottox @the-maldridge @Vaelatern

@superuser-does
Copy link

superuser-does commented Dec 10, 2019

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.

@Vaelatern
Copy link
Member

I personally am not working on a solution. Contributions probably welcome.

@vitiko98
Copy link

Is this still a thing? I'm ready to contribute with a spanish translation.

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

No branches or pull requests

6 participants