Swedish Translation Progress #1
Comments
|
@rloqvist, @machalvan please use this issue to track your progress and let me know if you have any questions! |
|
@tesseralis Hello Nat, thank you! |
|
@rloqvist @machalvan how's it going? Please let me know if you need any help |
|
@tesseralis Hello, we were initially waiting for more people to join in, but we will start the process of translating with just the two of us! We will be sure to ask if there is ever anything we require help with! |
|
@tesseralis |
|
Hi @nsadev! You are very welcome to help with the translations. I sign you up for the "Hello World" page. No forking is needed, just clone the repo and submit a PR when you are done. I hope you will enjoy the world of open source. |
|
@machalvan Great, thank you! |
|
Hello! Have finished the translation though it's still in a Word-doc since running into problems when trying to get Yarn and Gatsby to play nicely = can't see the site "live" which would be good, easier to see if the text flow is ok that way. It's the first time I'm using both Yarn and Gatsby (got the lastest stable verisons of both), anyone know what the most common problem is when getting the error "There was an error compiling the html.js component for the development server", or no need to ge it up and running and just add the translation and make the PR? |
|
Hi @nsadev ! First of all, welcome! Secondly, I've never experienced that particular error. What is the output of If you still have issues, you are more than welcome to submit a PR to my personal fork, where I can inspect it live. If it runs and looks good you can then submit a PR to this current fork. |
|
Hi @rloqvist and thank you! The versions are: v10.15.1, 1.15.2 and 2.5.9 so that shouldn't be the problem. Could it possibly be that it's "just" a clone (the info from machalvan said I only needed a clone) and not a fork that causes the problem? Have googled quite a bt and others have encountered the problem but it's been different solutions for most of them. |
|
A fork and a clone of a repo are exactly the same thing. I created a branch in this repo called |
|
And the newbie problems continue.. When pushing with the command given by @rloqvist I'm getting an error that the permission is denied. Did "checkout -b Hello-World-v1" before adding the translation, was that wrong and not needed? Edit: restarting and trying to make the change in all ways (that I know of) give the same error. |
|
If you create your own fork in github and create a pull request from there it will help with the permission error 🙂 |
|
Created my own fork but it didn't help with the permission error. Found the problem with getting Gatsby up and running, had swedish letters in the folder name. It only shows a blank page but always something. Could I email the translation to anyone of you instead? You can remove me from the Hello World-page, happy to provide the translation with no credit. |
|
I believe it is because you are still trying to push to this repo. If you push to your fork we could set up a pull request from there 🙂 |
|
Think I managed to figure out what you were referring to, at least got the push and all to work so a PR is sent. Still get a blank page when trying to view the site (several errors in the console to go through) so haven't been able to check if everything looks ok and works, etc. Do let me know if anything need to be changed/corrected. |
|
Hello again! Had a look at your translation and think we know the reason you get some errors. When translating everything needs to remain the same under the hood with links, paths, ids etc. There is also no need to create new files, the old files can be edited in place, e.g. First step could be to move all the contents of Secondly, take a look at the style guide for translations. And lastly, if you ever have any questions, just get back to us and we will try to help out in any way possible 🙂 Edit: Here is an example taken from the russian site https://github.com/reactjs/ru.reactjs.org/pull/2/files |
|
Shoot, read the style guide before asking about contributing and seem to have forgotten about it right away after, sorry! About to correct it all but just to (hopefully) keep errors to the minimum this time, should the title of the page (top of the page below the id) be translated or is that part of all the under the hood stuff as well? The problem with viewing the site in a browser seem to be something with Gatsby and looks like a semi-common problem, will look into it a bit more. |
|
I would make it as a rule of thumb that all the "text" the user sees should be translated 🙂 |
|
The title is seen both in the navigation and at the top of the page it self 😏 Didn't translate the title when making the corrections to the Hello World page though. New PR sent, still haven't found the right solution to view the site in browser so please check it (fingers crossed that there are a minimum of errors). |
|
That is fine, there is both precedence for that and it is supported in the style guide 🙂 please review the feedback on your PR and we will merge it as soon as possible |
|
I'm attempting to translate "Home Page". (see #3)
Also I'm having a hard time finding this "glossary" that was described in the guidelines, any pointers? |
|
Also, as part of the Home Page translation I also translated the few words in the |
|
I'm continuing with the Tutorial page, see #5. At around 1200 lines it might take me a few days to finish though. I'm currently around 14 % complete there... |
|
|
|
@rloqvist @machalvan |
|
Hello @rloqvist @machalvan I would love to help on this if you like, it looks like there are not too many contributors yet and progress is on 3% https://isreacttranslatedyet.com/ If you need help I will get busy with the next page in line (Basics: State and Lifecycle). I can also check some of the existing PRs Good job so far! |
|
@rloqvist @machalvan I'm doing Also note that I've translated |
|
@rloqvist @machalvan I'm doing |
|
Hej @rloqvist @machalvan Would be happy to help with this! Seems like no one has started translating the |
|
Hello @rloqvist and @machalvan I would like to translate the Give me a thumbs up and I’ll get going. 😃 Edit: I’ve translated the page already at #13 |
|
Would it make sense to partially translate |
|
I have translated the |
|
Moving on to translate the |
Does this mean ”translate a page, then wait for it to be reviewed and approved before moving onto translating another page”, or does it simply mean ”don’t start translating another page until you’re done translating the current one”? Asking for whether or not I can move through a bunch of pages. 😄 |
|
@danielpox I would say the latter. AFAIK it is just so that you don't waste your own time. I have several PRs open, same as my colleague @lofgrenfredrik just go ahead :) |
|
Finished translating the |
|
Hello @danielpox! Very good job so far. It is fine to work on multiple PRs at the time as long as you feel done with translating the previous page. I will update the progress on the pages you have worked with. |
|
Just to let you know I've closed my PR and removed the source fork on "State & lifecycle" due to inactivity, but please feel free to use the content but perhaps with a different author #9 |
|
Speaking of which, how is the progress on this? We also have the feeling of inactivity that @nAndreas expresses. What is the official status? What more can we do to move this along? @rloqvist @machalvan |
|
Admittingly, there have been some inactivity from our side. I'm looking through all the PR in the hope of getting the reviews done today. Tomorrow I will start consolidating all your great suggestions into the glossary. @nAndreas I'm sorry to hear that, I will go through your translation and use as much of it as possible. I apologize for this taking so long, I will try to do better in the future. |
|
@rloqvist No need to apologise, times of inactivity is totally understandable. Thanks for your efforts 🙇 |
|
So, what's the deal here? Can anyone claim a topic and try their hand at translating this? Is master up to date? Seems like there is an awful lot of PRs waiting to update the source. Who's "in charge"? |
|
@lekoaf well yes, that was the idea. But the "ones in charge" (@rloqvist and @machalvan ) have been inactive for a very long time. Me and @lofgrenfredrik from We ahead have been trying to move this along with numerous PRs. I'm still willing to contribute but I think the repo needs new owners. Not sure if there is any process or if @tesseralis can make something happen... |
|
There hasn't been much progress since last time and work really picked up for me and @machalvan and thats just how it is sometimes. @michaellopez We initiated this project in the hopes that more people would join the maintainer team as we went along since it is kind of a large undertaking. If anyone wants to be added to the maintainer list just let me know and I will submit a pull request |
|
Hi guys! I would like to translate the "Add React to a Website". I've forked and are ready to get going. :) |
|
It looks like this translation has stalled, and is now very outdated. |
Maintainer List
For New Translators
To translate a page:
Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:
When PRs are merged, make sure to mark that page as completed!
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.
Basics
API Reference
Navigation
These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.
Next Steps
These are the next most important translations, ordered by importance:
Installation
Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.
Warnings
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.
Advanced Guides
FAQ
Contributing
Priority: Low
Components
Components in
src/componentsthat have some text in them.Additional Translations
These are not the primary translation targets.
The text was updated successfully, but these errors were encountered: