Automating process of translation for new variables.

[Cyber-Syntax]

I wrote a basic script that compares en.json with tr.json to find missing variables and adds them to tr.json, which even adds the same lines.

Solutions:

1. I can make this script general so it updates all other i18n files and send PR.
2. Alternatively, you could add new variables in English to all of the other i18n files.
3. Or, there might be an easier way to do this that I'm not aware of

const fs = require('fs');
const path = require('path');

const i18nDir = path.resolve(__dirname, 'src/assets/i18n');
const enPath = path.join(i18nDir, 'en.json');
const trPath = path.join(i18nDir, 'tr.json');

function mergeInOrder(enObj, trObj) {
  if (typeof enObj !== 'object' || enObj === null) return trObj;
  const result = Array.isArray(enObj) ? [] : {};
  for (const key of Object.keys(enObj)) {
    if (
      typeof enObj[key] === 'object' &&
      enObj[key] !== null &&
      !Array.isArray(enObj[key])
    ) {
      result[key] = mergeInOrder(enObj[key], trObj[key] || {});
    } else {
      result[key] = (trObj && key in trObj) ? trObj[key] : enObj[key];
    }
  }
  return result;
}

if (!fs.existsSync(enPath) || !fs.existsSync(trPath)) {
  console.error('en.json or tr.json not found in src/assets/i18n/');
  process.exit(1);
}

const en = JSON.parse(fs.readFileSync(enPath, 'utf8'));
const tr = JSON.parse(fs.readFileSync(trPath, 'utf8'));

const merged = mergeInOrder(en, tr);

fs.writeFileSync(trPath, JSON.stringify(merged, null, 2), 'utf8');

console.log('tr.json updated with missing keys in the same order as en.json.');

[johannesjo]

Thanks for sharing! We could add this to tools and provide a script for it. I wouldn't want to include it in the automated build, since my tool for automated translations requires the keys NOT to be present to spot untranslated keys.

[Cyber-Syntax]

I wrote the general script to add all the missing variables to other i18n files compared to en.json. Currently, there are many missing variables that I've found in other i18n files. So, is it acceptable to publish them without translation (e.g., keeping the original English text) or should we not add variables for other i18n files if they haven't been translated?

This would help non-technical translators see the untranslated English text, but if that's not compatible with your tool, it might be better not to commit them.

[johannesjo]

So, is it acceptable to publish them without translation (e.g., keeping the original English text) or should we not add variables for other i18n files if they haven't been translated?

I don't think we should. Another reason is that usually the english fullback is used, which is imho what we want. When the value is populated with a placeholder, the placeholder is shown.