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
Parents

  • 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.

Comment

  • 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.

Children
No Data