From 193db78fc35b50f88fd48eb8add1e8c3486f5785 Mon Sep 17 00:00:00 2001 From: Damien Baty Date: Sun, 2 May 2010 10:22:13 +0000 Subject: Fixed typos in the new 'Detecting Available Languages' section. --- docs/narr/i18n.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/narr/i18n.rst') diff --git a/docs/narr/i18n.rst b/docs/narr/i18n.rst index 220755ba9..f97d655ec 100644 --- a/docs/narr/i18n.rst +++ b/docs/narr/i18n.rst @@ -787,7 +787,7 @@ languages" as indicated by the union of all languages in all translation directories on disk at the time of the call to the API. It is by design that :mod:`repoze.bfg` doesn't supply such an API. -Instead, the application itself responsible for knowing the "available +Instead, the application itself is responsible for knowing the "available languages". The rationale is this: any particular application deployment must always know which languages it should be translatable to anyway, regardless of which translation files are on disk. @@ -796,7 +796,7 @@ Here's why: it's not a given that because translations exist in a particular language within the registered set of translation directories that this particular deployment wants to allow translation to that language. For example, some translations may exist but they -may be be incomplete or incorrect. Or there may be translations to a +may be incomplete or incorrect. Or there may be translations to a language but not for all translation domains. Any nontrivial application deployment will always need to be able to @@ -827,7 +827,7 @@ Then as a part of the code of a custom :term:`locale negotiator`: from repoze.bfg.settings import get_settings languages = get_settings()['available_languages'].split() -This is only a suggestion. You can create a your own "available +This is only a suggestion. You can create your own "available languages" configuration scheme as necessary. .. index:: -- cgit v1.2.3