From f41a911703c477e6cb4fffde3b32b02b6ef0aad1 Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Fri, 16 Oct 2015 04:18:55 +0000 Subject: [PATCH] Add reports on PO translations and website CSS updates from wblock --- .../news/status/report-2015-07-2015-09.xml | 159 ++++++++++++++++++ 1 file changed, 159 insertions(+) diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml index c3b4495c43..02e1ada66b 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml @@ -1873,4 +1873,163 @@ + + PO Translation Project + + + + &os; Documentation Team + freebsd-doc@FreeBSD.org + + + + &os; Translators + freebsd-translators@FreeBSD.org + + + + + Warren + Block + + wblock@FreeBSD.org + + + + + PO + Translations + German + translation of the Leap Seconds article + Dutch + translation of the Explaining BSD article + &os; + Translators mailing list + + + +

The &os; documentation translation process has been in need + of modernization for quite some time. The existing process + was just too difficult for translators to keep translations up + to date.

+ +

With help from Benedict Reuschling, Shaun McCance, Ryan + Lortie, Hiroki Sato, and many others, the availability of a + new PO translation system was announced in August.

+ +

PO translations handle most of the overhead of the + translation process. Translators do not have to keep track of + commits to the upstream English version. The actual work of + translating is quicker and easier. PO editors show how much + of the document has been translated. If a translation is + already available for a given string, it can be easily + reused.

+ +

Early testing has been very successful. Most issues involve + discovering and documenting the new processes rather than + fixing bugs. New translations of English documents have + already been committed.

+ +

There will certainly be additional changes and improvements, + but the system works. We will continue to discover how to + share work between translation teams and the project as a + whole. This work will be much easier now that the initial + hurdle of being able to use PO software has been passed. +

+ + + + +

Continue testing. The system is new to us and there are + bound to be bugs and situations with unexpected results.

+ + + +

Improve documentation on using the new PO translations. + Much of this involves things that rarely happened with + the old system, like adding a completely new language + directory.

+ + + +

Add new translations for existing documents. There is much + less work to create and update a translated document + now. Existing and new translators are working on adding and + updating translations of the English documentation.

+ + + +

Figure out how to generate and share translation memory + with other members of a language team or translators outside + the team.

+ + + +

Test new PO editors like Pootle and Virtaal.

+ + + +

Determine a method to allow translators commit access for + translations.

+ + + +

Develop and test code to translate manual pages.

+ + + + + + Website CSS Update + + + + + Warren + Block + + wblock@FreeBSD.org + + + + + &os; Main Site + + + +

The &os; website has remained essentially unchanged in + appearance for many years. Like other legacy systems, it is + difficult to change. It is heavily used and therefore subject + to non-trivial bikeshedding.

+ +

The CSS shrunk the reader's font from the size they had + requested. It specified hardcoded font and object sizes in + pixels. On wide monitors, only the middle third of the screen + was used. Hardware has changed from what existed when + this version of the site was created. Screens have become larger + and wider, and increased in resolution at the same time.

+ +

It was time for a change. Font sizes were set to + percentages, with none smaller than 100%. The width of the + main box was changed to 90%. Other small adjustments were + added. These limited changes produced a rendered site that + better respects the reader's settings, is much easier to read, + and shows more information.

+ +

Although no content changed, the appearance was so different + that some viewers thought we had redesigned the site. It is + gratifying to know that so many people are using it. We would + also like to thank people for the response, which was + overwhelmingly positive and hardly bikesheddy at all.

+ + + + +

Fix other outdated assumptions in the CSS. + Alternately, rework the entire site. However, that is a much more + complex and ambitious project than it might seem.

+ + + +