Italian translations #1762
Italian translations #1762
Conversation
|
Thanks for your contributions first! /cc：@nodejs/nodejs-it |
|
Hi Alex, blog entries are not translated to other languages, so you can safely delete everything in |
|
We might also get an help from @mcollina in reviewing this PR |
locale/it/about/community.md
Outdated
| layout: about.hbs | ||
| --- | ||
|
|
||
| # Commissione Community |
There was a problem hiding this comment.
I would not translate this sentence. I would treat the various WGs, team names as proper names. Community Committee should stay as "Community Committee", just like my name does not become Matthew.
There was a problem hiding this comment.
I don't totally agree with that, in fact I think it's easier to read and understand if we translate roles; I don't think to roles as of names, I give more importance to what they represent to the reader.
There was a problem hiding this comment.
It probably is, but it makes it unsearchable on the web.
There was a problem hiding this comment.
What do you mean? Too much distance between english page and italian one can cause problems?
There was a problem hiding this comment.
Most of the content and the interaction is in English. The name of the github repos are in English etc. Name of things should stay costant so the barrier between Italian and English is as thin as possible.
There was a problem hiding this comment.
Ok. I disagree, but I do not want this initiative to stop. I’ll recuse myself from further reviews (because no, I cannot LGTM this).
There was a problem hiding this comment.
Why not # Community Committee (Commissione Community) ?
There was a problem hiding this comment.
That's cool to me, maybe I'd prefer Commissione Community (Community Committee) but it's great in both ways
There was a problem hiding this comment.
@nodejs/intl we can probably write some guidelines on what shouldn't be translated when we come to a consent.
There was a problem hiding this comment.
Since I don't have guidelines about this, I'll follow @allevo suggestion and use # Community Committee (Commissione Community) , applying this paradigm to all names and committees. We can correct it later on if necessary.
|
@xela92 are you aware of the https://github.com/nodejs/i18n effort? We are using a platform called Crowdin to facilitate community translations of the Node.js documentation. What you're doing here with this pull request is great, but your contributions will have more long-term value if you do your work here: https://crowdin.com/project/nodejs/it |
|
@zeke I didn't know about Crowdin, I checked but I couldn't find website md files to translate! |
|
@zeke The efforts on Crowdin are for the Node.js API docs while this PR is for the website's content. AFAIK there doesn't exist a setup for website translations there yet. @xela92 I'd love to see a basic version of the site in Italian, you already did quite a lot yourself. Thank you for that! I think this would also be a good starting point for others to chime in and help. You can also drop |
|
@xela92 Could you please update your PR as requested? Would be cool if we could land this change soon. |
|
Sorry I had no time, will update it soon on these days :-) |
|
@fhemberger I'm updating my work, but I saw there were some changes in upstream, and for instance Governance page has been made much simpler. Now I'm trying to get aligned with the actual contents and also to merge the enhancements suggested and finish the remaining pages. Now on I'll hopefully have more time to work on it, but it still may be a long road to a complete, redacted and up-to-date translation; I don't know how it usually works with NodeJS PRs but in the meantime do you think that would be possible to start publishing this work instead of having no italian translations? |
|
@xela92 You don't have to do a full translation before it gets approved and released. The best way is to get a +1 from other native speakers for the current status of the translation, so it can be merged. All further updated can be handled in a separate PR then. This makes reviewing also much easier. /cc @nodejs/nodejs-it Please review, so we can get this merged. |
|
@fhemberger thank you so much for the help :-) |
|
Ref：#2024 |
ghost
mentioned this pull request
|
@Maledong: still WIP, now I was waiting for the things already done to be merged, but seems it's not going to happen... @nodejs/nodejs-it please review so it can be merged, I don't want to complete a translation that maybe it's not going to be merged :-) |
|
Can we reduce the diff to only include translated content? This PR is huge and hard to review. |
|
If I'm not wrong only the following files have been translated:
In that case it would ideal to only have those files in the diff. |
|
@xela92：Since you've fixed almost of them, would you mind merging them together for us to see the final result? I mean you can do a rebase to merge all of your changes into files one by one and submit forcely. |
ghost
mentioned this pull request
I've never done a rebase before, I just tried doing a little change, running git rebase and then a forced push. |
Yes, you can just merge all of them into one for us to see clearly. But I didn't see anything forcely pushed ... |
|
@nodejs/website @nodejs/nodejs-it I'm thinking about merging this PR as it is for now and use subsequent PRs for fixes and updates. Otherwise it might be too big for further reviews. Thoughts? Afterwards, we can look at #2024. |
|
@fhemberger I would say go ahead and merge this. |
|
Great, thanks everybody! |
|
Thank you so much everybody! I will continue the translation soon :-) |
|
Hi all： |
Hello,
This is my first pull request ever, so I want to be sure that's fine.
I'm starting a translating process of the NodeJS.org website to Italian language. I saw that only some menu voice was translated, so I wanted to contribute.
Is it ok? Till now I translated Governance page and copied the other templates from EN layout, and I'm gonna translate everything as soon as I can.
PS: thank you for your awesome project, I love NodeJS.