You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Extract only the "added" keys that need translation
58
+
KEYS_TO_TRANSLATE=$(node -e "
59
+
const data = JSON.parse(require('fs').readFileSync('changed-keys.json', 'utf-8'));
60
+
console.log(JSON.stringify(data.added, null, 2));
61
+
")
62
+
63
+
echo "Keys to translate:"
64
+
echo "$KEYS_TO_TRANSLATE"
65
+
66
+
claude -p "You are a professional translator specializing in Bulgarian translations for software interfaces.
67
+
68
+
I have some English strings from a video conferencing application (Jitsi Meet) that need to be translated to Bulgarian.
69
+
70
+
IMPORTANT: First, read the file lang/main-bg.json to understand the existing Bulgarian translation style, terminology, and consistency patterns.
71
+
72
+
Here are the English strings to translate (JSON format):
73
+
$KEYS_TO_TRANSLATE
74
+
75
+
TRANSLATION GUIDELINES:
76
+
- Use professional, natural Bulgarian language
77
+
- Be consistent with the existing Bulgarian translations in lang/main-bg.json (terminology, formal/informal style, etc.)
78
+
- Mixed Bulgarian and English is unacceptable. Everything must be translated to proper Bulgarian.
79
+
- Exception: Established technical terms that are widely used in English (like 'WebAssembly', 'URL', 'API') can remain in English if they don't have good Bulgarian translations and are commonly used by Bulgarian speakers.
80
+
- Example: 'phone number' MUST be translated to Bulgarian, but 'WebAssembly' can stay in English.
81
+
- Preserve any placeholders like {{variable}} or {name} exactly as they appear.
82
+
- Maintain formal/informal consistency with existing translations.
83
+
84
+
Please respond with ONLY a JSON object mapping each key to its Bulgarian translation. No explanations, no markdown, just the JSON object.
0 commit comments