Skip to content

start reference translation in greek #240

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

Closed
wants to merge 1 commit into from
Closed

Conversation

mtsio
Copy link

@mtsio mtsio commented Apr 26, 2015

I'm not sure if that's the right way to translate the reference so please comment here. If I got it right I will do more commits soon, so don't merge yet.

@REAS
Copy link
Member

REAS commented Jun 4, 2015

This is how it's done, but we don't have the code in place to use it anymore. Many years ago, we had the reference and environment page translated into about six languages and it was possible to change between them from the reference page. When we made the transition to the 1.0 version of the software, so much changed so quickly that the translations went out of date and the loose community around the translations unfortunately fell apart. Maybe after we make some changes for the 3.0 launch, it will be a stable and good time to do this again. Thoughts?

@scotthmurray
Copy link
Member

@mtsio thank you for this contribution.

@REAS that sounds like a good plan. Since we are currently rethinking the contributions manager (and how to structure relationships with third-party contributors), it could be useful to reframe translation efforts as yet another type of contribution, with one person responsible for each. A translation contributor could keep in touch with us and be responsible for keeping updates in sync. When a translation isn't updated, it could disappear until it is updated.

Maybe shifting that working relationship could help increase the sustainability of these contributions (and avoid the problems that came up with 1.0). Also, less is changing now then during 1.0, so it should be an easier job for the translators. :)

@REAS
Copy link
Member

REAS commented Jun 4, 2015

We also didn't have GitHub in the 1.0 days. We should be able to make this happen.

@shiffman
Copy link
Member

shiffman commented Jun 4, 2015

In case it's useful to align work / approaches, I believe internationalization is in the works as a GSoC todo item for the p5.js web site this summer. I believe @lmccart is working on this with Maya so they can say more.

@shiffman
Copy link
Member

shiffman commented Jun 4, 2015

. . . and as if by a magical mysterious force, I discovered @mayaman26's github handle in my inbox moments after posting the above.

@REAS
Copy link
Member

REAS commented Jun 5, 2015

FYI, I will be re-writing much of the Environment page within the next week to align with the changes for 3.0. People shouldn't start translating that page until it is updated.

@Leamucho
Copy link

Hello, so is there already translation pages or forks to begin contributing? I'd like to for spanish, is Pedro Alpera leading this translation still?

@villares
Copy link

I would like to update a Portuguese reference I found from v1.0...

@Leamucho
Copy link

What I saw on some Reas page is that it is quite complicated to do the translations because one would have to clone three repositories, and make the changes for the language on all three cloned... repositories with files on xml, html, and java apis I believe... I don't have the knowledge to be sure to do that right, but if someone guides me, I'd be willing to learn... :)

@REAS
Copy link
Member

REAS commented Dec 14, 2019

We are starting work on a new way to build the site and a new translation system is a priority. I'm going to close this thread for now and we can discuss the translations in more detail when the time comes.

@REAS REAS closed this Dec 14, 2019
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

Successfully merging this pull request may close these issues.

6 participants