Increasing Access
The text-detail pages (about, code-of-conduct, contact, copyright, donate, download, privacy-policy, terms-of-use) are the main info pages on the site. Korean currently only has 3 of 8 translated (about, code-of-conduct, donate), so Korean speaking users hit English when they click Download, Contact, or Copyright. So adding the missing Korean translations gets these pages to the same level of access Korean users already have for the About page.
Most appropriate sub-area of p5.js?
Other (specify if possible)
Feature request details
The src/content/text-detail/ko/ directory is missing 5 files compared to the English source:
- contact.mdx
- copyright.mdx
- download.mdx
- privacy-policy.mdx
- terms-of-use.mdx
I'd like to address this in two batches:
- First PR: contact, copyright, download (smaller pages, around 70 lines combined)
- Follow up PR: privacy policy and terms of use (larger legal text, around 500 lines combined)
This continues the Korean localization work from #1267 (Korean UI translations) and brings ko/ closer to parity with the hi/ directory which has 4 of 8.
I already have the first batch drafted locally and can open the PR as soon as this issue gets a go ahead.
Increasing Access
The text-detail pages (about, code-of-conduct, contact, copyright, donate, download, privacy-policy, terms-of-use) are the main info pages on the site. Korean currently only has 3 of 8 translated (about, code-of-conduct, donate), so Korean speaking users hit English when they click Download, Contact, or Copyright. So adding the missing Korean translations gets these pages to the same level of access Korean users already have for the About page.
Most appropriate sub-area of p5.js?
Other (specify if possible)
Feature request details
The src/content/text-detail/ko/ directory is missing 5 files compared to the English source:
I'd like to address this in two batches:
This continues the Korean localization work from #1267 (Korean UI translations) and brings ko/ closer to parity with the hi/ directory which has 4 of 8.
I already have the first batch drafted locally and can open the PR as soon as this issue gets a go ahead.