Most libraries from Telerik Document Processing are affected after you install January 9, 2018, .NET Security and Quality Rollup (KB4055002). Applications that request a fallback font or a character that is not included in the currently selected font return the following error messages:
“FileFormatException: No FontFamily element found in FontFamilyCollection that matches current OS or greater: Win7SP1”.
Inner exception originates from: CompositeFontParser
Microsoft has released an update which fixes the issue. More information about it you can find here: Description of the Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4074880).
To keep .NET 4.7.1 installed and maintain protection against vulnerabilities that are addressed by the January security updates, uninstall the January .NET Framework Security and Quality Rollup (KB 4055002), and then install the January .NET Framework Security-Only Update (KB 4054183). To do this, follow these steps:
Roll back to the previous version of .NET Framework. To do this, follow these steps:
The documentation for the libraries included in Telerik Document Processing is available at http://docs.telerik.com/devtools/document-processing.
This week's latest resources are described below.
The content of this article is updated to describe the new properties added to the TextFragment class.
Headers and Footers
The article is introduced to describe the new feature in RadSpreadProcessing - applying headers and footers when printing a document or exporting to PDF.
A new help section that explains how you could use the new RadSpreadStreamProcessing library to achieve fast export of spreadsheet documents with minimal memory usage.
Hello! We are having an issue while using DocxFormatProvider to convert docx to RadFlowDocument. When the provider converts, it replaces all charts in the document with blank paragraphs, and we can't catch this case. (doc for example sample doc)
Not sure that this actually qualifies as a bug, but it was unexpected behavior. For unit testing I was creating an empty Workbook document and writing it to a file. It turns out, that the file is corrupt unless it has a Worksheet added to it. The XlsxFormatProvider does not issue any error and happily writes a 3k file, but Excel can't read it. Excel throws a dialog "We found a problem with some content in the 'test.xlsx'. Do you want us...". Selecting Yes eventually comes back with a "The workbook cannot be opened or repaired by Microsoft Excel because it is corrupt." message.
Simply adding a worksheet:
will allow it to create a file that Excel will handle. Again, not sure you could call this a bug, but it wasn't what I expected it to do. It might be better if the XlsxFormatProvider threw an exception for trying to write out an empty file.
At any rate, figured I throw this out there in case anyone else runs into this behavior.
I am making a catalog of pictures. During the process the user can either select on file or multiple files sorted by category.
Why would the pdf files be so much larger than the Word files? It’s usually the other way around!
I combined the individual pdf files and it became 45MB. I combined the word files and it was 37MB. I then turned the 37MB word doc into a pdf and it became 4MB. So as output from Smartview(my program) the pdf file is 45MB but generating a pdf from the word files it is 10x smaller!!!!
I have a form in a blazor web app that I need to export the content from to a pdf.
The form fields are rich textboxes that can have varying degrees of content, from single lines to who knows how many.
If I export this first to html, and then feed that html into your pdfprocesser, will it be able to automatically create as many pages as it needs or do I need to do calculations to see what will fit on a page and I create the new pages myself?
Hello, I have a project adopted from the code in the ManipulatePages example project from Telerik, the FitAndPositionMultiplePagesOnSinglePage routine to be precise.
Except instead of taking four pages and putting them on one, I'm taking two 5.5x8.5 pages and putting them on a new 11x8x5 page, left to right.
It's working great, when the input PDF is properly formatted.
I have a handful of PDFs that were created in some unknown way that appear to be malformed. When they are fed through my project, the odd pages never make it to the right side of the output. It looks like, among other things, the CropBox size isn't the same as the MediaBox size on the source doc, which I suspect is a source (maybe not THE source) of the problem.
It seems I should be able to read the content of the pages on the source doc and insert them into a new page on the output doc, instead of just copying the page from PdfFileSource.Pages to essentially rebuild the page, instead of copying the page?
However, I'm at a loss as to how to read the source page, as PdfFileSource.Pages don't seem to expose the content?
Help is appreciated! :)