Free icc software for linux

ics.el project is an Emacs mode for internet chess server interactions.
ics.el is a comint based Emacs major mode for handling the text portion of communications with internet chess servers such as FICS and ICC.
It is written in Emacs-Lisp and works best in conjunction with a graphical interface such as Xboard.
It handles colour highlighting and "buttonisation" (making certain portions of text active so that, for example, you can challenge opponents with a single mouse click) as well as command recall and editing and automation of commands based on regexps seen in the ICS output, all highly customisable using Emacs lisp.
Enhancements:
- added a require for overlay. This is part of the fsf-compat XEmacs package.
- added escapes into "----" and "++++" parts of regexps since not escaping them broke XEmacs version.
- added test for XEmacs into function tracing devel option
- changed the connection mechanism slightly to use a different variable ics-interface-with-helper-args when CONNECTMETHOD in ics-servers-alist is non-nil. This allows a different xboard commandline to be used if there is a timestamp/timeseal program available, rather than the same commandline with telnet for the helper program (which doesnt work for me anymore under Mandrake Linux 8.0 - I get a connection closed right before the password is prompted for).
- updated the default ics-servers-alist variable for new IP addresses and the BCF server and chess.net
- Fixed wholist buttonisation regexp to recognise "&" between rating and handle.
- Several fixes by John Wiegley to prevent ics.el from breaking other comint based modes - ics.el now uses local hooks instead of polluting the global comint hooks.
- Added support for running the interface program (e.g. xboard) under gdb in the ics sessions. The variable ics-gdb-interface controls this.

Little cms intends to be a small-footprint, speed optimized color management engine in open source form.
Since the initial release, back in 1998, lcms has been continuously evolving, mostly thanks to contributions done by skilled programmers, who generously donated their valuable time to review the engine and the documentation.
For now, little cms has been ported to a big number of platforms and is currently used in many open source and commercial products, as well as being distributed in major linux environments. Thanks to all for this great support!
Basic Features:
- Widely portable.
- Easy to use.
- Small, tight code.
- Fast, optimized for speed.
- Handles a wide range pixel formats.
- Implements ICC spec 4
- Profile to profile and multiprofile transforms.
- Supports all kind of profiles, including named color
- PostScript CSA and CRD generation
Advanced features:
- Full hi-fi support, including hexachrome restoration.
- Gamut checking
- Softproofing
- Precalculated device link transforms with prelinearization step.
- Virtual Gray, RGB profiles
- CIECAM02 appearance model
- Can write profiles as well.
- Built-In profiles
- Specialized abstract virtual profiles

iridium is a photo gallery which takes care of the tedious details associated with thumbnails, positioning, resizing and recoding.

After a simple upload, it resizes photos, renders thumbnails, and packages them up in an XML document for a Flash driven application.

Ever wanted to have a photo gallery, but hate the: thumbnails, resizing, positioning and recoding? iridium takes care of those details for you. After a simple upload, it resizes photos, renders thumbnails and packages it up in a flash application.

It’s just that darn easy! iridium can stand alone or embed itself!

Installation:

Installation file contents:

1. iridium.html - simple bare bones HTML file with flash file embedded
2. iridium folder - where the update application and your pictures will live
3. iridium/pictures folder - where you will make folders and put in images
4. iridium/_PHPtools - unless you know PHP its best to leave this folder alone.
5. iridium_v1a.fla - this is the flash source file that can be modified for your site
6. iridium_v1a.swf - this is the flash gallery thats embedded in the HTML page

Installation instructions:

1. unzip files into appropriate web folder. Be sure that iridium.html is in
the same folder as the iridium folder.

2. verify folder and .PHP file permissions for _PHPtools. Your server will
likely require specific permissions to read, write and execute any .PHP files.
Some server administrators may refer to this as CHMOD. Please refer to them
for the correct permissions as they will varry.

Further help (Frequently Asked Questions) can be found at:
http://www.steve-lux.com/atomilux/iridium.html

3. make a folder for each gallery you want in: iridium/pictures/*your gallery name*
i.e. a gallery named vacation would be found at: iridium/pictures/vacation/
i.3. a gallery named 1-05_newYearsPics would be found at: iridium/pictures/1-05_newYearsPics/

4. upload JPEGs ONLY into each folder that you make.
NOTE: significant problems have been found with PHPs GD library and ANY JPEGs
from a digital camera. For some reason, the ICC profile attached to each image
makes the GD library come to a screeching halt. I recommend running large batches
of files through a program called Web Photo Publish. Its a JAVA based application
that runs on any platform. It is FREE and open source.

http://webphotopublish.sourceforge.net/

If the product works for you please consider donating a meger $5 or more to
their project. Given the price of modern software, Id say its a steal.

5. launch the iridium.html page.

6. right mouse click (control click for mac users) on the gallery itself.
Youll likely see a black box at first sight. Choose Update Gallery from
the contextual menu.

7. The gallery update application will ask you to set up username, password and
email address one time to establish login information.

8. Allow a minute or so for the update application to finish, close the window,
and refresh the iridium.html page. Your gallery should load up.

NOTE: large amounts of new JPEG files may take longer

Conky is a light-weight system monitor.
Conky is a system monitor for X originally based on the torsmo code. Since its original conception, Conky has changed a fair bit from its predecessor.
Conky can display just about anything, either on your root desktop or in its own window. Conky has many built-in objects, as well as the ability to execute programs and scripts, then display the output from stdout.
We are always looking for help, and anyone interested in becoming a developer is welcome. Please use the facilities at SourceForge to make bug reports, feature requests, and submit patches.
Installation:
For users compiling from source, make sure you have the X development libraries installed. This should be a package along the lines of "libx11-dev or xorg-x11-dev".
Gentoo users -- Conky is in Gentoos Portage... simply use "emerge app- admin/conky" for installation. There is also usually an up-to-date ebuild within Conkys package or in CVS.
Debian,etc. users -- Conky will be in Debians repositories soon (by mid-September, hopefully), and then Ubuntu shortly thereafter. Until then, "dpkg -i" the .deb package to install.
Example to compile and run Conky with all optional components (note that some configure options may differ for your system):
sh autogen.sh # Only required if building from CVS
./configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --enable-xft --enable-seti --enable-dou-
ble-buffer --enable-own-window --enable-proc-uptime --enable-mpd
--enable-mldonkey --enable-x11 --enable-portmon
make
make install # Optional
src/conky
Conky probably doesnt compile with compilers other than gcc and icc. It doesnt compile with C89 compiler and not even with pure C99. It uses a few things that might not exist: strdup(), strcasecmp(), strn-casecmp(), optarg variable with getopt() and long long (not in C89). Crashes in file system statistics stuff when compiled with icc, I dont know exactly why.
You can disable drawing to own window feature in case you dont need it by passing --disable-own-window to configure -script.
Enhancements:
- FreeBSD cpu info patch
- Fixed issue where some WMs dont control conky own_window windows.
- Added newly-updated vim file detection and syntax hilighting files to svn.
- Fixed issue with graphs resetting colours (sf.net bug #1420473)
- Fixed battery problems when charged
- MPD code handles broken pipe now, instead of just killing conky
- Switch from CVS to SVN. Thanks SourceForge.
- Added patch to make $cpu stuff work on alpha (thanks Thomas Cort) http://bugs.gentoo.org/show_bug.cgi?id=122637#c3
- Stop using override_redirect true -- conky back under WM control when using own_window yes.
- Fixed texeci breakage when forking to background is on
- Drastically simplified own_window=yes window creation code.
- on_bottom and wm_class_name deprecated (they do nothing)
- Fixed typo bug in portmon code that caused incorrect monitor data to be displayed.

EasyBMPtoAVI project, a Movie Creator, is a cross-platform application that converts a series of windows bitmap (BMP) images to an AVI movie file. Currently, EasyBMPtoAVI Movie Creator is supported on little-endian (e.g., x86) machines on any platform, but big-endian support is expected soon.

Scientists may find this software particularly useful for creating animated visualizations from series of still images.

EasyBMPtoAVI Movie Creator provides a simple command line interface (CLI) that is consistent across platforms, and it interactively quizzes the user if any necessary information is missing. EasyBMPtoAVI Movie Creator is being designed with ease of use as a top goal. To that end, a graphical user interface (GUI) is planned for a future release.

The EasyBMPtoAVI project was first begun on SourceForge on May 19, 2006.

Installation:

To compile with mingw, g++, or icc:

1) Go to http://easybmp.sourceforge.net/download.html and download the most recent version of EasyBMP.

2) Extract the contents of EasyBMP_#.##.zip (where #.## is the version number) into the source directory. Take care not to overwrite the supplied makefile!

3) Type "make" without the quotes. Thats it!

To compile with Microsoft Visual Studio:

1) Go to http://easybmp.sourceforge.net/download.html and download the most recent version of EasyBMP.

2) Extract the contents of EasyBMP_#.##.zip (where #.## is the version number) into the source directory.

3) Open Visual Studio, and create a new, empty win32 console application.

4) In the "Solution Explorer" panel, right-click on the "Source Files" icon, choose "Add," then "Existing item..."

5) Browse to the source directory, and select both EasyBMP.cpp and EasyBMPtoAVI.cpp.

6) In the "Solution Explorer" panel, right-click on the "Header Files" icon, choose "Add," then "Existing item..." (This step is unnecessary in VS 2005)

7) Browse to the source directory, and select all the EasyBMP*.h files. (This step is unnecessary in VS 2005.)

8) Build the project.

Scribus is a GPL Desktop Publisher with many professional features including very high quality PDF, EPS, SVG import and export and CMYK color support.

Scribus project supports ICC color management, creates CMYK separations and interactive PDFs with form fields, scripting and presentation effects.

Scribus has a power ful Python plug-in extending its abilities. Scribus is translated into 30 languages and has excellent end user support via mailing list and irc.

FOP (Formatting Objects Processor) is the worlds first print formatter driven by XSL formatting objects (XSL-FO) and the worlds first output independent formatter.
Apache FOP project is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PCL, PS, SVG, XML (area tree representation), Print, AWT, MIF and TXT. The primary output target is PDF.
Enhancements:
- This release is the successor of version 0.20.5, FOPs production grade version.
- It contains the new API first introduced in 0.92 beta; support for Open Type fonts; support for the rgb-icc() function and a proprietary cmyk() function; copy/paste from PDF content using embedded TrueType fonts; support for PDF/A-1b and PDF/X-3:2003; improved Java2D, print, and bitmap renderers; and automatic support for all Java2D fonts for TIFF, PNG, print, AWT rendering.