Skip to content

[OLD] Legacy Polish Translation Progress #1

Closed
Closed
[OLD] Legacy Polish Translation Progress#1

Description

@tesseralis
tesseralis
opened on Feb 10, 2019

Slack

https://react-translations.slack.com - join to see the glossary and chat with other team members!
Channels:
#pl - general discussion
#pl-glossary - the glossary (use the search feature to find words)

Maintainer List

Retired maintainers

For New Translators

To translate a page:

  1. Check that no one else has claimed your page in the checklist and comments below.
  2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
  3. Clone this repo, translate your page, and submit a pull request!

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!
Note: We require two maintainers to approve a PR for it to be merged.

Note: Since most of the PRs are created from forks, we can't add our own commits to them. Let's make a rule that if a PR's author doesn't respond within 7 days, we take the translated page over. Another person can create their own PR with the translated content, apply any suggestions added to the old PR, and submit. To be fair, let's not remove entirely the original author from the list below - just add the new translator after comma.
If the author leaves a message that they won't be available for a few days - that's fine, we'll wait.

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.

Testing

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

  • How to Contribute
  • Codebase Overview
  • Implementation Notes
  • Design Principles

Components

Components in src/components that have some text in them.

Additional Translations

These are not the primary translation targets.

Activity

  1. jakubdrozdek commented on Feb 10, 2019

    @jakubdrozdek
    jakubdrozdek
    on Feb 10, 2019
    Member

    Do we (the maintainers) need to put the name of the page we want to translate in the comments here? Or do we just add our username next to the page without asking? ;-) Just curious.

  2. tesseralis commented on Feb 10, 2019

    @tesseralis
    tesseralis
    on Feb 10, 2019
    ContributorAuthor

    Up to you! But it might be a nice courtesy to other contributors and to the other maintainers.

  3. jakubdrozdek commented on Feb 10, 2019

    @jakubdrozdek
    jakubdrozdek
    on Feb 10, 2019
    Member

    Okay then, I'll start off with the style guide.

  4. jakubdrozdek
    pinned this issue on Feb 10, 2019

  5. TeoTN commented on Feb 10, 2019

    @TeoTN
    TeoTN
    on Feb 10, 2019
    Contributor

    Grand! I'll go for Basics first:

    • Hello World
    • Introducing JSX
    • Rendering Elements
    • Components and Props
      (If adjustments to align w/style guide are required, I'll follow)

  6. jakubdrozdek commented on Feb 10, 2019

    @jakubdrozdek
    jakubdrozdek
    on Feb 10, 2019
    Member

    @TeoTN:
    @tesseralis wrote above: "Please take only one page at a time". I'm actually okay with picking multiple pages at once, since there's only three of us right now and there's lots of work ahead. But I want to know for sure. What's the verdict? :-)

  7. TeoTN commented on Feb 10, 2019

    @TeoTN
    TeoTN
    on Feb 10, 2019
    Contributor

    I took these since they're relatively short and basic - I can adjust ;)

  8. jakubdrozdek commented on Feb 10, 2019

    @jakubdrozdek
    jakubdrozdek
    on Feb 10, 2019
    Member

    Where do you prefer to keep the glossary? Should we create an issue for it, put into the style guide (like the Spanish team did) or create a separate file?

  9. TeoTN commented on Feb 10, 2019

    @TeoTN
    TeoTN
    on Feb 10, 2019
    Contributor

    I'd vote for putting it into a style guide

  10. jakubdrozdek commented on Feb 10, 2019

    @jakubdrozdek
    jakubdrozdek
    on Feb 10, 2019
    Member

    I'll take these next:

    • State and Lifecycle
    • Handling Events

  11. tesseralis commented on Feb 10, 2019

    @tesseralis
    tesseralis
    on Feb 10, 2019
    ContributorAuthor

    It's up to you -- it's your project and you can change that rule if you want if you feel it's too restrictive for a small group. Even though it might be a few of you now, more people might join in later.

  12. tesseralis commented on Feb 10, 2019

    @tesseralis
    tesseralis
    on Feb 10, 2019
    ContributorAuthor

    Though I would encourage you to submit pull requests for pages as soon as you're done with them instead of, say, doing five pages and submitting one big pull request for all of them. One thing another language maintainer pointed out is that you could make one consistent style error that isn't caught until PR, which means you'll have to go back and change all your work!

  13. cvqprs commented on Feb 11, 2019

    @cvqprs
    cvqprs
    on Feb 11, 2019
    Contributor

    Guys @jakubdrozdek, @bartlomiejzuber, and @TeoTN I would like to help u with this translation. Where can I start? Do you have any slack etc. to communicate?

  14. jakubdrozdek commented on Feb 11, 2019

    @jakubdrozdek
    jakubdrozdek
    on Feb 11, 2019
    Member

    We communicate via Github Issues. Maybe later on we will add other ways to discuss.

  15. iamarek commented on Feb 11, 2019

    @iamarek
    iamarek
    on Feb 11, 2019
    Contributor

    I'd like to help. I would take care of Getting Started page, if that's fine, since I almost have it done?

  16. 58 remaining items

  17. stepek commented on Feb 3, 2020

    @stepek
    stepek
    on Feb 3, 2020
    Contributor

    i'll take Typechecking With PropTypes #185

  18. jakubdrozdek commented on Jul 20, 2020

    @jakubdrozdek
    jakubdrozdek
    on Jul 20, 2020
    Member

    @tesseralis Hey! I just noticed there are a couple of checkboxes missing on the translation list in the first post. Do you have the complete list and could you paste it here? Or at least tell me where can I get the latest pages list :-) Thanks in advance.

  19. polapolaczek commented on Aug 17, 2020

    @polapolaczek
    polapolaczek
    on Aug 17, 2020

    Hey! If I may - I started translation of Portals page #215

  20. jakubdrozdek commented on Aug 18, 2020

    @jakubdrozdek
    jakubdrozdek
    on Aug 18, 2020
    Member

    @polapolaczek @mbiesiad Please join our Slack workspace to see the glossary and check how we translate things here :-)
    Link to Slack workspace is in the first post of this thread.

  21. mbiesiad commented on Aug 18, 2020

    @mbiesiad
    mbiesiad
    on Aug 18, 2020
    Contributor

    @jakubdrozdek Is this still active? Is this link correct? I'm a member of several workspaces there, but here is a problem with log in.. I'll try again close to the Fri. Let's keep in touch, greetings.

  22. jakubdrozdek commented on Aug 18, 2020

    @jakubdrozdek
    jakubdrozdek
    on Aug 18, 2020
    Member

    It is. Maybe you need some kind of invite? I remember there's this link: https://rt-slack-invite.herokuapp.com/. Maybe it still works?

  23. mbiesiad commented on Aug 25, 2020

    @mbiesiad
    mbiesiad
    on Aug 25, 2020
    Contributor

    it works! thanks a lot 🦄

  24. marcin-wicha commented on Feb 3, 2021

    @marcin-wicha
    marcin-wicha
    on Feb 3, 2021
    Contributor

    Hi. I'd like to translate Reconciliation page. To me it's a very important part of the docs that's often misunderstood.

  25. marcin-wicha commented on Feb 19, 2021

    @marcin-wicha
    marcin-wicha
    on Feb 19, 2021
    Contributor

    @jakubdrozdek #236 Reconciliation is waiting for review 👍

  26. b3s23love commented on Oct 20, 2021

    @b3s23love
    b3s23love
    on Oct 20, 2021

    HI, I would like to translate: Versioning Policy

  27. rickhanlonii
    added a commit that references this issue on Apr 17, 2023

    Fix legacy link (#1)

    7863b5b
  28. gaearon
    changed the title [-]Polish Translation Progress[/-] [+][OLD] Legacy Polish Translation Progress[/+] on Apr 25, 2023

  29. gaearon commented on Apr 25, 2023

    @gaearon
    gaearon
    on Apr 25, 2023
    Member

    Thanks to everyone who contributed to the old website translation!
    Closing this issue in favor of the new translation: #287.

  30. gaearon
    closed this as completedon Apr 25, 2023
  31. gaearon
    unpinned this issue on Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions