Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Small style cleanups to the recent changes in docs/i18n.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@2059 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 78c8be92186d1af38c148073936b56c7b0835fd7 1 parent c12c225
Adrian Holovaty authored January 19, 2006

Showing 1 changed file with 13 additions and 13 deletions. Show diff stats Hide diff stats

  1. 26  docs/i18n.txt
26  docs/i18n.txt
@@ -447,24 +447,24 @@ Notes:
447 447
       en-us).
448 448
 
449 449
       .. _LANGUAGES setting: http://www.djangoproject.com/documentation/settings/#languages
450  
-    * the LocaleMiddleware can only select languages for which there is a
451  
-      django provided base translation. If you want to provide translations
  450
+    * The ``LocaleMiddleware`` can only select languages for which there is a
  451
+      Django-provided base translation. If you want to provide translations
452 452
       for your application that aren't already in the set of translations
453  
-      in Djangos source tree, you will want to at least provide basic
454  
-      translations for that language. For example Django uses technical
455  
-      message IDs to translate date formats and time formats - so you will
  453
+      in Django's source tree, you'll want to provide at least basic
  454
+      translations for that language. For example, Django uses technical
  455
+      message IDs to translate date formats and time formats -- so you will
456 456
       need at least those translations for the system to work correctly.
457 457
 
458  
-      A good starting point is to just copy over the english ``.po`` file
459  
-      and to translate at least the technical messages and maybe the validator
  458
+      A good starting point is to copy the English ``.po`` file and to
  459
+      translate at least the technical messages -- maybe the validator
460 460
       messages, too.
461  
-      
462  
-      Technical message IDs are easily recognized by them being all upper case.
463  
-      You don't translate the message ID as with other messages, you provide
464  
-      the correct local variant on the provided english value. For example with
  461
+
  462
+      Technical message IDs are easily recognized; they're all upper case. You
  463
+      don't translate the message ID as with other messages, you provide the
  464
+      correct local variant on the provided English value. For example, with
465 465
       ``DATETIME_FORMAT`` (or ``DATE_FORMAT`` or ``TIME_FORMAT``), this would
466  
-      be the format string that you want to use in your language.  The format
467  
-      is identical to the ``now`` tag date formattings.
  466
+      be the format string that you want to use in your language. The format
  467
+      is identical to the format strings used by the ``now`` template tag.
468 468
 
469 469
 Once ``LocaleMiddleware`` determines the user's preference, it makes this
470 470
 preference available as ``request.LANGUAGE_CODE`` for each `request object`_.

0 notes on commit 78c8be9

Please sign in to comment.
Something went wrong with that request. Please try again.