Author: buildbot
Date: Wed Jul 29 14:55:43 2015
New Revision: 960030

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/docs/multilingualization.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 29 14:55:43 2015
@@ -1 +1 @@
-1692427
+1693284

Modified: websites/staging/vcl/trunk/content/docs/multilingualization.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/multilingualization.html (original)
+++ websites/staging/vcl/trunk/content/docs/multilingualization.html Wed Jul 29 
14:55:43 2015
@@ -36,7 +36,18 @@
   </div>
 
   <div id="navigation"> 
-  <ul>
+  <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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>
+<ul>
 <li><a href="/index.html">Information</a><ul>
 <li><a href="/info/features.html">Features</a></li>
 <li><a href="/info/architecture.html">Architecture</a></li>
@@ -72,7 +83,18 @@
   
   <div id="content">
     <h1 class="title">Adding a New Locale to the VCL Web Frontend</h1>
-    <h2 id="introduction">Introduction</h2>
+    <style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+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="introduction">Introduction<a class="headerlink" href="#introduction" 
title="Permanent link">&para;</a></h2>
 <p>VCL 2.3 has the first step in multilingualization by allowing the parts of 
the site 
 that the basic user sees to be presented in different languages. The initial 
work was 
 done and contributed by Toru Yokoyama in JIRA-485.</p>
@@ -83,7 +105,7 @@ translations. This should be addressed i
 <p>There are three places where translation work needs to happen to add a new 
language: 
 a gettext translation file (.po or portable object file), a javascript 
translation 
 file, and a few database entries.</p>
-<h2 id="places-to-translate">Places to translate</h2>
+<h2 id="places-to-translate">Places to translate<a class="headerlink" 
href="#places-to-translate" title="Permanent link">&para;</a></h2>
 <p>There are two files to work with - a php translation file and a javascript 
translation 
 file. Also, there are entries that need to be added to the database in the 
connect
 method table.</p>
@@ -92,7 +114,7 @@ method table.</p>
 </pre></div>
 
 
-<h2 id="creating-a-gettext-translation-file">Creating a gettext translation 
file</h2>
+<h2 id="creating-a-gettext-translation-file">Creating a gettext translation 
file<a class="headerlink" href="#creating-a-gettext-translation-file" 
title="Permanent link">&para;</a></h2>
 <p>vcl/locale/po_files/vcl.po.template is a base translation file. You need to 
create 
 two new directories under vcl/locale for your new locale (using es_PR as an 
example):</p>
 <div class="codehilite"><pre><span class="n">vcl</span><span 
class="o">/</span><span class="n">locale</span><span class="o">/</span><span 
class="n">es_PR</span><span class="o">/</span><span class="n">LC_MESSAGES</span>
@@ -125,11 +147,11 @@ translated string.</p>
 <p>After you have translated everything, you need to compile the .po file into 
a .mo 
 file using msgfmt, also from the gettext suite, placing the .mo file under the 
 vcl/locale/es_PR/LC_MESSAGES/ path:</p>
-<div class="codehilite"><pre><span class="n">msgfmt</span> <span 
class="o">--</span><span class="n">output</span><span class="p">=</span><span 
class="n">vcl</span><span class="o">/</span><span class="n">locale</span><span 
class="o">/</span><span class="n">es_PR</span><span class="o">/</span><span 
class="n">LC_MESSAGES</span><span class="o">/</span><span 
class="n">vcl</span><span class="p">.</span><span class="n">mo</span> <span 
class="n">vcl</span><span class="o">/</span><span class="n">locale</span><span 
class="o">/</span><span class="n">po</span><span class="o">/</span><span 
class="n">es_PR</span><span class="o">/</span><span class="n">vcl</span><span 
class="p">.</span><span class="n">po</span>
+<div class="codehilite"><pre><span class="n">msgfmt</span> <span 
class="o">--</span><span class="n">output</span><span class="p">=</span><span 
class="n">vcl</span><span class="o">/</span><span class="n">locale</span><span 
class="o">/</span><span class="n">es_PR</span><span class="o">/</span><span 
class="n">LC_MESSAGES</span><span class="o">/</span><span 
class="n">vcl</span><span class="p">.</span><span class="n">mo</span> <span 
class="n">vcl</span><span class="o">/</span><span class="n">locale</span><span 
class="o">/</span><span class="n">po_files</span><span class="o">/</span><span 
class="n">es_PR</span><span class="o">/</span><span class="n">vcl</span><span 
class="p">.</span><span class="n">po</span>
 </pre></div>
 
 
-<h2 id="creating-a-javascript-translation-file">Creating a javascript 
translation file</h2>
+<h2 id="creating-a-javascript-translation-file">Creating a javascript 
translation file<a class="headerlink" 
href="#creating-a-javascript-translation-file" title="Permanent 
link">&para;</a></h2>
 <p>There is a base translation file at vcl/js/nls/messages.js.template. You 
need to create a new directory under vcl/js/nls (using es_PR as an example):</p>
 <div class="codehilite"><pre><span class="n">vcl</span><span 
class="o">/</span><span class="n">js</span><span class="o">/</span><span 
class="n">nls</span><span class="o">/</span><span class="n">es_PR</span>
 </pre></div>
@@ -148,7 +170,7 @@ language. The file has an English string
 
 <p>You must translate the string in the first set of quotes and place the 
translation 
 in the second set of quotes for each string in the file.</p>
-<h2 id="adding-entries-to-connectmethod-table-in-database">Adding entries to 
connectmethod table in database</h2>
+<h2 id="adding-entries-to-connectmethod-table-in-database">Adding entries to 
connectmethod table in database<a class="headerlink" 
href="#adding-entries-to-connectmethod-table-in-database" title="Permanent 
link">&para;</a></h2>
 <p>VCL 2.3 also introduced Connection Methods. This actually introduced a 
problem with 
 multilingualization because most of the text for the Connect page is now in 
the 
 database. Each connect method has a description and the text to be displayed 
on the 


Reply via email to