Currently, the best format to import and export is XAML, as it directly reflects our document structure. All other formats require some kind of processing, while XAML is directly imported as RadDocument. In this light, the preferred flow in your scenario would be editing with RadRichTextBox, saving as XAML and displaying that XAML in a RadBook. As for the other formats:
a) HTML is a very complicated standard and we currently don't support some parts of it, so authoring documents in another application and importing in in RadRichTextBox is not expected to provide the best results.
b) We support importing from DOCX, but unfortunately we still don't have an implementation for tables. Bullets and formatting are present and working. The support is limited, though, and some docx data might be lost when reading/writing documents with DocxFormatProvider.
c) PDF is not designed as a format for documents in the classic sense, but rather for print-ready documents. Because of this, unfortunately, we have postponed import from PDF for a later stage.
d) As I elaborated above, XAML is the preferred format for exporting and importing and should provide the best results.
All the best,
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items