svn commit: r1043390 - in /websites/staging/openoffice/trunk/content: ./ website-native.html

[bu...@apache.org]

Author: buildbot
Date: Tue Apr  9 11:57:41 2019
New Revision: 1043390

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/website-native.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr  9 11:57:41 2019
@@ -1 +1 @@
-1857142
+1857179

Modified: websites/staging/openoffice/trunk/content/website-native.html
==============================================================================
--- websites/staging/openoffice/trunk/content/website-native.html (original)
+++ websites/staging/openoffice/trunk/content/website-native.html Tue Apr  9 11:57:41 2019
@@ -129,15 +129,15 @@ h2:hover > .headerlink, h3:hover > .head
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h2 id="native-language-nl-websites">Native Language (NL) Websites<a class="headerlink" href="#native-language-nl-websites" title="Permanent link">&para;</a></h2>
 <p>Apache OpenOffice supports users around the world via our many OpenOffice localizations, via
-native language mailing lists and support forums, and by translations of our website. This 
+native language mailing lists and support forums, and by translations of our website. This
 page describes the steps to create and maintain an NL website. Following these steps you
-can create a website translation like our <a href="https://www.openoffice.org/es/">Spanish</a>, 
-<a href="https://www.openoffice.org/tr/">Turkish</a> or <a href="https://www.openoffice.org/nl/">Dutch</a> websites. </p>
-<p>Making updates to the Apache OpenOffice project's websites is simple. It's even easy 
-for non-committers (new contributors - like you) to create a patch to request that 
+can create a website translation like our <a href="https://www.openoffice.org/es/">Spanish</a>,
+<a href="https://www.openoffice.org/tr/">Turkish</a> or <a href="https://www.openoffice.org/nl/">Dutch</a> websites.</p>
+<p>Making updates to the Apache OpenOffice project's websites is simple. It's even easy
+for non-committers (new contributors - like you) to create a patch to request that
 pages are updated by the project community.</p>
 <h2 id="the-xx-website">The XX Website<a class="headerlink" href="#the-xx-website" title="Permanent link">&para;</a></h2>
-<p>The easiest way to get started is with the <a href="https://www.openoffice.org/xx/">XX website</a>.This 
+<p>The easiest way to get started is with the <a href="https://www.openoffice.org/xx/">XX website</a>.This
 website is a extract of the most-commonly visited pages from the English website, including:</p>
 <ul>
 <li>The home page</li>
@@ -146,11 +146,11 @@ website is a extract of the most-commonl
 <li>The download page</li>
 <li>The support information pages</li>
 </ul>
-<p>Altogether, there are around 30 pages in the XX website. These are the ones that you will 
+<p>Altogether, there are around 30 pages in the XX website. These are the ones that you will
 want to translate.</p>
 <h2 id="creating-the-test-directory">Creating the Test Directory<a class="headerlink" href="#creating-the-test-directory" title="Permanent link">&para;</a></h2>
 <p>In many cases there will already be an NL website for your language, but perhaps one that is
-badly out-of-date or is non-standard. However, until your new translation is ready to go it 
+badly out-of-date or is non-standard. However, until your new translation is ready to go it
 is probably best not to wipe out the existing NL page. So initially you will probably want
 to do your work in a test directory.</p>
 <p><strong>Let's take a concrete example:</strong>
@@ -177,7 +177,7 @@ to do an "svn export" of the new /test-i
 In any case, the complete "/xx" directory and its files are used as a template.
 Please always copy it to a different location first before you start any editing!</p>
 <h2 id="translating-the-website">Translating the Website<a class="headerlink" href="#translating-the-website" title="Permanent link">&para;</a></h2>
-<p>The files will be in two main formats: </p>
+<p>The files will be in two main formats:</p>
 <ol>
 <li>HTML files.</li>
 <li>Markdown text files.
@@ -225,7 +225,7 @@ a the separate Javascript file "msg_prop
 the variables. Look for the further section if you need more help on this.</li>
 <li>It is easy to miss the social networking messages in /download/index.html.
 These are in the HTML header block and in function shareTwitter(). The string is something
-like "Join the OpenOffice revolution, the free office productivity suite with over 225
+like "Join the OpenOffice revolution, the free office productivity suite with over 260
 million trusted downloads."
 You should translate these, but adapt if needed to keep the Twitter string within the 140
 limit for Twitter.</li>