Idea Delivered Partially

Capture string IDs as Document Structure for software filetypes

I loved seeing that string IDs were captured from Passolo SDLXLIFFs as Document Structure, although it would be a great help to be able to create a REGEX filter for string IDs (currently only 'ID' is displayed and users can only filter for 'ID').

I wonder now about the possibility of capturing string IDs directly in Studio for software filetypes such as JSON, properties, and RESX. This doesn't seem like it would be a major overhaul to the parsers.

Idea 1: instead of simply showing 'ID' with Passolo SDLXLIFFs, show the actual string ID. Make this filterable through Advanced Display Filter

Idea 2: capture string IDs as Document Structure for software filetypes: .properties, .resx, .JSON

Luke Hipsher

  • Ideally, this should allow for any part of the source document to be used as document structure to provide context. A RESX file which is XML also can provide that information as well as JSON, et cetera. Why not make this adaptable for all file types?

  • Ydes, definitly a must for UI translators to have the string IDs! Idead 1 would definitly be the better one! And also: Make that field editable (i.e. allow for coying the string ID), for example in case of questions etc.... At least in the  DSI viewer  this could be done independent of the other change...

  • in reply to Volker Uffelmann

    DSI viewer, of course. Document Structure Information.

  • We helped ourselves by adding a

    <context-group purpose="information">
          <context context-type="elementtitle">some.unique.key</context>
    </context-group>

    to the <trans-unit>s in our XLIFF file (which is generated from all the various soure file formats in our company).

    Using the SDI-Viewer plugin we now see both key AND comment for the current string.
    And with the Community Advanced Display Filter plugin the keys can even be filtered.
    So, mission accomplished.

    Duplicating stuff in the source file is a bit of a crude duct tape fix for sure, but now our LSPs and we are able to get our work done. :)

  • Idea 1 would be very helpful for me because I NEED to filter strings by their actual ID they have in the software. This is crucial for localization management. As long as I do not have this feature, I need a second/third tool that allows me to manage my complete string base. In daily business, I need to filter literally and by Regex, as well as by actual ID, by Original, by Translation, and by translator comment.