An object model for source text and translations. Find and extract translatable strings. Provide translations and seamlessly retrieve them at runtime.
R relies on GNU gettext
to
produce multi-lingual messages (if Native Language Support is
enabled). This is well-designed software offering an extensive set of
functionalities. It is ubiquitous and has withstood the test of time. It
is not the objective of transltr
to (fully) replace
it.
Package transltr
provides an alternative in-memory
object model (and further functions) to easily inspect and manipulate
source text and translations.
✅ It does not change any aspect of the underlying locale.
✅ It has its own data serialization formats for I/O purposes. Source text and translations can be exported to text formats that are sharable and easily modifiable, even by non-technical collaborators.
✅ Its features are extensively documented (even internal ones).
✅ It can always locate and extract translatable strings (litteral
character vectors passed to translate()
). They are treated
as regular R objects.
translate()
works everywhere, including in calls to
stop()
, warning()
,
and message()
.
Install the package from your preferred CRAN mirror.
install.packages("transltr")
While an extensive set of unit tests fully covers the current version
of transltr
, some features could be modified in the future.
Treat it as a beta version until version 1.0.0
is
released.
Write code as you normally would. Whenever a piece of text
(a literal character vector) must be available in multiple languages,
wrap it with translate()
.
Once you are ready to work on translating your project,
call find_source()
. This returns
a Translator
object.
Export the Translator
object
with translator_write()
. Fill in the underlying translation
files.
Import translations back into an R session
with translator_read()
.
Current language and source language are respectively set
with language_set()
and language_source_get()
.
By default, the latter is set equal to "en"
(English).
You may submit bugs, request features, and provide feedback by creating an issue on GitHub.
Warm thanks to Jérôme Lavoué, who gladly supported and sponsored the first release of this project.