OpenVanilla (OV) is an input method (IM)/output filter (OF) framework
designed for better end-user text processing experiences. For example,
OpenVanilla provides a comprehensive set of Traditional Chinese input
methods that are lacking or of which counterparts are functionally
deficient/unsatisfactory in Apple's Mac OS X. Many Simplified Chinese
users also find this framework useful. A Tibetan IM module is also
available.
OpenVanilla framework is a set of header files for OpenVanilla module
development.
This is a collection of modules that formats text from HTML syntax
trees. Bug reports and discussions about these modules can be sent
to the <libwww@perl.org> mailing list.
The modules present in this package are:
HTML::Formatter - Base class for various formatters. Formatters
traverse a syntax tree and produce some textual output.
None of the current formatters handle tables or forms yet.
HTML::FormatText - Formatter that converts a syntax tree to plain
readable text.
HTML::FormatPS - Formatter that outputs PostScript code.
Smi is a Simple Markup Interpreter / filter for simplified Markup dialect.
smi can be fed text in Markdown, and return HTML output. smi can be fed
HTML, and return the markup translated to entities. I use smi as a filter
for devel/cgit to parse the README.md files, returning HTML output. I am
also using it to markup wiki pages, for a git backed wiki. The use cases
are limited only by your imagination.
This module provides a parser which parses and interprets (though
not fully) LaTeX documents and returns a tree-based representation
of what it finds. This tree is a LaTeX::TOM::Tree. The tree contains
LaTeX::TOM::Node nodes.
This module should be especially useful to anyone who wants to do
processing of LaTeX documents that requires extraction of plain-text
information, or altering of the plain-text components (or
alternatively, the math-text components).
Plucene is a fully-featured and highly customizable search engine
toolkit based on the Lucene API.
It is not, in and of itself, a functional search engine - you are
expected to subclass and tie all the pieces together to suit your own
needs. The synopsis above gives a rough indication of how to use the
engine in simple cases. See Plucene::Simple in the distribution for one
example of tying it all together.
Pod::Autopod is designed to generate pod documentation of a perl
class by analysing its code. The idea is to have something similar
like javadoc. So it uses also comments written directly obove the
method definitions. It is designed to asumes a pm file which
represents a class.
Of course it can not understand every kind of syntax, parameters,
etc. But the plan is to improve this library in the future to
understand more and more automatically.
Pod works well, but writing it can be time-consuming and tedious. For example,
commonly used layouts like lists require numerous lines of text to make just a
couple of simple points. An alternative approach is to write documentation in
a wiki-text shorthand (referred to here as wikidoc) and use Pod::WikiDoc to
extract it and convert it into its corresponding Pod as a separate .pod file.
The format routine will format under all circumstances even if the width
isn't enough to contain the longest words. Text::Wrap will die under
these circumstances, although I am told this is fixed. If columns is set
to a small number and words are longer than that and the leading
'whitespace' than there will be a single word on each line. This will
let you make a simple word list which could be indented or right
aligned.
-Anton
<tobez@FreeBSD.org>
This is a CORE module. If you installed perl 5.003 or above, a
version of this module is already available to you. This CPAN
package is only here to update core distributions prior 5.005.
The version provided is the same that comes with perl 5.00502.
If you run a newer version of perl, the version of Text::ParseWords
included there may be newer. This package is not fully synchronized
with the perl distributions.
Please run "perldoc Text::ParseWords" to see what this module
is for.
About the project
We plan to build a program that will accept ASCII text as input and generate
International Morse Code as output. The output formats can be:
- . -..- - (text) on the console
Raw audio on /dev/audio (8bit PCM data)
.wav files
.ogg or (proprietary format) compressed audio
International Morse Code
Supported character set includes [A-Za-z] (all downcased as Morse is not case
sensitive), [0-9], ",-.?/" plus a few procedural characters (SK, AR, BT etc).