Document how to add additional localization packages
Blocks Tails -
#5 Updated by sajolida 2019-05-14 17:43:17
- Assignee deleted (
Here is my plan.
In order to be task-oriented, we should document how to install Thunderbird language packs in /doc/anonymous_internet/thunderbird.
For example, we could have a section called “Using Thunderbird in your language” (or something like that) at the bottom of the page.
In the release notes for 3.13.2 I wrote about “localization packages”. Actually, I’m afraid that most users won’t know what “localization” refers to while “translate” would be more common. Thunderbird talks about “language packs” (on the Thunderbird website) and about “language package” (in the Debian packages). The Libre Office packages talk about “language packages” so we might use that to be consistent.
Each such section would be super brief, something like:
To use Thunderbird in your language, you can install the <span class="command">thunderbird-l10n-<span class="command-placeholder">lang</span></span> package using the [[Additional Software|doc/first_steps/additional_software]] feature. Replace lang with the code for your language, for example, es for Spanish.
In addition, it would also be nice to start building a list of useful additional software on /doc/first_steps/additional_software. It could be a new section called “Example of useful additional software” (or something like that) between “Being careful about what you install” and “Installing additional software”.
It could have sections by type of packages and maybe something like:
# Language packs - For Libre Office: libreoffice-l10n-lang - For Thunderbird: thunderbird-l10n-lang Replace lang with the code for your language, for example, es for Spanish. # Spell-checking dictionaries - hunspell-lang Replace lang with the code for your language, for example, es for Spanish. The hunspell dictionaries are used for spell-checking by Tor Browser, Libre Office, Thunderbird, and many other applications.
@cbrownstein What do you think? Do you see anything else worth documenting? Then I propose that whoever wants to work on implementing this assign this ticket to him right when they start writing a branch.
#7 Updated by cbrownstein 2019-05-20 03:47:04
- Assignee changed from cbrownstein to sajolida
- QA Check set to Ready for QA
Here’s a branch: