lokalise-cli-2-go icon indicating copy to clipboard operation
lokalise-cli-2-go copied to clipboard

Wrong language mapping for Hebrew (he) in xml format

Open alikaragoz opened this issue 2 years ago • 3 comments

👋 Hello We are in the process of migrating from our previous service to Lokalise and when using the CLI we are encountering a weird behavior.

When running the command below the exported file for Hebrew ,which lang iso is normally he, is changed to iw; which seems to be the old code for Hebrew. This only happens when exporting in xml format (no issues with strings format`)

I've tried using the --language-mapping but it does not work.

The result we get: app/src/main/res/values-iw/strings.xml The result we expect: app/src/main/res/values-he/strings.xml

../bin/lokalise2 file download \
        --token \"LOKALIZE_TOKEN\" \
        --project-id \"LOKALIZE_PROJECT_ID\" \
        --export-empty-as skip \
        --export-sort a_z \
        --format xml \
        --unzip-to \"../app/src/main/res\" \
        --original-filenames=true \
        --language-mapping '[ \
            {\"original_language_iso\" : \"zh_Hans\", \"custom_language_iso\" : \"zh-rCN\"}, \
            {\"original_language_iso\" : \"zh_Hant\", \"custom_language_iso\" : \"zh-rTW\"}, \
            {\"original_language_iso\" : \"es_419\", \"custom_language_iso\" : \"es-rUS\"} \
          ]' \
        --replace-breaks \
        --include-description=false \
        --include-comments=false \
        --placeholder-format=printf \
        --indentation 4sp

On the Lokalize interface the code is the correct one: image

I can temporarily bypass the issue by moving the file to the correct location after the download but that's not robust.

There is probably a bug somewhere and do you guys know a workaround for this? 🙏

alikaragoz avatar Apr 13 '22 08:04 alikaragoz

Hey, @andrewLab-lokalise is this a bug or something we are not doing well? 🙏

alikaragoz avatar May 05 '22 07:05 alikaragoz

Hey, @alikaragoz! Could you please contact the Lokalise support directly on the topic. They might help to resolve this in timely manner.

andrewLab-lokalise avatar May 05 '22 08:05 andrewLab-lokalise

@andrewLab-lokalise thank you for the suggestion, and sorry I thought this was the right way to report issues. I will contact the support.

alikaragoz avatar May 05 '22 09:05 alikaragoz