Free gettext software for mac

TMSNC is a textbased (console) MSN client written in C. TMSNC should work on most Unix (Linux, BSD, MacOS) compatible operating systems. The goal of this project is to create a client like MSN Messenger (with sound, webcam and file transfer support), but without any graphical features.
TMSNC is an opensource project which is released under the IR Public Domain License which basically is a modification of the BSD license.
Enhancements:
- Display current playing song option in tmsnc.conf
- Added support for setting personal message (menu item)
- Removed gettext support
- Optimized panel handling
- Window in focus is now shown in yellow
- Changed the window border style.

Requirements:
Mac OS X 10.1 or later.

Enhancements:
Vesrion 2.6 adds the following:

• End of the line for darkstat 2
• (Jean-Edouard Babin) DLT_PPP_SERIAL linktype
• Print warnings from pcap_open_live()
• Considerable source code clean-up
• Updated to gettext 0.11.5, autoconf 2.57, automake 1.7
• Using ACX_PTHREAD macro in configure script
• (Daniel Lublin) WWW: Added title="..." to graph bars
• po: updated nl, added sk, added sr

Massively Parallel PO Editor is a simple text editor for editing multiple language files in parallel.
Corresponding translations are automatically highlighted in order to aid reviewing against multiple sources. Supports gettext PO and key = value format. Highly recommended for the polyglots.

System requirements:
-

Enhancements
- The Second Experimental Release Simple text editor for editing multiple gettext PO files or key=value files in parallel, scrolling through corresponding reference keys automatically. Purpose of the program is to help reviewing existing translations comparing them to other translations. Jar created with Fat Jar (http://fjep.sourceforge.net/) Java must be installed to run (http://java.com/en/download/manual.jsp) More information: http://sourceforge.net/projects/mp-poedit/ TODO
- More extensive comparison methods
- Adding of entries from open model files
- Smarter highlighting -- better hightlighting when moving up with cursor???!
- highlighting PO elements?
- File open dialogs?
- Some kind of report of differences?

XAMPP is a very easy to install Apache Distribution for Linux, Solaris, Windows and MacOS X.
XAMPP includes the Apache web server, MySQL, PHP, phpMyAdmin, Perl, and a FTP server.
Main features:
- Intel Mac only
- Apache 2.2.3
- MySQL 5.0.27
- PHP 4.4.4
- PHP 5.2.0
- Perl 5.8.8
- ProFTPD 1.3.0a
- phpMyAdmin 2.9.1
- OpenSSL 0.9.8d
- GD 2.0.33
- Freetype 2.1.10
- libjpeg 6b
- libpng 1.2.12
- libungif-4.1.4
- zlib 1.2.3
- expat 2.0.0
- Ming 0.3
- Webalizer 2.01-10
- pdf class 009e
- mod_perl 2.0.2
- SQLite 3.3.7
- phpSQLiteAdmin 0.2
- libiconv-1.9.2
- gdbm-1.8.3
- libxml-2.6.26
- libxslt-1.1.17
- openldap-2.3.27
- imap-2004g
- gettext-0.15
- libmcrypt-2.5.7
- mhash-0.9.7.1
- curl-7.15.5
- zziplib-0.10.82
- bzip2-1.0.3
- freetds-0.64

PHPStar2 2.35 offers you with a complete and advanced PHP 4 installer for 4DWebSTAR V 5.2.x or newer. Includes all necessary libs, binaries and support for ImageMagick, GD, PNG, JPEG, T1LIB, IMAP, Gettext, cURL, MCrypt, ZLib, IMAP and FreeType2. XML, PostGreSQL, MySQL, EXIF, OpenSSL, FTP, LDAP and Sendmail is also supported.

Requirements:

• Mac OS X 10.2.x
• rMac OS X Server 10.2.x4D
• WebStar V 5.2.x or higher (recommended but not needed)

PHPStar3 3.0.3 offers you a professional PHP 5 installer for 4DWebSTAR V 5.2.x or newer. Includes all necessary libs, binaries and support for ImageMagick, GD, PNG, JPEG, T1LIB, IMAP, Gettext, cURL, MCrypt, ZLib, IMAP and FreeType2. XML2, PostGreSQL, MySQL, EXIF, OpenSSL, FTP, LDAP and Sendmail is also supported.
An exclusive gui-based utility is included for easy and fast administration

Requirements:

• Mac OS X 10.2.x
• Mac OS X Server 10.2.x4D
• WebStar V 5.2.x or higher

The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community. The software is released under an Apache/BSD-style open source license.

• Most current CVS features.
Subversion is meant to be a better CVS, so it has most of CVSs features. Generally, Subversions interface to a particular feature is similar to CVSs, except where theres a compelling reason to do otherwise.
• Directories, renames, and file meta-data are versioned.
Lack of these features is one of the most common complaints against CVS. Subversion versions not only file contents and file existence, but also directories, copies, and renames. It also allows arbitrary metadata (properties) to be versioned along with any file or directory, and provides a mechanism for versioning the `execute permission flag on files.
• Commits are truly atomic.
No part of a commit takes effect until the entire commit has succeeded. Revision numbers are per-commit, not per-file; log messages are attached to the revision, not stored redundantly as in CVS.

• Apache network server option, with WebDAV/DeltaV protocol.
Subversion can use the HTTP-based WebDAV/DeltaV protocol for network communications, and the Apache web server to provide repository-side network service. This gives Subversion an advantage over CVS in interoperability, and provides various key features for free: authentication, wire compression, and basic repository browsing.
• Standalone server option.
Subversion also offers a standalone server option using a custom protocol (not everyone wants to run Apache 2.x). The standalone server can run as an inetd service, or in daemon mode, and offers basic authentication and authorization. It may also be tunnelled over ssh.
• Branching and tagging are cheap (constant time) operations
There is no reason for these operations to be expensive, so they arent.
Branches and tags are both implemented in terms of an underlying copy operation. A copy takes up a small, constant amount of space. Any copy is a tag; and if you start committing on a copy, then its a branch as well. (This does away with CVSs branch-point tagging, by removing the distinction that made branch-point tags necessary in the first place.)

• Natively client/server, layered library design
Subversion is designed to be client/server from the beginning; thus avoiding some of the maintenance problems which have plagued CVS. The code is structured as a set of modules with well-defined interfaces, designed to be called by other applications.
• Client/server protocol sends diffs in both directions
The network protocol uses bandwidth efficiently by transmitting diffs in both directions whenever possible (CVS sends diffs from server to client, but not client to server).
• Costs are proportional to change size, not data size
In general, the time required for a Subversion operation is proportional to the size of the changes resulting from that operation, not to the absolute size of the project in which the changes are taking place. This is a property of the Subversion repository model.

• Choice of database or plain-file repository implementations
Repositories can be created with either an embedded database back-end (BerkeleyDB) or with normal flat-file back-end, which uses a custom format.
• Versioning of symbolic links
Unix users can place symbolic links under version control. The links are recreated in Unix working copies, but not in win32 working copies.
• Efficient handling of binary files
Subversion is equally efficient on binary as on text files, because it uses a binary diffing algorithm to transmit and store successive revisions.
• Parseable output
All output of the Subversion command-line client is carefully designed to be both human readable and automatically parseable; scriptability is a high priority.
• Localized messages
Subversion uses gettext() to display translated error, informational, and help messages, based on current locale settings.