From f4305a5b4a493f7247a7872d9ab0d70ec6a5b3ac Mon Sep 17 00:00:00 2001
From: Mathieu Lu <mathieu@bidon.ca>
Date: Mon, 6 Nov 2017 22:15:02 -0500
Subject: [PATCH] developers.md: added background sections (why, other guides)

---
 docs/translation/developers.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/translation/developers.md b/docs/translation/developers.md
index f6a8315f..e3280cb3 100644
--- a/docs/translation/developers.md
+++ b/docs/translation/developers.md
@@ -112,3 +112,21 @@ and not:
 ```
 {ts}<p>This is a bad example.</p>{/ts}
 ```
+
+## Why not use the Drupal locale module?
+
+In most projects, strings are typically translated by either:
+
+* using Gettext (which is what CiviCRM does),
+* using arrays of key/string dictionaries,
+* using database lookups of strings (which is what Drupal does).
+
+In order to be support Joomla!, WordPress, Backdrop and eventually other content management systems. Gettext is the standard way to translate strings in PHP, used by most projects.
+
+## Other guides/references
+
+Here are the guides to other popular projects:
+
+* Drupal: https://www.drupal.org/node/322729
+* Joomla!: https://docs.joomla.org/Specification_of_language_files
+* WordPress: https://codex.wordpress.org/I18n_for_WordPress_Developers
-- 
GitLab