al files is in en folder then i need all files to es folder

with will be command for google and azure?

GOOGLE WORKS:

attranslate --srcFile=general.yml --srcLng=en --srcFormat=yaml --targetFile=general-es.yml --targetLng=es --targetFormat=yaml --service=google-translate --serviceConfig=traducciones-352415-79659df1c6f1.json

https://github.com/louislam/uptime-kuma/blob/master/src/languages/en.js

is possible have JS translate into your great app?

For most combinations of file formats, everything works as expected.
However, if the target file is an XML or YAML and the source file is something different, then things are messed up.
Details will follow.

Currently, there is a huge number of outdated linting packages.
While linting is a great tool, it is not really worth to update all those packages to the latest versions.
attranslate should be simple to fork and simple to throw in new code, since the architecture allows for features to be isolated.

Describe the bug
Hello,
I would love to use this tool but I cannot apparently. I work with .po files (But I've tried with csv and nested-json and I got the same problem).
It is well installed, it works (if I set a target location different from the source, the file is generated with the proper keys).
BUT nothing is translated. Even if I use service=manual, I don't get any prompt asking me to translate manually. I always get "Target is up-to-date".

To Reproduce
This is what I use :
attranslate --srcFile=/home/max/projects/yoschool_repo/main/locale/de/LC_MESSAGES/django.po --srcLng=en --srcFormat=po --targetFile=/home/max/projects/yoschool_repo/main/locale/de/LC_MESSAGES/django.po --targetLng=de --targetFormat=po --service=manual

Expected behavior
I expect a prompt asking me to enter a translation for each entry in the .po file

Files
Here is the beggining of my .po file

#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-06-27 13:39+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#: enums/EmailSubject.py:10
msgid "$0 invites you to join $1 on YoPlanning"
msgstr ""

#: enums/EmailSubject.py:11
msgid "Welcome to Yoplanning!"
msgstr ""

I tried to translate content of XML file and ended with this error:

"8 RESOURCE_EXHAUSTED: Quota Error: RESOURCE_EXHAUSTED Quota exceeded for quota metric 'v2 and v3 general model characters' and limit 'v2 and v3 general model characters per minute' of service 'translate.googleapis.com' for consumer"

I have invoked 'google-translate' from 'pl' to 'sk' with 223559 inputs. Does anyone knows what should I do? Minute limite in GCloud is by default set to 6 000 000 char. per minute. If I want to increase limit, it has to be approved by service provider. If I should increase limit, to what number? Can anyone help? Thanks.

Great project!

I'm trying to configure attranslate to work with the Azure translator. Unfortunately, I'm not getting very far and I can't find any documentation that explains how to configure it.

Any pointers / documentation would be appreciated.

Thanks!

Describe the bug

As described by the title, when using ICU matcher with multiple interpolations will only handle the first interpolation.

npx attranslate --srcFile=path/to/translations/en.json --srcLng=en --srcFormat=nested-json --targetFile sv.json --targetLng=sv --targetFormat=nested-json --matcher=icu --service google-translate

Example:

{
  "pageXofX": "{currentPage} of {numberOfPages}"
}

is generated into:

{
  "pageXofX": "{currentPage} av <span> 1 </span>"
}

To Reproduce

Translate the JSON example above.

Expected behavior

The generated file should not change/remove any of the interpolation values, i.e. {value}.

Files

N/A

Additional context

N/A

Describe the bug
If I run script to convert android xml to iOS Localizable.strings I have double quotes:

Android source:
"Incorrect id"

Actual results:
"incorrect_id" = ""Incorrect id.";

Expect results:
"incorrect_id" = "Incorrect id. ";

To Reproduce

ANDROID_EN="app/src/main/res/external/strings/values/strings.xml"
iOS_EN="/Base.lproj/Localizable.strings"

ANDROID_TO_iOS=( "--srcFormat=xml" "--targetFormat=ios-strings" "--service=sync-without-translate" "--cacheDir=android")

attranslate "${ANDROID_TO_iOS[@]}" --srcFile=$ANDROID_EN --targetFile=$iOS_EN --srcLng="en" --targetLng="en"

Expected behavior
Expect results:
"incorrect_id" = "Incorrect id. ";

Users of attranslate have nothing to worry about.
attranslate can still be used in any closed-source-projects.

However, if attranslate itself is modified, then those modifications must become opensource under the Gnu-GPL.

By default, attranslate deletes all stale translations in target-files. This is fine because it helps to keep translation-files in sync.

However, if you set the option --deleteStale=false, then the outcome depends on the exact target file format.
For JSON targets and some other target formats, stale translations will remain as is.
But for yaml and xml targets, the --deleteStale flag will be completely ignored.

https://github.com/diversen/simple-php-translation

that is working good, but havent options and arguments like yours

Describe the bug
Currently when translating JSON files from source to target, it converts any arrays inside the source JSON files to object representations of such like so from:

"address": {
    "lines": [
        "Line 1",
        "Line 2",
        "Line 3"
    ]
},

to

"address": {
  "lines": {
    "0": "Line 1",
    "1": "Line 2",
    "2": "Line 3"
  }
},

To Reproduce

1. Create a new source JSON file containing an array
2. Convert the JSON file to another language

Expected behavior
The expected behavior would be that the datatype stays the same.

Files
This could be done using any simple JSON file containing the above example content.

Additional context
N/A

https://gist.github.com/0b4ecd4380f47794c6f5a04f54d85325

attranslate --srcFile=wp-erp/i18n/languages/erp.pot --srcLng=en --srcFormat=po --targetFile=wp-erp/i18n/languages/erp-es.pot --targetLng=es --targetFormat=po --service=google-translate --serviceConfig=traducciones-352415-79659df1c6f1.json

and show me this

Bypass 7129 strings because they are empty...
Invoke 'google-translate' from 'en' to 'es' with 11 inputs...
Add 7140 new translations
Write target '/root/attranslate/wp-erp/i18n/languages/erp-es.pot'

https://gist.github.com/1b715430007ff5aec99af3594a3b7010

tnks for your help in this one

im using before this one https://github.com/sourcecodeit/po-gtranslator

Babelish is one of the role models for CSV support: https://github.com/netbe/Babelish
Major use cases are Google Docs and Microsoft Excel.

Describe the feature

Support FormatJS ICU Messages Format

Example https://formatjs.io/docs/react-intl/components#formattedmessage

Source (flat-json, icu, en)

{
  "active_value": "{value, select, true {active} false {inactive} other {INVALID_ACTIVE}}",
}

What Happens now (current attranslate behavior) [target lang de]

{
    "active_value": "{value, select, true {active} falsch {inaktiv} andere {unbekannt}}",
}

Desired attranslate behavior [target lang de]

{
    "active_value": "{value, select, true {active} false {inaktiv} other {unbekannt}}",
}

Basically, on FormatJS message syntax, the lib shouldn't mutate the keys that are not wrapped in inner bracelets ({})...

zero-config made it easy to use attranslate without configuring any API-keys.
However, the financial cost of zero-config was increasing rapidly over the last months.
Since I do not currently have any way of generating revenue, this cost is going to be unsustainable.
Therefore, I am shutting down zero-config and kindly request all existing users to migrate to google-translate or other serviceConfigs.

Description

Using following YAML-file definition:

users:
  welcome(String value): "Hello $value!"

Running the following script:

COMMON_ARGS=("--srcFile=$INTL_DIR/messages.i18n.yaml" "--srcLng=en" "--srcFormat=yaml" "--targetFormat=yaml" "--service=google-translate" "--serviceConfig=$SERVICE_ACCOUNT_KEY" "--cacheDir=$INTL_DIR/cache" "--overwriteOutdated=true")

attranslate "${COMMON_ARGS[@]}" --targetFile=$TRANSLATION_DIR/messages_de.i18n.yaml --targetLng=de
attranslate "${COMMON_ARGS[@]}" --targetFile=$TRANSLATION_DIR/messages_es.i18n.yaml --targetLng=es

Generates the following, correct YAML in German...

users:
  welcome(String value): "Hallo $value!"

...and the following, faulty YAML in Spanish, where the variable $value suddenly shows up as $valor:

users:
  welcome(String value): "¡Hola $valor!"

Expected behavior
The Spanish YAML should look as follows:

users:
  welcome(String value): "¡Hola $value!"

This does not work with our fork of https://github.com/Leonidas-from-XIV/node-xml2js.
It might be doable to add this functionality to the fork.
However, perhaps it would be better to migrate to a well-maintained XML-library.

I have a properly formatted en.json file translation file in the following format:

{
  "LOGIN": {
    "FORGOT_USERNAME": "Forgot your username?",
    "FORGOT_PASSWORD": "Forgot your password?",
  },
  "CUSTOMERSEARCH": {
    "CONTACT_EMAIL": "Contact Email",
    "BILLING_EMAIL": "Billing Email",
   }
}

I ran the command as:

attranslate --srcFile=en.json --srcLng=English --srcFormat=nested-json --targetFile=fr.json --targetLng=French --service=openai --serviceConfig=[my OpenAI key here] --targetFormat=nested-json

This fails with:

SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at readRawJson (C:\Users\user\AppData\Roaming\npm\node_modules\attranslate\dist\file-formats\common\managed-json.js:30:31)
at readManagedJson (C:\Users\user\AppData\Roaming\npm\node_modules\attranslate\dist\file-formats\common\managed-json.js:22:36)
at NestedJson.readTFile (C:\Users\user\AppData\Roaming\npm\node_modules\attranslate\dist\file-formats\nested-json\nested-json.js:11:57)
at readTFileCore (C:\Users\user\AppData\Roaming\npm\node_modules\attranslate\dist\core\core-util.js:43:34)
at async resolveOldTarget (C:\Users\user\AppData\Roaming\npm\node_modules\attranslate\dist\core\translate-cli.js:20:16)
at async translateCli (C:\Users\user\AppData\Roaming\npm\node_modules\attranslate\dist\core\translate-cli.js:72:23)
error: Failed to parse 'C:\Users\user\source\repos\portal\portal\src\assets\i18n\fr.json'

I assume nested-json is proper here. I tried flat-json but only get:

error: Failed to parse 'C:\Users\user\source\repos\portal\portal\src\assets\i18n\en.json' with expected format 'flat-json': Property 'LOGIN' is not a string or null

will be great have translator with IBM Watson

I have been using this tool with --service=azure but this support now seems to be removed?

Last version with Azure support seems to be v1.4.1.

For yaml files, the first line is the language code, such as 'en:'

en:
  hello: "Hello world"

The translation to another language such as 'es' creates a new file es.yml where the first line language code is still 'en:'

en:
  hello: "Hola Mundo"

It would be good if i18n-auto-translation would recognize the first line language code and update it as part of the output translated language file.

The issue is that when the first line language code is updated manually, attranslate no longer recognizes that all following sub or indented keys and their translations are existing already-translated lines if attranslate is run again for updates:

Example:

First run:

Invoke 'google-translate' from 'en' to 'es' with 1 inputs...
Add 1 new translations
Write target 'C:\Users\KG\app\config\locales\es-test.yml'

Manually edit first line language code to es:

es:
  hello: "Hola Mundo"

Expected on second run with edited existing file es-test.yml:

Target is up-to-date: '.\config\locales\es-test.yml'

Actual:

Invoke 'google-translate' from 'en' to 'es' with 1 inputs...
Add 1 new translations
Delete 1 stale translations
Write target 'C:\Users\KG\app\config\locales\es-test.yml'

Please advise how I can handle yaml file updates, thanks.

File to translate
https://gist.github.com/164b623aadc5c2442005d5342f3c9c6b

root@ubuntu20portatil:~/attranslate# attranslate --srcFile=general.yml --srcLng=en --srcFormat=yaml --targetFile=general-es.yml --targetLng=es --targetFormat=yaml --service=azure --serviceConfig=blablablabla

Bypass 1 strings because they are empty...
Invoke 'azure' from 'en' to 'es' with 727 inputs...
An error occurred:
Azure Translation failed: {"error":{"code":401000,"message":"The request is not authorized because credentials are missing or invalid."}}
Error: Azure Translation failed: {"error":{"code":401000,"message":"The request is not authorized because credentials are missing or invalid."}}
    at AzureTranslator.translateBatch (/usr/local/lib/node_modules/attranslate/dist/services/azure-translator.js:26:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
    at async AzureTranslator.translateStrings (/usr/local/lib/node_modules/attranslate/dist/services/azure-translator.js:40:25)
    at async runTranslationService (/usr/local/lib/node_modules/attranslate/dist/core/invoke-translation-service.js:62:24)
    at async invokeTranslationService (/usr/local/lib/node_modules/attranslate/dist/core/invoke-translation-service.js:29:28)
    at async translateCore (/usr/local/lib/node_modules/attranslate/dist/core/translate-core.js:106:29)
    at async translateCli (/usr/local/lib/node_modules/attranslate/dist/core/translate-cli.js:84:20)

may be need to config region with any command?

attranslate set --key blablablabla
attranslate  set --region eastus

greetings

Describe the bug
I get an UNAUTHENTICATED error, despite having registered for Google Cloud Translate API and getting a key. I suspect my json file has the wrong structure.

To Reproduce
A description of what the bug is. When I attempt to run the script below

#!/bin/bash
set -e # abort on errors

# This example translates an english JSON-file into spanish, chinese and german. It uses Google Cloud Translate.
BASE_DIR="static/locales"
SERVICE_ACCOUNT_KEY="gcloud_translation_key.json"
COMMON_ARGS=( "--srcLng=en" "--srcFormat=nested-json" "--targetFormat=nested-json" "--service=google-translate" "--serviceConfig=$SERVICE_ACCOUNT_KEY" )

# install attranslate if it is not installed yet
attranslate --version || npm install -g attranslate

attranslate --srcFile=$BASE_DIR/en/translation.json --targetFile=$BASE_DIR/de/translation.json --targetLng=de "${COMMON_ARGS[@]}"

I get the following error

1.8.1
Invoke 'google-translate' from 'en' to 'de' with 8 inputs...
An error occurred:
16 UNAUTHENTICATED: Failed to retrieve auth metadata with error: key must be a string, a buffer or an object
Error: 16 UNAUTHENTICATED: Failed to retrieve auth metadata with error: key must be a string, a buffer or an object

I suspect it is because my gcloud_translation_key.json file is malformed

{
  "key": "<the key I got from 'Enable APIs and services' on GCloud for translation>",
  "project_id": "<my project id>"
}

Expected behavior
I expect the translated files to be output.

Files
I've added the script and config I use inline.

Additional context
Nothing else.

Thank you in advance for your help.

Will be great if you add .TS files for translate...

https://github.com/statisticssweden/PxWeb/blob/master/PXWeb/Resources/Languages/pxlang.xml

attranslate --srcFile=pxlang.xml --srcLng=en --srcFormat=xml --targetFile=pxlang-es.xml --targetLng=es --targetFormat=xml --service=google-translate --serviceConfig=traducciones-352415-79659df1c6f1.json


Bypass 1285 strings because they are empty...
Add 1285 new translations
Write target '/root/attranslate/pxlang-es.xml'

how can solve this?