lbwww/site/news/translations.md

71 lines
2.8 KiB
Markdown
Raw Normal View History

% Translations wanted
2021-12-11 10:03:42 +00:00
% Leah Rowe
2022-11-13 21:12:15 +00:00
% 4 January 2022
2021-12-11 10:03:42 +00:00
The libreboot website is currently only available in English.
2021-12-11 10:03:42 +00:00
2021-12-11 10:06:15 +00:00
I've recently added support for translations to
2021-12-11 10:03:42 +00:00
the [Untitled Static Site Generator](https://untitled.vimuser.org/), which the
libreboot website uses. Pages on libreboot.org are written in Markdown, and
2021-12-11 10:03:42 +00:00
this software generates HTML pages.
This very page that you are reading was created this way!
2021-12-11 10:06:15 +00:00
Getting started
===============
The libreboot website is available, in Markdown, from a Git repository:\
<https://notabug.org/libreboot/osbwww>
2021-12-11 10:03:42 +00:00
Instructions for how to send patches are available here:\
<https://libreboot.org/git.html>
2021-12-11 10:03:42 +00:00
2022-11-13 21:12:15 +00:00
If you're working on a translation, make note of the commit ID from `osbwww.git`
2021-12-11 10:03:42 +00:00
and keep track of further changes (to the English website) in that repository.
2022-11-13 21:12:15 +00:00
When you send the translation, please specify what commit ID in `osbwww.git` it
2021-12-11 10:03:42 +00:00
is up to date with. From then on, I will keep track of changes to the English
website, which is what I work on. My native language is English. When the first
translation is made available on libreboot.org, I will create a new page (in
2021-12-11 10:03:42 +00:00
English only), and add notes to it whenever I make site changes, and show
where these changes need to then be performed in translated versions of each
page that I change.
How to translate libreboot.org
2021-12-11 10:03:42 +00:00
==============================
The documentation on <https://untitled.vimuser.org/> tells you how to handle
translations.
I recommend that you set up a local Nginx HTTP server on your computer, and
configure Untitled for it, using the instructions on the Untitled website. This
will make it easier to see what your translated website looks like, before it
goes live.
2021-12-11 10:25:30 +00:00
**It is recommended that you install a firewall, if you're running Nginx,
unless you actually want it to be publicly accessible. The `ufw` software is
quite nice:**
sudo apt-get install ufw
sudo ufw enable
This will block all unsolicited incoming traffic. It's good practise anyway,
for workstations. You don't have to use ufw, but it's a nice frontend for
iptables/ip6tables on systems that use the Linux kernel. More information
about `ufw` available here:
<https://help.ubuntu.com/community/UFW>
When viewing your local website, you can just type `http://localhost/` in your
browser. This will resolve to your local loopback address.
2021-12-11 11:10:20 +00:00
In general, you will be working with `md` files and `include` files.
2021-12-11 10:03:42 +00:00
Keep an eye out for files with `template`, `footer` and `nav` in the name.
More information about how Untitled works is available on the Untitled
website. You should also add a translated `strings.cfg` file to Untitled, for
your translation, if Untitled doesn't support it.
You can add pages in any language to Untitled. The software automatically
generates language selection menus, on a per-page basis, when a translation is
available for a given page.