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

Adding document and Wiki translations #149

Closed
yolowex opened this issue Jun 17, 2023 · 5 comments
Closed

Adding document and Wiki translations #149

yolowex opened this issue Jun 17, 2023 · 5 comments
Labels
feedback wanted Opinions on this are welcome!

Comments

@yolowex
Copy link

yolowex commented Jun 17, 2023

I can translate the libGDX wiki and documentation into Persian (فارسی).

I believe this would be a valuable contribution to both the libGDX community and Persian developers who may not have a strong command of English.

I have discussed this idea with some contributors on the Discord server, and Damios suggested that I open an issue here.

@crykn
Copy link
Member

crykn commented Jun 17, 2023

Hey @yolowex!

It's very kind of you to offer to translate the wiki! As I've already written on the Discord server, there are two things we'd need to figure out first:

  • Is there a good technical solution for doing this with Jekyll? A quick look didn't turn up any good out-of-the-box solutions, but I think this shouldn't be too difficult if we adapt the wiki template file.
  • Do we even want multi-language support for the wiki? That would certainly increase the work needed for maintaining the site and could sooner or later lead to one of the versions of the wiki being outdated. This all depends on finding people willing to translate new changes in a timely manner.

Since this is quite a big decision, I'd certainly appreciate the input of other people on this!

@crykn crykn added the feedback wanted Opinions on this are welcome! label Jun 17, 2023
@yolowex
Copy link
Author

yolowex commented Jun 18, 2023

@crykn

For the second question, I believe yes.

It's obvious that anyone who wants to learn programming and advance in it, has to know English.

But many people who are just starting to learn programing, aren't as fluent as needed to read the docs.

Ofc they have to learn English eventually, but in the early stages of their learning course (programming), this can be a such a barrier that has the potential to easily reduce their motivation.

So in short, I think having the docs translated makes the framework more beginner friendly, and is beneficial for both the newbies and the framework (in the long run).

And for the maintenance part, after each update, the translated docs can be tagged as outdated.

And the translators can be pinged/informed, so they can add the latest changes in the translations.

@Frosty-J
Copy link
Collaborator

Even in English, the wiki is lacking maintainers. Some of the Android stuff in particular is very old, circa 2009 I reckon, which is an eternity when Android's best practices change annually. I'm not against manual translations, but it would be a challenge to maintain (there's even more wiki than it appears at first glance - see #70).

@obigu
Copy link
Contributor

obigu commented Jun 18, 2023

I'd agree better focus the efforts on better mantaining the English wiki than adding a new translation which would quickly become out of sync with the English one.

@yolowex Imo a way to spread libGDX in your community/language would be to create your own content on that language and we could link it from the libGDX site if we consider it useful.

@crykn
Copy link
Member

crykn commented Dec 26, 2023

Considering the maintenance required for this, the consensus seems to be that non-english resources are better suited for third-party sites. If there ever are any serious translation projects, we can link to them on the starting page of the wiki.

@crykn crykn closed this as completed Dec 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback wanted Opinions on this are welcome!
Projects
None yet
Development

No branches or pull requests

4 participants