Not Considering

Not considering as this should be filed as a bug report.

Support OTF fonts in the Studio editor

It would be great if the Studio Editor could also have support for OTF fonts. Currently, if you have such a font installed and it's used in a file you're translating, then the characters are garbled:

You can change the setting of File > Options > Editor > Sidy-by-side Editor to "Show all tags but do not show formatting" to see the characters as a workaround. This removes all formatting though so you end up turning this option off and on whenever you have to open a document that uses OTF fonts.

SDL Support suggested to use True Type Fonts (TTF) instead. Of course that would work but the reality is that translators just have to deal with whatever documents they receive for translation and that includes documents with Open Type fonts.

  • Hard to believe but true: Windows never delivered a font component and editing component that was good enough for us to use so we had to come up with our own extension mechanisms to support localization matters well (such as the semi-WYSIWYG). Those mechanisms are of course based on the Windows tech stack. In any event, we have tried other Open Type fonts such as "Sikta Display" which work just well. So whenever we see this, typically the fonts are just buggy. See also gateway.sdl.com/.../communityknowledge.

  • It's somehow hard to believe that SDL would be using own font management instead of using the Windows built-in one... which DOES support OpenType fonts of course.

  • Thanks Rian - I have asked the support team to work with you to get a bug report logged, rather than treat this as an idea here. BTW it might also be possible to use a converter to convert OTF to TTF - see here for instance - everythingfonts.com/otf-to-ttf - maybe this will help also. I am setting the idea to "not planned" for now, which just means it's not treated as an enhancement request, and we can  then see if we can take a look at the bug report in future.

  • Hi Daniel, I've seen a few fonts I received from our customer that show this behaviour. I didn't really test any further because Support said "Open Type Fonts are not supported by us". If you can tell me where I can find OTF fonts that are well programmed, then I can test. BTW I did file this first as a bug with support but they suggested I post the idea here. Please do feel free to file a bug and let me know the bug number...

  • Hi Rien, is this happening with all OTF fonts, or just some? I believe we have only seen that with poorly programmed fonts in the past, but I am not 100% sure. Thanks, Daniel

    PS: Also, this might be more of a bug report than an idea...