Thursday, August 26, 2021

Solid Documents is now part of the PDFTron family of companies!

 

 This acquisition combines PDFTron’s world-leading digital content platform with Solid Documents’ best-in-class document reconstruction and archiving solutions.

 Learn more ->

Monday, February 13, 2017

Solid Framework 7514

In the last 6 months, we have worked on 500+ issues across all of our products.  80% of our time has been spent focusing on our Solid Framework product.

Solid Framework 7514 is now available in our Developer Portal.  We have resolved several high priority (showstopper / crash / hang) issues, related to:
-Page Range
-Generic Print Provider
-Job Processor Rendering PDF Page Collection
-Infinite loop in CLineInfo::correctCharSpacings()
-Conversions with JBIG2DECODE

New features:
Tesseract OCR for CJK content
Solid Core Model API - Text Bounding
C++ Sample - Extract Text using Text Bounding
PDF to Word - Annotations to Word comments
Support for Superscript and Subscript content

We have made various improvements and bug fixes to:
-Conversion layout and fonts
-Rendering
-Table detection and merging
-Lists and bullets
-Scanned page detection
-Performance
-CGM/NSE improvements
-OCR

Log into your developer portal account to access the latest SDK. If you don't have an account, create one on our website.

Wednesday, March 9, 2016

C++ Sample Project using Solid Framework SDK

With Solid Framework C++ SDK you can integrate the same PDF to Word technology used in Adobe® Acrobat® into your product for as little as a 10 MB increase in your installer size.

These C++ sample applications are available as ready-to-build Visual Studio projects and also as ready-to-run downloadable MSI installers. In both cases the samples work with developer licenses that you can generate using our self-service Developer Portal. In addition, the ready-to-run samples will also work with regular Solid PDF Tools desktop licenses (contact sales@soliddocuments.com for a reviewer license).


C++ sample is on our SDK documentation page along with other sample projects to get you going.

Solid Framework comes in two editions: a tools version and a professional version and is immediately available for download. Pricing for internal use of the professional version of the SDK starts at $1500/year. Licensing is also available for public redistribution. Licensing, distribution and product feature information is available at: http://www.solidframework.net/

Tuesday, November 10, 2015

Solid Framework - v9.1 build 6068

v9.1 build 6068 of Solid Framework Released


We have released an update to the Solid Framework SDK. A few of the highlights include:

- OCR Performance Improvements

- Reduced XML Complexity for .DOCX.



While this work was done primarily to help Apple software open .DOCX files, this improvement is also beneficial for making .DOCX output more editable.

- Vector Text and Graphics Conversion Work


- General PDF conversion quality improvements

The SDK is available from the developer portal.

Monday, December 15, 2014

Extracting Solid Framework for Installations.

Solid Framework is designed to extract its support files to the current users %AppData% directory on load. This is convenient, as there is only one dll to manage in your installer. But sometimes this can cause issues. One issue that can arise is a sporadic issue with overzealous 3rd party malware applications deleting the support files in the %AppData% folder, even though they are signed, strong named and time stamped. To work around this, you can extract the support files beforehand and reference these files in your installer.


To extract the 32 and 64 bit support folders from Solid Framework, you use the ExtractFramework.exe tool. Download the tool and SolidFramework AnyCPU dll into a folder. On the command line, run “ExtractFramework.exe .\SolidFramework.dll <Extraction folder> All”. <Extraction folder> should be replaced with a directory of your choosing. 



The All parameter tells ExtractFramework.exe to extract both the 32 and 64 bit folders. If you are releasing a 32 bit, or 64 bit only application, you can use Win32 or Win64 in place of All. 


We include both Win32 and Win64 folders in our installers. During installation, we detect if the OS is 32 or 64 bit, and install the appropriate folder to the application’s program directory. Do not include the larger SolidFramework AnyCPU dll in your install, because a smaller, 32 or 64 bit version is included in the Win32 or Win64 folders that will be installed in the application’s program directory that satisfies the application’s reference to SolidFramework.dll.



Wednesday, August 6, 2014

v9.1 build 5015 of Solid Framework Released

We have just released an update to the Solid Framework SDK. A few of the highlights include:
  • Improved rendering
  • OCR improvements to French, German and Russian language
  • Improved OCR support for san-serif high aspect ratio fixed pitch fonts
  • Better table detection and conversion
  • Improved font scaling
  • Improved image processing
The SDK is available from the developer portal.

Wednesday, June 11, 2014

New release of Solid Framework v9 Available

v9 build 4823 of Solid Framework Released
We have just released a major update to the Solid Framework SDK. A few of the highlights include:
  • Multi-processor parallel performance improvements with OCR (scanned PDF to Word, scanned PDF to PDF/A)
  • Less complex XML output for .DOCX which improves machine consumption of output and improves editing of Word documents
  • Many PDF to Microsoft Word, Powerpoint, Excel and text conversion improvements
  • Complex table reconstruction improvements
  • Data recovery from scanned PDFs into Microsoft Excel
The SDK is available from the developer portal.

Sunday, December 1, 2013

Eating our own dog food ...

Eating your own dog food, also called dogfooding, is slang used to reference a scenario in which a company uses its own technology to demonstrate the quality and capabilities of the product.

All our v8 applications are built using Solid Framework.

The v8 rewrite was a conscious shift back to our core features: a focus on document reconstruction functionality. The rewrite was required to take advantage of 64-bit architectures and multi-core processors. A rewrite using Microsoft .NET was required so that we could engineer the product using our own Solid Framework SDK (unlike the older products which were based on legacy architecture).

We have confidence that our .NET Solid Framework SDK is the best document reconstruction SDK available on the market. We have built our latest desktop and batch solutions using this technology.

You can use Solid Framework with confidence too. Create a developer portal account and get started today.



Tuesday, November 5, 2013

Solid Framework 8.2.4053 Available

New release of Solid Framework SDK is available from the developer portal.

Wednesday, May 22, 2013

Solid Framework 8.1.3544

Solid Framework Update available: 8.1.3544.

Access dlls from the developer portal.

Friday, September 21, 2012

7.3 of Solid Framework Released

7.3 of Solid Framework Released

Solid OCR (Optical Character Recognition) has been improved:
8 languages now supported (English, Dutch, French, Italian, Polish, Portuguese and Spanish).
Improved text recognitions. OCR allows you to apply a searchable text layer when scanning or easily add a text layer to an existing scanned PDF file.

Other v7.3 improvements include:

  • PDF to Word: heading/style detection, table of contents reconstruction, hierarchical list reconstruction
  • Complete rework of PDF to PowerPoint reconstruction including transitions, master slides and PowerPoint specific layout engine
  • Great improvements to PDF to HTML conversion to take advantage of table of contents reconstruction and style detection. Single page output with navigation frame or multiple linked HTML pages for navigation.
  • PagesModel and Thumbnail Controls to allow construction of PDF page manipulation applications complete with User Interface.
Trial developer licenses and SDK available from the Developer Portal at soliddocuments.com.

Sunday, September 2, 2012

How to change the configuration in your project to 64 bits

This example uses Visual Studio 2010.

1. Open your project in Visual Studio.  From the Build menu select Configuration Manager...


2. From the Active solution configuration menu select Debug or Release depending on what are you want to set up.


Then from the Active solution platform menu select New...
 

3. Select x64 (the Create new project platforms is checked by default).


4. Change the Copy settings from option to  Empty then click OK.

Wednesday, August 29, 2012

Code Samples and Video Tutorials

Did you know we now have Solid Framework video tutorials available from our website?

You can find them here under our documentation page.

Email us at support@soliddocuments.com to request other code samples.

Monday, November 15, 2010

Adobe Licenses Solid Document Technology for Acrobat X

Adobe Systems Incorporated (Adobe) has licensed Solid Framework SDK for Adobe® Acrobat® X. Adobe Acrobat X takes advantage of Solid Documents’ PDF to Word and Excel conversion capabilities, allowing Acrobat X users to easily reuse and repurpose PDF content.

Read the press release here.

Recent rave reviews for Solid Framework’s core conversion features in the new Adobe Acrobat X:

Ed Mendelson of PC Magazine:
http://www.pcmag.com/article2/0,2817,2370981,00.asp

Darryl K. Taft of eWeek:
http://www.eweek.com/c/a/Application-Development/Adobe-Acrobat-X-10-Reasons-to-Move-to-It-Now-179555/

Alan Stafford of PC World:
http://www.pcworld.com/reviews/product/707770/review/acrobat_x_pro.html

PDF for Lawyers:
http://www.pdfforlawyers.com/2010/10/improved-export-to-word-in-acrobat-x.html
http://www.pdfforlawyers.com/2010/10/adobe-announces-acrobat-10-my-quick-review.html

Steven Kovach of Business Insider:
http://www.businessinsider.com/hands-on-with-adobe-acrobat-x-pro-2010-11

Wednesday, July 28, 2010

New 7.0 of Solid Framework Released

Newest version enhances conversion and reconstruction features; Gives developers power to build applications for the creation, modification and conversion of PDF files within 64-bit native environment.

See full press release here.

Saturday, December 5, 2009

Solid Framework updated with new Installer and ProgressTicker classes.

We've released a new version of Solid Framework SDK 6.0.255.0. This build addresses a couple issues:

  1. PdfPage.DrawBitmap always adds a watermark regardless of the license. It now properly disables the watermark if the license is a non free version.
  2. When converting Pdf pages to image files, the first page is blank. The GDI+ module is now loaded before the page drawing starts.
  3. Extraction of the support files is now faster because we are using memory streams instead of file streams.

This version also includes the new Configuration.Installer class, that we will talk about today in this blog post. With this class Solid Framework can be installed in one of three ways:

  1. Self extraction to the current users local application data folder.
  2. Self extraction to a folder handed to the Installer class.
  3. Pre extraction.

The first method is the default method that the previous versions of Solid Framework has been using. When the application calls one of the Solid Framework methods, it will check to see if the support files have been extracted to the current users application data folder, and if it has not, it will extract it at this point.


The second method allows these support files to be extracted to any folder the developer wishes. Before any Solid Framework method is called, the developer can set the Configuration.Installer.NativePlatformDirectory string property to a full path, and that path will be used as the root folder for the support files. This is useful if you want to share the support folder between many users and don't want each user to have their own copy of the support files, or you wish to remove this known folder location during an uninstall.


The third method is to use the ExtractFramework tool to extract the support files from Solid Framework beforehand and install them to a folder you want in your application installer. You have to let the Framework know where these files are by setting the Configuration.Installer.NativePlatformDirectory string property in the application. This gives the developer total control during the install and uninstall.


Another feature of this release is the ProgressTicker event class. You can register for this event to show progress UI while Solid Framework is extracting the support files (if needed).


The default for ProgressTicker is 50 ticks for the extraction. This tick value can be set to any value you wish by setting the TicksPerEpisode property off the ProgressTicker to any integer value. This also enables feedback in console applications, which didn't work in previous versions of Solid Framework, that needed a Windows message pump to work.


The extraction tool link above uses this feature to show feedback of the extraction. Source code for the ExtractFramework tool is included, it shows you how ProgressTicker works. Both Visual Studio 2005 and Visual Studio 2008 projects are included in the package.

Thursday, November 19, 2009

New Solid Framework released

We have released a new version (6.0.251) of Solid Framework SDK that now includes full support for image processing and optical text recognition to allow conversion of scanned PDF files to editable Word documents. Solid Framework takes advantage of the MODI API (part of Microsoft Office) to provide OCR capability.

When converting PDF to Office documents, you can specify when OCR is used by setting the TextRecoveryType:







To one of the following settings:











Always - All pages are rendered to images and processed as scanned pages.

Automatic - Pages that contain scanned text-like images are recognized automatically.

Default - Same as Automatic.

Never - No scanned page processing. Scanned pages converted as images.

Friday, September 4, 2009

Convert PDF pages to Image files

Another comment question we get in email is if Solid Framework can convert PDF pages into image files. Solid Framework can be used to convert PDF pages into image files, and we use this feature to create page thumbnail images and the main page view for PDF Navigator. Here is a diagram of how this works:


You can download the sample project [zip file] to see this in action yourself. The project contains both Visual Studio 2005 and Visual Studio 2008 solutions. Those without Microsoft Visual Studio can use Visual C# 2008 Express Edition for free to work with the sample project.

Earlier we talked about using a C# class library to allow you to use the scripting functionality of Solid PDF Tools Scan to PDF from the command line. We use this class again to parse out the command line arguments we need to convert the pages into image files:


  Arguments CommandLine = new Arguments(args);‍
  if (CommandLine["f"] == null)‍
  {
    ShowUsage();‍
    return -1;
  }‍
  else
    pdfFile = CommandLine["f"];‍

  if (CommandLine["p"] != null)‍
    password = CommandLine["p"];

‍  if (CommandLine["o"] == null)
  {‍
    ShowUsage();
    return -2;‍
  }
  else‍
    outputfolder = CommandLine["o"];

‍  // Note: We default to 96 dpi if the parameter was not provided.
  if (CommandLine["d"] != null)‍
    dpi = Convert.ToInt32(CommandLine["d"]);
‍
  if (CommandLine["t"] != null)
  {‍
    switch (CommandLine["t"].ToUpper())
    {‍
      case "TIF":
      case "TIFF":‍
        imagetype = ImageType.TIFF;
        break;‍
      case "BMP":
        imagetype = ImageType.BMP;‍
        break;
      case "JPEG":‍
      case "JPG":
        imagetype = ImageType.JPG; ‍
      break;
      case "PNG":‍
      default:
        imagetype = ImageType.PNG;‍
        break;
    }‍
  }
‍
  if (CommandLine["r"] != null)
  {‍
    pagerange = CommandLine["r"];
  }‍

  DoConversion(pdfFile, password, outputfolder, dpi, pagerange, imagetype);‍

The code above takes care of setting up the arguments to hand off to DoConversion. So lets say we have a pdf file at c:\mypdfs\pdftest.pdf that is encrypted with a user password of "mypassword" and we want to make JPEG images of pages 1-5, 7, 8 with a dpi of 127 and put these images in c:\myimages. The commandline would look like this:

PDFtoImage.exe -f:c:\mypdfs\pdftest.pdf -p:mypassword -o:c:\myimages -d:127
-t:JPG -r:1-5,7,8


Note: -p -d -t and -r are optional. No password is used if -p is missing. DPI will default to 96, and image type will default to PNG. If -r is missing, all pages will be used to make images.

The DoConversion function is the meat of the project. First we set the trial license:

  // Setup the license
  SolidFramework.License.ActivateDeveloperLicense();

It then loads the PDF file with password if supplied:

  // Load up the document
  SolidFramework.Pdf.PdfDocument doc =
    new SolidFramework.Pdf.PdfDocument(file, password);

  doc.Open();

After the document is open, we check to see if the output folder exists, and if it doesn't, we create it:

  // Setup the outputfolder
  if (!Directory.Exists(folder))
  {
    Directory.CreateDirectory(folder);
  }
  // Setup the file string.
  string filename = folder + Path.DirectorySeparatorChar +
    Path.GetFileNameWithoutExtension(file);

Now walk the Pages dictionary and finds the page items by following the references.

  // Get our pages.
  List<SolidFramework.Pdf.Plumbing.PdfPage> Pages =
    new List<SolidFramework.Pdf.Plumbing.PdfPage>(doc.Catalog.Pages.PageCount);

  SolidFramework.Pdf.Catalog catalog =
    (SolidFramework.Pdf.Catalog)SolidFramework.Pdf.Catalog.Create(doc);

  SolidFramework.Pdf.Plumbing.PdfPages pages =
    (SolidFramework.Pdf.Plumbing.PdfPages)catalog.Pages;

  ProcessPages(ref pages, ref Pages)

Then if a page range is specified, parse the argument into page number integers. For each page that is specified, or all if not specified.

  // Check for page ranges
  PageRange ranges = null;
  bool bHaveRanges = false;
  if (!string.IsNullOrEmpty(pagerange))
  {
    bHaveRanges = PageRange.TryParse(pagerange, out ranges);
  }

  if (bHaveRanges)
  {
    int[] pageArray = ranges.ToArray();
    foreach (int number in pageArray)
    {
      CreateImageFromPage(Pages[number], dpi, filename, number, extension, format);
      Console.WriteLine(string.Format("Processed page {0} of {1}", number,
      Pages.Count));
    }
  }
  else
  {
    // For each page, save off a file.
    int pageIndex = 0;
    foreach (SolidFramework.Pdf.Plumbing.PdfPage page in Pages)
    {
      // Update the page number.
      pageIndex++;

      CreateImageFromPage(page, dpi, filename, pageIndex, extension, format);
      Console.WriteLine(string.Format("Processed page {0} of {1}", pageIndex,
      Pages.Count));
    }
  }

We load each requested Page object and request a bitmap from that object. We then request that the bitmap object save itself to a file in the output directory with the requested ImageFormat type.

  private static void   CreateImageFromPage(SolidFramework.Pdf.Plumbing.PdfPage page,
    int dpi, string filename, int pageIndex, string extension,
    System.Drawing.Imaging.ImageFormat format)
  {
    // Create a bitmap from the page with set dpi.
    Bitmap bm = page.DrawBitmap(dpi);

    // Setup the filename.
    string filepath = string.Format(filename + "-{0}.{1}", pageIndex, extension);
    // If the file exits already, delete it. I.E. Overwrite it.
    if (File.Exists(filepath))
      File.Delete(filepath);

    // Save the file.
    bm.Save(filepath, format);

    // Cleanup.
    bm.Dispose();
  }

And there you have it. The requested images should have been created in the specified output directory. Since we are using the free developer trial license, each page image will have a watermark at the bottom if the page. To remove this watermark, read more about an annual license for the Solid Framework Tools Edition here ($250 or $500 per year depending on distribution, no royalties).

Have any thoughts that you'd like to share? Please contact us with your feedback.

Friday, August 28, 2009

App Domain Switches and Solid Framework

It has come to our attention that there is an issue with Solid Framework finding its support files when 3rd party assemblies are being used. The problem manifests itself as "Cannot find framework.dll" exception.

To work around this issue your license call, or instance of the LicenseCollection Object should be placed at the very beginning of your application. This license call should happen before any other 3rd party assembly is called.

The 3rd party assemblies can change the App Domain and then the call to Solid Framework fails. It looks within the App Domain searching for its support resources and when it doesn’t find them it assumes they have already been extracted and tries to load them.

We have tracked this down with Oracle and other assemblies and fixed the bug. We should be releasing a new version of Solid Framework sometime in the next week.

Monday, August 24, 2009

Extracting Solid Framework support files.

Developers may need to extract the support files in Solid Framework for a couple of reasons.

  • To use the native C++ interface
  • Running scripts with SolidScript.exe
To facilitate this issue, we have uploaded a small console app that works with Solid Framework version 225 or greater here. Place the exe anywhere you like and run it with 2 parameters. The first parameter is the full path to Solid Framework.dll, and the second parameter is the path to where you want the extracted files to be placed.

Example:

ExtractFramework.exe "c:\development\Solid Framework\SoldFramework.dll" "d:\My Files\Framework"

This will extract the support files from SolidFramework.dll sitting in c:\development\Solid Framework to the location d:\My Files\Framework.

Note: We wrapped both paths with quotes on the command line because of spaces in the folder names. If your path has spaces, you should also use quotes.