Joel H. Nitta Source on GitHub: https://github.com/joelnitta/carp-i18n-guide Preface As of writing (2024-02), there is no official support for translation of The Carpentries materials. This unofficial guide is a work in progress based on using Crowdin as the translation platform for lessons written using the Workbench format. Another system by David Pérez-Suárez for translating Carpentries lessons in the "Styles" lesson format using Transifex is no longer being maintained. Concepts i18n: Stands for "internationalization", the process of maintaining a technical framework to support translation. Does not require knowledge of the target language, but does require technical knowledge. l10n: Stands for "localization", the process of translating strings into a different language and cultural context. Does require knowledge of the target language/culture, but does not require technical knowledge.

Info website COC 「2024年2月版 LLM情報アップデート」 久米慧嗣 Satoshi Kume (@skume) OpenAI to release Text to Video generative AI

Local rendering of Ukrainian git-novice In R, install {sandpaper}: options(repos = c( carpentries = "https://carpentries.r-universe.dev/", CRAN = "https://cran.rstudio.com/" )) install.packages("sandpaper", dep = TRUE) Also install {dovetail}, which is used for building the translated website:

100 + people engaged so far googlegroups seems to work fine in China (at least people received/sent emails ok) Format/template for proposalsJoel has a draft template in place in the issue functionality in github Capturing discussion, maintaining in perpetuity Need a format that won't disappearCould use the github "issue" tracking functionality. Any user with a github account can comment on each proposal (each issue). Need some instructions for the discussion? Maybe it'll work ok without guidance This format wouldn't work well for actually voting, in part because anyone could vote--it wouldn't be restricted to PPG For PPG members who are averse to git, someone else could make comments on their part