From ece6c5630ff06d35f466c7fc0cdbb2296a23c587 Mon Sep 17 00:00:00 2001
From: Larissa Reis <larissa@colivre.coop.br>
Date: Thu, 13 Nov 2014 01:16:22 -0300
Subject: [PATCH] Documentation for custom locales

---
 INSTALL.locales.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+), 0 deletions(-)
 create mode 100644 INSTALL.locales.md

diff --git a/INSTALL.locales.md b/INSTALL.locales.md
new file mode 100644
index 0000000..ae32bd2
--- /dev/null
+++ b/INSTALL.locales.md
@@ -0,0 +1,28 @@
+Using custom locales
+====================
+
+Personalized translations go into the `custom_locales/` directory. Custom
+locales can be identified by the rails environment, schema name in a
+multitenancy setup or domain name until the first dot (e.g env1.coop.br for the
+example below).
+
+Currently, the only filename prefix for the localization file which is
+processed is "environment". For instance, a POT file would be called
+"environment.pot".
+
+The structure of an environment named env1 with custom translations for both
+Portuguese and Spanish and an environment named env2 with custom Russian
+translation would be:
+  
+    custom_locales/
+      env1/
+        environment.pot
+        pt/
+          environment.po
+        es/
+          environment.po
+      env2/
+        environment.pot
+        ru/
+          environment.po
+
--
libgit2 0.21.2