Support for shouldTranslate in xcstrings format

File Formats (Import/Export)
1

Is Crowdin supposed to be supporting the "shouldTranslate": false attribute in an xcstrings file? I just modified an xcstrings file to include these and updated the file on the Crowdin website, but these strings are still visible to translators.

FWIW, I haven’t found any documentation of what the xcstrings schema looks like, but you can add this UI in XCode by right- or ctrl- clicking on a string in an xcstrings file and choosing Mark as "Don't Translate".

2

Hi @kueda , you’re welcome to check the currently supported fields and .xcstrings file sample by the following link:

3

There is nothing on that page about the shouldTranslate attribute. If you don’t support it, then please consider this a request for this feature: if "shouldTranslate: false is present, the string should be hidden from translators on Crowdin.

4

Hi @kueda

Many thanks for your suggestion, we’ll consider this for sure.

The internal task 51579 is added to our product improvement roadmap.

1 Like
5

This seems to be supported now. However, Crowdin puts the key at a different position than Xcode does, which leads to unnecessary diffs when importing translated files from Crowdin.

Xcode:

    "RHN-51-qgk.title" : {
      "comment" : "Class = \"NSTextFieldCell\"; title = \"Folder Name\"; ObjectID = \"RHN-51-qgk\";",
      "extractionState" : "extracted_with_value",
      "localizations" : {
        ...
      },
      "shouldTranslate" : false
    },

Crowdin:

    "RHN-51-qgk.title" : {
      "comment" : "Class = \"NSTextFieldCell\"; title = \"Folder Name\"; ObjectID = \"RHN-51-qgk\";",
      "shouldTranslate" : false,
      "extractionState" : "extracted_with_value",
      "localizations" : {
        ...
      }
    },
6

Hi @Eitot ,

This has indeed been supported in XCStringCatalog for some time already. Regarding the key positioning in the file — let me forward this to our development team for review. We’ll keep you posted as soon as we have any updates!

7

Hi @Eitot!

Just a quick update here:
We have created the task for our devs’ team to preserve the same order as Xcode does. Once it’s completed - we’ll notify you additionally.