From 4ce336327dfc9ad519a5d8fee7a92e7ef3f406e4 Mon Sep 17 00:00:00 2001
From: William Kendrick <wkendrick@users.sourceforge.net>
Date: Thu, 10 Jul 2008 18:37:59 +0000
Subject: [PATCH] Further updates relating to locale case.

---
 docs/EXTENDING.txt       | 8 ++++----
 docs/html/EXTENDING.html | 9 +++++----
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/docs/EXTENDING.txt b/docs/EXTENDING.txt
index 717baaf7e..326a5f584 100644
--- a/docs/EXTENDING.txt
+++ b/docs/EXTENDING.txt
@@ -263,7 +263,7 @@ Stamps
          running in a different locale (like French or Spanish).
 
          The beginning of the line should correspond to the language code of
-         the language in question (e.g., "fr" for French, and "zh_tw" for
+         the language in question (e.g., "fr" for French, and "zh_TW" for
          Traditional Chinese), followed by ".utf8=" and the translated
          description (encoded in UTF-8).
 
@@ -297,8 +297,8 @@ Stamps
          filename, in the form: "STAMP_LOCALE.EXT"
 
          "picture.png"'s sound effect, when Tux Paint is run in Spanish mode,
-         would be "picture_es.wav". In French mode, "picture_fr.wav". And so
-         on...
+         would be "picture_es.wav". In French mode, "picture_fr.wav". In
+         Brazilian Portuguese mode, "picture_pt_BR.wav". And so on...
 
          If no localized sound effect can be loaded, Tux Paint will attempt
          to load the 'default' sound file. (e.g., "picture.wav")
@@ -555,7 +555,7 @@ Translations
      file, "tuxpaint.pot" (found in Tux Paint's source code, in the folder
      "src/po/"). Rename the copy as a ".po" file, with an appropriate name
      for the locale you're translating to (e.g., "es.po" for Spanish; or
-     "pt_br.po" for Brazilian Portuguese, versus "pt.po" or "pt_pt.po" for
+     "pt_BR.po" for Brazilian Portuguese, versus "pt.po" or "pt_PT.po" for
      Portuguese spoken in Portugal.)
 
      Open the newly-created ".po" file - you can edit in a plain text edtior,
diff --git a/docs/html/EXTENDING.html b/docs/html/EXTENDING.html
index c98879cd9..132416f52 100644
--- a/docs/html/EXTENDING.html
+++ b/docs/html/EXTENDING.html
@@ -358,7 +358,7 @@ effect.</p>
 
       <p>The beginning of the line should correspond to the language code
       of the language	in question (e.g., "<code>fr</code>" for French, and
-      "<code>zh_tw</code>" for Traditional Chinese), followed by
+      "<code>zh_TW</code>" for Traditional Chinese), followed by
       "<code>.utf8=</code>" and the translated description (encoded
       in UTF-8).</p>
       
@@ -397,7 +397,8 @@ effect.</p>
 
       <p>"<code>picture.png</code>"'s sound effect, when Tux&nbsp;Paint is run
       in Spanish mode, would be "<code>picture_es.wav</code>".
-      In French mode, "<code>picture_fr.wav</code>".  And so on...</p>
+      In French mode, "<code>picture_fr.wav</code>".  In Brazilian
+      Portuguese mode, "<code>picture_pt_BR.wav</code>". And so on...</p>
 
       <p>If no localized sound effect can be loaded, Tux&nbsp;Paint will
       attempt to load the 'default' sound file.
@@ -714,8 +715,8 @@ effect.</p>
   source code, in the folder "<code>src/po/</code>").  Rename the copy as a
   "<code>.po</code>" file, with an appropriate name for the locale you're
   translating to (e.g., "<code>es.po</code>" for Spanish; or
-  "<code>pt_br.po</code>" for Brazilian&nbsp;Portuguese, versus
-  "<code>pt.po</code>" or "<code>pt_pt.po</code>" for Portuguese spoken in
+  "<code>pt_BR.po</code>" for Brazilian&nbsp;Portuguese, versus
+  "<code>pt.po</code>" or "<code>pt_PT.po</code>" for Portuguese spoken in
   Portugal.)</p>
 
   <p>Open the newly-created "<code>.po</code>" file &mdash; you can edit