General

Even when the website for Apache OpenOffice looks like that everything is in a single place, the website is separated into a content part (mainly the text in HTML and MD files) and an asset part (for graphics, CSS, JavaScript).

When it should be translated, then both parts have to be considered.

The website is separated into 3 sections:

Text is managed dynamically

Parts of the header and the complete footer is not designed for translation, so it stays as it is.

Preferred parts are - of course the main page (index.html), download and why. But also the other pages can be translated.

To work with data that can be changed dynamically (e.g., when new releases happen), some parts are only working when HTML and JavaScript parts are translated together.

Example for variable / value

The content on https://www.openoffice.org/xx/download/ is coming from https://www.openoffice.org/xx/download/msg_prop_l10n_xx.js.

Every text has 2 parts: A variable and its actual value.

Variable "l10n.dl_green_box_headline_text" and value "Download Apache OpenOffice". There are some control characters like sum (=) and the semicolon (;). Please ensure not to delete or change them. Otherwise, unforeseen problems can happen.

Note: All Graphics are representations of the variables they are describing, and may not include all possibilities.

There are special things like the content of the drop-down-boxes for languages on https://www.openoffice.org/xx/download/ which is also coming from https://www.openoffice.org/xx/download/msg_prop_l10n_xx.js.

Every list item has 3 parts: A variable and its actual value.

Variable" l10n.dl_green_box_select_box_lang_values_custom" it's items for value, visible text and tooltip.

Example for hard-coded text

However, not every text can be managed with JavaScript. Especially when JavaScript is no option, it has to be hard-coded in the HTML files. You can see the difference when you browse the webpages with enabled and disabled JavaScript in your web browser.

The text string "I want to learn more about OpenOffice" on the main page is actually in the HTML file itself.

Template

There is a template to look at:

https://www.openoffice.org/xx/

Here you have a visual example which areas can be translated and where specific text parts can be found.

What to do when translating the ... ?

The strings on the following webpages need to be translated.

Main page

https://www.openoffice.org/xx/index.html

Which parts?

• The 6 navigation boxes, from "I want to learn more about OpenOffice" down to "I want to stay in touch with OpenOffice".
• The right part with "Recent Blog Posts" and "Recent News" is optional.

Note: The portions to the right of the red line are the optional part.

Header on the page

These text parts just have to be translated only once to be shown on all webpages.

They can be found in: brand.md and topnav.md.

Which parts?

• The label text for the "Search" button.
• The label text for the language switcher (Note: The items in the drop-down-list cannot be translated).
• The slogan "The Free and Open Productivity Suite".
• The text for the newest release, "Released: Apache OpenOffice X.Y.Z".
• The link can be customized, too. Here it's needed to translate the release notes for the respective release.
• The links in the colored line.

TODO

Visualize with a screenshot.

Download page

https://www.openoffice.org/xx/download/index.html

Which parts?

• Every text parts in the green, light-green, blue, light-blue boxes. Incl. the text in the drop-down-boxes, links and icons.
• Every link in the navigation part on the right.

TODO

Visualize with a screenshot.

Subpage

Important hints for the chosen platform

https://www.openoffice.org/xx/download/platform_hints.html

Which parts?

• All text.

TODO

Visualize with a screenshot.

Why and its subpages

https://www.openoffice.org/xx/why/index.html

Which parts?

• Every text on the index page.
• Every text on each subpages that can be reached via the links.

TODO

Visualize with a screenshot.