Sign In  Sign Up Live-Chat
Spacer

Aspose.Words for .NET, Java, Reporting Services and JasperReports

  • Aspose.Words for Reporting Services 3.1.0: Document Layout Gets Smarter

    While working on Aspose.Words for Reporting Services, we have been constantly thinking on how to maintain a good balance between the "editability" and appearance of the documents being generated. Produce documents as simple as possible, but don't let layout and formatting suffer - that's been our rule.

    Following this rule is often difficult. RDL reports and Microsoft Word documents are basically very different things. RDL reports are easy to draw (for example, as a PDF document or image), but try to compose them from flow layout paragraphs and tables so that the design would not suffer - and you will understand what I mean.

    RDL reports often contain page breaks. Lots of. There are page breaks before and after report items, before and after table groups, etc. How many page breaks should a Word document contain so that it would stay easy to edit?

    Obviously, if there are too many breaks, working with the document may become a torture. But if there are too few, the layout may appear corrupted.

    So far Aspose.Words for Reporting Services offered three modes affecting page breaks placement. The active mode is controlled by the PageBreaks configuration setting. The modes are:

    • Smart (default) - the engine decides how to place page breaks
    • OnEachPage - each page has a page break at its end
    • None - no page breaks in the document at all

    The latter two modes are just plain, while the first one is interesting. How should the algorithm work to produce an optimal quantity of page breaks? At what points page breaks are necessary and where they can be omitted?

    Apparently, page breaks must appear where they are supposed to appear by designer. So the algorithm places explicitly specified breaks once encountered. Where else?

    Before we answer the question, let's talk a little about tables in Word documents. Most of RDL reports contain tables and matrices (Reporting Services 2005) or tablix items (Reporting Services 2008). These report items are converted to Word tables. So we can confidently state that most of documents generated by Aspose.Words for Reporting Services contain tables. Many tables commonly.

    Tables in Word documents may not contain page breaks inside. If a table is split by a page  break, there are two tables actually: before and after the break. And the more tables are in the document, the harder it is to edit by the users.

    The conclusion is: avoid breaking tables whenever possible.

    That's how the algorithm works. Starting with version 3.1.0, it uses the Word's "Repeat as header row at the top of each page" feature to represent repeatable headers. That allows to keep the table continuous and avoid excessive breaks.

    Unfortunately, there are two special cases that still make breaking the table inevitable:

    • Repeatable headers change throughout the table
    • The table contains repeatable footers

    Luckily, those are not very frequent cases, based on my experience.

    But what if you need your tables to be unbroken at all? Remember, broken table is multiple tables. Imagine you want to work with a table as a whole instead of a bunch of its pieces, one per page.

    You could set PageBreaks to None, but then all page breaks will disappear from the document. That is not nice, for instance, if you still want your table aligned with the beginning of a page and therefore inserted a page break before. So what you need is page breaks retained all over the document except tables.

    That's why we have just introduced the fourth mode - DontBreakTables. It preserves explicit page breaks outside the tables thus keeping tables unbroken but making the rest of the document as close to the original design as possible.

    It works just fine if your table has no repeatable headers or they don't change throughout the table - in the latter case they will simply be marked with the "Repeat as header row at the top of each page" attribute like if you did that manually. But if they do change, or if your table have repeatable footers - there is no guarantee headers and footers will appear at the beginning and end of the page, respectively. This is a trade-off because you have instructed the engine to omit page breaks within tables.

    Choose a page breaks mode that suits your needs the best and enjoy the editing!

    To download the latest Aspose.Words for Reporting Services 3.1.0, please visit http://www.aspose.com/community/files/52/ssrs-rendering-extensions/default.aspx

  • Aspose.Words for JasperReports Now Supports Rich Text Format (RTF) and OpenDocument Text (ODT)!

    We proudly announce a new release of Aspose.Words for JasperReports. In this release, you will find that a number of exciting features have been added.

    First off, apart from DOC, DOCX, TXT and HTML, the product now supports two additional formats - Rich Text Format (RTF) and OpenDocument Text (ODT)!

    Secondly, lines and rectangles are now exported along with other report elements. Note however that they are disabled by default because the way some JasperReports are currently designed may lead to corrupted document layout. Consider enabling this feature by setting the EXPORT_LINES and EXPORT_RECTANGLES parameters to true. Switch them back to false (one of them or both) if the document layout becomes corrupted - this basically means that you should redesign the report or accept the document without lines or rectangles exported.

    Thirdly, this release introduces the SPACING_FACTOR parameter. This parameters allows you to decrease spacing between report elements when being set to a value less than 1.0 (which is default). If you notice that page breaks in your document are being pushed to subsequent pages, thus leading to excessive blank pages to appear, try setting the parameter to a smaller value, say 0.9 or 0.75. This will "shrink" spacing and make page contents more compact. Keep on until the report looks as expected.

    To download, please visit http://www.aspose.com/community/files/67/jasperreports-exporters/aspose.words-for-jasperreports/default.aspx

  • Aspose.Words for Reporting Services 3.0.4 Released

    We have released a new hotfix of Aspose.Words for Reporting Services. It addresses a number of issues and also introduces the new SpacingFactor configuration setting.

    What is the new setting for? Imagine you have a report that you export to a Microsoft Word document via Aspose.Words. The default layout mode is flow mode that means the docuemnt consists of "normal" paragraphs and tables. Alas, this mode has a trade-off: we cannot set coordinates of document items explicitly, so we only may assume page contents will actually fit the page. Sometimes the contents may "flow" off the page and push the ending page break to the subsequent page, causing excessive (usually blank) pages to appear.

    If you notice this happens in your case, try setting SpacingFactor to a value less than 1.0, say to 0.9 or 0.75. It will reduce spacing between report (document) items thus making page contents more compact. Decrease the value until you confirm there are no more excessive pages in the resulting document.

    To download the hotfix, please visit

    http://www.aspose.com/community/files/52/ssrs-rendering-extensions/aspose.words-for-reporting-services/default.aspx

  • Aspose.Words participates in the ODF Plugfest Interoperability Workshop

    The first of a series of events that will bring together implementors of OASIS OpenDocument Format/ISO 26300 to unilaterally test and discuss implementation issues of ODF with each other. All ODF implementors and/or those looking into the matter are invited to participate in this event on behalf of the Netherlands government and OpenDoc Society.

    Here is the website of the event http://www.odfworkshop.nl/

    Thanks to the organizers of the workshop, Aspose was invited to participate in the workshop. Although we could not attend this event in person, we are making Aspose.Words available for testing by the event participants.

    The Plugfest's testing environment (probably one of) is accessible here http://www.officeshots.org/. At the moment this testing framework is in Closed Beta and available only to the event participants and members of the OpenDoc Society, but you still can see Aspose.Words listed as one of the conversion/rendering engines available on the Officeshots homepage.

    Officeshots allows to upload an ODF document and request it to be converted to PDF, Screenshot (render a page to an image) or to ODF (round-tripping) and select one or more engines that you want to do the job. Once the request is processed, you can download and view the results.

    Aspose.Words "subscribes" and allows to do all possible conversions: ODT to ODT, ODT to PDF and ODT pages to PNG images. It will be interesting to see what event participants have to throw at Aspose.Words.

    By the way, here is a table that we added recently that details what OpenDocument features are supported by Aspose.Words http://www.aspose.com/documentation/file-format-components/aspose.words-for-.net-and-java/save-in-the-opendocument-text-odt-format.html

     

  • New DOCX (Microsoft Office 2007 Open XML) fixes in Aspose.Words for Java 3.0.1.

    The recently released Aspose.Words for Java 3.0.1 includes two critical DOCX bug fixes:

    1. Images resized during DOC->DOCX->DOC roundtrip under some European locales that used comma as decimal symbol.
    2. Microsoft Word 2007 SP2 reports “file was created using a newer version of Microsoft Word”.

    Please visit http://www.aspose.com/community/files/51/file-format-components/aspose.words-for-.net-and-java/default.aspx for more info and download.

  • Aspose.Words for .NET 6.4.0 supports exporting to PDF/A-1b and more!

    We have just released Aspose.Words for .NET 6.4.0 that includes the following:

    • Export to PDF/A supported
    • Export to ODT details are included in the documentation
    • 70+ fixes

     

    PDF/A Supported

    By default, when converting documents to PDF, Aspose.Words for .NET creates PDF 1.5 comliant files. But now you can specify whether you want to have PDF 1.5 or PDF/A-1b compliance. We are planning to support PDF/A-1a in the next few months as well.

    Here is an example how to use the new option:

        Document doc = new Document(@"C:\TestRendering.doc");

        PdfOptions options = new PdfOptions();
        options.Compliance = PdfCompliance.PdfA1b;

        doc.SaveToPdf(0, doc.PageCount, @"C:\TestRendering Out.pdf", options);

     

    Documentation Updates

    The following documentation pages were updated:

     

    70+ Fixes

    For the detailed list of fixes and to download the new release please see http://www.aspose.com/community/files/51/file-format-components/aspose.words-for-.net-and-java/entry180062.aspx

     

  • Rich Text Format (RTF) and OpenDocument Text (ODT) are now supported in Aspose.Words for Java!

    We've just released Aspose.Words for Java 3.0 that adds support for two new formats RTF and OpenDocument Text (ODT). Now you can load/convert/save and generate documents in these formats too.

    Please visit http://www.aspose.com/community/files/51/file-format-components/aspose.words-for-.net-and-java/default.aspx for more info and download.

  • Aspose.Words for Reporting Services 3.0.3 Released

    Following the Aspose.Words for JasperReports hotfix release, we have just published a hotfix of another great product - Aspose.Words for Reporting Services. This version includes a number of important updates as well; the SSRS 2008 users should pay special attention to this release as it contains a couple of essential bugfixes.

    You can download the new hotfix at http://www.aspose.com/community/files/52/ssrs-rendering-extensions/aspose.words-for-reporting-services/default.aspx

  • Aspose.Words for JasperReports 1.0.1 Released

    We have just released the first hotfix of our brand new product Aspose.Words for JasperReports. It contains a number of important updates. Please try it out.

    The hotfix is available to download at http://www.aspose.com/community/files/67/jasperreports-exporters/aspose.words-for-jasperreports/default.aspx

  • Aspose.Words for Reporting Services 3.0.2 Released

    We have just released a hotfix of Aspose.Words for Reporting Services. It contains a number of minor improvements, including the fact it is now built on top of the newest Aspose.Words for .NET 6.0.3.

    To download, please visit http://www.aspose.com/community/files/52/ssrs-rendering-extensions/aspose.words-for-reporting-services/default.aspx

  • Did you know Aspose.Words for .NET supports EPUB export?

    EPUB is an open digital book format. There are now many publishers, stores and reader software for EPUB books. While PDF is for paginated documents, EPUB is for reflow-centric documents that makes them easy to read on various mobile devices.

    EPUB export was first made available in Aspose.Words for .NET in December 2008, but we only briefly mentioned it at that time.

    Now I would like to mention EPUB again because of another great news. The recent release of Adobe Buzzword continues to utilize Aspose.Words to provide import/export to various document formats and now this includes export to EPUB.

    More info http://blogs.adobe.com/billmccoy/2009/03/adobe_buzzword.html.

    It is very easy to convert any document loaded into Aspose.Words to EPUB. You can load any DOC, OOXML, ODT, RTF or HTML document and just save it as EPUB.

    Document doc = new Document(@"C:\\my test.docx");
    doc.Save(@"C:\\my test out.epub");

    Aspose.Words Online Demos were also updated to provide the ability to save any document generated by the demo as EPUB. The demo will send the EPUB document to your browser. If you have some EPUB reader installed (such as Adobe Digital Editions) then you will be able to open and view the document.

    Let us know if you like this feature in Aspose.Words.

     

  • Four New How To Articles for Aspose.Words

    We are adding more technical articles in the "How To" style to the documentation. Let us know if you like it and what else do you want to learn.

    In the meantime enjor the new articles:

     

     

     

  • Aspose.Words for Java 2.7.0 Released!

    This MEGA FIX release contains 91 fixes and enhancements.

     

    Aspose.Words for Java has become more tolerating of documents generated by third-party software or even to slightly corrupted documents. Such (real-world!) documents can contain strange things: image resolution that set to 0xFFFFFFFF (-1) or even Integer.MAX_VALUE, open Xml tag without closing one, bookmark start field without bookmark end and vice versa and so on.

     

    Besides this we added few new features to this release:

     

    • Full DrawingML support
    • HTML Image Export Customizations
    • Smart tags are now supported in DOC and DOCX
    • Access to Font Information and Panose

     To see all fixes and download http://www.aspose.com/community/files/51/file-format-components/aspose.words-for-.net-and-java/default.aspx

  • Aspose.Words for JasperReports 1.0.0 Released!

    The Aspose.Words family is growing again. We are happy to announce our brand new product, Aspose.Words for JasperReports!

    Aspose.Words for JasperReports is the only known solution on the market that makes possible exporting reports from JasperReports and JasperServer to editable Microsoft Word documents with the highest degree of precision. JasperReports and JasperServer do not have built-in abilities to export reports as Microsoft Word documents; the only exception is the RTF format that uses positioned items such as textboxes, which makes the generated documents very hard to edit. Using Aspose.Words for JasperReports, you will get access to such formats as DOC, DOCX, HTML, and TXT. The documents produced by Aspose.Words for JasperReports are easy to edit in Microsoft Word.

    Aspose.Words for JasperReports is built on top of Aspose.Words for Java, the world-class library for server-side Microsoft Word documents processing. This is our second solution with such architecture. The other one is Aspose.Words for Reporting Services which is based on Aspose.Words for .NET.

    Let's overview some major features of the product.

    Export formats

    Aspose.Words for JasperReports 1.0.0 supports the following export formats:

    • DOC - Microsoft Word document
    • DOCX - Office Open XML (OOXML) document
    • HTML - Web page
    • TXT - Plain text

    More export formats will be available in the future.

    High Fidelity to Report Design

    Aspose.Words for JasperReports exports reports as Microsoft Word documents in such a way that they look identical to reports exported by the built-in exporters of JasperReports.

    Easy and Lightweight Deployment

    Aspose.Words for JasperReports is provided as a single JAR file that can be easily integrated with JasperReports or JasperServer.

    To install Aspose.Words for JasperReports, simply copy the JAR file to a correct folder. To integrate with JasperServer you will also need to edit a JasperServer configuration file.

    Editable Documents

    Aspose.Words for JasperReports exports flow layout documents. This means they consist of “normal” paragraphs, tables and images that are easy to further edit in Microsoft Word, if necessary. The built in JasperReports RTF exporter produces documents consisting of positioned text frames and that makes further editing hard.

    Aspose.Words for JasperReports uses a number of techniques to make the resulting document as easy to edit as possible. For example, tables in JasperReports are normally built from a bunch of text elements. Aspose.Words for JasperReports attempts to export those as normal, editable Microsoft Word tables.

    To download our new product, please visit http://www.aspose.com/community/files/67/jasperreports-exporters/aspose.words-for-jasperreports/default.aspx

  • Aspose.Words for .NET 6.3.0 Released

    What's New

    • About 50 fixes and enhancements
    • Support for Glossary Document in OOXML import/export.
    • New classes GlossaryDocument, DocumentBase, BuildingBlock and enums.

    To see all fixes and download http://www.aspose.com/community/files/51/file-format-components/aspose.words-for-.net-and-java/default.aspx

     

    Aspose.Words Supports Glossary Documents in OOXML

    The ECMA-376 specification (2.12 Glossary Document) defines the glossary document as:

    Within a WordprocessingML file, the glossary document is a supplemental storage location for additional document content which shall travel with the document, but which shall not be displayed for printed as part of the main document until it is explicitly added to that document by deliberate action.

    I can add that a Glossary Document is an "invisible document inside the main document". Microsoft Word uses Glossary Documents to store AutoText, AutoCorrect entries and Building Blocks.

    Earlier versions of Aspose.Words ignored Glossary Documents and therefore after an open/save cycle using Aspose.Words your Glossary Document was always missing in the output file. This is changed now.

    Aspose.Words now preserves Glossary Documents during open/save cycles (in OOXML files only at the moment). Glossary Documents can occur in OOXML and in DOC files. Support for glossary in DOC will be available later.

     

    New Public API for Glossary Documents/Building Blocks

    Aspose.Words.Document was the only class to represent a document. We have added a new class Aspose.Words.BuildingBlocks.GlossaryDocument to represent the glossary document. You can access the glossary document from the main document using the Document.GlossaryDocument property.

    It turned out that the main and glossary documents have so much in common that we had to factor out common functionality into a new base class Aspose.Words.DocumentBase. The DocumentBase class contains styles, lists and font definitions.

    The GlossaryDocument class contains BuildingBlock nodes as its children. You can enumerate/walk nodes in the glossary document in the same way you do in the main document. You can also find a building block using the GlossaryDocument.GetBuildingBlock method.

    You can programmatically create/modify/delete building blocks and their content in the same way as other nodes in the document tree. However, the most important use case for building blocks is inserting them into the main document at a certain location.

    To insert content of a building block into the main document, one needs to copy nodes from the building block to the right place in the main document tree. This can be done in the current release, but the process is "manual". E.g. it requires a lot of coding and dealing with nodes. We are now working to add helper methods that will allow you to insert building blocks in any place in the main document using just one line of code.

    See the Aspose.Words for .NET API Reference for more information on new classes and methods.

     

    More Work on Glossary Documents is in Progress

    Stay tuned, future releases will have more functionality:

    • Support of Glossary Documents in DOC files (and DOC to/from OOXML conversion of course).
    • Friendly methods to insert contents of a BuildingBlock anywhere in your document.
    • Documentation examples and articles about Building Blocks.

     

More Posts Next page »