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

Portuguese translation #1361

Open
27 tasks
raphaelavelar opened this issue May 16, 2023 · 7 comments
Open
27 tasks

Portuguese translation #1361

raphaelavelar opened this issue May 16, 2023 · 7 comments

Comments

@raphaelavelar
Copy link
Contributor

raphaelavelar commented May 16, 2023

Language

Portuguese (brazilian)

What improvement are you suggesting?

Translate the P5.js website to Portuguese

@Qianqianye and @limzykenneth, please let me know if you'd rather break this issue in specific sections.

Items to translate

src/data

src/data/examples

  • Create pt-BR folder
  • 00_Structure
  • 01_Form
  • 02_Data
  • 03_Arrays
  • 04_Control
  • 05_Image
  • 07_Color
  • 08_Math
  • 09_Simulate
  • 10_Interaction
  • 11_Objects
  • 12_Lights
  • 13_Motion
  • 15_Instance_Mode
  • 16_Dom
  • 17_Drawing
  • 18_Transform
  • 19_Typography
  • 20_3D
  • 21_Input
  • 22_Advanced_Data
  • 33_Sound
  • 35_Mobile
  • 90_Hello_P5

src/data/reference

  • pt-BR.json

Would you like to work on the issue?

yes

@limzykenneth
Copy link
Member

Ah, the .ftl files are still there. They are actually localization files from back when I was experimenting with Pontoon. Their data should currently be up to date with those in src/data/reference/pt-BR.json and currently I don't have the Pontoon site setup to work with .ftl. I probably should remove the FTL files since they also don't have great compatibility with the JSON file we use.

@raphaelavelar
Copy link
Contributor Author

No problem, I'll remove them from the list to avoid unnecessary work

@raphaelavelar
Copy link
Contributor Author

@limzykenneth and @Qianqianye , would you mind if I released small PRs with a mix of Portuguese and English in the files as I translate? I think it would be better to review and spot any mistakes.

@limzykenneth
Copy link
Member

It is preferred to have a single PR but with many smaller commits. Reviewing one PR is a bit easier than reviewing many PRs and many small commits easier than one large commit. Although having said that, there is currently no language stewards for Portuguese translation and it is also not officially released yet so I suggest waiting for confirmation from @Qianqianye about plans for this translation before working on it.

@raphaelavelar
Copy link
Contributor Author

@limzykenneth, I'm actually the language steward for the Portuguese translation. I understand that, as it isn't officially released yet, it's also not a priority at the moment. Please, correct me if I'm wrong.

@limzykenneth
Copy link
Member

Ah right sorry, I was just checking the readme page's list. You can go ahead with a PR (draft is fine as well if you plan to work on it over time) if you like to.

@raphaelavelar
Copy link
Contributor Author

No problem, it's not actually in the table as it isn't released, as you said

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

2 participants