Website Translation

KDE websites are written in a variety of formats: Markdown (with Hugo shortcodes), reStructuredText (as Sphinx websites), or others. Regardless of the format, websites available for translation are all set up to be translated via the same PO file format as GUI and Doc translation.

Each website has a project, for example website-kde-org for the https://kde.org website. Websites all go into the trunk-kf5 branch instead of kf6. You may work on website translations almost exactly as you would with GUI translations.

Things to watch out

• You will have to figure out yourself what the input format is, and try to match it.

• If you see things like {{< alert color="info" >}}, that is a Hugo shortcode which should be left as-is. If the shortcode closing tag like {{< /alert >}} is in the source text, please ensure that it is also present in the right format in the translated text. This is not automatically checked for, so if an incorrect shortcode is committed, the string will actually be synchronized into the website and then cause it to fail to build.

• Many languages delimit words with spaces, but some don't. Both Sphinx's reStructuredText and Hugo's Markdown may require special escaping if you need to not have spaces around pieces of syntax:

  • In reStructuredText, you can escape a space like \ to make it act as a delimiter for syntaxes while not actually emitting a space.
  • In Hugo, **foo**bar may end up rendering as **foo**bar instead of foobar. If you find this is happening, you may try using an escaped space \ just like in reStructuredText, or fall back to using HTML tags like <strong> for ** or <em> for *.

---

Article contributed by Kisaragi Hiu under the GFDL-1.2-or-later license.