Date: Fri, 16 Oct 2015 04:18:55 +0000 (UTC) From: Benjamin Kaduk <bjk@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r47592 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201510160418.t9G4It3S069593@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: bjk Date: Fri Oct 16 04:18:55 2015 New Revision: 47592 URL: https://svnweb.freebsd.org/changeset/doc/47592 Log: Add reports on PO translations and website CSS updates from wblock Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Fri Oct 16 03:44:54 2015 (r47591) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Fri Oct 16 04:18:55 2015 (r47592) @@ -1873,4 +1873,163 @@ </help> </project> + <project cat='doc'> + <title>PO Translation Project</title> + + <contact> + <person> + <name>&os; Documentation Team</name> + <email>freebsd-doc@FreeBSD.org</email> + </person> + + <person> + <name>&os; Translators</name> + <email>freebsd-translators@FreeBSD.org</email> + </person> + + <person> + <name> + <given>Warren</given> + <common>Block</common> + </name> + <email>wblock@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/po-translations.html">PO + Translations</url> + <url href="https://www.FreeBSD.org/doc/de_DE.ISO8859-1/articles/leap-seconds/">German + translation of the Leap Seconds article</url> + <url href="https://www.FreeBSD.org/doc/nl_NL.ISO8859-1/articles/explaining-bsd/">Dutch + translation of the Explaining BSD article</url> + <url href="https://lists.FreeBSD.org/pipermail/freebsd-translators/">&os; + Translators mailing list</url> + </links> + + <body> + <p>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.</p> + + <p>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.</p> + + <p>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.</p> + + <p>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.</p> + + <p>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. + </p> + </body> + + <help> + <task> + <p>Continue testing. The system is new to us and there are + bound to be bugs and situations with unexpected results.</p> + </task> + + <task> + <p>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.</p> + </task> + + <task> + <p>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.</p> + </task> + + <task> + <p>Figure out how to generate and share translation memory + with other members of a language team or translators outside + the team.</p> + </task> + + <task> + <p>Test new PO editors like Pootle and Virtaal.</p> + </task> + + <task> + <p>Determine a method to allow translators commit access for + translations.</p> + </task> + + <task> + <p>Develop and test code to translate manual pages.</p> + </task> + </help> + </project> + + <project cat='doc'> + <title>Website CSS Update</title> + + <contact> + <person> + <name> + <given>Warren</given> + <common>Block</common> + </name> + <email>wblock@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://www.FreeBSD.org/">&os; Main Site</url> + </links> + + <body> + <p>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.</p> + + <p>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.</p> + + <p>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.</p> + + <p>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.</p> + </body> + + <help> + <task> + <p>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.</p> + </task> + </help> + </project> + </report>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201510160418.t9G4It3S069593>