![virtaal translation editor virtaal translation editor](https://make.wordpress.org/polyglots/files/2019/05/new-editor-forms-1024x504.png)
To further add translations in your desired language, include the target language in the translate_package() call. Translate_package('potools') As a translator – generating a. # run from the directory into which potools is cloned, i.e., 'potools' here is a file path pot template can be used by translators to produce translations just running translate_package() on your package’s source will produce this file (or files, if your package has both R and C/C++ messages to translated), e.g. The primary feature of potools is the translate_package() function, which is designed to be your first & only stop for typical experience internationalizing a package As a developer – generating a. Translating your package interactively with translate_package() pot files it produces will be treated as UTF-8. The core function of potools, translate_package, is a one-stop-shop for interactively setting your package up for translation and providing those translations, all without ever having to touch a. Potools is designed to minimize the friction to translating your package by abstracting away as many details of the. mo binaries – another syntax rife with quirks and idiosyncrasies. Unfortunately, to do so has some tedious aspects, namely, learning the gettext system of. If the target audience of your package extends beyond the English-speaking world, or if you want to make the user experience for the non-native English speakers using your tools, you can consider internationalizing your package by translating its user-facing communications (verbose messages, warnings, errors, etc.). From Xiamen to Santiago, Addis Ababa to Tbilisi, Ogallala to Adelaide, R users are legion and their native languages are as well. README potools: Tools for Portability and Internationalization of R packages Overview