Free locale files for south africa 0.4 software for linux

Locale files for South Africa project are scripts to aid in localization of software. Deals with conversion between different translation formats (such as gettext-based .po formats, OpenOffice.org formats, and Mozilla formats). Also tools to help process localizations etc.
Translate.org.za is a non-profit organisation producing Free and Open Source software that enables and empowers South Africans.
The Translate Project started in 2001 with the vision of providing Free Software translated into the 11 official languages of South Africa. Free Software in your language is true empowerment.
Enhancements:
- The international dialing code has been changed from 09 to 00.

Locale::Memories is a Perl module for L10N Message Retrieval.

SYNOPSIS

my $lm = Locale::Memories->new();
$lm->load_index(path_to_index);
$lm->index_msg($locale, $msg_id, $msg_str);
$lm->translate_msg($locale, $msg_id);

This module is specialized module for indexing and retrieving .po messages.

fortune-mod-southpark project consists of a fortune file with quotes from South Park.
South Park Fortunes is a package containing various quotes from "South Park: Bigger, Longer, and Uncut" in the UNIX fortune file format.
Examples:
Rub my nipples as I torture this little piggy!
No dude, Id be scared too, youre mom is a fucking bitch.
Dont call my mom a bitch, you fat fuck!
Dont call me fat you buttfucking son of a bitch.
Should we blame the government?
Or blame society?
Or should we blame the images on TV?
NO! Blame Canada!
Enhancements:
- Fixed typos, nothing noteworthy. Released for the sake of the English language
- probably final release

Locale::Framework is a Perl module for internationalization.

SYNOPSIS

use Locale::Framework;
use Locale::Framework::SQL;

Locale::Framework::init(new Locale::Framework::SQL(
DSN => "dbi:Pg:dbname=zclass;host=localhost",
DBUSER => "test",
DBPASS => "testpass",
[TABLE => "testtrans"]));

print _T("This is a test");

Locale::Framework::language("nl_NL");

print _T("This is a test");
Alternative interface (using wxLocale backend as an example), which does exactly the same. There is no local object scope, theres only a global class (or program that is) scope. OO interface is only for conveniance.
use Locale::Framework;
use Locale::Framework::wxLocale;

my $LOC=new Locale::Framework;

$LOC->init(new Locale::Framework::wxLocale("./locale","test"));

print _T("This is a test");
$LOC->language("nl_NL");
print _T("This is a test");

ABSTRACT

This module provides simple string based internationalization support. It exports a _T function that can be used for all text that need displayed. It can work with different backends, e.g. SQL or file based backends. The backend defaults to Locale::Framework::Dumb, which doesnt translate at all.

Locale::Maketext::Lexicon is a Perl module to use other catalog formats in Maketext.

SYNOPSIS

As part of a localization class, automatically glob for available lexicons:

package Hello::I18N;
use base Locale::Maketext;
use Locale::Maketext::Lexicon {
* => [Gettext => /usr/local/share/locale/*/LC_MESSAGES/hello.mo],
### Uncomment to decode lexicon entries into Unicode strings
# _decode => 1,
### Uncomment to fallback when a key is missing from lexicons
# _auto => 1,
### Uncomment to use %1 / %quant(%1) instead of [_1] / [quant, _1]
# _style => gettext,
};
Explicitly specify languages, during compile- or run-time:
package Hello::I18N;
use base Locale::Maketext;
use Locale::Maketext::Lexicon {
de => [Gettext => hello_de.po],
fr => [
Gettext => hello_fr.po,
Gettext => local/hello/fr.po,
],
};
# ... incrementally add new lexicons
Locale::Maketext::Lexicon->import({
de => [Gettext => local/hello/de.po],
})

Alternatively, as part of a localization subclass:

package Hello::I18N::de;
use base Hello::I18N;
use Locale::Maketext::Lexicon (Gettext => *DATA);
__DATA__
# Some sample data
msgid ""
msgstr ""
"Project-Id-Version: Hello 1.3.22.1n"
"MIME-Version: 1.0n"
"Content-Type: text/plain; charset=iso8859-1n"
"Content-Transfer-Encoding: 8bitn"

#: Hello.pm:10
msgid "Hello, World!"
msgstr "Hallo, Welt!"

#: Hello.pm:11
msgid "You have %quant(%1,piece) of mail."
msgstr "Sie haben %quant(%1,Poststueck,Poststuecken)."

This module provides lexicon-handling modules to read from other localization formats, such as Gettext, Msgcat, and so on.

If you are unfamiliar with the concept of lexicon modules, please consult Locale::Maketext and http://www.autrijus.org/webl10n/ first.

A command-line utility xgettext.pl is also installed with this module, for extracting translatable strings from source files.

Locale::TextDomain is a Perl Interface to Uniforum Message Translation.

SYNOPSIS

use Locale::TextDomain (my-package, @locale_dirs);

use Locale::TextDomain qw (my-package);

my $translated = __"Hello World!n";

my $alt = $__{"Hello World!n"};

my $alt2 = $__->{"Hello World!n"};

my @list = (N__"Hello", N__"World");

my @plurals = (N__ ("One world", "{num} worlds"),
N__ ("1 file", "%d files"));

my $question = __x ("Error reading file {file}: {err}",
file => $file, err => $!);

printf (__n ("one file read",
"%d files read",
$num_files),
$num_files);

print __nx ("one file read", "{num} files read", $num_files,
num => $num_files);

The module Locale::TextDomain(3pm) provides a high-level interface to Perl message translation.

Textdomains

When your request a translation for a given string, the system used in libintl-perl follows a standard strategy to find a suitable message catalog containing the translation: Unless you explicitely define a name for the message catalog, libintl-perl will assume that your catalog is called messages (unless you have changed the default value to something else via Locale::Messages(3pm), method textdomain()).
You might think that his default strategy leaves room for optimization and you are right. It would be a lot smarter if multiple software packages, all with their individual message catalogs, could be installed on one system, and it should also be possible that third-party components of your software (like Perl modules) can load their message catalogs, too, without interfering with yours.

The solution is clear, you have to assign a unique name to your message database, and you have to specify that name at run-time. That unique name is the so-called textdomain of your software package. The name is actually arbitrary but you should follow these best-practice guidelines to ensure maximum interoperability:

File System Safety

In practice, textdomains get mapped into file names, and you should therefore make sure that the textdomain you choose is a valid filename on every system that will run your software.

Case-sensitivity

Textdomains are always case-sensitive (i. e. Package and PACKAGE are not the same). However, since the message catalogs will be stored on file systems, that may or may not distinguish case when looking up file names, you should avoid potential conflicts here.

Textdomain Should Match CPAN Name

If your software is listed as a module on CPAN, you should simply choose the name on CPANS as your textdomain. The textdomain for libintl-perl is hence libintl-perl. But please replace all periods (.) in your package name with an underscore because ...

Internet Domain Names as a Fallback

... if your software is not a module listed on CPAN, as a last resort you should use the Java(tm) package scheme, i. e. choose an internet domain that you are owner of (or ask the owner of an internet domain) and concatenate your preferred textdomain with the reversed internet domain. Example: Your company runs the web-site www.foobar.org and is the owner of the domain foobar.org. The textdomain for your companys software barfoos should hence be org.foobar.barfoos.

If your software is likely to be installed in different versions on the same system, it is probably a good idea to append some version information to your textdomain.
Other systems are less strict with the naming scheme for textdomains but the phenomena known as Perl is actually a plethora of small, specialized modules and it is probably wisest to postulate some namespace model in order to avoid chaos.

Binding textdomains to directories

Once the system knows the textdomain of the message that you want to get translated into the users language, it still has to find the correct message catalog. By default, libintl-perl will look up the string in the translation database found in the directories /usr/share/locale and /usr/local/share/locale (in that order).

It is neither guaranteed that these directories exist on the target machine, nor can you be sure that the installation routine has write access to these locations. You can therefore instruct libintl-perl to search other directories prior to the default directories. Specifying a differnt search directory is called binding a textdomain to a directory.

Locale::TextDomain extends the default strategy by a Perl specific approach. Unless told otherwise, it will look for a directory LocaleData in every component found in the standard include path @INC and check for a database containing the message for your textdomain there. Example: If the path /usr/lib/perl/5.8.0/site_perl is in your @INC, you can install your translation files in /usr/lib/perl/5.8.0/site_perl/LocaleData, and they will be found at run-time.

Locale::Maketext::Simple is a simple interface to Locale::Maketext::Lexicon.

SYNOPSIS

Minimal setup (looks for auto/Foo/*.po and auto/Foo/*.mo):

package Foo;
use Locale::Maketext::Simple; # exports loc
loc_lang(fr); # set language to French
sub hello {
print loc("Hello, [_1]!", "World");
}
More sophisticated example:

package Foo::Bar;
use Locale::Maketext::Simple (
Class => Foo, # search in auto/Foo/
Style => gettext, # %1 instead of [_1]
Export => maketext, # maketext() instead of loc()
Subclass => L10N, # Foo::L10N instead of Foo::I18N
Decode => 1, # decode entries to unicode-strings
Encoding => locale, # but encode lexicons in current locale
# (needs Locale::Maketext::Lexicon 0.36)
);
sub japh {
print maketext("Just another %1 hacker", "Perl");
}

This module is a simple wrapper around Locale::Maketext::Lexicon, designed to alleviate the need of creating Language Classes for module authors.
If Locale::Maketext::Lexicon is not present, it implements a minimal localization function by simply interpolating [_1] with the first argument, [_2] with the second, etc. Interpolated function like [quant,_1] are treated as [_1], with the sole exception of [tense,_1,X], which will append ing to _1 when X is present, or appending ed to otherwise.

Geotrace is a geographical traceroute utility. Geotrace provide graphical view on the map. It has many geographical maps.
In order to be able to use a new map with geotrace, you only need to know one thing: the longitude/latitude of the top left and bottom right corners. Most maps you will find will be centered on 0,0 (about 5 degs south of Ghana and 10 degs west of Gabon. for those of you who dont know, its in Africa.). So, lets do it step by step:
1) Find a map. there are plenty on the web. Nasas a good place to find them (it is a mess though). Or grab one of the few maps at a site with maps for XGlobe and XPlanet.
The image must be in a format understood by gdk-pixbuf (most images youll find will be jpeg or gif which work).
2) Go to the maps/ directory in geotrace. Put the map in there and open up maps.properties
3) on the second line, youll see MAPS:World50.gif, World100.gif etc... Thats a list of all the maps. Add the name of your recently downloaded map on that line.
4) now, you need to tell geotrace what the coordinates are. Add a line to the file that looks as follows:
filename:BOUNDARY=lon1,lat1,lon2,lat2
filename: case sensitive, map has to be in the maps/ folder
lon1 and lat1: longitude and latitude of the top left corner
lon2 and lat2: longitude and latitude of the bottom right corner
As I said earlier, for most maps youll find, youll get -180,90,180,-90 which means that the map is centered on 0,0. However, the two world maps (World100 and World50) in geotrace are centered on 10W,0
You might notice that the three maps of the US have another line associated with them. Thats the alber projection. You probably wont have to deal with that.
4) Run geotrace, select your map from the drop-down and enjoy.
Version restrictions:
- Some hops may have extravagant locations, but for once, its not my fault. The netgeo server does not have fully updated records. So my advice is, just live with it
Enhancements:
- added line color and width options.
- added cmdline args. host to trace, and startup map.
- added map options: path to maps and startup map.
- warning to check paths when run for the first time.
- added status bar
- fixed draw_trace_on_map which didnt draw in certain cases (timeouts)
- fixed bug that caused crash when a hop times out and more hops repond later
- 2001-04-05
- added option: resolve host name or not
- load/save options from file (~/.geotrace) 2001-04-04
- fixed bug that caused last map in file not to be read (world100) 2001-04-03 added options for traceroute (path to exec, timeout and maxttl)