Free article software for linux

PloneArticle provides a Plone content type to store elaborate content.
PloneArticle : A Plone Document that can incorporate images and attachments and that allows you to choose from different layout models.
Behaves mostly like the standard Plone Document type. When you add a Plone Article, you can enter the name, title, description and text information.
When you look at the Plone Article, the images will appear in the right column as a thumbnail and optionally with their title. When you click on the thumbnail, a popup window will appear with the image at its actual size. Attachments will be listed below the article for download in rows of three.
You will notice two tabs that dont exist on the standard Plone Document: images and attachments.
Images Tab:
This interface shows the Images that you have uploaded to the article, and allows you to add new images as well as deleting them. Images can have an optional title. The position of images as they will appear in the right column of the Plone Article View can be changed with up and down arrows that allow you to individually move images up or down one step.
Attachments Tab:
This interface shows the Attachments that you have uploaded to the article, and allows you to add new attachments as well as deleting them. If no title is given, the name of the uploaded file is taken in its place.
Links Tab:
This interface shows the Links that you have added to the article, and allows you to add new links as well as deleting them.
The Models Tab:
Here you can choose from the stock layout models that come with PloneArticle, and also the models that you have created somewhere in the skins path.
Enhancements:
- Fix reindexation bug after migration from Plone 2.0.5 and Zope 2.7
- Add brazilian and slovenian translation
- Fix some docs

MARC is a Perl extension to manipulate MAchine Readable Cataloging records.

SYNOPSIS

use MARC;

# constructors
$x=MARC->new();
$x=MARC->new("filename","fileformat");
$x->openmarc({file=>"makrbrkr.mrc",format=>"marcmaker",
increment=>"5", lineterm=>"n",
charset=>%char_hash});
$record_num=$x->createrecord({leader=>"00000nmm 2200000 a 4500"});

# input/output operations
$y=$x->nextmarc(10); # increment
$x->closemarc();
print $x->marc_count();
$x->deletemarc({record=>2,field=>110});
$y=$x->selectmarc([4,21-50,60]);

# character translation
my %inc = %{$x->usmarc_default()}; # MARCMaker input charset
my %outc = %{$x->ustext_default()}; # MARCBreaker output charset

# data queries
@records = $x->searchmarc({field=>"245"});
@records = $x->searchmarc({field=>"260",subfield=>"c",
regex=>"/19../"});
@records = $x->searchmarc({field=>"245",notregex=>"/huckleberry/i"});
@results = $x->getvalue({record=>12,field=>856,subfield=>u});

# header and control field operations
$rldr = $x->unpack_ldr($record);
print "Desc is $rldr->{Desc}";
next if ($x->bib_format($record) eq SERIALS);
$rff = $x->unpack_008($record);
last if ($rff->{Date1}=~/00/ or $rff->{Date2}=~/00/);

# data modifications
$x->addfield({record=>"2", field=>"245",
i1=>"1", i2=>"4", ordered=>y, value=>
[a=>"The adventures of Huckleberry Finn /",
c=>"Mark Twain ; illustrated by E.W. Kemble."]});

my $update245 = {field=>245,record=>2,ordered=>y};
my @u245 = $x->getupdate($update245);
$x->deletemarc($update245);
$x->addfield($update245, @u245_modified);

# outputs
$y = $x->output({format=>"marcmaker", charset=>%outc});
$x->output({file=>">>my_text.txt",format=>"ascii",record=>2});
$x->output({file=>">my_marcmaker.mkr",format=>"marcmaker",
nolinebreak=>y,lineterm=>n});
$x->output({file=>">titles.html",format=>"html", 245=>"Title: "});

# manipulation of individual marc records.
@recs = $x[1..$#$x];
grep {$_->unpack_ldr() && 0} @recs;
@LCs = grep {$_->unp_ldr{Desc} eq a &&
$_->getvalue({field=>040}) =~/DLCc_.DLC/} @recs;
foreach my $rec (@LCs) {
print $rec->output({format=>usmarc});
}

# manipulation as strings.
foreach my $rec (@LCs) {
my $stringvar = $rec->as_string();
$stringvar=~s[^(
100s # main entries of this stripe..
..s # (dont care about indicators)
c_.s*
)(S) # take the first letter..
] [
${1}uc($2) # and upcase it. All authors have
# upcase first letters in my library.
]xm; # x means ignore whitespace and allow
# embedded comments.
$rec->from_string($stringvar);
my ($i2,$article) = $stringvar =~/245 .(.) c_.(.{0,9})/;
$article = substr($article,0,$i2) if $i2=~/d/;
print "article $article is not common" unless $COMMON_ARTS{$article};
}

MARC.pm is a Perl 5 module for reading in, manipulating, and outputting bibliographic records in the USMARC format. You will need to have Perl 5.004 or greater for MARC.pm to work properly. Since it is a Perl module you use MARC.pm from one of your own Perl scripts. To see what sorts of conversions are possible you can try out a web interface to MARC.pm which will allow you to upload MARC files and retrieve the results (for details see the section below entitled "Web Interface").

However, to get the full functionality you will probably want to install MARC.pm on your server or PC. MARC.pm can handle both single and batches of MARC records. The limit on the number of records in a batch is determined by the memory capacity of the machine you are running. If memory is an issue for you MARC.pm will allow you to read in records from a batch gradually. MARC.pm also includes a variety of tools for searching, removing, and even creating records from scratch.

Postfilter is a perl filter for Internet Net News (innd) which checks all messages sent by local users searching for spam and invalid contents.
Although Postfilter is designed for large sites that need a complex tool, Postfilter could by used also by local or private servers.
Main features:
- A powerful banlist: rules can be based on every header and each article could be rejected, silently discarded, tracked throught syslog or saved for further inspection
- A content-based filter. A score could be assigned to every regex; when the body matches an expression, the assigned score is added to the total. If an article exceeds the maximum allowed score, its rejected by the script.
- A fine regulation of clients activity. Postfilter allows to set a max number of articles, bytes, groups, followups, crossposts, hierarchies and errors per time. A second shorter interval is also setable to avoid floods. All these rules can be applied to IP, domain (level n-1) or userid.
- Several built-in syntax checks that scans the headers searching for errors commonly made by spammers.
- A white list that allows to exclude from the check every article that matches a regular expression or every article that includes a predefined header.
Postfilter is released under the terms of BSD License.

News::Archive is a Usenet news archiving package for downloading and later accessing news articles in bulk.

It can load articles laid out in INN format, retrieve them from a running news server, or just take articles one-by-one. News::Archive module is compatible with News::Web and Net::NNTP::Server, so the articles can be shared either via the Web or via NNTP.

SYNOPSIS

use News::Archive;
my $archive = new News::Archive
( basedir => /home/tskirvin/kiboze );

# Get a news article
my $article = News::Article->new(*STDIN);
my $msgid = article->header(message-id);

die "Already processed $msgidn"
if ($archive->article( $messageid ));

# Get the list of groups were supposed to be saving the article into
my @groups = split(s*,s*, $article->header(newsgroups) );
map { s/s+//g } @groups;

# Make sure were subscribed to these groups
foreach (@groups) { $archive->subscribe($_) }

# Actually save the article.
my $ret = $archive->save_article(
[ @{$article->rawheaders}, , @{$article->body} ], @groups );
$ret ? print "Accepted article $messageidn"
: print "Couldnt save article $messageidn";

News::Archive keeps several files to keep track of its archives:

active file

Keeps track of all newsgroups we are "subscribed" to and all of the information that changes regularly - the number of articles we have archived, the current first and last article numbers, etc.

Watched over with News::Active.

history database

A simple database keeping track of articles by Message-ID. Makes access by ID easy, and ensures that we dont save the same article twice. The database chosen to maintain these is user-determined.

newsgroup file

Keeps track of more static information about the newsgroups we are subscribed to - descriptions, creation dates, etc.

Watched over with News::GroupInfo.

archive directory

Directory structure of all articles, with each article saved as a single textfile within a directory structure laid out at one section of the group name per directory, such as "rec/games/mecha". Crossposts are hardlinked to other directory structures.

Articles are actually divided into sub-directories containing up to 500 articles, to avoid Unix directory size performance limitations. Individual files are thus stored in a file such as "rec/games/mecha/1.500/1".

Each newsgroup also contains overview information, watched over with
News::Overview. This overview file goes in the top of the structure,
such as "rec/games/mecha/.overview".

You may note that these files are very similar to how INN does its work. This is intentional - this package is meant to act in many ways like a lighter-weight INN.

Usage:

Global Variables

The following variables are set within News::Archive, and are global throughout all invocations.

$News::Active::DEBUG
Default value for "debug()" in new objects.

$News::Active::HOSTNAME
Default value for "hostname()" in new objects. Obtained using
"Sys::Hostname::hostname()".

$News::Active::HASH
The number of articles to keep in each directory. Default is 500;
change this at your own peril, since things may get screwed up later
if you change it after archiving any articles!

NNTP Client Lib is a Java implementation of RFC 997 for newsreaders, with support for authentication and logging.
NNTP Client Lib is meant to be used by newsreader implementations as some NNTP commands irrelevant for newsreaders are not implemented. Support for MIME or any other article encoding is not included.
If you want to quickly see nntpClientLib working, run NewsDemo . Note that this prints every message to System.err; you can edit NewsDemo.java and choose any other PrintStream.
KNOWN ISSUES:
- The POST and AUTHUSER commands havent been tested (yet).
TODO List:
- FIX NNTPConnectionImpl.disconnect() NullPointerException if host is unreachable.
- Add SSL support.
Enhancements:
- A new logging system and code cleanup.

Bash Blogger is a small, bash-powered, weblog engine. Bashblogger generates valid, semantic, XHTML 1.1 webpages styled with a single CSS for layout and appearance without relying on popular, server-side scripting languages (i.e. Perl, Python, PHP, ASP, SSI, etc.).
Why program in the shell instead of (Perl, Python, etc)?
You may not have Perl, PHP or any number of the other scripting languages available on your hosting provider. Its a fairly safe bet that if you have shell access to your account, you can use Bash Blogger.
Enhancements:
- When I change the name of an article and rebuild the site the name change only changes in the bash blogger menu. The index/article etc ... still list the original title. FIXED
- If you attempt to delete an article and fail to confirm with Y/n (just press enter) bblog exits instead of returning to previous menu. FIXED

Wikipedia search is a superkaramba theme for searching on en.wikipedia.org.

Based on Answers.com karamba by sg1 http://www.kde-look.org/content/show.php?content=30887

Thanks to Rcio Zienke for language config entry.

To-do

- make some transtalations
- display article in wikipedia search window