Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:release:3.09_release_notes [2018/12/13 18:44]
anupama [Content Encoding Error when visiting the local solr servlet page]
en:release:3.09_release_notes [2019/02/04 16:17] (current)
anupama [PDF plugin restructuring and the NEW PDFv2Plugin]
Line 94: Line 94:
   * **the recommended "//​PDFv2Plugin//"​**,​ which will contain the new functionality and should handle a greater range of PDF versions, including the newer ones that the old ''​pdftohtml''​ (now used by PDFv1Plugin) can't handle. The "​PDFBox conversion"​ facility has been moved to the new PDFv2Plugin,​ but is now invisible: it will be triggered automatically depending on the "​convert_to"​ format that you select when you Configure the PDFv2Plugin. PDFv2Plugin also uses additional conversion tools in the background to support the additional output formats.   * **the recommended "//​PDFv2Plugin//"​**,​ which will contain the new functionality and should handle a greater range of PDF versions, including the newer ones that the old ''​pdftohtml''​ (now used by PDFv1Plugin) can't handle. The "​PDFBox conversion"​ facility has been moved to the new PDFv2Plugin,​ but is now invisible: it will be triggered automatically depending on the "​convert_to"​ format that you select when you Configure the PDFv2Plugin. PDFv2Plugin also uses additional conversion tools in the background to support the additional output formats.
  
-For the eventual 3.09 release, the old PDFPlugin that you're familiar with, the one which has the ''​pdfbox_conversion''​ flag but also makes use of the old ''​pdftohtml''​ tool behind the scenes, will hang around with a deprecated warning, to allow people to port over their collections and keep rebuilding with the old settings or to rebuild their collection with one of the 2 new PDF plugins. However, **new collections will have the //​PDFv2Plugin//​ in the Document Plugins pipeline by defaultfor GS3, and PDFv1Plugin by default for GS2, since GS2 doesn'​t come with the PDFbox extension out of the box.** So GS2 users will have to manually add in PDFv2Plugin in place of PDFv1Plugin for new collections,​ after setting up the pdfbox extension. But then it should work as usual.+For the eventual 3.09 release, the old PDFPlugin that you're familiar with, the one which has the ''​pdfbox_conversion''​ flag but also makes use of the old ''​pdftohtml''​ tool behind the scenes, will hang around with a deprecated warning, to allow people to port over their collections and keep rebuilding with the old settings or to rebuild their collection with one of the 2 new PDF plugins. However, **new collections will have the //​PDFv2Plugin//​ in the Document Plugins pipeline by default for GS3, and PDFv1Plugin by default for GS2, since GS2 doesn'​t come with the PDFbox extension out of the box.** So GS2 users will have to manually add in PDFv2Plugin in place of PDFv1Plugin for new collections,​ after setting up the pdfbox extension. But then it should work as usual.