Idea Delivered

This has been delivered in the XML2 version of the file type that ships with Studio 2019 SR2 released on 1 August. Be aware, however, that this is still a beta version at the time of writing (2 August 2019) and there are known issues with it (see Studio 2019 SR2 release notes), for example when it comes to converting entities in embedded content. But you should already be able to test this new capability - just in files without embedded content for now. We are planning to update the XML2 file type again with the next cumulative update for Studio, in the meantime any and all feedback is welcome.

Separate reader and writer settings for all XML/HTML entities

It would be good if in a future version of Studio, users would have the possibility to define separate reader and writer rules for named entities in XML / HTML files, but not only of the 5 default XML entities 'lt', 'gt', 'quot', 'apos' and 'amp', but also for all other named entities like 'nbsp' or 'uuml'.
This way, users would avoid enabling and disabling "Enable entity conversion" back and forth between "Convert to Translatable Format" and "Generate Target Translations", which is both a waste of time and a source of errors.

Ideally these writer settings should give the user the flexibility to select between plain Unicode character, named entity like 'nbsp' and numerical character reference like '#160' for each character defined, or for a range of characters like from #128-#64260.

 

Frank Lempp