npm run translate translate feels weird.

E.g.

npm run translate -- --language fr it

This would make it easier to work around the rate limiter if there is a lot to translate.

When running npm run translate to tanslate the i18n json files, only the first sentence of each string gets translated.
Any further sentence is dropped from the translation.

Especially for the help texts in jsonConfig, sometimes multiple sentences in one string are required.

Example:
en (source)

"Emoji to react with on mentions. Default is 👍.": "Emoji to react with on mentions. Default is 👍.",

de (tranlated)

"Emoji to react with on mentions. Default is 👍.": "Emoji zum Reagieren auf Erwähnungen. ",

(note the space at the end)

This could be done the easy way, just add /* eslint quotes: off */ at the top of the file.

Or detect quote settings of eslint and respect them in words.js file.

Currently, if words.js is recreated, you have to add the eslint directive to the file again to not have linting fail.

a) Currently npm run translate writes translated text records into the target files only if the corresponding record does not exist there.

npm run translate should keep a record of the source file (i18n/en/translate,json) and hence detect if a text has been changed. In this case the target records should be replaced with the new translations too. Note: npm run traslate MUST NOT write the full target file if no change in source json is detected as this would override manual corrections.

b) at least optionally npm translate should remove outdated record from the target files. Outdated records should be defined as records no longer exist in source file.

Hi,
might it be possible, to add an option "--r Word" for example, which removes the translation for a word in all translation files as well as the word.js.

The background/idea behind that is, if you change or extend a translation to another word, you need to open all the files, remove this particular translation and then change it inside the en directory, to get it translated again into the new/changed word/sentence.

Thanks!

in the options the .watch directory is defined if you start the admin ui developement for an adapter in react.
but in the template of the html page there is fixed the build directory linked.
https://github.com/ioBroker/create-adapter/blob/61859f109562d2a9072c1288381455a879d28510/templates/admin/index_m.html.ts#L110
this should be dynamic

I just switched from Gulp to @iobroker/adapter-dev in Backitup and ran into a problem.

Due to felxible translations within the code, the word.js is non-standard and contains "module.exports"

If I now update the word.js via npm run translate adminLanguages2words, the complete content is overwritten.

Is it possible that only the actual translation is overwritten and everything else remains in its original state?

Like we have it already in this project, we should provide tsconfig files for all adapters that contain all (or almost all) configs.

Different files should be provided for:

• JS adapter
• TS adapter
• HTML/JS admin GUI
• React admin GUI
  • JS
  • TS

I would suggest having a folder tsconfig/ with the different configs, so one could for example write:

{
    "extends": "@iobroker/adapter-dev/tsconfig/adapter-js.json",
    ...
}

When sharing modules between the config and tab for example, it makes sense to use module splitting to avoid duplication. In this case, esbuild creates new chunks for each watch build, so we should clean up afterwards

npm run translate all issues the following errors is any key has an empty value:

Using Legacy Google Translate
Could not translate to "de": TypeError: Cannot read properties of null (reading 'map')

Could not translate to "de": TypeError: Cannot read properties of null (reading 'map')

Could not translate to "de": TypeError: Cannot read properties of null (reading 'map')

incorrect source example:

    "lblOptNoRawStates": "",
    "lblOptNoValStates": "",

It would be good to add the json key (i.e. lblOpNoRawStates) to the error message. This woul help locating the empty string.

Please add the following tokens:

I just found out that DeepL has a free API:
https://www.deepl.com/pro#developer

Since this is MUCH better than Google, we should offer this as an option atleast - if not the default.

We decided to add ukrainian language.

Hi,
if you have a translation like this in the json file
"ex_custom_circle_icon":"How to get the Icon? Visit <a href='_top'>https://materialdesignicons.com</a> and search for an icon. Click the Icon and in the below row click '</>', choose 'View SVG' and copy only the text inside <b>d</b>",
It will be cut after: How to get the Icon?

npm run build works fine in my environment (see create-adapter.json and package.json etc.

This readme mentions following, but I get errors

1. npm run build-adapter all throws npm ERR! Missing script: "build-adapter"
2. npm run build all results in Unknown argument: all

Currenty, translating produces huge diffs because it indents files differently than my VSCode settings. If possible, this should be avoided.

Separate for JS/TS

https://eslint.org/docs/developer-guide/shareable-configs

• title
• text

Example: https://github.com/ioBroker/ioBroker.influxdb/blob/4f9ed11bd3cc13c377292a56aaaa87aeeec81b3f/io-package.json#L170-L260

If the source json file (i18n/en/translate.json) contains an empty string, i.e.

    "lblDevsEnable":     "",

the command npm run translate issues an error message:

Could not translate to "pl": TypeError: Cannot read property '0' of null

In some situations is useful to replace the test in jsonConfig.json to an empty string (i.e. if you want to remove a text without changing jsonConfig or if you want to add the text to some languages only).

npm run translate should simply "translate" the empty string to an empty string.

see Apollon77/ioBroker.smartmeter@fa6d671

• do not send "empty strings" to translation
• on errors (e,.g. rate limti) at least store the progress so far on words translations

Currently only 1 line of translations is handled, separation by /n are cut off.
Example:

"0.2.0": {
    "en": "Initialization error for Nano V1 solved\nError logging and reporting improved\nAdapter rebuild to TypeScript\nTest & Release workflow updated\nAdded indicator for connection status\nReconnecting to offline devices improved\nEnsure support of all WLANThermo-Nano Devices",
    "de": "Unterstützt mehrere Geräte"
}

Expected outcome:

"0.2.0": {
    "en": "Initialization error for Nano V1 solved\nError logging and reporting improved\nAdapter rebuild to TypeScript\nTest & Release workflow updated\nAdded indicator for connection status\nReconnecting to offline devices improved\nEnsure support of all WLANThermo-Nano Devices",
    "de": "Unterstützt mehrere Geräte\nFehler-/Debug-Protokollierung Verbessert\nUmbau des Adapters auf TypeScript\nTest- und Release-Workflow aktualisiert\nIndikator für den Verbindungsstatus hinzugefügt\nWiederverbinden mit Offline-Geräten verbessert\nStellen Sie sicher, dass alle WLANThermo-Nano-Geräte unterstützt werden",
    "ru": "Поддержка нескольких устройств\nВедение журнала ошибок/отладки Улучшено\nАдаптер пересобран на TypeScript\nОбновлен рабочий процесс тестирования и выпуска\nДобавлен индикатор состояния соединения\nУлучшено повторное подключение к автономным устройствам.\nОбеспечьте поддержку всех устройств WLANThermo-Nano",
    "pt": "Suporta vários dispositivos\nRegistro de erros/depuração aprimorado\nReconstrução do adaptador para TypeScript\nFluxo de trabalho de teste e lançamento atualizado\nIndicador adicionado para o status da conexão\nReconectando-se a dispositivos off-line aprimorado\nGaranta o suporte de todos os dispositivos WLANThermo-Nano",
    "nl": "Ondersteuning voor meerdere apparaten\nLogboekregistratie van fouten/foutopsporing Verbeterd\nAdapter opnieuw opbouwen naar TypeScript\nTest & Release-workflow bijgewerkt\nIndicator toegevoegd voor verbindingsstatus\nOpnieuw verbinding maken met offline apparaten verbeterd\nZorg voor ondersteuning van alle WLANThermo-Nano-apparaten",
    "fr": "Prend en charge plusieurs appareils\nJournalisation des erreurs/débogages Amélioré\nReconstruction de l'adaptateur vers TypeScript\nFlux de travail de test et de publication mis à jour\nIndicateur ajouté pour l'état de la connexion\nReconnexion à des appareils hors ligne améliorée\nAssurer la prise en charge de tous les périphériques WLANThermo-Nano",
    "it": "Supporta più dispositivi\nRegistrazione errori/debug Migliorata\nRicostruzione dell'adattatore in TypeScript\nFlusso di lavoro di test e rilascio aggiornato\nAggiunto indicatore per lo stato della connessione\nRiconnessione ai dispositivi offline migliorata\nGarantire il supporto di tutti i dispositivi WLANThermo-Nano",
    "es": "Soporta múltiples dispositivos\nRegistro de error/depuración Mejorado\nReconstrucción del adaptador a TypeScript\nFlujo de trabajo de prueba y lanzamiento actualizado\nIndicador agregado para el estado de la conexión.\nSe mejoró la reconexión a dispositivos sin conexión\nAsegurar el soporte de todos los dispositivos WLANThermo-Nano",
    "pl": "Obsługa wielu urządzeń\nRejestrowanie błędów/debugów Ulepszone\nOdbudowa adaptera do TypeScript\nZaktualizowano przepływ pracy Test & Release\nDodano wskaźnik statusu połączenia\nUlepszone ponowne łączenie z urządzeniami offline\nZapewnij obsługę wszystkich urządzeń WLANThermo-Nano",
    "zh-cn": "支持多种设备\n错误/调试日志记录改进\n适配器重建到 TypeScript\n测试和发布工作流程更新\n添加了连接状态指示器\n重新连接到离线设备得到改进\n确保支持所有 WLANThermo-Nano 设备"
},

There seems to be some partial sorting, but not completely: