Free t9 predictive text software for linux

HyperLinked Text project is a Wiki-esque text file format and accompanying viewer.

HyperLinked Text (Hylt) is both a file format and a viewer for that format.

It uses (almost) flat text files to generate a Wiki-style database of hyperlinked pages, without either the complex markup of HTML or the esoteric database formats in which most Wikis store data.

It is geared towards users who desire a minimal interface between them and their data or like to store their data in formats which can be meaningfully stored in version control systems.

It was developed originally to match both of those goals, specifically for individuals writing fiction and wishing to track inter-character and inter-location relationships.

There are some interesting projects (OpenDocumentPHP, OpenDocument Fellowship) around the creation of OpenDocument Text from a Web-application.

Thus far none of these projects yielded a result to create an OpenDocument Text. Therefore - and inspired by an article in the German cumuter magasin ct - I desiced to implement a libary that takes a template document and adds some to it.

OpenOffice::OODoc::Text is a Perl module for the text processing submodule of OpenOffice::OODoc.

This manual chapter describes the text-oriented methods of OpenOffice::OODoc, implemented by the OpenOffice::OODoc::Text class, and inherited by the OpenOffice::OODoc::Document class.

These methods are not essentially dedicated to string processing; they are more precisely focused on text containers. A text container is a document element which can (and must) be used in order to support a text and integrate it at the right place and according to the right presentation rules. The OpenDocument specification defines a lot of such containers, and the present API supports many of them, such as paragraphs, headings, tables (or spreadsheets), lists, sections, and draw pages. Some of these containers can host other containers: for example, a table contains rows, a row contains cells, a section can contain almost everything including other sections, etc.

These features are text-oriented, but can be used on documents of any class, such as spreadsheets or presentations as well as text documents. So, the Text word doesnt mean that the features described in the present manual chapter are dedicated to OpenOffice.org Writer documents only. In the other hand, a few methods cant apply to any document class (ex: creating or retrieving draw pages makes sense with presentation and drawing documents only).

OODoc::Text should not be explicitly used in an ordinary application, because all its features are available through the OpenOffice::OODoc::Document class, in combination with other features. Practically, the present manual is provided to describe the text-oriented features of OpenOffice::OODoc::Document (knowing that these features are technically supported by the OpenOffice::OODoc::Text component of the API).

The OpenOffice::OODoc::Text class is a specialist derivative of OpenOffice::OODoc::XPath for XML elements which describe the text content of OOo/ODF documents. Here, "text content" means containers that can host text containers (i.e. tables, lists...) as well as flat text.
Knowing that the "styles.xml" member of an OpenOffice.org file can contain text (because some style definitions, such as page headers or footers, can contain text), the presently described features can be used against this member as well as the "content.xml" member.

This module should be used in combination with OpenOffice::OODoc::Styles, via the OpenOffice::OODoc::Document class, if the application has to handle detailed presentation parameters of text elements. This is because such parameters are held in styles elements and not in the text elements themselves, according to the principle of separation of content and presentation which is one of the foundations of the OpenDocument format.

XML From Plain Text (xfpt) is a program that reads a file of plain text that contains relatively simple markup, and outputs an XML file. It is intended to simplify the management of XML data.
The project is not a program that attempts to turn a plain text document into XML. Markup within text is introduced by ampersand characters, but is otherwise "soft". You can define what follows the ampersand, for example, &" to generate a "quote" element. There is also a macro facility that allows for higher level concepts such as chapters, displays, tables, etc.
Enhancements:
- The macro library has been extended to include preface, appendix, colophon, footnote, figure, and table.
- The program has one new directive to enable it to handle "nested" sections such as footnotes.

GD::Text is a Perl module with text utilities for use with GD.

SYNOPSIS

use GD;
use GD::Text;

my $gd_text = GD::Text->new() or die GD::Text::error();
$gd_text->set_font(funny.ttf, 12) or die $gd_text->error;
$gd_text->set_font(gdTinyFont);
$gd_text->set_font(GD::Font::Tiny);
...
$gd_text->set_text($string);
my ($w, $h) = $gd_text->get(width, height);

if ($gd_text->is_ttf)
{
...
}
Or alternatively
my $gd_text = GD::Text->new(
text => Some text,
font => funny.ttf,
ptsize => 14,
);

This module provides a font-independent way of dealing with text in GD, for use with the GD::Text::* modules and GD::Graph.

XML::DOM::Text is a piece of XML text in XML::DOM.

XML::DOM::Text extends XML::DOM::CharacterData, which extends XML::DOM::Node.

The Text interface represents the textual content (termed character data in XML) of an Element or Attr. If there is no markup inside an elements content, the text is contained in a single object implementing the Text interface that is the only child of the element. If there is markup, it is parsed into a list of elements and Text nodes that form the list of children of the element.

When a document is first made available via the DOM, there is only one Text node for each block of text. Users may create adjacent Text nodes that represent the contents of a given element without any intervening markup, but should be aware that there is no way to represent the separations between these nodes in XML or HTML, so they will not (in general) persist between DOM editing sessions. The normalize() method on Element merges any such adjacent Text objects into a single node for each block of text; this is recommended before employing operations that depend on a particular document structure, such as navigation with XPointers.

METHODS

splitText (offset)

Breaks this Text node into two Text nodes at the specified offset, keeping both in the tree as siblings. This node then only contains all the content up to the offset point. And a new Text node, which is inserted as the next sibling of this node, contains all the content at and after the offset point.

Parameters: offset The offset at which to split, starting from 0.

Return Value: The new Text node.

DOMExceptions:

INDEX_SIZE_ERR

Raised if the specified offset is negative or greater than the number of characters in data.

NO_MODIFICATION_ALLOWED_ERR

Raised if this node is readonly.

Tk::Text::Viewer is a text widget that can display text files under TK. It enable the user to search text and navigate in a Text widget. The reason for creating this module is that it doesnt require downloading of modules other that Tk; Look for widget options in the Tk::Text manpage. A separate viewer.pl program is included and can be used as a stand alone file browser.
The Viewer widget also inherits all the methods provided by the generic Tk::Widget and Tk::Text classes.
The following additional method is available for viewer widgets:
$text_view->Load($filename)
Load file into the text widget.
$text_view->LabelConfig(string or hash ref)
$text_view->LabelConfig(``Search:)
Change label for the search entry field. You might want to change this label if the widget is used in a non English application.
$text_view->LabelConfig(``-cursor=> dot)
Change one label widget option (for example cursor).
$text_view->LabelConfig({text=>Find:,-cursor=>dot,...})
Replace label widget options with your own set of options. Do not change the Name option of the label widget. See the Tk::Label manpage for valid options
$text_view->EntryConfig(string or hash ref)
Change the entry widget options. Read LabelConfig for information about parameters. See the Tk::Entry manpage for valid options.
Enhancements:
- This version requiers Tk 804. If you have older Tk you my use version 0.91
- fix Tk::Entry options like -text to comply with Tk 804.027
- Enable utf8 support for UTF-8 locale on Perl 5.8