Some classes have Strings that aren’t wrapped with the TRANS() macro. Mind adding it to them?
Where I’ve noticed that needs it:
AudioProcessorGraph::AudioGraphIOProcessor’s “name”-related methods[/][/list]
Most of those: no… I don’t think it’s appropriate for an audio driver to have to worry about translations, and there could even be code out there which relies on the names they return. Perhaps the UI that displays the names should be the place where it gets translated?
I guess… Just figured it would be simpler to have translations be part of the lowest level of things possible.