Reporting Engine Release Notes

These notes are also in the readme.rtf file that is included with the program.

4.1.74

• If a font used in the template is not on the server and the server cannot find a direct substitute, then the standard font would always be displayed in 12 pt - fixed
  

4.1.72

• A recent Word service pack changed the way Word saves section/footer settings in an rtf file breaking header/footers in some cases - now handle it.
  

4.1.71

• Column breaks for newspaper columns in PDF reports were ignoring "keep together" - fixed

4.1.70

• Generation of Numbered List with line breaks and Last Page Footer causes error - fixed
• Link tag space before URL in XML file causes error - fixed
• Handle a case where the rtf template settings for table column widths is inconsistent - fixed

4.1.69

• License error when computer name starts with digit – fixed.

4.1.67

• Handled WordML spec exception for nested tables without paragraph in cell creating empty cells - fixed.

4.1.66

• Handled tabs wrong if was given a tab at 0 - fixed.

4.1.65

• Fixed problem in .NET engine when running in a locale whose resources we do not support.

4.1.64

• Bitmap in Header causes space in footer error fixed

4.1.63

• In rare cases would lowercase the first letter after a unicode character in a rtf template - fixed

4.1.60

• In rare cases the background in a cell for a table that breaks across pages was not fully drawn in pdf reports - fixed
• In rare cases a table where the cell breaks across pages occured in the middle of a paragraph in the cell had bad placement on the second page - fixed.

4.1.59

• When document locale is different than text locale in a document – fixed

4.1.58

• Threw an exception if run on a computer who's name starts with a digit in some cases (java/J# bug) - fixed.

4.1.57

• If a PDF report had a section break in the middle of a page and that break chaged the left page margin, the created report had the old margin for that page - fixed.

4.1.56

• PDF report generation is now much faster.

4.1.55

• Added DB2, MySql to RunReport and SQL samples in sample12.
• HTML reports had the wrong line height if the paragraph spacing was set to an exact height - fixed.

4.1.54

• Can now set a default for the BaseDirectory in app.exe.config.
• In very rare cases the first line of a new page in newspaper columns would be at the end of the previous page in PDF reports - fixed.

4.1.53

• In some additional cases for pdf reports justified column text would justify the last line of the paragraph - fixed.

4.1.52

• In some cases for pdf reports justified column text would justify the last line of the paragraph - fixed.
• PDF reports that started in column modes was wrong - fixed.

4.1.51

• In some cases for pdf reports the bullet character was slightly off - fixed.
• In very rare cases when a unicode character preceeded a number, the number could disappear in a rtf report - fixed.

4.1.50

• If a table breaks across a page and a cell is not align top and the last paragraph in a cell has spacing after the paragraph, the text will be mis-aligned in a pdf report - fixed.

4.1.49

• If a license exception is thrown for too many servers, will list the IP address of all servers.

4.1.48

• Wrong page number after section break (4.1.47 only) - fixed.

4.1.47

• Multiple paragraphs inside a table in html output closed paragraphs wrong - fixed.
• Different first header/footer for pdf reports used regular header/footer instead - fixed.

4.1.45

• Did not place bullets properly in pdf paragraphs that were indented on all lines - fixed.
• Added iio.cache=off for AIX systems. This should be set on all AIX systems.
• A <wr:if test=${var.node}...> tag where the value for ${var.node} is empty or the node does not exist does not evaluate correctly - fixed.

4.1.44

• Added the program SystemTest to check java platform performance.

4.1.43

• Fields with character formatting would show their text twice in rtf output - fixed.
• Vertically merged cells breaking across pages have problems in pdf reports. They would continue down on the first page - that is fixed. They should continue as needed on the second page - that is not supported.

4.1.40

• Japanese Word 2000 (and possibly Japanese Word 2002 & 2003) uses a combination of SBCS and DBCS characters in rtf which caused characters to disappear when reading the template - fixed.
• inline='true' did not work for some rtf files - fixed.
• If the last paragraph in a header/footer had a border, it was not drawn in pdf reports - fixed.
• Tabs with leader characters that were the first item in a paragraph did not display the leader text correctly in a pdf report - fixed.
• If the <wr:html.../> tag returned text with tabs in it, the tabs were placed in the report and Word would then hid the text after the tabs (we think this is a Word bug). Tabs are now removed to avoid this issue.

4.1.39

• Added inline='true' attribute to <wr:import.../> tag.
• Bullet placement was wrong in pdf reports using newspaper columns - fixed.
• .NET only - Problem with xpath queries like ${var}[atr = 3] - fixed.
• .NET only - Minor change in AdoDataSource to handle MySql ADO.NET driver.
  
• .NET only - Latest version of JFreeChart added.
• .NET only - Reworked the license checking.

4.1.38

• Newspaper column layout in pdf reports had some minor problems - fixed.
• If the first character of a paragraph was a superscript or subscript, did not super/sub in rtf output - fixed.
• If a field had taller text than the rest of the text in a line, it would shift just part if the line down in pdf output - fixed.
• Changed how resources are read from jar files because Tomcat didn't handle the way we were doing it (java only).

4.1.37

• If a <wr:set name="abcd" value="1"/> had a value that was shorter than the name, it would only find the first ${abcd} in other selects - fixed.
• Could occasionally get an exception when using newspaper columns - fixed.
• Added support for Windward Reports Express.

4.1.36

• Did not handle "keep row on one page" in the table style (did handle it fine as a row setting) - fixed.
  

4.1.35 (release)

• Added report.embed.info to WindwardReports.properties.
• Did not handle "keep row on one page" in the table style (did handle it fine as a row setting) - fixed.
• Slightly increased the size of superscript & subscript text.

4.1.34

• Our change in 4.1.29 to handle the new header format caused it to not see odd/even headers saved by earlier versions of Word - fixed.

4.1.33

• A customer sent us invalid rtf files that Word created and can read - now handles this (bad values for bulleted lists).

4.1.32

• Added support for <sub> and <sup> in the html tag.
• If a bitmap displayed with <wr:out.../> had a null value, threw an exception. Now displays nothing.
• Some very unusual combinations of calling <wr:set.../> repeatedly for the same value had problems - fixed.

4.1.31

• .NET only - Problem in 4.1.30 loading resources for locales other than en_US - fixed.
• Java only - Improved error messages if required libraries are not in the classpath.

4.1.30 (release)

• If called <wr:set .../> a second time with the same name, would throw an exception - fixed.
  

4.1.29

• Charts & graphs now supported in .NET (has been in the Java engine since 4.0).
• Reports in XLS format now supported in .NET (has been in the Java engine since 4.0).
• Provides more information in an exception when and ADO.NET connection fails.
• Word sometimes stores the header and footer as the odd page header/footer even if odd/even is not set. Now handles that case.
• Style based on parent styles could cause character and paragraph formatting to be wrong in paragraphs using the child style in WordML reports - fixed.
• If the top of a page has a Word Field, will throw an exception generating the report - fixed.
• If an unrecognized image type is in a WordML template, will throw an exception - fixed.
• When a very unusual combination of settings were used to format a bulleted list, the first line of each bulleted paragraph would be started too far to the right in pdf reports - fixed.

4.1.28 (release)

• ProcessReport.getInfo() returned ${var.column} elements as map vars - fixed.
  

4.1.27

• If a table with width set in percentage has a sub-table, will throw an exception in some cases - fixed.
• Justified text for bi-di (Hebrew/Arabic) was off in some cases with bullets and/or line breaks - fixed.

4.1.26

• If a rtf template style had a bulleted list setting but never used the list in any paragraph then creating a rtf report would throw an exception - fixed.

4.1.25

• If a WordML template paragraph had no indent but the style for that paragraph did, the paragraph would be indented in WordML and rtf reports - fixed.
• WordML reports sometimes did not have the inner lines of tables drawn - fixed.
• The location of bulleted paragraphs in Hebrew & Arabic was sometimes too far to the right - fixed.
• The font names were sometimes incorrect for pdf reports built from rtf templates for non Western-European character sets - fixed.

4.1.24

• When using a WordML template, if the Normal style did not specify the font size and the paragraph did not specify a font size, it defaulted to 12 instead of 10 points - fixed.
• Having ${var} in field based tags, the {} did not get copied to the output if the field was not used when generating the report - fixed.
• If a cell is align center or bottom and the first paragraph in the cell has space before, the text in the cell will be shifted too far down in a pdf report - fixed.
• Bullets inside tables in pdf reports ignored the table pad left value when positioned (so they were too far to the left) - fixed.
• If a line in a paragraph was just a subscript or superscript, it would overlap the previous or next line in a pdf report - fixed.

4.1.23

• Sometimes did not get list properties for outline numbered lists in a WordML template - fixed.
• AutoFit tables in a WordML template were not marked AutoFit in the report templates - fixed.
• Images that are scaled differently in the X and Y direction were not displayed correctly in a pdf report - fixed.

4.1.22

• When using a WordML template, if the Normal style did not specify the font size, it defaulted to 12 instead of 10 points - fixed.
  

4.1.21

• .NET only - If there were open query tags for an XPathNavDataSource at the end of a template, it would throw an exception - fixed.
• .NET only - The XPathNavDataSource could not handle a ${var} inside a [node=value] part of the xpath - fixed.
• note: No changes for the java version except the change in version number to match the .NET version.

4.1.20

• The class TemplateInfo was obfuscated by mistake - fixed.
  

4.1.19

• The var= for out & function was saving the formatted result - now saves the raw result.
• A WordML file that started with the 3 byte utf signature bytes was not recognized - fixed.
• Character formatting at the start of a paragraph in a WordML report was wrong in some very unusual (and complicated) cases - fixed.
• In some cases WordML reports had tables set to autofit when the template was set to a fixed width - fixed.

4.1.18

• The out and function tag now have an optional var= attribute. If this is set, then the value displayed is also added using the equivilent of the <wr:set .../> tag to add this as a variable that can be later used.
• If SYMBOL fields font size was an odd number, threw an exception - fixed.
• Calling evaluate="1.23E4 + 1" would throw an exception on numbers in exponential form - fixed.

4.1.17

• Vendor specific handlers (see 4.1.16) written for Sql Server, Oracle, MySql, and DB2. (Also for OleDb for the .NET version.)
• When using a rtf template and creating a WordML report, sometimes it would place multiple "Normal" styles in the document - fixed.
• If a cell ended with a table, it would place a blank line after the table in the cell - fixed.
• Newspaper columns with a rtf template would have their settings wrong for the final paragraph if that was different than the paragraph before - fixed.
• Fixed a number of minor issues with bullet list formatting.
• Blank header lines would be placed in the TOC and following header lines skipped - fixed.

4.1.16

• .NET only - layout of bold text in pdf reports was long (the bold was ignored in the text sizing) - fixed.
• ${var} substitution for SQL datasources has the following two changes. First, it does no wildcard substitution if the var starts with an underscore such as ${_var}. Second, when it does do substitution, it does it based on the syntax of the vendor and does none for vendors we have not written a syntax handler for. (Previously we tried to do this generically but it just doesn't work well.)

4.1.15

• Nothing (version matched to AutoTag).

4.1.14

• Some minor problems with bullet characters in certain settings were wrong - fixed.

4.1.13

• If a table cell starts with a bulleted list would throw an exception (4.1.11/12 only) - fixed.
• If a numbered bulleted list was not in the form 1.2.3. but instead just had 3. in the inner list, it did not display the correct value - fixed.
• If a WordML template had a table as the first text in a header/footer, it did not display in the report - fixed.
• The .NET engine threw an exception when displaying Asian characters in a pdf report - fixed.

4.1.12

• Added documentation for new features in 4.1.11.
• Added documentation for how licenses are checked for number of servers running.
• Underlining not handled properly for bullet points - fixed.
• Sometimes had the wrong font for bullets - fixed.
• Text after a line (not paragraph) break where the line was empty was positioned wrong in pdf - fixed.
• Multi-character bulleted lists for Hebrew/Arabic were not RTL - fixed.
• Formatting problems with XLS reports after generating the first one - fixed.
• Could not use ${var.column} in an out tag for a bitmap using JDBC where var was from a forEach loop - fixed.
• Newspaper columns with justified text did not display correctly in pdf reports - fixed.
  

4.1.11 (release)

• function, html, import, and out tags now support display='value' attribute. Value can be 'always' (always show the line for this tag), 'notNull' (show the line for this tag if the select is not null, even if it is empty), 'notEmpty' (show the line only if the select returns a string), or a boolean expression as used in <wr:if test='expression'>. If display='false' then if the paragraph is solely composed of tags set to false the paragraph will be deleted.
  
• The set tag now supports evaluate='expression' in addition to the value='data'.
• import tag now supports pdf files - only for pdf output. Imported pages are inserted as distinct pages.
• Added support for thick underlines in the template.
• RunReport now opens the template file using a share that will work if Word also has the file opened.
• RunReport now supports -xml:name, -sql:name, ... so that you can use multiple datasources and name them.
• RunReport now handles http:... as well as files for xml datasources.
• minor problems with bulleted lists for Hebrew/Arabic - fixed.
• If a table had all rows set as shorter than table width, right border of table was not drawn for pdf reports - fixed.
• Settings in the app.exe.config file can also be placed in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Windward Studios\Reporting Engine Dot Net\Settings. Just place each property as a String value. For each property the program looks first in the config file and then the registry ss you can mix your usage. (.NET only)
• Some of the samples used the java version instead of the .NET version in their run.bat commands - fixed. (.NET only)

4.1.10

• If a table broke across pages and the break occured between paragraphs with two or more paragraphs after the break, the table would be positioned too high on the next page in pdf reports - fixed.
• If a table had vertically merged cells that broke across a page and the break was in the second row of the vertical merge, and the last column of the row was vertically merged, then the table borders would not be drawn on the second page in a pdf report - fixed.

4.1.9

• Tag attribute value check moved to datasource to allow datasources to add additional attributes to their tags.

4.1.8

• wr:out value="1 * 2 - 3" was sometimes off (when a - sign was at the end of a more than 2 variable equation) - fixed.
• Bullets were always black in pdf reports and if the very last paragraph in a rtf report - fixed.

4.1.6 (release)

• Some images did not appear in the final report in earlier versions of 4.1 - fixed.
• <wr:html tag with <p><p> or <br><br> only processed the last tag - fixed.
• Numbered bullets with no character at the end, such as 2.2 instead of 2.2. would display as 2.'01 in pdf reports - fixed.

4.1.5

• html tag now supports <br> and <p> also.
• If the text in a line after a field is taller than all text in the line so far, the preceeding text is adjusted down but the field text was not. This was only a problem in pdf reports - fixed.
• Displaying non-rectangular images in rtf files for display using write.exe (not a problem with other word processors) had the x and y size switched - fixed.
• Line breaks on a blank line did not space down for a pdf report - fixed.
• Error in 4.1.3 only, the left margin of justified text on pdf reports was left shifted for all except the last line - fixed.
• Word does not underline spaces after last word in a line of text, windward now does the same. Only an issue for pdf reports.
• Problem with bullet and left aligned table positioning using Hebrew or Arabic in pdf reports - fixed.
  

4.1.3.1 (release)

• Small change in html help layout.

4.1.3

• Bitmap files created in html reports have permissions of the folder they are created in, not of the temp directory (unless that is the directory they are placed in). (.NET version only)
• Upgraded to the latest version of jfreechart. You must switch to the latest jfreechart.jar and jcommon.jar in the lib directory. (java version only)
• Added new html based Help Center.
• Bullet in pdf reports character formatting same as previous line instead of as list formatting - fixed.
• Bold text did not word wrap correctly in pdf reports - fixed.
• If a font did not exist on the server and was used in a report, then was never displayed as bold in a pdf report - fixed.

4.1.2

• Some Word processors set table column widths using various measurments within one row. Now handles this.
• Large images for \nonshppict needed to be stored in a different format - done.
• rtf reports for bi-di text did not always show the correct font - fixed.
• Several minor fixes for bi-di text in pdf reports and 1 fix for rtf reports.

4.1.1 (release)

• Now has a setBaseDirectory() to set the base for <wr:import.../> when the imported filename is not an absolute path.
• Fixed some cases where metafiles would not convert such as WordML template and rtf report.
• Many versions of word could not handle a placeable metafile in \nonshppict, switched to standard metafile.
• If a pdf file has a blank page, Acrobat discards that page. Now writes a space to any blank page so it still displays in Acrobat.
• Some minor fixes for Hebrew & Arabic.

4.1.0

• Now handles bi-directional reports (Hebrew & Arabic).
• If the JdbcDataSource or AdoDataSOurce had two vars such as long and longer where one var matched all of the first var name, it would throw an exception when processing that var - fixed.
• Fixed some minor problems with metafiles and \nonshippict images.
• .NET only - Threw an exception flushing the output stream for a PDF, WordML, or SpreadsheetML report - fixed.

4.0.20

• Some minor tweaks for the .net server.
• The .net server has a C# wrapper library.
• The .net server has a RunReport example.
• Problem with \nonshippict images - fixed.
• An empty WordML template would throw an exception generating a PDF report - fixed.

4.0.19

• Images now includes support for wmf and emf files (Windows MetaFiles).
• OLE objects in the templates will be displayed in the report as an image showing the OLE object.
• Lotus Domino returns null classloader in some cases which caused a NullPointerException - fixed.

4.0.18

• pdf reports would mis-position text & images in newspaper columns if they are not left aligned - fixed.
• Logic for handling table width sizing was adjusted to use the row width overriding the cell width as Word does.

4.0.17 (Release)

• Text output uses the set font and font size for measuring the report page as well as the input text.
• pdf reports using internal line breaks would split words around an image - fixed.

4.0.15

• license file different for .net and java engines.
• If the document properties had a { or } in the property the report would generate as an empty document - fixed.
• The template files in sample12 had a problem - fixed.
• <wr:out ... type='BITMAP'/> was broken for JDBC datasources - fixed.

4.0.14

• Alpha of .NET report engine.
• If the footer or header y position was not the standard 1/2", it would reset to that value on a section break - fixed.
• If a tag was saved as a field and was a TOC (table of contents) item, it would not be linked to from the TOC is some cases - fixed.

4.0.12 (Release)

• Did not handle a default tab setting of 0 - fixed.
• Vertically merged cells with rows of a fixed height in some cases would throw an exception - fixed.
• Inline images were not lined up with text baseline - fixed.
• Could not handle images in files imported via wr:out or wr:import - fixed.
• if tags on table cells could shift the cell borders in a pdf report - fixed.
• If over a page of a table was marked as header rows, would throw an exception - fixed.
• If a paragraph is just a field then the field formatting was not shown in a rtf report - fixed.
• If a paragraph is justified, has a hanging indent, has no tab settings, and is tab-ed in the first line to the indent location, the text would appear wrong in a pdf report - fixed.

4.0.11

• Updated to the latest 3rd party jar files.
• Rtf templates with a table entry that was just a tag in field format did not use the field character formatting - fixed.
• xml datasources forEach tags with begin='N' where N > number of nodes returned threw an exception on ${var[x]} - fixed.
• Raw text in a wr:html tag would drop the last character of text - fixed.

4.0.10

• An out tag with evaluate='4 * 3 / 5' would evaluate to 2 instead of 2.4 (used integer math). Now converts to float and returns 2.4.
• tables in headers not handled correctly - fixed.
• xls reports with multiple lines in the header would throw an exception - fixed.
• Some html tables borders were a little off - fixed.
• Table of Contents entries inside a forEach loop did not set their hyperlinks correctly - fixed.
• In some cases Table of Contents character formatting was incorrect - fixed.
• WordML reports Table of Contents links did not work - fixed.

4.0.9 (Release)

• Chart attributes changed.
• Chart schema settings finalized.
• A field formatted in a table did not carry it's formatting to the output - fixed.
• PDF reports with vertically merged cells with a vertical alignment other than top did not align the text correctly - fixed.
• PDF reports with vertically merged cells with a shaded background did not shade the cells other than the first - fixed.

4.0.8 (Release, except for charts)

• PrintDate field uses format setting for displayed date.
• Chart schemas finalized.
• Tables in headers/footers did not print vertical lines in pdf reports - fixed.
• <wr:forEach end='5'> the end attribute was ignored for xml datasources - fixed.
• The left edge border of a cell, where a wr:if crossed rows, was sometimes drawn in the wrong place for a pdf report - fixed.
• Sometimes placed a space before the first letter of a rtf report - fixed.
• Sometimes the body text would overwrite the footer in a PDF report if the footer extended up into the document area - fixed.

4.0.7 (Release Candidate)

• For a rtf report, if the paragraph started in bold (or other character formatting), then was normal, it would switch back to cold, etc. on the 2nd plus lines of the paragraph - fixed.
• Word97 sometimes writes cell border information so that WR thought there was no border - fixed.

4.0.6 (Release Candidate)

• Graphs & charts are by attributes only - the separate xml file has been removed.
• Warning on startup if running without an X client on unix and not in headless mode.
• Sample16 added - lots of new template examples.
• If a tag is a field and just the field is formatted differently from the text before it, the formatting did not carry over to the output - fixed.
• Minor change in how xls files are created as the old way would throw exceptions in Excel 2000/XP if add-ins were enabled.
• Non unicode characters (like webdings) did not translate across to reports correctly - fixed.

4.0.5 (beta)

• Did not output nested tables properly if the template was WordML and the output was not WordML - fixed.
• Did not handle <wr:out.../> in paragraphs used in TOC (Table of Contents) - fixed.
• Did not read headers/footers in WordML templates - fixed.

4.0.4 (beta)

• Wrapped all calls to TextLayout.getAdvance() in a synchronized due to a bug in the JVM that throws an exception if this is called by multiple threads.
• Now breaks newspaper columns ok if a table is in one at the column break.

4.0.2 (beta)

• Placed fields incorrectly if not left aligned in pdf reports - fixed.
• Tables that go over the page margins placed incorrectly in pdf reports - fixed.
• Server did not return Error Throwables (just Exception Throwables) - fixed.

4.0.1 (alpha)

• Graphs & charts are now included. However, we want feedback on how the properties are set and so that part is subject to change. Take a look at chart.zip for a sample of how to do this. Whatever method we end up with, AutoTag will fully support it. (Note: for sql datasources the select must return just the data to be charted with the row description as the first column. Column names are pulled from the metadata but can be overridden in the properties.xml file.)
• Newspaper type columns now supported.
• Added a <wr:set var='name' value='${stat}'/> tag.
• tabs now support leader characters of . - _
• New properties setting "default.chart.dpi=300" which sets the resolution of the created bitmaps. For screen (html) displays, anything more than 104 is a waste. For hi-res print pre-press you want 1200 or maybe even 2400. For everything else, 300 works fine.
• Did not handle fields with formatting within the field name - fixed.

4.0.0 (alpha)

• Table of Contents, Index, and bookmarks now supported.
• Templates can be in WordML (xml) instead of rtf. Program automatically detects template file type.
• Can now set the font and point size used when generating TXT reports.
• <wr:out.../> value= and evaluate= now handle ${var} values from a query. For xpath this must be of the form ${var.xpath} and not ${var}/xpath.
• <wr:import.../> now handles xml (WordML) files similiar to how it handles rtf files.
• <wr:out.../> now supports type='RTF', 'XML' where a rtf or xml file is that data element.
• Added ProcessReportAPI.duplicate() so a template can be parsed once and then used to generate multiple reports.
• The forEach column break is not going to be implemented. Instead if the forEach has step='N' where N > 1, then any select can have ${var[x]} where 0 <= x < N and the select is for that subsequent row of data. If that row is past the end of the data, wr:out will list nothing - it will not throw an exception. There is als a wr:if test that can be done for values of x > 0 (x == 0 is always good). This allows repeating N columns across and then a new row or table for each subsequent set of N columns.
• The JdbcDataSource now allows values of step='N' where N can be > 1.
• Jdbc <wr:if test='${@var[0]}'> Tests if the specified row of data exists.
• Line breaks (as opposed to paragraph breaks) in a table caused a fault - fixed.
• Now supports i,I,a,A for numbered bullets (previously only supported 1,2,3...) - fixed.
• If last paragraph of a list had no text, the bullet was not written in a pdf report - fixed.
• RunClientReport threw an exception if the host was listed on the command line - fixed.
• <wr:if...> in an imported rtf file ended the import at the end of the if - fixed.