You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2013/10/08 23:08:14 UTC
svn commit: r881760 - in /websites/staging/openoffice/trunk/content: ./
website-native.html
Author: buildbot
Date: Tue Oct 8 21:08:14 2013
New Revision: 881760
Log:
Staging update by buildbot for openoffice
Added:
websites/staging/openoffice/trunk/content/website-native.html
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Oct 8 21:08:14 2013
@@ -1 +1 @@
-1529029
+1530424
Added: websites/staging/openoffice/trunk/content/website-native.html
==============================================================================
--- websites/staging/openoffice/trunk/content/website-native.html (added)
+++ websites/staging/openoffice/trunk/content/website-native.html Tue Oct 8 21:08:14 2013
@@ -0,0 +1,235 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+<meta name="google-site-verification" content="wIHUbgA-JO5PaJHpR5jeI8N9E2y2iF94o4oUwpaAdk8" />
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
+<script type="text/javascript">
+
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-30193653-3']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+
+</script>
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice" href="http://openoffice.apache.org/">
+ <img id="logo" alt="Apache OpenOffice" src="http://www.openoffice.org/images/AOO_logos/AOO4_website_logo.png"/></a></div>
+
+ <div id="bannercenter"><br/> The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="sidenav">
+ <h1 id="general">General</h1>
+<ul>
+<li><a href="/index.html">About</a></li>
+<li><a href="/downloads.html">Downloads</a></li>
+<li><a href="/license.html">License</a></li>
+<li><a href="/trademarks.html">Trademarks</a></li>
+<li><a href="/press.html">Press</a></li>
+<li><a href="http://www.openoffice.org/">OpenOffice.org website</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/get-involved.html">Get Involved</a></li>
+<li><a href="/orientation/index.html">Orientation</a></li>
+<li><a href="/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/social.html">Social Networking</a></li>
+<li><a href="/events.html">Events</a></li>
+<li><a href="http://www.openoffice.org/support/">Support</a></li>
+<li><a href="/native-lang.html">Native Language</a></li>
+<li><a href="https://cwiki.apache.org/confluence/display/OOOUSERS/">Planning Wiki</a></li>
+<li><a href="/people.html">People</a></li>
+<li><a href="/community-faqs.html">Community FAQs</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/source.html">Source Code</a></li>
+<li><a href="/bug-tracking.html">Bug Tracking</a></li>
+<li><a href="/qa.html">Quality Assurance</a></li>
+<li><a href="/translate.html">Translation</a></li>
+<li><a href="/website-local.html">Website</a></li>
+<li><a href="/security.html">Security Reports</a></li>
+<li><a href="/contributing-code.html">Contributing Code</a> </li>
+<li><a href="/developer-faqs.html">Developer FAQs</a></li>
+</ul>
+<h1 id="project-management-pmc">Project Management PMC</h1>
+<ul>
+<li><a href="http://blogs.apache.org/OOo/">Project Blog</a></li>
+<li><a href="/pmc-faqs.html">PMC FAQs</a> </li>
+</ul>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<ul>
+<li><a href="http://www.apache.org/">Website</a></li>
+<li><a href="http://www.apache.org/foundation/contributing.html">Donations</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+</ul>
+ </div>
+ <div id="contenta">
+
+
+ <h2 id="native-language-nl-websites">Native Language (NL) Websites</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
+page describes the steps to create and maintain an NL website. Following these steps you
+can create a website translation like our <a href="http://www.openoffice.org/es">Spanish</a>,
+<a href="http://www.openoffice.org/tr">Turkish</a> or <a href="http://www.openoffice.org/nl">Dutch</a> websites. </p>
+<p>user interface
+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</h2>
+<p>The easiest way to get started is with the <a href="http://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>
+<li>The product description pages</li>
+<li>The "Why OpenOffice?" pages</li>
+<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
+want to translate.</p>
+<h2 id="creating-the-test-directory">Creating the Test Directory</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
+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>Let's take an example. Suppose your target language is Italian (it). You will want to do
+the following. If you are not a Committer and are familiar with Subversion then you will
+want to get help with these steps by asking on the mailing list.</p>
+<ol>
+<li>Make a copy (svn copy) of the <a href="https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/xx/">ooo-site/trunk/content/xx directory</a>
+ as ooo-site/trunk/content/test-it. In the copy replace all instances of "/xx"
+in paths with "/test-it"/.</li>
+<li>Also make a copy of <a href="https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/">ooos-site/trunk/templates/xx</a>
+and call the copy ooo-site/trunk/templates/test-it.</li>
+<li>Commit these changes and publish via the CMS</li>
+<li>If you are a committer then you can translate the contents of the files in /test-it locally
+or via the CMS, whatever you prefer. If you are not a committer than ask someone to do an
+"svn export" of the new /test-it and send a ZIP file of the contents.</li>
+</ol>
+<h2 id="translating-the-website">Translating the Website</h2>
+<p>The files will be in two main formats: </p>
+<ol>
+<li>HTML files.</li>
+<li>Markdown text files. You can read more about Markdown Text <a href="http://daringfireball.net/projects/markdown/basics">here</a>.</li>
+</ol>
+<p>In your translation, do not change the file or directory names. Be careful to preserve the
+markup of the HTML and the indentation levels of the MDText files.</p>
+<h2 id="the-template">The Template</h2>
+<p>You will notice that there is more on the openoffice.org website than what you see in the
+/test-it content files. The content files give the central part of each page, but the header,
+footer as well as navigation menus are generated by the template. There are special MDText
+files that you will need to translate for the template. They are:</p>
+<ul>
+<li>/xx/topnav.mdtext</li>
+<li>/xx/why/leftnav.mdtext</li>
+<li>/xx/product/leftnav.mdtext</li>
+<li>/xx/brand.mdtext</li>
+</ul>
+<p>For example, the /xx/topnav.mdtext has lines like this:</p>
+<div class="codehilite"><pre><span class="k">[Product][m0]</span>
+<span class="k">[Download][m1]</span>
+<span class="k">[Support][m2]</span>
+</pre></div>
+
+
+<p>Here you should translate the words "Product", "Download" and "Support". Also, at the
+bottom of the file you will see hyperlinks, which should not be changed, and text hints for
+the hyperlinks which should be translated.</p>
+<p>A special word about brand.mdtext. This contains several values that control the overall
+branding on the website. The name and logo must not be changed, since these are our
+trademarks, but the "tagline" can be translated. Note also the announcement and
+announcementurl fields. These control the blue announcement that is the top of every website
+page. That should be translated and the URL changed if needed. For example, in a new release
+you would want to point to a translated version of the release notes, if they exist.</p>
+<h2 id="other-hints">Other Hints</h2>
+<p>A few other things to watch out for.</p>
+<ol>
+<li>Some files contain an Apache License header at the top of the page. You should not translate that.</li>
+<li>Some files contain comments. These don't need to be translated, but no harm is done if they are.</li>
+<li>The /download/index.html requires special care since some of the language strings are within
+Javascript blocks. Ask for help if you need it here.</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 60 million trusted downloads."<br />
+You should translate these, but adapt if needed to keep the Twitter string within the 140 limit for Twitter.</li>
+</ol>
+<h2 id="nl-specific-content">NL-Specific Content</h2>
+<p>It may be desired to add language-specific custom content to the website. For example:</p>
+<ul>
+<li>A localized Arabic website might want a special page dedicated to a description of how
+to use the bidirectional text features in OpenOffice. The Tamil website might want a page
+that links to a particular open source font download that is recommended.</li>
+<li>There may be a local OpenOffice-related event that you want to publicize.</li>
+</ul>
+<p>New content pages can be added to your NL directory and links page from a navigator or from
+a news article on the home page as appropriate.</p>
+<h2 id="after-translation">After Translation</h2>
+<p>Once your translation is done, you can check it in (if you are a committer) or ask someone to help
+you check it in and publish it to the website. Review the published pages to verify that the
+translation is as you want it, and that all links work. Once it is ready you can rename your
+"test" directory and make it the new NL website for your language!</p>
+<p>Please Note: If there is an existing NL website it is recommended that you do the switch over like this:</p>
+<ol>
+<li>First delete the existing NL page, e.g., svn del /it. Commit and publish that change.</li>
+<li>Then rename the content/test-it directory, e.g., svn move content/test-it content/it. </li>
+<li>Also rename the templates/test-it to /templates/it</li>
+<li>Commit these changes and commit them via the CMS</li>
+</ol>
+<p>This order is recommended, with the commit and publish after the deletion of the old directory,
+due to a CMS build issue we've run into if all these steps are done together in a single commit.</p>
+<h2 id="maintaining-nl-websites">Maintaining NL Websites</h2>
+<p>Do try to check your NL website every few weeks to see if any changes are needed. Try to keep it in sync
+with the English website. Is there a new announcement header? A new release? A new blog post?</p>
+ </div>
+
+ <div id="footera">
+ <div id="poweredby">
+ <p><img src="/images/feather-small.gif" alt="Apache Feather"/></p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Copyright © 2011-2012 The Apache Software Foundation Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> | <a href="/contact.html">Contact Us</a> | <a href="/terms.html">Terms of Use</a>
+ </p>
+ <p>
+ Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+
+ </div>
+ </div>
+
+</body>
+</html>