text processing
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5279
Docutils 0.4
Docutils is an open-source text processing system for processing plaintext documentation into useful formats. more>>
Docutils is an open-source text processing system for processing plaintext documentation into useful formats, such as HTML or LaTeX.
Docutils project includes reStructuredText, the easy to read, easy to use, what-you-see-is-what-you-get plaintext markup language.
<<lessDocutils project includes reStructuredText, the easy to read, easy to use, what-you-see-is-what-you-get plaintext markup language.
Download (1.2MB)
Added: 2006-01-11 License: Public Domain Price:
1382 downloads
WebService::GoogleHack::Text 0.15
WebService::GoogleHack::Text is a Perl module that implements some basic text processing such as parsing data etc. more>>
WebService::GoogleHack::Text is a Perl module that implements some basic text processing such as parsing data etc.
SYNOPSIS
use WebService::GoogleHack::Text;
#create an object of type Text
my $text = GoogleHack::Text->new();
# returns an hash words
%results=$text->getWords("file location");
# returns an hash of 3 word sentences
%results=$text->getSentences("file location", 3);
# this function reads the configuration file
%results=$text->readConfig("location of configuration file");
#removes HTML tags
%results=$text->removeHTML("string");
This is a simple Text processing package which aids GoogleHack and Rate modules. Given a file of words, it retreives the words in the file and stores it in a simple hash format. In addition, given a file of text, it can also form n word sentences.
<<lessSYNOPSIS
use WebService::GoogleHack::Text;
#create an object of type Text
my $text = GoogleHack::Text->new();
# returns an hash words
%results=$text->getWords("file location");
# returns an hash of 3 word sentences
%results=$text->getSentences("file location", 3);
# this function reads the configuration file
%results=$text->readConfig("location of configuration file");
#removes HTML tags
%results=$text->removeHTML("string");
This is a simple Text processing package which aids GoogleHack and Rate modules. Given a file of words, it retreives the words in the file and stores it in a simple hash format. In addition, given a file of text, it can also form n word sentences.
Download (0.088MB)
Added: 2006-12-04 License: Perl Artistic License Price:
616 downloads
MKDoc::Text::Structured::Inline 0.83
MKDoc::Text::Structured::Inline is a Perl module to convert text to HTML without handling block-level tags. more>>
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);
<<lessSYNOPSIS
my $text = some_structured_text();
my $this = MKDoc::Text::Structured::Inline::process ($text);
my $that = MKDoc::Text::Structured::Inline::process_entities_only ($text);
Download (0.014MB)
Added: 2006-08-24 License: Perl Artistic License Price:
1156 downloads
OpenOffice::OODoc::Text 2.032
OpenOffice::OODoc::Text is a Perl module for the text processing submodule of OpenOffice::OODoc. more>>
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.
<<lessThis 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.
Download (0.21MB)
Added: 2007-03-09 License: GPL (GNU General Public License) Price:
959 downloads
Text::MetaText 0.22
Text::MetaText is a Perl extension implementing meta-language for processing template text files. more>>
Text::MetaText is a Perl extension implementing meta-language for processing "template" text files.
SYNOPSIS
use Text::MetaText;
my $mt = Text::MetaText->new();
# process file content or text string
print $mt->process_file($filename, %vardefs);
print $mt->process_text($textstring, %vardefs);
# pre-declare a BLOCK for subsequent INCLUDE
$mt->declare($textstring, $blockname);
$mt->declare(@content, $blockname);
SUMMARY OF METATEXT DIRECTIVES
%% DEFINE
variable1 = value # define variable(s)
variable2 = "quoted value"
%%
%% SUBST variable %% # insert variable value
%% variable %% # short form of above
%% BLOCK blockname %% # define a block blockname
block text...
%% ENDBLOCK %%
%% INCLUDE blockname %% # include blockname block text
%% INCLUDE filename %% # include external file filename
%% INCLUDE file_or_block # a more complete example...
variable = value # additional variable definition(s)
if = condition # conditional inclusion
unless = condition # conditional exclusion
format = format_string # printf-like format string with %s
filter = fltname(params) # post-process filter
%%
%% TIME # current system time, as per time(2)
format = format_string # display format, as per strftime(3C)
%%
<<lessSYNOPSIS
use Text::MetaText;
my $mt = Text::MetaText->new();
# process file content or text string
print $mt->process_file($filename, %vardefs);
print $mt->process_text($textstring, %vardefs);
# pre-declare a BLOCK for subsequent INCLUDE
$mt->declare($textstring, $blockname);
$mt->declare(@content, $blockname);
SUMMARY OF METATEXT DIRECTIVES
%% DEFINE
variable1 = value # define variable(s)
variable2 = "quoted value"
%%
%% SUBST variable %% # insert variable value
%% variable %% # short form of above
%% BLOCK blockname %% # define a block blockname
block text...
%% ENDBLOCK %%
%% INCLUDE blockname %% # include blockname block text
%% INCLUDE filename %% # include external file filename
%% INCLUDE file_or_block # a more complete example...
variable = value # additional variable definition(s)
if = condition # conditional inclusion
unless = condition # conditional exclusion
format = format_string # printf-like format string with %s
filter = fltname(params) # post-process filter
%%
%% TIME # current system time, as per time(2)
format = format_string # display format, as per strftime(3C)
%%
Download (0.085MB)
Added: 2007-08-06 License: Perl Artistic License Price:
810 downloads
libany2uni 1.0.3
libany2uni is a library to extract raw unicode text from any written documents (office documents). more>>
libany2uni is a library to extract raw unicode text from any written documents (office documents).
It should be useful to developpers of search engine, text processing, corpus analysis, ....
UTF8 tool:
In the utils directory, you can find a tool using libany2uni. It is called any2utf8 It reads a document and outputs the text in UTF8, to the standard output.
To compile it, just type make.
Run it with ./any2utf8 < path + name of the document >.
You can also get metadata with the -m option.
<<lessIt should be useful to developpers of search engine, text processing, corpus analysis, ....
UTF8 tool:
In the utils directory, you can find a tool using libany2uni. It is called any2utf8 It reads a document and outputs the text in UTF8, to the standard output.
To compile it, just type make.
Run it with ./any2utf8 < path + name of the document >.
You can also get metadata with the -m option.
Download (0.22MB)
Added: 2006-08-21 License: GPL (GNU General Public License) Price:
1163 downloads
Emdros 1.2.0 pre262
Emdros is a text database engine for annotated or analyzed text. more>>
Emdros is an Open-Source text database engine for storage and retrieval of analyzed or annotated text.
Emdros has a powerful query-language for asking relevant questions of the data.
Emdros has wide applicability in fields that deal with analyzed or annotated text. Application domains include linguistics, publishing, text processing, and any other fields that deal with annotated text.
Main features:
- Linguistic analyses are the primary target domain. This includes all levels of analysis, such as morphology, syntax, and discourse analysis, and even phonology to some extent.
- Publishing is also a field where Emdros can be useful. Emdros supports breaking a text down into pages, chapters, paragraphs, etc.
- Text processing may benefit from Emdros if the problem involves annotating the text.
Emdros provides a conceptual model of text which can be quite liberating to use once it has been grasped.
Meta-data may also be stored, so long as there is some textual element with which it can be associated.
Emdros is good both for corpus linguistics (large amounts of text) and for field-linguistics (smaller amounts of data).
Fixed corpora, such as Biblical texts, are good candidates for making Emdros useful. Emdros is currently being used for large databases of the Hebrew Bible.
Dictionaries are also a target possibility. Emdros supports structuring of text documents down to minute details, while not losing the big picture.
Emdros embodies a particular model of text called the EMdF model. The primary advantage over XMLs data model is that object types (such as pages and chapters) need not be hierarchically structured or embedded, but may overlap. In addition, objects (such as a clause or a phrase) need not be contiguous, but may have gaps.
Emdros can output its results in XML. The XML carries its own standalone DTD and validates with a validating parser.
Emdros architecture
Emdros fits into a software architecture as follows:
+---------------+
| Client | User-written
+---------------+
|
+---------------+
| MQL | Emdros
+---------------+
|
+---------------+
| EMdF | Emdros
+---------------+
|
+---------------+
| DB | PostgreSQL or MySQL
+---------------+
At the top, there is a client which you, the user, must write. This client will take advantage of Emdross services to provide for the needs of your particlar database domain.
Then come the two Emdros-layers: The MQL layer and the EMdF layer. The MQL layer provides an interface to the MQL language. The MQL layer automatically takes advantage of the EMdF layer, which translates the MQL queries into SQL calls to the underlying database.
The underlying database takes care of storing the data, and retrieving it as directed by the EMdF layer.
The data domain which Emdros handles is that of text. Emdros provides a certain abstraction of text that makes it ideally suited to storing and retrieving annotated text, such as linguistic analyses of a text.
These analyses can be, e.g., syntactic analyses, morphological analyses, or discourse analyses, or all of these. Phonological analyses are also supported to some extent.
Emdros is particularly useful in domains where research questions need to be asked of databases of annotated text. This would include dictionary-making, Biblical language-research (Greek or Hebrew), other linguistic research, and research on annotated text in general.
Emdros has a particular model of text called the EMdF model. Users have attested, and our experience shows, that the EMdF model can be quite liberating when dealing with text as a programmer or program designer. Thus any application that deals with annotated text will likely benefit from the Emdros and the EMdF model.
Enhancements:
- The topographic part of the language was expanded.
- A TIGER XML importer was added.
- Beta quality C# bindings were added.
- Bugfixes were made, and the regression test suite was enhanced.
<<lessEmdros has a powerful query-language for asking relevant questions of the data.
Emdros has wide applicability in fields that deal with analyzed or annotated text. Application domains include linguistics, publishing, text processing, and any other fields that deal with annotated text.
Main features:
- Linguistic analyses are the primary target domain. This includes all levels of analysis, such as morphology, syntax, and discourse analysis, and even phonology to some extent.
- Publishing is also a field where Emdros can be useful. Emdros supports breaking a text down into pages, chapters, paragraphs, etc.
- Text processing may benefit from Emdros if the problem involves annotating the text.
Emdros provides a conceptual model of text which can be quite liberating to use once it has been grasped.
Meta-data may also be stored, so long as there is some textual element with which it can be associated.
Emdros is good both for corpus linguistics (large amounts of text) and for field-linguistics (smaller amounts of data).
Fixed corpora, such as Biblical texts, are good candidates for making Emdros useful. Emdros is currently being used for large databases of the Hebrew Bible.
Dictionaries are also a target possibility. Emdros supports structuring of text documents down to minute details, while not losing the big picture.
Emdros embodies a particular model of text called the EMdF model. The primary advantage over XMLs data model is that object types (such as pages and chapters) need not be hierarchically structured or embedded, but may overlap. In addition, objects (such as a clause or a phrase) need not be contiguous, but may have gaps.
Emdros can output its results in XML. The XML carries its own standalone DTD and validates with a validating parser.
Emdros architecture
Emdros fits into a software architecture as follows:
+---------------+
| Client | User-written
+---------------+
|
+---------------+
| MQL | Emdros
+---------------+
|
+---------------+
| EMdF | Emdros
+---------------+
|
+---------------+
| DB | PostgreSQL or MySQL
+---------------+
At the top, there is a client which you, the user, must write. This client will take advantage of Emdross services to provide for the needs of your particlar database domain.
Then come the two Emdros-layers: The MQL layer and the EMdF layer. The MQL layer provides an interface to the MQL language. The MQL layer automatically takes advantage of the EMdF layer, which translates the MQL queries into SQL calls to the underlying database.
The underlying database takes care of storing the data, and retrieving it as directed by the EMdF layer.
The data domain which Emdros handles is that of text. Emdros provides a certain abstraction of text that makes it ideally suited to storing and retrieving annotated text, such as linguistic analyses of a text.
These analyses can be, e.g., syntactic analyses, morphological analyses, or discourse analyses, or all of these. Phonological analyses are also supported to some extent.
Emdros is particularly useful in domains where research questions need to be asked of databases of annotated text. This would include dictionary-making, Biblical language-research (Greek or Hebrew), other linguistic research, and research on annotated text in general.
Emdros has a particular model of text called the EMdF model. Users have attested, and our experience shows, that the EMdF model can be quite liberating when dealing with text as a programmer or program designer. Thus any application that deals with annotated text will likely benefit from the Emdros and the EMdF model.
Enhancements:
- The topographic part of the language was expanded.
- A TIGER XML importer was added.
- Beta quality C# bindings were added.
- Bugfixes were made, and the regression test suite was enhanced.
Download (4.6MB)
Added: 2007-07-05 License: GPL (GNU General Public License) Price:
843 downloads
fig2ps 1.3.6
fig2ps is a perl script which converts xfig files to postscript or PDF, processing text with LaTeX. more>>
fig2ps is a perl script which converts xfig files to postscript or PDF, processing text with LaTeX. fig2pss primary aim is to produce documents (such as articles) with a high quality, in which the pictures are seamlessly integrated with the text (notably, the font in the figures is exactly the same as in the text).
The way to use it is simple : draw your picture with xfig, marking all text as special (there is one way to force this, look at the manual page). Then, invoke fig2ps on your xfig file. Then, you can integrate the picture in a LaTeX document by simply saying, for instance, includegraphics{file}
<<lessThe way to use it is simple : draw your picture with xfig, marking all text as special (there is one way to force this, look at the manual page). Then, invoke fig2ps on your xfig file. Then, you can integrate the picture in a LaTeX document by simply saying, for instance, includegraphics{file}
Download (0.076MB)
Added: 2006-09-18 License: GPL (GNU General Public License) Price:
1132 downloads
Text::MacroScript 1.38
Text::MacroScript is a macro pre-processor with embedded perl capability. more>>
Text::MacroScript is a macro pre-processor with embedded perl capability.
SYNOPSIS
use Text::MacroScript ;
# new() for macro processing
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_ ) if $_ ;
}
# Canonical use (the filename improves error messages):
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_, $ARGV ) if $_ ;
}
# new() for embedded macro processing
my $Macro = Text::MacroScript->new( -embedded => 1 ) ;
# Delimiters default to
# or
my $Macro = Text::MacroScript->new( -opendelim => [[, -closedelim => ]] ) ;
while( ) {
print $Macro->expand_delimited( $_, $ARGV ) if $_ ;
}
# Create a macro object and create initial macros/scripts from the file(s)
# given:
my $Macro = Text::MacroScript->new(
-file => [ local.macro, ~/.macro/global.macro ]
) ;
# Create a macro object and create initial macros/scripts from the
# definition(s) given:
my $Macro = Text::MacroScript->new(
-macro => [
[ MAX_INT => 32767 ],
],
-script => [
[ DHM2S =>
[
my $s = (#0*24*60*60)+(#1*60*60)+(#2*60) ;
"#0 days, #1 hrs, #2 mins = $s secs"
],
],
-variable => [ *MARKER* => 0 ],
) ;
# We may of course use any combination of the options.
my $Macro = Text::MacroScript->new( -comment => 1 ) ; # Create the %%[] macro.
# define()
$Macro->define( -macro, $macroname, $macrobody ) ;
$Macro->define( -script, $scriptname, $scriptbody ) ;
$Macro->define( -variable, $variablename, $variablebody ) ;
# undefine()
$Macro->undefine( -macro, $macroname ) ;
$Macro->undefine( -script, $scriptname ) ;
$Macro->undefine( -variable, $variablename ) ;
# undefine_all()
$Macro->undefine( -macro ) ;
$Macro->undefine( -script ) ;
$Macro->undefine( -variable ) ;
# list()
@macros = $Macro->list( -macro ) ;
@macros = $Macro->list( -macro, -namesonly ) ;
@scripts = $Macro->list( -script ) ;
@scripts = $Macro->list( -script, -namesonly ) ;
@variables = $Macro->list( -variable ) ;
@variables = $Macro->list( -variable, -namesonly ) ;
# load_file() - always treats the contents as within delimiters if we are
# doing embedded processing.
$Macro->load_file( $filename ) ;
# expand_file() - calls expand_embedded() if we are doing embedded
# processing otherwise calls expand().
$Macro->expand_file( $filename ) ;
@expanded = $Macro->expand_file( $filename ) ;
# expand()
$expanded = $Macro->expand( $unexpanded ) ;
$expanded = $Macro->expand( $unexpanded, $filename ) ;
# expand_embedded()
$expanded = $Macro->expand_embedded( $unexpanded ) ;
$expanded = $Macro->expand_embedded( $unexpanded, $filename ) ;
This bundle also includes the macro and macrodir scripts which allows us to expand macros without having to use/understand Text::MacroScript.pm, although you will have to learn the handful of macro commands available and which are documented here and in macro. macro provides more documentation on the embedded approach.
The macroutil.pl library supplied provides some functions which you may choose to use in HTML work for example.
<<lessSYNOPSIS
use Text::MacroScript ;
# new() for macro processing
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_ ) if $_ ;
}
# Canonical use (the filename improves error messages):
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_, $ARGV ) if $_ ;
}
# new() for embedded macro processing
my $Macro = Text::MacroScript->new( -embedded => 1 ) ;
# Delimiters default to
# or
my $Macro = Text::MacroScript->new( -opendelim => [[, -closedelim => ]] ) ;
while( ) {
print $Macro->expand_delimited( $_, $ARGV ) if $_ ;
}
# Create a macro object and create initial macros/scripts from the file(s)
# given:
my $Macro = Text::MacroScript->new(
-file => [ local.macro, ~/.macro/global.macro ]
) ;
# Create a macro object and create initial macros/scripts from the
# definition(s) given:
my $Macro = Text::MacroScript->new(
-macro => [
[ MAX_INT => 32767 ],
],
-script => [
[ DHM2S =>
[
my $s = (#0*24*60*60)+(#1*60*60)+(#2*60) ;
"#0 days, #1 hrs, #2 mins = $s secs"
],
],
-variable => [ *MARKER* => 0 ],
) ;
# We may of course use any combination of the options.
my $Macro = Text::MacroScript->new( -comment => 1 ) ; # Create the %%[] macro.
# define()
$Macro->define( -macro, $macroname, $macrobody ) ;
$Macro->define( -script, $scriptname, $scriptbody ) ;
$Macro->define( -variable, $variablename, $variablebody ) ;
# undefine()
$Macro->undefine( -macro, $macroname ) ;
$Macro->undefine( -script, $scriptname ) ;
$Macro->undefine( -variable, $variablename ) ;
# undefine_all()
$Macro->undefine( -macro ) ;
$Macro->undefine( -script ) ;
$Macro->undefine( -variable ) ;
# list()
@macros = $Macro->list( -macro ) ;
@macros = $Macro->list( -macro, -namesonly ) ;
@scripts = $Macro->list( -script ) ;
@scripts = $Macro->list( -script, -namesonly ) ;
@variables = $Macro->list( -variable ) ;
@variables = $Macro->list( -variable, -namesonly ) ;
# load_file() - always treats the contents as within delimiters if we are
# doing embedded processing.
$Macro->load_file( $filename ) ;
# expand_file() - calls expand_embedded() if we are doing embedded
# processing otherwise calls expand().
$Macro->expand_file( $filename ) ;
@expanded = $Macro->expand_file( $filename ) ;
# expand()
$expanded = $Macro->expand( $unexpanded ) ;
$expanded = $Macro->expand( $unexpanded, $filename ) ;
# expand_embedded()
$expanded = $Macro->expand_embedded( $unexpanded ) ;
$expanded = $Macro->expand_embedded( $unexpanded, $filename ) ;
This bundle also includes the macro and macrodir scripts which allows us to expand macros without having to use/understand Text::MacroScript.pm, although you will have to learn the handful of macro commands available and which are documented here and in macro. macro provides more documentation on the embedded approach.
The macroutil.pl library supplied provides some functions which you may choose to use in HTML work for example.
Download (0.036MB)
Added: 2007-05-31 License: Perl Artistic License Price:
876 downloads
Text::Emoticon::GoogleTalk 0.01
Text::Emoticon::GoogleTalk is a Perl module emoticon filter of GoogleTalk. more>>
Text::Emoticon::GoogleTalk is a Perl module emoticon filter of GoogleTalk.
SYNOPSIS
use Text::Emoticon::GoogleTalk;
my $emoticon = Text::Emoticon::GoogleTalk->new;
my $text = "I<<less
SYNOPSIS
use Text::Emoticon::GoogleTalk;
my $emoticon = Text::Emoticon::GoogleTalk->new;
my $text = "I<<less
Download (0.002MB)
Added: 2006-11-30 License: Perl Artistic License Price:
1062 downloads
phppdflib 2.8
phppdflib allows dynamic generation of PDF files using PHP. more>>
phppdflib is a class written in php that presents an easy to use API for generating PDF files dynamically.
Main features:
- Its freely licensed under the GNU GPL.
- Since its written in php, it doesnt require you to recompile or reconfigure your web server in any way
- Since its written in php, its platform independent. It will run on any system that supports php, such as Windows, Linux, Macintosh, and BSD.
- Its specifically designed to allow easy programming for text processing applications (such as reporting)
<<lessMain features:
- Its freely licensed under the GNU GPL.
- Since its written in php, it doesnt require you to recompile or reconfigure your web server in any way
- Since its written in php, its platform independent. It will run on any system that supports php, such as Windows, Linux, Macintosh, and BSD.
- Its specifically designed to allow easy programming for text processing applications (such as reporting)
Download (0.10MB)
Added: 2005-05-05 License: GPL (GNU General Public License) Price:
1633 downloads
SILGraphite 2.2.0
SILGraphite is an extensible cross-platform rendering technologies for non-roman scripts. more>>
SILGraphite project is an extensible cross-platform rendering technologies for non-roman scripts.
Graphite is a project under development within SILs Non-Roman Script Initiative and Language Software Development groups to provide rendering capabilities for complex non-Roman writing systems.
Graphite can be used to create "smart fonts" capable of displaying writing systems with various complex behaviors. With respect to the Text Encoding Model, Graphite handles the "Rendering" aspect of writing system implementation.
Graphite is intended to serve as the principal non-Roman renderer for the FieldWorks package, the new generation of linguistic and translation tools under development within SIL. We also want to make the Graphite library available to any software developer who is working to develop multilingual text processing applications.
<<lessGraphite is a project under development within SILs Non-Roman Script Initiative and Language Software Development groups to provide rendering capabilities for complex non-Roman writing systems.
Graphite can be used to create "smart fonts" capable of displaying writing systems with various complex behaviors. With respect to the Text Encoding Model, Graphite handles the "Rendering" aspect of writing system implementation.
Graphite is intended to serve as the principal non-Roman renderer for the FieldWorks package, the new generation of linguistic and translation tools under development within SIL. We also want to make the Graphite library available to any software developer who is working to develop multilingual text processing applications.
Download (1.5MB)
Added: 2005-04-13 License: Common Public License Price:
1656 downloads
Apache::Pod::Text 0.22
Apache::Pod::Text is a mod_perl handler to convert Pod to plain text. more>>
Apache::Pod::Text is a mod_perl handler to convert Pod to plain text.
SYNOPSIS
A simple mod_perl handler to easily convert Pod to Text.
CONFIGURATION
See Apache::Pod::HTML for configuration details.
<<lessSYNOPSIS
A simple mod_perl handler to easily convert Pod to Text.
CONFIGURATION
See Apache::Pod::HTML for configuration details.
Download (0.005MB)
Added: 2006-08-16 License: Perl Artistic License Price:
1164 downloads
XML::Twig 3.26
XML::Twig is an XML transformation module. more>>
XML::Twig is a Perl module used to process efficiently XML documents.
Twig offers a tree-oriented interface to a document while still allowing the processing of documents of any size. I think the current buzzword for it would be "push-pull" processing.
When I was younger I wanted to grow up and write a tool that would allow people to process text the way they wanted, offering tons of feature, various ways to achieve the same result, not forcing them into any processing model but allowing them to use the one they felt the most comfortable with.
Eventually I grew up and I realized a guy named Larry Wall had already written a language named Perl... Darn! So as I was quite involved in dealing with SGML, then XML, I decided to settle for the next best thing: writing a module that would allow people to process XML the way they wanted, offering them tons of feature, various ways... you get the point.So I wrote XML::Twig.
XML::Twig gives you a tree interface to XML documents... if you want. It also lets you dump parts of the tree, set callbacks during processing, both on tags and on subtrees, process only part of the tree, write powerful filters... you name it.
The only thing XML::Twig does not do is follow standards (except XML of course): no DOM, no XPath (well, not quite, it implements a subset of XPath), no SAX ( it is planned though, as of 3.05 you can output SAX using the toSAX1 and toSAX2 methods). Consider yourself warned!
<<lessTwig offers a tree-oriented interface to a document while still allowing the processing of documents of any size. I think the current buzzword for it would be "push-pull" processing.
When I was younger I wanted to grow up and write a tool that would allow people to process text the way they wanted, offering tons of feature, various ways to achieve the same result, not forcing them into any processing model but allowing them to use the one they felt the most comfortable with.
Eventually I grew up and I realized a guy named Larry Wall had already written a language named Perl... Darn! So as I was quite involved in dealing with SGML, then XML, I decided to settle for the next best thing: writing a module that would allow people to process XML the way they wanted, offering them tons of feature, various ways... you get the point.So I wrote XML::Twig.
XML::Twig gives you a tree interface to XML documents... if you want. It also lets you dump parts of the tree, set callbacks during processing, both on tags and on subtrees, process only part of the tree, write powerful filters... you name it.
The only thing XML::Twig does not do is follow standards (except XML of course): no DOM, no XPath (well, not quite, it implements a subset of XPath), no SAX ( it is planned though, as of 3.05 you can output SAX using the toSAX1 and toSAX2 methods). Consider yourself warned!
Download (0.28MB)
Added: 2006-11-12 License: Perl Artistic License Price:
1076 downloads
Text::Kakasi::JP 2.04
Text::Kakasi::JP is a Japanese Perl extension for Text::Kakasi. more>>
Text::Kakasi::JP is a Japanese Perl extension for Text::Kakasi.
SYNOPSIS
use Text::Kakasi;
# functional
$res = Text::Kakasi::getopt_argv(kakasi, -ieuc, -w);
$str = Text::Kakasi::do_kakasi($japanese_text);
# object-oriented
$obj = Text::Kakasi->new(-ieuc,-w);
$str = $obj->get($japanese_text);
<<lessSYNOPSIS
use Text::Kakasi;
# functional
$res = Text::Kakasi::getopt_argv(kakasi, -ieuc, -w);
$str = Text::Kakasi::do_kakasi($japanese_text);
# object-oriented
$obj = Text::Kakasi->new(-ieuc,-w);
$str = $obj->get($japanese_text);
Download (0.022MB)
Added: 2006-08-02 License: Perl Artistic License Price:
1178 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above text processing search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed