iSiloX and iSiloXC revision history

iSiloX

home | information | support | download | iSilo.com

iSiloX/iSiloXC revision history

iSiloX for Windows® 6.15 (January 6, 2014)

Version 6.15 addresses the following issues:

iSiloX for Windows®:

When converting an EPUB file, non-ASCII characters in the table of contents page may convert to question mark characters.

iSiloX for Windows® 6.10 (February 13, 2013)

Version 6.10 addresses the following issues:

iSiloX for Windows®:

Groups may not save.

iSiloX for Windows®, iSiloXC for Windows®, and iSiloXC for Mac OS X 6.09 (January 9, 2013)

Version 6.09 makes the following changes:

iSiloX for Windows®:
iSiloXC for Windows®:
iSiloXC for Mac OS X:

When parsing CSS files, changed to ignore a semicolon immediately after a selector identifier.

Version 6.09 addresses the following issues:

iSiloX for Windows®:
iSiloXC for Windows®:
iSiloXC for Mac OS X:

JPG images that utilize a horizontal sampling ratio of 4:1 convert into a green monochrome image.
Parsing of CSS fails when a pseudo function uses numeric parameters.

iSiloX for Windows®, iSiloXC for Windows®, and iSiloXC for Mac OS X 6.04 (January 3, 2012)

Version 6.04 adds the following new features:

iSiloX for Windows®:
iSiloXC for Windows®:
iSiloXC for Mac OS X:

Added ability to convert unencrypted EPUB files.
Added option to generate web links for unresolved http and mailto URLs.

Version 6.04 addresses the following issues:

iSiloX for Windows®:
iSiloXC for Windows®:
iSiloXC for Mac OS X:

Documents with a large number of external document links may fail to convert correctly.

iSiloX for Windows® 5.18 (July 2, 2010)

Version 5.18 adds the following new features:

iSiloX platforms:

Added support for generating registration codes keyed to the device ID.
Added support for generating 18-character extended registration codes.

Version 5.18 addresses the following issues:

All platforms:

List items that use an alphabetic numbering style results in incorrect lettering starting from Z.

iSiloX for Windows® 5.12 (April 5, 2010)

Version 5.12 addresses the following issues:

All platforms:

Source files with non-ASCII characters in their filenames may fail to convert.

iSiloX for Windows®:

Adding or modifying a cookie results in the cookie expiration time getting mangled.
Modifying or adding an external document entry results in only the first character of the document name, link prefix, and map file being saved or displayed.
Modifying or adding a URL filter may result in the filter parameters being saved incorrectly.
The destination column does not correctly show non-ASCII characters.
The categories list gets corrupted upon restarting the application.

iSiloX for Windows® 5.10 (February 1, 2010)

Version 5.10 adds the following new features:

iSiloX platforms:

Added support for scheduling using the native Task Scheduler on Windows Vista and Windows 7.
Added support for installing documents through Windows Mobile Device Center on Windows Vista and Windows 7.
Added support for iSiloX Clipper running in Protected Mode in Internet Explorer on Windows Vista and Windows 7.
Added Groups feature for use in organizing conversion entries.

All platforms:

Added automatic removal of the byte order mark (BOM) character from Unicode source HTML content.
Changed to allow tables to inherit style values instead of starting with default styles.

Version 5.10 addresses the following issues:

All platforms:

A link element with a css type attribute that has a media attribute with no value causes the conversion to hang.

iSiloXC 4.41 for Mac OS X (July 10, 2009)

Version 4.41 adds the following new features:

iSiloXC for Mac OS X:

Initial release of universal binary that runs natively on both Intel and PowerPC computers running Mac OS X 10.4 and later.

iSiloX for Windows®/iSiloXC 4.37 (January 1, 2008)

Version 4.37 adds the following new features:

iSiloX platforms:

Added Windows Mobile 5 and Windows Mobile 6 to ActiveSync quick setup device list.

Version 4.37 addresses the following issues:

All platforms:

Conversion of PNG images that use a palette and a filter may result in a garbled image.

iSiloX for Windows®/iSiloXC 4.36 (September 6, 2007)

Version 4.36 adds the following new features:

All platforms:

When updating the IXL file after conversion, create a temporary file first, then overwrite the original.

Version 4.36 addresses the following issues:

All platforms:

When using the title as the destination file name and the title has a line break, the file does not get created.

iSiloX 4.35 for Windows® (July 9, 2007)

Version 4.35 addresses the following issues:

iSiloX for Windows®:

iSiloX Clipper crashes in Internet Explorer 7.

iSiloX/iSiloXC 4.32 (May 15, 2006)

Version 4.32 addresses the following issues:

All platforms:

When a set of source HTML files contains a hyperlink to an image, one or more other images in the document may disappear.
When converting a local file, the application may report the file as having an unsupported content type.

iSiloX/iSiloXC 4.31 (March 7, 2006)

Version 4.31 addresses the following issues:

All platforms:

Added support for handling HTTP responses with multiple Content-Type headers.
A text transform property applied to a block level element would have no effect.

iSiloX for Windows®:

When shutting down the system and the option is set to save the document list automatically, iSiloX still presents a prompt to save the document list.

iSiloX/iSiloXC 4.3 (January 9, 2006)

Version 4.3 addresses the following issues:

All platforms:

Added URL correction logic to handle the case where a link uses a URL with one too many "../".

iSiloX/iSiloXC 4.29 (November 7, 2005)

Version 4.29 adds the following new features:

All platforms:

Added recognition of application/xhtml+xml and .xhtml/.xhtm as HTML extensions.

Version 4.29 addresses the following issues:

All platforms:

External document links whose original source URLs included a query portion would not be properly converted.

iSiloX/iSiloXC 4.28 (September 6, 2005)

Version 4.28 adds the following new features:

All platforms:

Added support for interpretation of percentage line height styles.

iSiloX for Windows®:

Added support for GZIP compressed content in iSiloX Clipper.

Version 4.28 addresses the following issues:

All platforms:

When using a proxy that requires authentication, accessing a page that redirects results in a failure to correctly authenticate with the proxy.

iSiloX for Windows®:

When exiting iSiloX when it is on a secondary monitor, it does not restart on the secondary monitor.

iSiloX for Mac OS:

When performing a HotSync with files to install to the memory card, the iSilo Install conduit would only install every other file during each sync.

iSiloX/iSiloXC 4.27 (July 5, 2005)

Version 4.27 adds the following new features:

All platforms:

Added messages for when page limit or text limit is exceeded.

Version 4.27 addresses the following issues:

All platforms:

Conversion of JPEG images that use 16-bit quantization values do not convert correctly and may cause conversion to crash.
Links to external document targets by name may be generated incorrectly.

iSiloX platforms:

When selecting multiple entries to add a common schedule, if one or more of the selected entries does not already have a schedule, the new schedule may not be added.

iSiloX/iSiloXC 4.26 (May 10, 2005)

Version 4.26 adds the following new features:

All platforms:

Added support for id attributes in all elements as link targets.

Version 4.26 addresses the following issues:

All platforms:

RSS files using a lastBuildDate element before an image element would result in the URL of the image appearing instead of the image.
If two or more URLs in a document are different but equal up to about 500 characters, conversion fails with a message about one or more errors.
Content with a specified encoding of US-ASCII fails to convert.

iSiloX platforms:

The iSiloX Install conduit does not install files when the HotSync® synchronization mode is Fast or Slow.

iSiloX/iSiloXC 4.25 (March 7, 2005)

Version 4.25 adds the following new features:

All platforms:

Added recognition of application/rdf+xml as an RSS content type.
Added recognition of text/plain RSS content.
Added ability to specify a maximum link depth for off-site URLs.
New .ixl element: Under the <LinkOptions> element, added the <MaximumOffsiteDepth> element for specifying the maximum off-site link depth.

iSiloX platforms:

In the Link properties, added the "Maximum off-site link depth" field.

iSiloX for Windows®:

For Tools/Make Font, added ability to specify the character set for the font with support for the following:
- Central European (Windows-1250)
- Cyrillic (Windows-1251)
- Western European (Windows-1252)
- Greek (Windows-1253)
- Turkish (Windows-1254)
- Hebrew (Windows-1255)
- Arabic (Windows-1256)
- Baltic (Windows-1257)
- Vietnamese (Windows-1258)

Version 4.25 addresses the following issues:

All platforms:

A page with both frames and a meta refresh tag causes conversion to fail.
Area tags that do not specify a shape are incorrectly ignored instead of assuming a default of rectangle.
RSS files with processing instructions such as <?xml-stylesheet> would cause an unrecognized content type error.
Empty image maps cause conversion to silently fail.
HTML files with multiple image maps with the same names cause conversion to silently fail.
Domain comparisons were performed as exact matches instead of being case-insensitive.

iSiloX for Windows®:

In iSiloX Clipper, adding a Path destination via the context menu adds an External memory card destination instead of a Path destination.
In iSiloX Clipper, adding a Path destination via the Properties dialog adds an incorrectly formatted entry to the destination list.

iSiloX/iSiloXC 4.2 (January 5, 2005)

Version 4.2 adds the following new features:

All platforms:

Added RSS conversion capability.
Added handling of image maps.

Version 4.2 addresses the following issues:

All platforms:

Links with non-ASCII characters in the name in source files with multi-byte encodings may not work in the converted document.
Redirected URLs may result in unresolved links in cases where there is a direct link to the final URL from elsewhere.
Converting a text file where the length of the file name minus the .txt extension if any plus the number of non-alphanumeric characters multiplied by two is greater than 32 characters may result in a crash.
The file names of files queued for installation to external media where the document entry specified a dynamic title component would be the title with the dynamic title specification instead of the evaluated specification.

iSiloX/iSiloXC 4.15 (October 4, 2004)

Version 4.15 adds the following new features:

All platforms:

Added support for the following dynamic title components:
- \Xdate; for the conversion start date with the optional parameters Y, Y2, M, M2, D, and D2.
- \Xtime; for the conversion start time with the optional parameters, H, H2, M, M2, S, and S2.
- \Xtitle; for the first source file title.
- Manuals updated with documentation for dynamic title components.

Version 4.15 addresses the following issues:

All platforms:

Exporting all targets as named targets may generate a corrupt document.
A received cookie with a domain field value that starts with a period may not be saved, preventing its correct sending.
Conversion fails if an image file has an invalid format.

iSiloX/iSiloXC 4.1 (August 13, 2004)

Version 4.1 adds the following new features:

All platforms:

Added support for external document linking (e.g., cross-document linking).
To support external document linking, added the following new .ixl elements:
- Under the <LinkOptions> element, added the <ExternalDocuments> element for specifying links to external documents using <Specification> sub-elements. See the .ixl file format documentation for more information.
- Added the <Targets> element for specifying anchors that can be targets of links from other documents. See the .ixl file format documentation for more information.
If an anchor target name begins with '#', ignore it (i.e., effectively becomes )
Added support for conversion of table cell CSS specified-widths using inches to assume 72 pixels per inch.
When parsing CSS, if the previous selector ended with a comma but there is no additional selector, ignore the error. Ex: #super h3, { display: block; }
Added support for handling of relative URLs in <meta http-equiv="Refresh"> that have a zero delay.

iSiloX platforms:

In the Link properties, added External Documents button for accessing new External Documents dialog for specifying links to external documents.
In the Properties dialog, added the Targets properties for specifying anchors that can be targets of links from other documents.

Version 4.1 addresses the following issues:

All platforms:

When copying an entry with both cookies and scheduling, the application may crash.
URL filters were being ignored.
When exporting all targets, a crash may result.
Having many external targets or exported targets may generate a corrupt document.

iSiloX for Mac OS:

On systems without Palm Desktop 4.0 or later, a message saying that HotSyncLib.PPC appears when attempting to start iSiloX.

iSiloX/iSiloXC 4.05 (June 23, 2004)

Version 4.05 adds the following new features:

All platforms:

Added mapping of Unicode 0xFF0D long hyphen to JIS 01 3D.
For HTTP requests, added sending of the "Referer" header line. Some sites check the Referer header line to prevent deep-linking, thus causing conversion of content at such sites to not convert correctly.
Added automatic redirection to the target page of a meta refresh element in an HTML page when the refresh delay is zero. (i.e., <meta http-equiv="Refresh" content="0;URL=http://www.acme.org">)

iSiloX for Windows®:

The iSilo™ Install conduit gets support for installation of documents to user-specified paths.
The iSilo™ ActiveSync® service provider gets support for installation of documents to user-specified paths.
In the HotSync® Users dialog used for adding HotSync® destinations, added new Destination option Path for user-specified paths.
In the ActiveSync® Devices dialog used for adding ActiveSync® destinations, added new Destination option Path for user-specified paths.
On the Destination properties page, added Path item to right-click context menu for changing the HotSync® and ActiveSync® destinations to Path, including destination path modification.

iSiloX for Mac OS:

For Mac OS 9.1 or later or Mac OS X version 10.1 or later with Palm™ Desktop 4.0 or later added iSilo™ Install conduit to support automatic installation of converted documents to external memory card during HotSync®.
In the HotSync® Users dialog used for adding HotSync® destinations, added new Destination options External memory card and Path. The Path option is for user-specified paths.
On the Destination properties page, added control-click context menu for User Name list for changing the destination to any of the available destination options of Handheld device memory, External memory card, and Path, including destination path modification.
For installation on Mac OS X, help files now go to the User Domain instead of the Local Domain, thus no longer requiring administrator privileges to install the help files.

Version 4.05 addresses the following issues:

All platforms:

Lines longer than 128 characters in source files may become truncated.
Conversion of grayscale JPEG images may result in a garbled image.
List elements may have extraneous spaces following them causing insertion of blank lines in display.
In HTML source files, if the opening bracket of a tag begins on a two kilobyte boundary following a line break consisting of a CR and a LF, it may be incorrectly skipped during parsing, resulting in the following characters being interpreted as content.
Conversion of JPG images may result in a blank green image in the converted document.
Long paragraphs in multi-byte encoded text may become truncated.

iSiloX for Windows®:

Documents created with iSiloX Clipper and given the Unfiled category creates an "Unfiled" category in iSilo™ 4.05.

iSiloX for Mac OS:

If two identical URLs are added as sources to the same entry, start of conversion fails.

iSiloX/iSiloXC 4.01 (January 2, 2004)

Version 4.01 adds the following new features:

All platforms:

Added support for id attribute in div tag to serve as a hyperlink target.
If a document specifies that its content is UTF-16 encoded, but does not appear to be so, assume that it is Windows-1252 encoded.

Version 4.01 addresses the following issues:

All platforms:

CSS data containing non-ASCII characters may result in incorrect formatting of content.
Tables containing cells with large rowspans may fail to convert.
If a file is specified as UTF-16 encoded and has an odd number of bytes, conversion may hang.
If a file has multiple meta tags, only the first one is used, whereas the last should be used.
When using the option to include tables reachable only up to a certain level, the converted document may display blank and show a fixed percentage of 99%.
Converting a file that uses Big5 encoding but which does not specify its encoding may result in a corrupt converted document.

iSiloX for Windows®:

When the Windows task bar is either at the left or top, the position of the iSiloX window would shift in the direction of the task bar by the width of the task bar each time the application is launched.
If two HotSync names differ only in case, installation to one may incorrectly install to the other.
If two HotSync names differ only in case, it may not be possible to add both as destinations.
The enabled/disabled state of the lossy image controls in the Image properties would not being set correctly.

iSiloX/iSiloXC 4.0 (October 15, 2003)

Version 4.0 adds the following new features:

All platforms:

Added ability to apply lossy compression to images to significantly reduce the size of converted documents containing images. This type of compression is best applied to continuous-tone images. The following options were added to support this feature:
- Do not apply lossy compression to any images
- Apply lossy compression to lossy source images only (i.e., JPEG source images)
- Apply lossy compression to images with at least 200 unique colors
- Apply lossy compression to images with at least 100 unique colors
- Apply lossy compression to images with at least 50 unique colors
- Apply lossy compression to images with at least 20 unique colors
- Apply lossy compression to images with at least 10 unique colors
- Apply lossy compression to all images
- Adjustable image quality setting for images compressed using lossy compression
Added transcoding capabilities, giving the ability to convert text between different text encodings. Content in a given source encoding can thus be transcoded to the supported encoding of a target device.
Example of use: The source content is encoded using EUC-JP, an encoding for Japanese, while the target device only supports the Shift-JIS encoding for Japanese. This means that the source content can not be viewed correctly on the target device. The new transcoding support gives the ability to transform the EUC-JP encoded source content to content encoded using Shift-JIS, making the content viewable on the target device.
With transcoding capabilities, iSiloX/iSiloXC can now properly translate numeric character referencies and character entity references, which are defined with Unicode values, from HTML source files to their equivalent representations in the supported target encodings, where such representations are available in the target encoding.
The following output text encoding options were added to support this feature:
- Use the encoding of the first source file
- Do not transcode (e.g., raw character data)
- Specify any of the supported output encodings
For source files that do not specify their encoding, the option to specify the encoding to assume was added.
This feature supports the following input text encodings:
- Western European (ISO-8859-1)
- Western European (ISO-8859-15)
- Western European (Windows-1252)
- Greek (ISO-8859-7)
- Greek (Windows-1253)
- Southern European (ISO-8859-3)
- Baltic (ISO-8859-4)
- Baltic (Windows-1257)
- Central European (ISO-8859-2)
- Central European (Windows-1250)
- Cyrillic (ISO-8859-5)
- Cyrillic (KOI8-R)
- Cyrillic (Windows-1251)
- Turkish (ISO-8859-9)
- Turkish (Windows-1254)
- Vietnamese (Windows-1258)
- Arabic (ISO-8859-6)
- Arabic (Windows-1256)
- Hebrew (ISO-8859-8)
- Hebrew (Windows-1255)
- Chinese Simplified (GB18030)
- Chinese Simplified (GB2312)
- Chinese Traditional (Big5)
- Japanese (EUC-JP)
- Japanese (Shift-JIS)
- Korean (EUC-KR)
- Unicode (UTF-16)
- Unicode (UTF-8)
This feature supports the following output text encodings:
- Western European (Windows-1252)
- Greek (Windows-1253)
- Baltic (Windows-1257)
- Central European (Windows-1250)
- Cyrillic (Windows-1251)
- Cyrillic (KOI8-R)
- Turkish (Windows-1254)
- Vietnamese (Windows-1258)
- Arabic (Windows-1256)
- Hebrew (Windows-1255)
- Chinese Simplified (GB18030)
- Chinese Simplified (GB2312)
- Chinese Traditional (Big5)
- Japanese (EUC-JP)
- Japanese (Shift-JIS)
- Korean (EUC-KR)
- Unicode (UTF-8)
Added support for converting inline document drop-down menus specified using HTML <select> elements. Menus have the following capabilities:
- Menu items can be configured to jump to target locations within the document giving them hyperlink functionality.
- A menu can be styled with individually specified background and text colors.
- A menu can have a title that is not part of the menu item choices.
- The width of a menu can be automatic so it sizes to fit the widest item, or can be specified explicitly with a pixel width or as a percentage of the display width.
- See the iSilo Display Sample document that accompanies any iSilo™ 4.x installation for examples.
- From 4.0b1: Added hyperlink menu support for any select onchange attributes containing the text "location" followed by the text "value".
Added ability to include vCard (.vcf) and vCalendar (.vcs) files that are targets of links and which are within the maximum link depth. When the converted document is viewed and such links are followed on platforms with vCard and vCalendar support, the result is importation of the information into the appropriate registered applications.
Generation of documents in iSilo™ 4.x document format which has the following new features:
- Support for lossy compressed images
- Support for text encoding information
- Support for inline document menus
- Storage of vCard/vCalendar objects
- Backwards compatible with iSilo™ 3.x readers. Note: To use new features requires iSilo™ 4.x readers.
New .ixl elements:
- Under the <Source> element, added the <CharSet> element for specifying the text encoding to assume for source files that do not specify their encoding.
- Under the <ImageOptions> element, added the <LossyLevel> element for specifying whether to apply lossy compression to images and if so, which types of images.
- Under the <ImageOptions> element, added the <LossyQuality> element for specifying the image quality for images compressed using lossy compression.
- Under the <Document> element, added the <CharSet> element for specifying the output text encoding.

iSiloX platforms:

Added ability to select multiple document entries and apply property changes that affect all selected entries. This removes the laborious task of needing to modify each entry individually when the same changes are to be applied to more than one entry.
In Image Properties, added Lossy compression option and Lossy image quality option.
In Document Properties, added Text Encoding Options button, which displays the Text Encodings dialog for setting the output text encoding and the text encoding to assume for source files that do not specify their encoding.

iSiloX for Windows®:

Added Make Font command to Tools menu for invoking utility for generating bitmapped font sets for use with iSilo™ for Palm OS® and FontSilo™ with the following options:
- Select from any Windows® installed font
- Automatic resolution determination based on your device
- Automatic resolution determination based on screen resolution
- Specify any resolution from 50 to 300 DPI
- Include multiple font sizes from 5 to 99 point
- For each size, include multiple styles from plain, bold, italic, and bold italic
- User-specifiable font set name
- Option to queue created font set for automatic installation during HotSync®
- Option to save created font set to a file for later installation

Version 4.0 addresses the following issues:

All platforms:

The background color specified for an inline element such as <span> would not be inherited by an enclosed element.
Corrected handling of 1-bit, 2-bit, and 4-bit PNG images that use filters.
When performing an HTTP request on other than port 80, the port number was not being sent in the request header line.
In table cells where the HTML source has trailing whitespace before the closing tag, the last character of the cell content would be missing.
In the case where a link is to a page composed of frames, the link would be unresolved.
Content received from an HTTP URL without a content type header would not be converted.
When an error is encountered while receiving content during a redirect, iSiloX/C may fail to redirect.

iSiloX for Windows®:

Using iSiloX Clipper on a page with IFRAMES may clip just the frame and not the body content or any selected text.
Removed registration of ShellNew and Printing shell commands.
When the help is open within iSiloX Clipper for Internet Explorer, converting a text file may cause a crash.

iSiloX for Mac OS:

In iSiloX for Mac OS, when the Default Properties has no destinations, adding a new entry causes a crash.

iSiloX/iSiloXC 3.x

Click here for the iSiloX/iSiloXC 3.x revision history.