Corrections:

Conversion from Word

*When the header or footer contained a tab, text decorations were not processed.
*Images in the header were not output correctly.
*When page breaks were inserted continuously, some pages were not outputted.
*When a bookmark’s starting position was set outside a table and ended inside a table, hyperlinks were not converted correctly.
*Center aligned or right aligned auto shapes were not placed correctly.
*Flame layouts with no text wrapping were not processed correctly.
*When the table style was specified, the conversion finished by outputting only the first single character.
*When the border was arranged in the layout frame, the left end of the border inside the frame was hidden.
*The underline was not converted when it was specified to the page break code.
*Line numbers set to the captions were not outputted correctly.
*Text with a hyperlink in the hierarchical table was not converted.
*When the paragraph style was specified, the font specification did not convert correctly.

Conversion from Excel

*When only the cell field with valid data was specified as the print range and fit-to-page option was selected, the layout collapsed.
*When specifying fit-to-option and using the default print scaling ratio, the same content was extended over two pages depending on the environment.
*The gradation of the text box did not convert correctly.
*The space between dots differed from the original file.
*The text in the shape was displayed with zero width.
*When slicers were added in Excel 2010, the figure displayed was all black.

Conversion from PowerPoint

*When the OLE data was arranged as an object in Powerpoint 2010, it was not converted and was missing.
*When there was white space at the end of a line, the layout collapsed.
*The arrangement and the margin in a cell were not correctly processed.
*When a line break occurred, the layout of the border collapsed.
*When the figure was arranged just before the end of the page, it was not converted correctly.
*The layout of the vertical writing text in the text box collapsed.

Conversion from PDF

*Failing to read the font information, font sizes were increased.
*Images in the file were not converted and were missing.
*The conversion failed when JBIG2 images were included in the file.
*The color space was not processed correctly and it failed to display.

Conversion to Flash

*Bold and italic specifications were not outputted correctly.
*A white border, which was not in the original layout, was outputted.

Conversion to images

*The background color became black after converting to TIFF.
*JPEG compression was invalid when outputting to CMYK TIFF.
*The file was outputted in reverse when converting from EMF.

Conversion to INX

*The stream output failed.

Other

*The conversion from the text file failed.
*When deleted data in the graph was read, a memory shortage occurred.
*When # was included in the file name, the conversion failed.

Enhancements

1. PDF Output Support:

• AES-128 bit/AES-256 bit encryption output
• PDF/A-1b:2005 output

2. Supports MS Word 2010 conversions

3. Supports MS Excel 2010 conversions

4. Supports MS PowerPoint 2010 conversions

5. Image Output Support (for Windows only):

• progressive JPEG output
• interlace PNG output
• 256 tone grayscale output
• 256 color output
• GdiPlus smoothing
• TIFF/CMYK output
• TIFF Compression output with the following:
• LZW
• JPEG
• DEFLATE
• RUNLENGTH
• CCITT Group 4
• CCITT Group 3

6. Flash Output Support:

• Allows users to use ActionScript 1.0 to stop random pages, disable page navigation button or links…etc.
• Each individual page from the original file can be outputted to a separate file
• Allows users to downsample raster images with arbitrary sizes
• Enhanced text manipulation including search, select or reverse display…etc. through the text output method

7. Other:

• Support for Microsoft.NET Framework 4.0 (for Windows only)

Corrections:

Conversion from Word

*The text box in an anchored paragraph in the table cell was not correctly arranged or dropped with Word 2007/2010 conversions.
*The height of the margin was not correctly reflected even if the output position was specified to the figure or the text box with Word 2007/2010 conversions.
*Figures with insufficient attribute information were not outputted correctly with Word 2007/2010 conversions.
*When the text was added between parentheses, it overlapped with Word 2007/2010 conversions.
*Grouped shapes in header/footer were not always positioned correctly with Word 97-2003 conversions.
*When there was a problem in the calculation of the number of lines in one page, the page position would shift with Word 97-2003 conversions.
*Table titles were not effective with Word 97-2003 conversions.
*Unnecessary work files were created with Word 97-2003 conversions.
*Tab positions in header/footer were not correctly positioned with Word 97-2003 conversions.
*Problems with processing occurred when the minimum value was specified for line spacing, which resulted in wide spaces between lines with Word 97-2003 conversions.
*Characters were squeezed together and overlapped with Word 97-2003 conversions.
*When problems with the character-code output for symbol fonts occurred, it resulted in garbled numbers and cirlces with Word 97-2003 conversions.
*The space between lines changed when the OLE object had been inserted with Word 97-2003 conversions.
*The table of contents was not outputted with Word 97-2003 conversions.
*When multiple bookmarks were set to the same position their hyperlinks were lost with Word 97-2003 conversions.
*The position of ruled lines around characters in a table shifted with Word 97-2003 conversions.
*The character attribute settings in Style was not correctly reflected with Word 97-2003 conversions.
*Problems with the default table border occurred so borders were not correctly outputted with Word 97-2003 conversions.
*The header and the body text overlapped with Word 97-2003 conversions.

Conversion from Excel

*Unnecessary text box background was outputted.
*The magnification of the worksheet display in print settings was not reflected, the stroke width was not correctly outputted.
*The magnification of the worksheet display in print settings was not reflected when the font size in header/footer was changed.
*When the number of pages for either width or height were specified, Fit to Page settings in Page Setup were ignored, but now it ouputs with the specified page number.
*When the number of pages for both width and height were not specified, Fit to Page settings in the Scale in Page Setup were ignored. Therefore, the width and height values for only the first page was outputted by default.
*The cell border specified to the row title was outputted to the cell below it.

Conversion from PowerPoint

*Support for the setting of the slide beginning number with PowerPoint 2007/2010.
*Vertical writing in the text box did not rotate when it was specified to rotate by certain degrees.
*When symbols were specified for the bullets in a list, it would result in garble.
*Figures and text with a hidden attribute were outputted and shown.
*The fixed-pitch font was allocated to the alternative font of the variable-pitch font which increased the width of the text.
*Some figures were not able to correspond to the vertical and horizontal flips.
*If the system color was set to a fill color, an invalid color would be outputted. It can now be outputted by setting the color value with the fixed table.
*There was a problem in calculation of the distance between text area and images causing the text to shift.

Other

*The conversion terminated abruptly when -GDI Smooth was specified with the image output.
*There was a problem in detecting file formats, causing text file conversions to fail.
*Sometimes font sizes decreased because the selector of the tagname.classname was not supported with SVG conversions.
*XPS would not convert with the NET Interface. It is fixed now. (XPS output is only available for SBC Plus)
*The conversion failed if # was included in the target file name.
*The default value of 100% when neither width nor height were specified in SVG was applied to the default A4 size with the conversion from SVG. Now it is made available to output the % size as the height and width of viewBox if viewBox is effective when directly converting SVG.

An example of a possible application is to utilize Formatter to generate a report and then use Digital Signature to sign the report before sending it to customers. The signature assures customers the report has not been tampered with. Another scenario is if a contract were being generated on the server, signature fields could be added when the contract is generated and sent to the customer. Then the customer using a desktop solution, like Acrobat or Acrobat Pro could sign it and and send it back. Automated verification is very useful and valuable when used together with a content management system.

Each individual has a public key and a private key which is either generated on the owner’s desktop or by a Certificate Authority.  A private key is a key only the owner knows, while the public key is available to everyone.  Your public key is your digital address. Users can locate public keys in a certificate store such as Windows Certificate Store or the owner can send it to you directly. The public key is used to encrypt data (lock), while the private key is used to decrypt data (key). For example I would use a co-worker’s public key to encrypt a document, so that only they can open it.

Although it is very difficult to forge a signature, it is possible. One method of preventing forgery is using a  Certificate Authority. The Certificate Authority (CA) is a third party between the sender and the receiver. The CA create the public/private key pair in place of the owner, after the owner has  provided proof of  identity. The Certificate Authority also issues a digital certificate containing the owner’s information and current standing with the Certificate Authority. With the addition of a Certificate Authority the work flow would proceed as follows; I have a message, which I first digitally sign with my public key and then I encrypt the entire message with the receiver’s public key and attach my digital certificate. The receiver then decrypts the message using their private key and uses the digital certificate to verify my identity. The Rainbow PDF Digital Signature is a software that facilitates adding and reading digital signatures and certificates. However unlike desktop solutions, it is a server-based digital signing module.

To learn more about digital signatures check out our posts and the FAQ.

Disruptive technologies are nothing new and the difference between a good company and a great company is how the transition is managed. The most common fear is obsolescence. The best way to handle disruptive technology is to embrace it and have criteria in place to measure each new technology that comes along to see if it fits your business. Luck is created when preparation meets opportunity.

All too often as companies, we forget that we are offering a solution to someones real problem and not simply a product or service. For example when I purchase a car, I’m buying mobility, status and a sense of control in that I can choose when I arrive at my destination. This need is great enough that I’m willing to forgo cheaper alternatives like the bus or train. What customers are actually purchasing from you will vary from person to person. Knowing and understanding what customers are purchasing will empower you to be ready for any disruptive technology. Carefully examine the new disruptive technologies in your field and see if they improve the quality of your solution or delivers it faster or cheaper. If they fulfill one of those areas and are worth the cost, then it makes sense to try to incorporate that technology into your business model..

By understanding the solution customers are purchasing and the attributes of your product that affect the quality of the solution, you’ll be much better prepared for the next disruptive technology. And when the right technology comes along you’ll be able to create your own luck.

The following issues have been corrected:
1) Conversion from PDF
*Yen mark was outputted as back slash. It is now possible to output the Yen mark in Japanese font.

2) Conversion from Word
*The width of the row in the table was not correctly acquired and the layout before and after the table occasionally collapsed.
*There was a problem in the judgment of the height of the header and the image in the header was not always outputted.
*There was a problem in the judgment of the Orient character and a line break occurred in the middle of the English word.
*An unnecessary character string in the field was outputted.
*Left margin of a border around the paragraph in header/footer was not considered.
*An extra white space occasionally appeared at the head of the next page because the space set after the paragraph was pushed to the next page.
*An extra white space occasionally appeared at the head of the next page because the space between paragraphs was pushed to the head of the next page.
*There was a problem in acquiring the font and the layout occasionally collapsed due to the difference of the width of the characters.
*The hanging indent was not reflected in the paragraph.
*Text in was missing.
*The margins were wider in the text box and the line break point changed or overflow of text would occur.
*The reverse rotation attribute of a figure was not correctly processed from MR2.
*The text box position in the table and the output order were wrong.
*The line drawing of the paragraph occasionally shifted.
*Borders set around the character strings in the table occasionally
shifted.

3) Conversion from Excel
*Number of copies in the Page Setup was disregarded.
*Line styles were not correctly reproduced. A line occasionally outputted twice.
*Support for conversion of a file deviated from the file format specification of Excel.

4) Conversion from PowerPoint
*The shadow set to a transparent image was not correctly processed.
*The character from the master template that was not supposed to output occasionally appeared.
*The ”unknown document type” error occurred failing in the file distinction.

5) Other
*The font size was not always correct when converting to SVG.
*Bold and italic were not correctly reflected when converting to Flash.
*When converting from JPEG to images, there was a problem in acquiring the resolution and the specified resolution was ignored.