Dear Team,

when I create a pdf with your components (RadFixedDocument, RadFixedPage, FixedContentEditor) I cannot add a "german umlaut" in that report because then it cannot be viewed in your own pdfviewer- control (the exception is: Error loading document: Position is out of range).

I tried to solve this in "creating/ loading" arial.ttf as external font (even this is weird as idea), but this also did not work.

What is your solution for that?

I bought the Telerik components basically for PDF processing, this simply needs to work...

Many thanks for an urgent update on that!

Best regards

Tobias

OpenDocument Format is an open format for many software supported like OpenOffice, I hope the Telerik Document Processing libraries could support for import/export format.

Based on how Excel works, VLookup doesn't need to be sorted, if the 4th parameter is FALSE.  The 4th Parameter determines whether an approximate search is used or an exact match is used.  by default true is used and an approximate search requires a sorted range.  However, if set to FALSE,  then the range doesn't need to be sorted.  the value is checked against the entire column of cells and can be unsorted. 

We process spreadsheets that use VLOOKUP with 4th parameter set to FALSE and unsorted data in range.  These work in Excel, but not in Telerik Spreadsheet processing.

thanks, 

Even without flattening the form the Barcode font gets lost.

Noticed that manually setting the font using the font name with spaces seems to work.

Other custom fonts on our form appear to work, however the Free 3 of 9 does not.

Attached a project to demonstrate some issues we're seeing that need resolving in order to use the component.

1. When using a font like Tahoma on a form field, the value no longer displays or contains garbled text.

2. Input file is 24KB, output is 2MB!

3. Rotated field lose their rotation after being flattened.

4. Simulate merging with other files, 100 times the file is now 150MB! It's as though it's not re-using the fonts, but keeps adding the same ones.

5. when merging, but not flattening, the form fields are all lost on pages after page 1

Allow to export the documents to image.

Being able to generate a thumbnail for example.

The value of the TextBoxField is not visible until the field is clicked.

Workaround: Force content update:

foreach (var widget in textBoxField.Widgets)
{
    widget.RecalculateContent();
}

If the update still doesn't fix the issue, change the font prior to setting the value of the field:

foreach (var widget in textBoxField.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}

I'm trying to use RadWordsProcessing

to replace text in .docx documents.

when i try to open a document i have an error:

BadImageFormatException: Could not load file or assembly 'PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Reference assemblies should not be loaded for execution.  They can only be loaded in the Reflection-only loader context. (0x80131058)

We would like to have image formats like JPG, PNG and TIFF supported in addition to the PDF and Office document support in DPL.

The NuGet packages don't differ .Net Core projects from .Net Core with Desktop Compatibility Pack. This leads to incorrect resolving of the dependencies and the .Net Core projects targeting .Net Core 3.0 cannot be built.

Workaround: An option applicable for all the libraries is to extract the assemblies from the .nupkg files. For PdfProcessing and ZipLibrary you can use the assemblies directly from the pdfviewer installation folder.

I'm working on a project that has a service component that will be generating Excel xlsx documents for distribution.  While there is a UI for administrative tasks, the service itself will run without an interface.  I'm using the Documents.Core, and several other associated libraries to accomplish this.  Two issues I've encountered, one is setting up the project with the appropriate libraries and keeping the version in sync with the Admin application, second is protecting those libraries once they are packaged for release.  I had a support ticket open to determine how to accomplish the latter, but the first is still a manual issue.  

So the feature request is to include the ability in the project templates and/or Convert to Telerik WPF Application to support a headless document solution.  It would ideally include (only) the required libraries and maintain their linkage to the appropriate library version with the rest of the solution which occurs with a full Telerik WPF UI app.  It would also include the necessary boilerplate code and references to properly protect the libraries.  I was referred to another feedback request on improving the overall library protection build process, but while related, what I'm asking for here is not exactly the same.