Permalink
Browse files

Update l10n.rst

replace references to base.lang by download_button.lang (see bug 851545)
  • Loading branch information...
1 parent eeceeb0 commit 35e6e21c1099aade4db87efba483af22e3fc1e2c @pascalchevrel pascalchevrel committed Mar 15, 2013
Showing with 3 additions and 3 deletions.
  1. +3 −3 docs/l10n.rst
View
@@ -117,7 +117,7 @@ know which one to use when translating a particular string?
* All translations from Python files are put into main.lang. This
should be a very limited set of strings and most likely should be
available to all pages.
-* Templates always load in `main.lang`, `base.lang`, and `newsletter.lang`
+* Templates always load in `main.lang`, `download_button.lang`, and `newsletter.lang`
* Additionally, each template has its own .lang file, so a template at
`mozorg/firefox.html` would use the .lang file at
`<locale>/mozorg/firefox.lang`.
@@ -131,7 +131,7 @@ know which one to use when translating a particular string?
{% add_lang_files "foo" "bar" %}
That will make the page load `foo.lang` and `bar.lang` in addition to
-`main.lang`, `base.lang`, and `newsletter.lang`.
+`main.lang`, `download_button.lang`, and `newsletter.lang`.
When strings are extracted from a template, that are added to the
template-specific .lang file. If the template explicitly specifies
@@ -155,7 +155,7 @@ value should be either a string, or a list of strings, similar to the
sometext = _('Foo about bar.')
This file's strings would be extracted to `foo.lang`, and the lang files
-`foo.lang`, `bar.lang`, `main.lang`, `base.lang`, and `newsletter.lang`
+`foo.lang`, `bar.lang`, `main.lang`, `download_button.lang`, and `newsletter.lang`
would be searched for matches in that order.
l10n blocks

0 comments on commit 35e6e21

Please sign in to comment.