Free predictive text on blackberry storm software for linux

Edit by Text Editors allows you to open a file with Kate, Kwrite, Kedit, Khexedit by a KDE service menu.

To install the service menu you must copy editby.desktop in ~/.kde/share/apps/konqueror/servicemenus

Tartan is a text parsing engine targeted at wiki text. The syntax specification is defined in YAML in the form of regex-based rules.

It supports layering and multiple output types. Rules for Markdown to HTML are included, with optional layered extensions for tables. Tartan text parser is implemented in Ruby, but looking to have implementations in other languages.

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.

Palm::Progect::Converter::Text is a Perl module to convert between Progect databases and Text files.

SYNOPSIS

my $converter = Palm::Progect::Converter->new(
format => Text,
# ... other args ...
);

$converter->load_records();

# ... do stuff with records

$converter->save_records();

This converts between Text files and Palm::Progect records and preferences.
The Text format used for import/export looks something like this:
[x] Level 1 Todo item
[10%] Child (progress)
. Child of Child (informational)

[80%] (31/12/2001) Progress item
[ ] Unticked action item
Here is a summary of the various types of records:
[ ] action type
[x] completed action type
< > action type with todo link
completed action type with todo link

[80%] progress type
[4/5] numeric type

. info type

[ ] [5] action type with priority
[ ] (15/7/2001) action type with date

[80%] [5] (15/7/2001) {category} progress type with priority and date and category

[80%] [5] (15/7/2001) {category} progress type with priority and date and category >

Text::Macro Perl module is a template facility whos focus is on generating code such as c, java or sql. While generating perl code is also possible, there is a potential conflict between the control-symbol and the perl comment symbol.
Perl is excelent at manipulating text, and it begs the question why one would need such a tool.
The answer is that good code design should be such that applications should not have to be modified so as to make configuration changes. Thus external configuration files/data is used. However, if these files are read in as perl-code, then simple errors could crash the whole application (or provide subtle security risks). Further, it is often desired to invert the control flow and text-data (namely, make the embedded strings primary, and control-flow secondary). This is the ASP model, and for 90% HTML, 10% code, this works great.
This module supports many control facilities which directly translate into perl-control facilities (e.g. inverting the ASP-style code back into perl-style behind the scenes). The inversion process is cached in a simple user object.
The module was initially inspired by Text::FastTemplate by Robert Lehr, whos module didnt completely fullfill my needs.
Main features:
- fast, simple, robust
- code-generating-centric feature-set
- substitutions stand-out from template
- macro-code embedded in text
- OOP
- external and internal includes (for clearifying complex control-flow)
- scoped variable-substitutions
- line-based processing (like cpp)
- usable error messages

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::Reform is a Perl module for manual text wrapping and reformatting.

SYNOPSIS

use Text::Reform;

print form $template,
$data, $to, $fill, $it, $with;


use Text::Reform qw( tag );

print tag B, $enboldened_text;

The form sub

The form() subroutine may be exported from the module. It takes a series of format (or "picture") strings followed by replacement values, interpolates those values into each picture string, and returns the result. The effect is similar to the inbuilt perl format mechanism, although the field specification syntax is simpler and some of the formatting behaviour is more sophisticated.

A picture string consists of sequences of the following characters:

<

Left-justified field indicator. A series of two or more sequential

Right-justified field indicator. A series of two or more sequential >s specify a right-justified field to be filled by a subsequent value. A single < is formatted as the literal character <



Fully-justified field indicator. Field may be of any width, and brackets need not balance, but there must be at least 2 < and 2 >.

^

Centre-justified field indicator. A series of two or more sequential ^s specify a centred field to be filled by a subsequent value. A single ^ is formatted as the literal character <

>>>. br ]]].[[[[ br br A numerically formatted block field with the specified number of digits to either side of the decimal place. Just like a >>.<<less