<DocumentOptions>

The DocumentOptions element specifies miscellaneous options for the document.

Full element example

    <DocumentOptions>
      <PageBounds               value="hard"/>
      <UseDefaultCategory       value="no"/>
      <DefaultCategory>Unfiled</DefaultCategory>
      <HomePageNumber           value="1"/>
      <OpenHomePageOnDateChange value="yes"/>
      <CharSet>Windows-1252</CharSet>
    </DocumentOptions>

Sub-element summary

TagTypeDefaultDescription
<PageBounds> value hard Behavior at page boundaries
<UseDefaultCategory> value no Whether to set a default category for the document
<DefaultCategory> string n/a Default category for the document
<HomePageNumber> value 1 Page number of the document's home page. This option requires version 3.25 or later of iSiloX and iSiloXC.
<OpenHomePageOnDateChange> value no Whether to open the document on its home page if the document has changed. This option requires version 3.25 or later of iSiloX and iSiloXC.
<CharSet> string n/a Output document text encoding. This option requires version 4.0 or later of iSiloX and iSiloXC.

Sub-element descriptions

<PageBounds>

Description
Each file comprising the source of the document ends up as an individual page in the resulting iSilo™ document. The value of the PageBounds tag determines what happens when a document is scrolled or paged at a page boundary. Scrolling refers to using the scroll bars, dragging, or other software based means to scroll the document content. Paging refers to the use of hardware page up and page down keys or buttons to move across pages. Set the value attribute of the PageBounds tag to either rigid, hard, or soft, depending on how you want page boundaries treated: Examples
This example specifies that page boundaries should be hard.
  <PageBounds               value="hard"/>
This example specifies that page boundaries should be rigid.
  <PageBounds               value="rigid"/>
This example specifies that page boundaries should be soft.
  <PageBounds               value="soft"/>

<UseDefaultCategory>
<DefaultCategory>

Description
Set the value attribute of the <UseDefaultCategory> tag to yes and provide a category name in the DefaultCategory element to specify the default category in which to place the document.

Set the value attribute of the <UseDefaultCategory> tag to no to not specify a default category for the document.

The following describes what happens when opening a document with a default category for the very first time within iSilo™:

Read the following sub-sections for important notes on category support in iSilo™.

Palm OS® basic category support
Basic category support became available as of version 3.05 of "iSilo™ for Palm OS". This support utilized the built-in Palm OS® category functionality and thus has the same limitations, listed here:

Auto-categorization in "iSilo™ for Palm® OS"
In "iSilo™ for Palm® OS" version 3.05 and later, auto-categorization occurs in the background when the user is in the document list view. iSilo™ goes through the internal storage memory and the /Palm/Programs/iSilo, /Palm/Launcher, and /Palm/Programs/MSFiles folders of mounted memory cards and searches for documents that have never been opened nor categorized. For each such document, iSilo™ checks to see whether the document has a default category, and if so adds the document to the specified default category, creating the category if necessary first.

Auto-categorization in "iSilo™ for Pocket PC" and "iSilo™ for Windows Mobile™ Smartphone"
In "iSilo™ for Pocket PC" version 4.05 and later and in "iSilo™ for Windows Mobile™ Smartphone", auto-categorization occurs in the background when the user is in the document list view. iSilo™ goes through the /My Documents/iSilo folder and searches for documents that have never been opened nor categorized. For each such document, iSilo™ checks to see whether the document has a default category, and if so adds the document to the specified default category, creating the category if necessary first.

Hierarchical categories
Hierarchical categories and hence category support in general is available as of version 4.05 of all platform versions of iSilo™. This capability supports for up to ten levels of sub-categories, allowing for hierarchical organization of categories. You can specify a default category using a category path that specifies the categories at each level that lead to the final category. Use forward slashes as component separators in the path. An example hierarchical category path is /Business/Accounting, where Business is the top-level category and Accounting is a sub-category of the Business category.

No support in other versions
The default category of a document has no effect in versions of iSilo™ for which there is no category support.

Examples
This example specifies that the document has a default category and that it is "Photos".

  <UseDefaultCategory       value="yes"/>
  <DefaultCategory>Photos</DefaultCategory>
This example specifies that the document does not have a default category.
  <UseDefaultCategory       value="no"/>
This example specifies that the document has a default category and that the path of the category is "/Personal/Letters".
  <UseDefaultCategory       value="yes"/>
  <DefaultCategory>/Personal/Letters</DefaultCategory>

<HomePageNumber>

Description
Set the value attribute of the tag to the page number that you want to be the document's home page. The first page of a document is page one.

Examples
This example specifies that the home page is page one.
  <HomePageNumber           value="1"/>
This example specifies that the home page is page 15.
  <HomePageNumber           value="15"/>

<OpenHomePageOnDateChange>

Description
Set the value attribute of the tag to yes so that when the document is opened after being reconverted, it will open on the home page. Use the
<HomePageNumber> tag to specify the home page. Documents converted with this setting only have an affect in iSilo™ 3.25 and later.

Set the value attribute of the tag to no if you want the document to always open at the last location each time you open the document regardless of whether the document creation date has changed.

Examples
This example specifies that the document should open on the home page if it has changed.

  <OpenHomePageOnDateChange value="yes"/>
This example specifies that the document should not open on the home page even if it has changed.
  <OpenHomePageOnDateChange value="no"/>

<CharSet>

Description
The value of this tag specifies the output document text encoding. The target device must support the output text encoding in order for text to display correctly.

The following lists the possible values for this tag:

Also see the notes for the <CharSet> tag under the Source element.

Examples
This example specifies the output text encoding to be the UTF-8 Unicode text encoding.

  <CharSet>UTF-8</CharSet>

©1999-2017 DC & Co. All rights reserved.