Merge branch 'processing:main' into save-frames-doc-update

.all-contributorsrc

@@ -3059,6 +3059,15 @@
       "contributions": [
         "doc"
       ]
+    },
+    {
+      "login": "tapioca24",
+      "name": "tapioca24",
+      "avatar_url": "https://avatars.githubusercontent.com/u/12683107?v=4",
+      "profile": "https://github.com/tapioca24",
+      "contributions": [
+        "plugin"
+      ]
     }
   ],
   "repoType": "github",

README.md

@@ -562,6 +562,7 @@ We recognize all types of contributions. This project follows the [all-contribut
     <td align="center"><a href="https://github.com/smilee"><img src="https://avatars.githubusercontent.com/u/5793796?v=4?s=100" width="100px;" alt=""/><br /><sub><b>smilee</b></sub></a><br /><a href="https://github.com/processing/p5.js/commits?author=smilee" title="Code">💻</a></td>
     <td align="center"><a href="https://github.com/CommanderRoot"><img src="https://avatars.githubusercontent.com/u/4395417?v=4?s=100" width="100px;" alt=""/><br /><sub><b>CommanderRoot</b></sub></a><br /><a href="https://github.com/processing/p5.js/commits?author=CommanderRoot" title="Code">💻</a></td>
     <td align="center"><a href="http://philipbell.org"><img src="https://avatars.githubusercontent.com/u/3860311?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Philip Bell</b></sub></a><br /><a href="https://github.com/processing/p5.js/commits?author=processprocess" title="Documentation">📖</a></td>
+    <td align="center"><a href="https://github.com/tapioca24"><img src="https://avatars.githubusercontent.com/u/12683107?v=4?s=100" width="100px;" alt=""/><br /><sub><b>tapioca24</b></sub></a><br /><a href="#plugin-tapioca24" title="Plugin/utility libraries">🔌</a></td>
   </tr>
 </table>
 

contributor_docs/friendly_error_system.md

@@ -6,15 +6,24 @@ The Friendly Error System (FES, 🌸) aims to help new programmers by providing
 
 The FES prints messages in the console window, as seen in the [p5.js Web Editor] and your browser JavaScript console. The single minified file of p5 (p5.min.js) omits the FES.
 
- *We have an ongoing survey!* Please take a moment to fill out this 5-minute survey to help us improve the FES: [🌸 SURVEY 🌸]
-
 [p5.js Web Editor]: https://editor.p5js.org/
-[🌸 SURVEY 🌸]: https://bit.ly/p5fesSurvey
 
+## Lowering the Barriers to Debugging
+The design of a tool should match the need of the people who will use it. As a tool that aims to lower the barriers to debugging, the design of FES is no exception.
+
+The best way to evaluate our existing design is to hear directly from people using p5.js. We ran a community survey in 2021 to gather feedback and future wishes for Friendly Errors.
+
+We believe the insights from our community members will be helpful for our contributors. You can see the results through the summary comic or the full report:
+* [21-22 FES Survey Report Comic]
+* [21-22 FES Survey Full Report]
+
+
+[21-22 FES Survey Report Comic]: https://almchung.github.io/p5jsFESsurvey/
+[21-22 FES Survey Full Report]: https://observablehq.com/@almchung/p5-fes-21-survey
 
 ## Writing Friendly Error Messages
 
-In this section, we will describe how you can contribute to the p5.js library by writing and translating error messages.
+How to contribute to the p5.js library by writing and translating error messages?
 
 The FES is a part of the p5.js' [internationalization] effort. We generate all FES messages' content through [i18next]-based `translator()` function. This dynamic error message generation happens for all languages, including English - the default language of the p5.js.
 
@@ -26,21 +35,24 @@ We welcome contributions from all around the world! 🌐
 
 #### Writing Best Practices
 
-FES message writers should prioritize lowering the barrier of understanding error messages and debugging.
+FES message writers should prioritize lowering the barrier of understanding error messages and increasing the accessibility of debugging process.
 
-Here are some highlights from our upcoming best-practice doc:
+[Friendly Errors i18n Book] discusses challenges and best practices for writing friendly error messages within the cross-cultural i18n context. Here are some points from the book:
 
-* Use simple sentences. Consider breaking your sentence into smaller blocks for best utilizing i18next's [interpolation] feature.
-* Keep the language friendly and inclusive. Look for possible bias and harm in your language. Adhere to [p5.js Code of Conduct].
-* Avoid using figures of speech. Prioritize cross-cultural communication.
-* Try to spot possible "[expert blind spots]" in an error message and its related docs.
-* Introduce one technical concept or term at a time—link one external resource written in a beginner-friendly language with plenty of short, practical examples.
+* Understand your audience: do not make assumptions about the audience of our error messages. Try to learn who is using our library and how they use it.
+* Keep language inclusive. We strive to make error messages "friendly," what does it mean for you? Look for possible bias and harm in your language. Adhere to [p5.js Code of Conduct].
+* Use simple sentences whenever possible. Consider breaking your sentence into smaller blocks for best utilizing i18next's [interpolation] feature.
+* Prioritize cross-cultural communication and provide a great experience across languages. Avoid using figures of speech.
+* Introduce one technical concept or technical term at a time. Keep consistency in technical writing. Try to link one external resource written in a beginner-friendly language with plenty of short, practical examples.
 
+[Friendly Errors i18n Book]: https://almchung.github.io/p5-fes-i18n-book/
 [interpolation]: https://www.i18next.com/translation-function/interpolation
 [p5.js Code of Conduct]: https://github.com/processing/p5.js/blob/main/CODE_OF_CONDUCT.md#p5js-code-of-conduct
 [expert blind spots]: https://tilt.colostate.edu/TipsAndGuides/Tip/181
 
+[Friendly Errors i18n Book] is a public project, and you can contribute to the book through this separate [repo].
 
+[repo]: https://github.com/almchung/p5-fes-i18n-book
 #### Location of Translation Files
 
 `translator()` is based on i18next and imported from `src/core/internationalization.js`. It generates messages by looking up text data from a JSON translation file:

translations/ko/README.md

@@ -1,15 +1,26 @@
 # Welcome to the FES Korean branch!
 안녕하세요, FES 한국어 브랜치에 어서오세요!
 
-## 한국어 Translation Credits
+## 한국어 공동 번역 기여자 Korean Translation Credits
 2021년 가을부터 공동작업으로 진행되어 2022년 1월에 마무리된 FES 에러메시지 공동 번역 작업은 아래 분들이 함께하셨습니다.
 * [염인화](https://yinhwa.art/) (Inhwa Yeom): artist/XR researcher based in South Korea. (Take a look at her works on [p5 for 50+](https://p5for50.plus/) ([Processing Foundation Fellows 2020](https://medium.com/processing-foundation/p5-js-for-ages-50-in-korea-50d47b5927fb)) and p5js website Korean translation)
 * 전유진 (Youjin Jeon): artist/organizer based in Seoul, South Korea. [여성을 위한 열린 기술랩(Woman Open Tech Lab.kr)](http://womanopentechlab.kr/) and [Seoul Express](http://seoulexpress.kr/)
 * [정앎](https://www.almichu.com/) (Alm Chung, organizer): Korean-American artist/researcher based in Seattle, WA.
 * 이지현 (Jihyun Lee): Korean publishing editor based in South Korea
 
-## 한국어 Translation Resources
-* 추후 추가될 예정입니다!
+## 영한 번역 리소스 (Korean-English Translation Resources)
+* 영한 [번역에 도움이 되는 툴과 유의점들]입니다.
+* 또한 영한 [번역 작업 중 마주치는 딜레마들] 속에서 저희가 채택한 방식을 모아 적어봤습니다.
+* 외래 [기술 용어 다루기]에 대한 논의입니다.
+* p5js 웹사이트와 기술 문서에서 사용하는 기술 용어들을 통일하기위해 사용하고 있  [p5js.org/ko 기술 용어 색인] 입니다.
+* 현존하는 검색툴/번역 툴들과 연계 가능한 "[사이를 맴도는]" 번역문에 대해 생각해보는 글입니다.
 
+이 외에도 FES의 세계화 작업 과정, 그리고 과정 중 논의된 이슈들을 [Friendly Errors i18n Book ✎ 친절한 오류 메시지 세계화 가이드북]에서 읽어보실 수 있습니다. "친절한 오류 메시지 세계화 가이드북"은 오픈 소스 프로젝트이며, 이 [독립된 레파지토리 (repository)]를 통해 기여 가능합니다.
 
-질문이나 건의 사항은 @almchung 에게 문의주시길 바랍니다.
+
+[번역에 도움이 되는 툴과 유의점들]: https://almchung.github.io/p5-fes-i18n-book/ch4/#tools
+[번역 작업 중 마주치는 딜레마들]: https://almchung.github.io/p5-fes-i18n-book/ch4/#dilemmas
+[기술 용어 다루기]: https://almchung.github.io/p5-fes-i18n-book/ch3/
+[사이를 맴도는]: https://almchung.github.io/p5-fes-i18n-book/ch5/
+[Friendly Errors i18n Book ✎ 친절한 오류 메시지 세계화 가이드북]: https://almchung.github.io/p5-fes-i18n-book/
+[독립된 레파지토리 (repository)]: https://github.com/almchung/p5-fes-i18n-book