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

Docs: Italian version #24391

Open
AngyDev opened this issue Jul 27, 2022 · 12 comments
Open

Docs: Italian version #24391

AngyDev opened this issue Jul 27, 2022 · 12 comments

Comments

@AngyDev
Copy link
Contributor

AngyDev commented Jul 27, 2022

Hello, I'm a software developer and a three.js user.

I'd like to contribute to the library and I think that the best way to start is by documentation. I'd like to translate the documentation into Italian.

What do you think? Is it possible?

@Mugen87
Copy link
Collaborator

Mugen87 commented Jul 27, 2022

That would be a great contribution! We have an issue per language (see #24375 or #14748) so I suggest to use this one for Italian.

It's best to file PRs for specific sections (e.g. "Manual" ,"Animation" or "Core") and not for individual pages. It would be also good to only add translated pages to the it folder and not the English ones as placeholders.

@AngyDev
Copy link
Contributor Author

AngyDev commented Jul 28, 2022

Great!! I can start with the Manual section. I create it folder for the translation.
Is it correct to start from the dev branch?

@Mugen87
Copy link
Collaborator

Mugen87 commented Jul 28, 2022

Is it correct to start from the dev branch?

Yes.

@AngyDev
Copy link
Contributor Author

AngyDev commented Jul 28, 2022

Thanks!
@Mugen87 I have a question, I saw that in the manual pages the title <h1>[name]</h1> is generated at the load of the documentation. Is it right to maintain the English name also for the Italian translation or can I translate it?

@Mugen87
Copy link
Collaborator

Mugen87 commented Jul 28, 2022

I would handle this use case similar to other translations. Meaning translating the titles but keep [name] in parentheses.

@AngyDev
Copy link
Contributor Author

AngyDev commented Aug 6, 2022

Hi @Mugen87!
Which is the next step? Is better to continue the translation with the reference section or with the fundamentals one?

@Mugen87
Copy link
Collaborator

Mugen87 commented Aug 6, 2022

I would continue with the API reference 👍.

@davidedemarco
Copy link

Is there any way I can help with this? I'm an italian sw developer and I'm getting started with three.js, it would be a great way to read the documentation and help out at the same time

@AngyDev
Copy link
Contributor Author

AngyDev commented Dec 12, 2022

Hi @davedema, if you want you can translate from the Addons section, for now, I stopped there. Every time you complete a subsection you do a PR, for example, if you translate Animations you do a PR, then Controls, and so on. That way we keep each other aligned on developments. What do you think?

@davidedemarco
Copy link

looks good! I will work on animations then

@mrdoob
Copy link
Owner

mrdoob commented Mar 15, 2023

We currently have a problem with documentation translations: #24984

@AngyDev
Copy link
Contributor Author

AngyDev commented Apr 11, 2023

Hi @davedema!!! How is the translation of the animation section going? Are you still interested in doing it?

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

No branches or pull requests

4 participants