Skip to content

Add translations for Korean#857

Open
scientificpythontranslations wants to merge 1 commit into
numpy:mainfrom
scientificpythontranslations:add/translations-ko
Open

Add translations for Korean#857
scientificpythontranslations wants to merge 1 commit into
numpy:mainfrom
scientificpythontranslations:add/translations-ko

Conversation

@scientificpythontranslations
Copy link
Copy Markdown
Contributor

This PR adds the translations for Korean to the project.

This PR was automatically created by the @scientificpythontranslations bot and only commits that resolve any merge conflicts should be pushed directly to this branch/PR. Any modifications of the translated content should be addressed directly on the Crowdin Project Site.

The Crowdin integration for this repository is located at https://github.com/Scientific-Python-Translations/numpy.org-translations.

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 28, 2025

Deploy Preview for numpy-org ready!

Name Link
🔨 Latest commit 57a96e7
🔍 Latest deploy log https://app.netlify.com/sites/numpy-org/deploys/680fbe916c19e80008eb1423
😎 Deploy Preview https://deploy-preview-857--numpy-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@kangwonlee
Copy link
Copy Markdown

Hi @melissawm @steppi @goanpeca,

Korean translations on Crowdin are now at 100% progress. The final ~5% (concentrated in install.md, news.md, and a few names in about.md / teams/index.md) was just completed.

Sync request: The Sync Translations workflow on scientific-python-translations/numpy.org-translations has its cron schedule commented out and last ran 2025-05-01. Could one of you trigger a manual workflow_dispatch so the new ko strings propagate to this PR's add/translations-ko branch?

Acknowledgements: Carrying this over the line was only possible thanks to the contributors who built up the foundational ~95% over the past several years. Sincere thanks to:

Note: @archsyscall isn't currently in translators.yml under ko: despite being the foundational contributor. Happy to send a small PR to numpy.org-translations adding him before this merges, so he appears on the auto-rendered numpy.org/ko/teams/translations-team page.

Methodology disclosure: This proofreading pass was completed in an LLM-assisted session (Anthropic's Claude, Opus 4.7). The LLM was used to: (a) run corpus-frequency analysis across the existing ko translations to derive canonical terminology (e.g., 배포 for "release", keeping European maintainer names in Latin); (b) flag subtle mistranslations such as the obligation vs expectation distinction for "should" (e.g., 해야 합니다할 것입니다 for "this should print X"); (c) drive the Crowdin editor under my direction to commit each row. Every terminology decision and each per-string save was reviewed and approved by me as the credentialed proofreader — the LLM did not generate new translations autonomously. The methodology and a glossary of locked-in terminology decisions is available on request.

I'll also separately open a small PR against numpy/numpy.org adding the ko: block to config.yaml.in so Hugo builds the /ko/ pages once this merges.

Thanks again to everyone — and to the tooling — for getting us here.

@melissawm
Copy link
Copy Markdown
Member

Thank you @kangwonlee for the effort and for the detailed description (including LLM use disclosure) above, much appreciated!

The sync issue is known and I'm trying to fix it asap, will ping you once I get it right on the crowdin side.

Yes please for the PR to add @archsyscall - since the translations workflow moved projects within crowdin at one point, this information may have been lost in the transition. Thanks for noticing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants