Skip to content

Add Korean translations for intro-to-p5-strands.mdx#1357

Open
eupthere wants to merge 2 commits intoprocessing:2.0from
eupthere:intro-to-p5-strands-ko
Open

Add Korean translations for intro-to-p5-strands.mdx#1357
eupthere wants to merge 2 commits intoprocessing:2.0from
eupthere:intro-to-p5-strands-ko

Conversation

@eupthere
Copy link
Copy Markdown
Contributor

  • added src/content/tutorials/ko/intro-to-p5-strands.mdx for Korean translation

resolves #1356

@eupthere eupthere changed the title Add intro to p5.strands tutorial in Korean Add Korean translations for intro-to-p5-strands.mdx Apr 23, 2026
@ksen0
Copy link
Copy Markdown
Member

ksen0 commented Apr 27, 2026

Thanks @eupthere ! It would be great to get at least one volunteer review on this one before merging. We can post it on social media this week to ask for help, but please feel free to find others who could review as well:)

For any volunteer reviewers: you can check the original tutorial this translates here. Please also check out #1360 if you have time! Thanks so much!

Copy link
Copy Markdown

@sosunnyproject sosunnyproject left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed up to line 370. Please feel free to wait before you make changes, until someone else or I review the rest of the page -- so that you can edit at once without the hassle of too many back and forth.

Great job and thanks for starting the translation!
I will try to review the rest within few days. If you're a reviewer, please feel free to start after line 370.

Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated

셰이더는 WebGL에서 GLSL 같은 특수 언어로 작성하는 GPU 프로그램입니다. 크게 두 종류가 있습니다:
- **정점 셰이더:** 도형의 꼭짓점을 변형합니다 (어디에 그릴지)
- **프래그먼트 셰이더:** 각 픽셀의 색을 결정합니다 (어떻게 그릴지)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be a good idea to follow the original writing's style (e.g., bold or italic) on specific words when you can: 어디에, 어떻게

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed at 1881562

nit: I tend to avoid italic for Korean, because Korean fonts do not really support it. The glyphs get slanted algorithmically, and this usually leads to awkward typographic look. Maybe we could instead use bold, 겹낫표(『』), 낫표(「」)?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll merge this one as is but @eupthere that seems like the sort of thing that belongs with a list of language specific formatting/vocabulary notes? The one in #1376

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ksen0 I will add it once @Nwakaego-Ego drafts the reorganization PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

http://koreantypography.org/wp-content/uploads/thesis/kst_j9_3.pdf

Also, for anyone interested in this topic, here is a good paper addressing this typographic issue

Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
Comment thread src/content/tutorials/ko/intro-to-p5-strands.mdx Outdated
@eupthere
Copy link
Copy Markdown
Contributor Author

eupthere commented May 5, 2026

@sosunnyproject Thanks for the review!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants