can be the same 1.7 with Aspose.Pdf.Generator namespace?
how about other pdf saving methors, such as aspose.words.document save method into PDF stream files (and other aspose documents, excel, powerpoint etc)?
Convert Word Excel PowerPoint Files to PDF 1.7 Version Standard File or Stream using C# .NET or Java
Hi Valerio,
Aspose.Pdf.Generator.Pdf
pdf = new Pdf();<o:p></o:p>
pdf.Sections.Add();
pdf.Sections[0].Paragraphs.Add(new Aspose.Pdf.Generator.Text("sample text"));
//pdf.Save("c:/pdftest/GeneratorOutput.pdf");
Document doc = new Document(pdf);
doc.Convert(myDir + "log.xml", PdfFormat.v_1_7, ConvertErrorAction.Delete);
FileStream fs = new FileStream(myDir + "PDF_1.7.pdf", FileMode.Create, FileAccess.Write);
doc.Save(fs);
fs.Close();
Moreover, default version of PDF generated by other Aspose APIs is as following. You can save PDF file to stream object using all APIs as every API has a Save() method with stream parameter.
- Aspose.Cells generates PDF file in version: 1.4 (Acrobat 5.x).
- Aspose.Words saves the PDF with version 1.5.
- Aspose.Slides saves presentation to PDF version 1.5.
and how about Aspose.imaging pdf conversion?
there is some technical limitations cause all of your APIs can’t create 1.7 version of PDF?
Could They all be the same 1.7 ?
Thank you for your work.
Hi Valerio,
Although other Aspose APIs do not generate 1.7 version of PDF but you do not need to worry about that as Aspose.Pdf supports this feature. You can convert your documents to PDF and then use the code shared by Tilal to convert output PDFs to PDF 1.7 using Aspose.Pdf.
Best Regards,
Yes, but this is time consuming way (two step for one conversion, two streams to deal with, almost double time for conversion)
Why all API’s save() method could not generate latest version of PDF ?
Hi Valerio,
We have logged this issue for other APIs and will update you as soon as this feature is available in other APIs. Issue IDs for Aspose.Cells, Aspose.Words and Aspose.Slides are CELLSNET-43181, WORDSNET-11083 and SLIDESNET-35917 respectively. In the meantime, you can continue using Aspose.Pdf for this purpose.
Sorry for the inconvenience.
Best Regards,
any news about CELLSNET-43181, WORDSNET-11083 and SLIDESNET-35917?
Hi Valerio,
These issues have low priority because a solution is available and you can use Aspose.Pdf for this purpose. Also, there is a lot of difference between 1.5 and 1.7 versions of the PDF and a lot of features need to be implemented for this purpose so it will take considerable time.
Sorry for the inconvenience.
Best Regards,
The issues you have found earlier (filed as WORDSNET-11083) have been fixed in this Aspose.Words for .NET 19.12 update and this Aspose.Words for Java 19.12 update.
Regarding Aspose.Words (WORDSNET-11083), it is to update you that starting from the 19.12 versions, Aspose.Words for .NET and Aspose.Words for Java APIs support converting various Word document formats (such as DOC, DOCX, RTF, XML etc) to PDF 1.7 standards compliance level.
Aspose.Words also provides the PdfCompliace enumeration to support the conversion of Word document to various PDF format standards (such as PDF 1.7, PDF 1.5, etc.).
You can use the following C# Code to explicitly specify PDF standards compliance level by using PdfSaveOptions
class:
Document doc = new Document("E:\\Temp\\input.docx");
PdfSaveOptions opts = new PdfSaveOptions();
opts.Compliance = PdfCompliance.Pdf17;
doc.Save("E:\\Temp\\20.5.pdf", opts);
And since the default value of PdfSaveOptions.Compliance
option is Pdf17
, even the following simple C# code will convert DOCX to PDF 1.7 version:
Document doc = new Document("E:\\Temp\\input.docx");
doc.Save("E:\\Temp\\pdf 1.7 version.pdf");
Hi @BooleServer ,
Regarding Aspose.Cells(CELLSNET-43181), in next release, we add PdfCompliance.Pdf17
, you can use the following code to generate pdf file with PDF17
compliance.
Workbook wb = new Workbook(srcFile);
PdfSaveOptions pdfSaveOptions = new PdfSaveOptions();
pdfSaveOptions.Compliance = PdfCompliance.Pdf17;
wb.Save("output.pdf", pdfSaveOptions);
The issues you have found earlier (filed as CELLSNET-43181) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi