reactjs / translations.react.dev Goto Github PK

Link to ReactJS localization team at Ask for help in README.md is broken

Hey!

Please setup DNS for reactjs/fi.react.dev. The Vercel instance is already available, but not connected to the subdomain.

At the time of writing, all pages for the Learn side are translated and more is to follow on the Reference side.

Thanks!

www.isreacttranslatedyet.com seems to be expired and claimed by someone else.) seems to be expired and claimed by someone else.

My PR #191 for adding a new language should have triggered the creation of a new repository last Monday to the reactjs org but it hasn't.

From the readme:

Once the PR is accepted, the bot will:

• Create a new repository for you at reactjs/{lang-code}.reactjs.org
• Add/invite all maintainers listed to a "reactjs.org {language} Translation" team in the reactjs organization
• Create an issue from PROGRESS.template.md in the new repository to track your translation progress

The Procfile has the scripts automated to run on Mondays at 08:00.
https://github.com/reactjs/reactjs.org-translation/blob/720817338730965829cfe192ef1bbd4da47b3be5/Procfile#L1

I've already created a repository under my profile, but for the sake of consistency, I would like to migrate it under the reactjs org. Thanks!

Greetings everyone?, There is dependabot's alert saying critical severity for other localization projects. Do we need to wait for the reactjs.org to upgrade it ? or we can upgrade it by ourselves(localization contributors)?

Is the react translation bot up and running? We (ja.reactjs.org) did not receive auto-generated PRs on the last two Mondays (Apr 27 and May 4). Maybe the schedule has changed?

By the way, is there a way to check the log or manually invoke the sync process?

The translation tracker app has moved to the website folder in this repo.

We need to do a few things:

• Move translation tracker to react.dev domain
• Update https://github.com/reactjs/translations.reactjs.org/blob/main/PROGRESS.template.md to match new docs
• Update all repos with a fresh checklist issue of pages to translate
• Ensure the tracking website works properly (it appears broken)
• Archive all languages that don't have active maintainers
• Ensure sync workflows are working
• Ensure permission sync workflows are working Remove the need for permission syncs

Unfortunately, it appears that the current maintainers of the Arabic translation have been inactive for a prolonged period of time. Nobody reviews the PRs. So I'am interested in taking over some work.

Allow me to introduce myself and provide some information about my translation experience:

1. Native Arabic Speaker.
2. graduated from Alazhar Translation Center.
3. Part-time Translator at localistars.com.

Furthermore, I have already made substantial contributions to the Arabic translation of ar.reactjs.dev. Here is a list of pull requests I have submitted:

• Tutorial tic-tac-toe
• Add React to an existing project
• React Developer tools
• Render and Commit
• Editor Setup
• Writing markup with JSX
• Importing and Exporting Components

Ahmed Abdelbaset

The React docs translation bot has stopped working because "there hasn't been activity in this repository for at least 60 days". Please resume the scheduled run so we can start translating the new React 19 blog posts.

Related docs: https://docs.github.com/en/actions/using-workflows/disabling-and-enabling-a-workflow

Warning: To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

@gaearon @rickhanlonii @harish-sethuraman

" id: hooks-faq title: «Хуки: ответы на вопросы» permalink: docs/hooks-faq.html prev: hooks-reference.html "
is displayed there https://ru.reactjs.org/docs/hooks-faq.html

Currently, if the sync script runs again before the previous one is merged, a duplicate PR is created (including new changes), and it's up to the maintainers to manually close the previous PR.

Honestly, I don't really know what's the best behavior in this situation. A few possibilities:

• Open a new PR and not do anything to the old one, and let the maintainers handle it (current behavior)
• Close out the previous PR (this means if someone has fixed the conflict before, they have to do it again)
• Just not open a new PR if the bot finds a current open sync PR.

What do people think?

Hello, I'm translating the original page to my primary language which is Persian(named Farsi). I translated some pages like tutorial page which is too long but since my financial situation isn't good I can't share it completely free. Can I to bring ads to special page(my translated content page) or something else?

~~Assign each sync issue to (some subset of) the maintainers of the repo.

It's just kind of annoying to do it using GitHub's API.~~

The current system of managing managers for different translations is kind of annoying. We're using Github Teams for each language, which hasn't been the best.

• It doesn't automatically assign reviewers to PRs/issues
• It's impossible for people who are not members of the React organization to see who is in charge of a repo
• It requires us to manage private ~50 teams that people never actually use
• It requires us to maintain a separate inventory of maintainers in this repo that needs to be synced.

Code owners would fix these issues and hopefully more.

Open questions:

• What happens when someone who is not a member of an organization (but has an invitation) becomes a code owner? Need to make sure this works.

Right now each translation has its own subdomain (es.reactjs.org, ja.reactjs.org) run as a separate website. This follows the convention of Vue and Angular but has several disadvantages.

• We lose the advantage of single page apps, since switching languages requires you to load a completely new site.
• Each language site doesn't have access to data from other sites, so we can't do things like only showing languages that have been translated in a dropdown.

Since I'm doing work on doing translations for Gatsby, which the site is based on, I'm thinking of doing some work to consolidate all the different translations under one main site.

This work entails:

• Moving all strings to markdown/yaml in content and removing src/
• Add logic in the main repo to source content from the language repositories and serve them at reactjs.org/es/docs etc.
• Redirect all languages to the main site: e.g. es.reactjs.org to reactjs.org/es

Currently, we keep three separate lists of languages:

• The one in this repo in the langs/ folder
• The one in Is React Translated Yet
• The "official" one in the reactjs.org repo

Whenever a language is created, I have to update all three of this sources. When one is finished, I need to update the official React list too. I'd like to automate some of this.

Languages that don't have a subdomain yet:

• Greek (el)
• Gujarati (gu)
• Kurdish (ku)
• Central Khmer (km)
• Telugu (te)
• Lithuanian (lt)
• Urdu (ur)
• Swedish (sv)
• Thai (th)
• Georgian (ka)
• Kannada (kn)

Currently, maintainers of a translation are listed in the langs/ directory, but we don't have any way to credit contributors -- community members who provide translations but don't take care of the repo management.

Some ideas for this:

• Put it in the README or a CONTRIBUTORS page of the translation repo
• Add a "translators" property in the frontmatter of markdown docs, and show it on the page
  • I think this works for blog posts but not for other docs for the same reason people don't put authors on the docs in English. There's a lot of authors and the docs will change over a long period of time

Anyone have any ideas?

We need new subdomains for new translations of reactjs.org:

• Catalan (ca)
• Hungarian (hu)

I've found the pt-BR json, but it doesn't appear on ReactJS Translations page.
It's possible find the Portuguese (Portugal), but not the Brazilian language.

Wasn't sure where to ask this question, but I noticed that the Algolia configuration for the es.react.dev is almost the same as the one in the main repository, and all the search is appearing in English.

We are very close to finishing the translations of the content and would be nice to have this working as well.

Is this something the React team can help with or do we use our own config?

In README.md,

Check www.isreacttranslatedyet.com to see if your language already has a translation effort in progress. Click on "Track Progress" on the language you want to contribute to in order to receive further instructions.

However,

• (https://www.isreacttranslatedyet.com , the https URL shows no webpage.)
• http://www.isreacttranslatedyet.com (the http URL)
  

سلام
ابتدا یک ریپازیتوری جدید با نام دقیق کاربری خودتون بسازید.
بعد از اون با مارک دوون فایل readme.markdown رو ویرایش کنید👍

Hello,

I maintain the Modern JavaScrtipt Tutorial at https://javascript.info, also translated to other languages. Thinking about using your automation tools :)

Is there any documentation for that? Maybe someone could help us to set it up?

There is a Korean translation: https://github.com/reactjs/ko.reactjs.org
but it is not list on the translations.reactjs.org Please add it.

ref: reactjs/react.dev#4135 (comment)

Hello,
I am a loyal user of React. I would like to contribute to translating the React documentation into Simplified Chinese. However, I noticed that there's an entry for Simplified Chinese in the langs.json file, but I can't find Simplified Chinese on https://translations.react.dev/. Was there any change made in between? Do I need to submit a new PR?

Dear Team,
I have clone the project and i am trying run inlocal machine but i am getting error..please help me out how to use this project

Hello React Community,

The existing maintainers of the Telugu React Translation repository te.react.dev, became unresponsive for the past few months. So I contacted the existing maintainers via Email and other social platforms regarding adding me as a new maintainer, to the Telugu React Translation repository. But received no response.

So I commented on the reactjs/te.react.dev#1 issue and one of the existing maintainers replied that they are no longer maintainers of the Telugu translation repository.

As stated in Adding a maintainer of this repository readme, I'm creating this issue.

Thank you

It is Franćais but should be Français

Add the "Testing" section to the list of docs to translate. Each language can do it manually, or we could write a script to automate it.

Now that Spanish and Brazilian Portuguese are both one page away from completing translations, I wanted to think about how to approach translating the Blog and Community sections.

Community

I think we can just do a straight translation just like with the other sections. In addition, I think it would be cool if each language was allowed to add resources in their own language instead of just providing the English language resources.

Blog

My best heuristic right now is "translate starting from the newest blog post going back". We should probably focus more on blog posts that contain additional documentation/tips (such as You Probably Don't Need Derived State) rather than just released.

When creating the list of conflicts, it might be a good idea to link the file to its "history" page on the reactjs.org repo. For example:

• content/tutorial/tutorial.md

This is probably the best way for now to discover what has changed in the file since the last merge.

There is no documentation available in Marathi.

Kannada language is missing for the documentation

I noticed some misspellings while reading Apresentando o novo JSX Transform and instead of let them pass I decided to point them for correction.

O Que Há de Diferente na Nova Transformação?

There is a "vocÊ" right at the end of the section, it should be "você".

Eslint

In the following phrase "Se você estiver usando eslint-plugin-react, as regas de", "regas" should be "regras".

Obrigado

The word "Gostaríamso" should be "Gostaríamos" and "intergação" should be "integração".

If you appreciate more corrections like this let me know! I hope I could help a little. 😊