Free predictive text swearing software for linux

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.

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.

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.

Text::Starfish.pm and starfish is a Perl-based System for Text-Embedded Programming and Preprocessing.

SYNOPSIS

starfish [ -o=outputfile ] [ -e=initialcode ] [ -replace ] [ -mode=mode ] file...
where files usually contain some Perl code, delimited by < ? and ! >. To produce output to be inserted into the file, use variable $O or function echo.

(The documentation is probably not up to date.)

Starfish is a system for Perl-based text-embedded programming and preprocessing, which relies on a unifying regular expression rewriting methodology. If you know Perl and php, you probably know the basic idea: embed Perl code inside the text, execute it is some way, and interleave the output with the text. Very similar projects exist and some of them are listed in "SEE ALSO". Starfish is, however, unique in several ways. One important difference between starfish and similar programs (e.g. php) is that the output does not necessarily replace the code, but it follows the code by default. It is attempted with Starfish to provide a universal text-embedded programming language, which can be used with different types of textual files.

There are two files in this package: a module (Starfish.pm) and a small script (starfish) that provides a command-line interface to the module. The options for the script are described in subsection ""starfish_cmd list of file names and options"".

The earlier name of this module was SLePerl (Something Like ePerl), but it was changed it to starfish -- sounds better and easier to type. One option was `oyster, but some people are thinking about using it for Perl beans, and there is a (yet another) Perl module for embedded Perl Text::Oyster, so it was not used.
The idea with the `starfish name is: the Perl code is embedded into a text, so the text is equivalent to a shellfish containing pearls. A starfish comes by and eats the shellfish... Unlike a natural starfish, this starfish is interested in pearls and does not normally touch most of the surrounding meat.

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

MKDoc::Text::Structured::Inline is a Perl module to convert text to HTML without handling block-level tags.

SYNOPSIS

my $text = some_structured_text();
my $this = MKDoc::Text::Structured::Inline::process ($text);
my $that = MKDoc::Text::Structured::Inline::process_entities_only ($text);

Text::Templar is a document-generation object class.

SYNOPSIS

use Text::Templar;

my $template = < title >This is the title: < % METHOD title % >< /title >< /head >

< body >

< % METHOD body % >

< address >
< % METHOD footer % >
< /address >

< /body >
< /html >
EOF

my $templateObject = new Text::Templar
[ $template ];

$templateObject->title( "The Rest of the Story" );
$templateObject->body( @content );
$templateObject->footer( "Page 1" );

print $templateObject->render;