From f0e74abb2b9254e90725a7691ded9955e0b1c59a Mon Sep 17 00:00:00 2001
From: Michael Telatynski <7t3chguy@gmail.com>
Date: Wed, 23 Aug 2023 11:06:24 +0100
Subject: [PATCH] Iterate

---
 docs/translating-dev.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/translating-dev.md b/docs/translating-dev.md
index 728f2c3b5d..ea30213675 100644
--- a/docs/translating-dev.md
+++ b/docs/translating-dev.md
@@ -44,6 +44,9 @@ function getColorName(hex) {
 ### Key naming rules
 
 These rules are based on https://github.com/vector-im/element-x-android/blob/develop/tools/localazy/README.md
+At this time we are not trying to have a translation key per UI element as some methodologies use,
+whilst that would offer the greatest flexibility, it would also make reuse between projects nigh impossible.
+We are aiming for a set of common strings to be shared then some more localised translations per context they may appear in.
 
 1. Ensure the string doesn't already exist in a related project, such as https://localazy.com/p/element
 2. Keys for common strings, i.e. strings that can be used at multiple places must start by `action_` if this is a verb, or `common_` if not