Free para software for linux

Convert::Wiki::Node::Para is a Perl module that represents a text paragraph node.

SYNOPSIS

use Convert::Wiki::Node::Para;

my $para = Convert::Wiki::Node->new( txt => Foo is a foobar., type => para );

print $para->as_wiki();

A Convert::Wiki::Node::Para represents a normal text paragraph.

AxKit2::Transformer::XSP Perl module contains eXtensible Server Pages.

SYNOPSIS

< xsp:page
xmlns:xsp="http://apache.org/xsp/core/v1" >

< xsp:structure >
< xsp:import >Time::Piece< /xsp:import >
< /xsp:structure >

< page >
< title >XSP Test< /title >
< para >
Hello World!
< /para >
< para >
Good
< xsp:logic >
if (localtime->hour >= 12) {
< xsp:content >Afternoon< /xsp:content >
}
else {
< xsp:content >Morning< /xsp:content >
}
< /xsp:logic >
< /para >
< /page >

< /xsp:page >

XSP implements a tag-based dynamic language that allows you to develop your own tags, examples include sendmail and sql taglibs. It is AxKits way of providing an environment for dynamic pages. XSP is originally part of the Apache Cocoon project, and so you will see some Apache namespaces used in XSP.

Also, use only one XSP processor in a pipeline. XSP is powerful enough that you should only need one stage, and this implementation allows only one stage. If you have two XSP processors, perhaps in a pipeline that looks like:

... => XSP => XSLT => XSLT => XSP => ...

it is pretty likely that the functionality of the intermediate XSLT stages can be factored in to either upstream or downstream XSLT:

... => XSLT => XSP => XSLT => ...

This design is likely to lead to a clearer and more maintainable implementation, if only because generating code, especially embedded Perl code, in one XSP processor and consuming it in another is often confusing and even more often a symptom of misdesign.

Likewise, you may want to lean towards using Perl taglib modules instead of upstream XSLT "LogicSheets". Upstream XSLT LogicSheets work fine, mind you, but using Perl taglib modules results in a simpler pipeline, simpler configuration (just load the taglib modules in httpd.conf, no need to have the correct LogicSheet XSLT page included whereever you need that taglib), a more flexible coding environment, the ability to pretest your taglibs before installing them on a server, and better isolation of interface (the taglib API) and implementation (the Perl module behind it). LogicSheets work, and can be useful, but are often the long way home. That said, people used to the Cocoon environment may prefer them.

Result Code

You can specify the result code of the request in two ways. Both actions go inside a < xsp:logic > tag.

If you want to completely abort the current request, throw an exception:

throw Apache::AxKit::Exception::Retval(return_code => FORBIDDEN);

If you want to send your page but have a custom result code, return it:

return FORBIDDEN;

In that case, only the part of the document that was processed so far gets sent/processed further.

Debugging

If you have PerlTidy installed (get it from http://perltidy.sourceforge.net), the compiled XSP scripts can be formatted nicely to spot errors easier. Enable AxDebugTidy for this, but be warned that reformatting is quite slow, it can take 20 seconds or more on each XSP run for large scripts.

If you enable AxTraceIntermediate, your script will be dumped alongside the other intermediate files, with an extension of ".XSP". These are unnumbered, thus only get one dump per request. If you have more than one XSP run in a single request, the last one will overwrite the dumps of earlier runs.

Text::TemplateFill is a Perl module for formatting of reports with templates from files, use for I18N.
SYNOPSIS
use Text::TemplateFill;
my $tmpl = new Text::TemplateFill;
$tmpl->SetOpt(BaseDir => "paras/$Country");
$tmpl->SetOpt(ErrorFunction => &LogMsg, LineTerminator => "rn");
# Must read all the files before printing a paragraph
$tmpl->ReadPara(Header, "head");
$tmpl->ReadPara(FirstPage);
$tmpl->ReadPara(Footer);
$tmpl->ReadPara(Body);
$tmpl->SetOpt(StartPageTag => Header);
my ($a, $b, $cn, $d) = (a, letter b, ACME Inc, 4.92);
$tmpl->BindVars(NameOfA => $a, B => $b, CustomerName => $cn, VarD => $d);
print $tmpl->GeneratePara(FirstPage); # Optional - since we want a specific 1st page
print $tmpl->GeneratePara(Body);
... $a = ...; $b = ...
print $tmpl->GeneratePara(Body);
print $tmpl->CompletePage;
Main features:
- I18N formatting support, eg: decimal comma in France
- I18N date support
- Automatic page breaks
- Variables are registered, not passed to each GeneratePara
- Items of text (paragraphs) that are output are initially read from a text file.
- Calculations may be defined as part of the paragraph definition in the file.
- Optional use of your own Error reporting code
- Variables can be formatted by the full power of printf
- Automatic page/paragraph counting
- Output is a string that may be then written anywhere

GPLIGC is a software package for glider* pilots. IGC flight data files can be analysed and visualised.
The package contains two components:
*and all others who want to view GPS track logs (para-glider pilots, hang-glider pilots and even pilots of radio-controlled (sail)planes.
- GPLIGC, analysation
- openGLIGCexplorer, 3d visualisation (can be used as a viewer for digital elevation data too)
GPLIGC can be used on Linux, Unix, Windows and Mac OS X.
GPLIGC application can be used under the terms of the GNU General Public License (GPL).
Enhancements:
- This release fixes a few bugs.
- Some options were added that allow you to specify a destination folder and filenames for screenshots.
- The background colors (including gradients) can be changed.

Kydpdict is a graphical frontend to Collins Polish-English, English-Polish and Langenscheidt Polish-German. German-Polish dictionaries published by Young Digital Poland.
This is a front-end to YDP Collins dictionary. You need to have windows version installed. In fact you need only four files:
dict100.dat, dict101.dat, dict100.idx, dict101.idx
for German language these will be needed:
dict200.dat, dict201.dat, dict200.idx, dict201.idx
It is very possible that there is also French version of YDP dictionary that also can be used with this program. Please contact me if you have such thing.
The program will ask you to supply the path to a directory where these files are located. Additionaly, if you would have mounted CD-ROM with the dictionary, the program is able to play samples with prononciation of English words. (note that you can simply copy files from CD-ROM somewhere and pass that path to kydpdict. The player is configurable so you can encode these files to mp3 or ogg).
Most notable feature of kydpdict is that every time you copy a word to the clipboard (it is enough to highlight it) the application will catch it and try to find in the current dictionary, then will put its window on top so you can actually read the definition of that word (or the most similar one). To turn off this behavior simply minimize kydpdict window or use toolbal or tray icon menu. In order to quickly enter a new word without using mouse just press ESC and then type.
This application is heavily based on ydpdict by Wojciech Kaniewski.
Enhancements:
- This version brings some usability fixes and a new option to have program initially hidden.

HTML::Simple is a simple, dependency free module for generating HTML (and XML).

SYNOPSIS

Note: It turns out that TOMC owns the HTML::Simple namespace so Ive moved development of this module to HTML::Tiny. Please use HTML::Tiny in preference to this module.

use HTML::Simple;

my $h = HTML::Simple->new;

# Generate a simple page
print $h->html(
[
$h->head( $h->title( Sample page ) ),
$h->body(
[
$h->h1( { class => main }, Sample page ),
$h->p( Hello, World, { class => detail }, Second para )
]
)
]
);

# Outputs
< html>
< head>
< title>Sample page< /title>
< /head>
< body>
< h1 class="main">Sample page< /h1>
< p>Hello, World< /p>
< p class="detail">Second para< /p>
< /body>
< /html>