Pathway supports output to four different output media:

Word processor

Word processor outputs include Open Office, Word, and PDF files created from these processors.


Typeset output include InDesign and XeTeX outputs. InDesign creates an IDML file that can be imported and edited in the InDesign program. It requires the user have a license for this program. XeTeX generates a PDF file. Consequently the settings in Pathway need to produce the desired output without further editing. Unlike InDesign, XeTeX supports Graphite fonts which can be used to render languages with very complex scripts.


GoBible is the principle mobile output. It currently only works for scripture content. It could be made to work with dictionary (or other) content. Please let us know if this is a priority for you. Also, the current GoBible output depends on the fonts in the phone. If you need full Unicode support for the mobile media, let us know that too.

Smart Device

Epub is the main output format for the smart devices. This format optionally embeds the fonts. Epub can be converted to Kindle and other formats. It can display on smart phones, kindle, Nook, Sony Reader, etc. On the Windows platform it can be displayed with Calibre or Adobe Digital Edition. (These are free downloads). On the Android platform, epub output has been tested with Gitden. There are similar programs for displaying Epub on other platforms. Let us know if there are additional features you would like to see in this format.


HTML5 is a browser-oriented output that can be used on a desktop (Windows, Linux, or Mac), on a tablet or on a mobile phone device. It can also be used for archiving in a presentation format. Each word is displayed on its own page. The Table of Contents is converted to an Index to allow browsing to entries (main or reversal). A search feature is available that displays the page that has the word. If the FieldWorks Language Explorer data has semantic domains (for example as the result of a rapid word collection workshop), the program will also create a semantic index based on the semantic domains. It is also searchable.

Next topic: Special content processing