Commit 560ecd11 authored by James A. Treacy's avatar James A. Treacy

a few small updates plus a big update to the 'what to translate' section

CVS version numbers

english/devel/website/translation_hints.wml: 1.9 -> 1.10
parent fb9453b1
......@@ -2,16 +2,33 @@
<h3>What to translate?</h3>
<p>Our suggestion is to start with the pages that users
would be most likely to visit:
main page, package page, vendor list, files in the intro
directory, security, etc.
Creating the <a href="navbar_images">images for the navigation bar</a>
should also be a high priority.
Pages that would not interest many users should be low
priority. For example, the developer pages.
<h3>How accurate should translations be?</h3>
<p>New translations should always start by adding translated slices to
the .wml files in english/templates/debian/. Be careful when adding
your translation as you can easily break all the web pages if a
mistake is made.
<p>Once you start translating pages, we recommend you start with pages
that users are most likely to visit (in rough order of importance):
<ul>
<li><strong>Most important:</strong> main page, .wml files in the main
directory. Files in the following directories: intro, misc, releases,
distrib, doc, events, searchtmpl and security(*).
Also create the translated <a href="navbar_images">images for the navigation bar</a>.
<li><strong>Standard:</strong> Files in the following directories:
Bugs, banners, logos, MailingLists(*), consultants, ports, partners and
News(*).
<li><strong>Least Important:</strong> Files in the devel(*), vote and
mirror directories. Since they are mostly for developers, and the primary
language of developers is English, it is only when you have a strong
translation team should you attempt to tackle these. Files or
directories marked by an asterisk, '*', above are modified frequently,
so are harder to keep up to date.
</ul>
<strong>It is important that you only translate files that you have
the time to maintain. A few well maintained pages is much more useful
than a lot of out of date ones.</strong>
<h3>How closely should translations follow the original?</h3>
<p>There are times when you may want to make a change to the content when
you are translating. One example is on the support page; you will probably
......@@ -67,10 +84,31 @@ final page.
<h3>What are these foo.def and foo.data files?</h3>
<p>To make it easier to keep the translations up to date, we separate the
generic parts (data) from the textual parts (text) of such pages. You only
generic parts (data) from the textual parts (text) of some pages. You
most likely only need to copy and translate the .wml version of the file.
You then need to add the translated slices in the data file (usually called
foo.data or foo.def).
If there are any slices in the data file, the translated slices go in
the original (in other words, don't make a copy in your translation
directory).
<p>Slices in the data file should be updated very infrequently and a
note is usually sent to debian-www when this happens. Other changes to
the data file will cause your translation to be rebuilt.
<p>An example may help in understanding this. It takes three files to
generate the page of vendor listings:
<ul>
<li>vendors.wml: The text at the top of the vendors page is in this
file. A translated copy of this should be placed in your language
directory.
<li>vendors.CD.def: This contains all the pieces of text which are
needed for each vendor entry. You add your translations directly to
the original, which is in english/distrib/vendors.CD.def.
<li>vendors.CD: Due to the large number of vendors, the actual vendor
entries are put in a separate file. You don't need to touch this file.
</ul>
New vendors are added by one of the webmasters modifying vendors.CD.
The next time the web pages are updated all the translations will
automatically be rebuilt. An updated translation for free!
<h3>How do translators know when files need to be updated?</h3>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment