All fonts which are the sub font style of a font family in c:\windows\fonts are not able to set to bold or italic( bold/Italic are not shown in richtextbox but when exported to word, they are showing correctly). Is there any solution on it?
Some examples: Arial Black, Arial Narrow, Bodoni MT Black, Bodoni MT Condensed,Calibri Light, Franklin Gothic Medium, ...
8 Answers, 1 is accepted

I have compared RadRichTextBox with the WPF RichTextBox behavior when displaying bold, italic etc. on the mentioned font families and the behavior is the same.
About your second question, the font "Arial Narrow" is already registered. Please take a look at the attached screenshot from our demos. Also, I exported and then imported the document and the text is still there.
Please have in mind that the RadRichTextBox will initially show all fonts that are installed on the operation system.
Regards,
Boyko
Telerik by Progress

Not all font families allow , italic, etc. to be applied to them. You could compare RadRichTextBox with the WPF RichTextBox behavior when displaying bold, italic etc. on the mentioned font families and the behavior is the same. I confirm that everything works as expected.
Regards,
Boyko
Telerik by Progress

As to our notion, the issue with the font styles is related to the WPF framework. RadRichTextBox is built and dependent on that framework, so I am afraid that there is not much we can do in this case. What are the applications you mentioned that work properly? Are they WPF applications or are different?
The public item you have encountered is related to the Document Processing libraries. These components are independent of platform and don't have UI. Therefore, the nature of the issue in this context is different.
Regards,
Tanya
Telerik by Progress

From my research on the net I thought the PDF problem was related to the richtextbox problemand since I read that defect was fixed I thought the text box problem was also fixed. Also, all the apps I tried worked fine but they are Microsoft apps (Word, Wordpad, OneNote) and it seems they have internal workaround but for whatever reason aren't fixing the problem in WPF even though it's a know issue since 2008. Sorry for the confusion.
Yes, both issues seem related, but actually are pretty different when it comes to the implementation, so it is possible to confuse them. The Microsoft applications are working as expected with those fonts, however, their internal implementation is different and doesn't utilize the WPF platform so we cannot compare the applications in this specific case.
Regards,
Tanya
Telerik by Progress