Free epic movie part 1 software for linux

3gp movie wizard is a small perl/kommander script that helps you to convert almost any movie format to 3gp movie, suitable for watching on the modern mobile phones (tested only on Motorola V360 but should work with any mobile with 3gp support and 176 pixel wide screen).

It should be extremely easy to use, yet offer advanced options such as a good subtitle support and video equalizer.

Movie Mapper project is a small program for indexing movie collections.

Movie Mapper is a small program for indexing movie collections. It browses given directory trees, searching for text files that contain IMDB URLs.

These URLs are used to generate database entries for movies.

Movie Mapper can also be used for offline indexing by creating text files that contain offline movie titles.

It tries to find matches from IMDB for those titles listed in the text files.

Quake 3 Movie Makers Edition is a customized Quake 3 engine for the movie making community.
It simplifies required tasks and adds new features to the engine that are related to the movie making.
Enhancements:
- Fixes TGA compatibility with VirtualDub.

lzMovieDB provides a Web-based database for movies and series.
lzMovieDB is an PHP/MySQL Database script to sort and archive movies and series.
It grabs the user rating and movie cover from IMDB (Internet Movie Database => www.imdb.com).
Main features:
- Categorys
- show newest entrys
- search function
- sort by genre
- two languages (english,german)
- templates
- IMDB rating
- IMDB cover

Kexi Report Part is a reporting component for Kexi 1.6 based on OpenRPT 1.2.
Main features:
- A report viewer for Kexi
- An external report designer (KexiReportWriter) based on the OpenRPT writer program
Known Working Features
- Page Header
- Page Footer
- Report Header
- Report Footer
- Detail section
- Labels
- Lines
- Fields
- Page Browser
How To Create Report
1. Install the component following the instructions in INSTALL
2. Run KexiReportWriter to start designing a report
3. Select Database->Connect to DB
4. Browse to an existing Kexi Database and open it
5. Create a new report (File->New)
6. Assign a data source to the report (Document->Properties)
7. Create the report using labels/fields/lines
8. Assign columns to the field objects (Double click for properties)
9. Save the report. (Database->Save to DB)
10. Load the database in Kexi and double click the report to view it
Enhancements:
- Removed requirement to have kexi source available to install the plugin.Done this by including the needed kexi headers in the package. Only downside is that kexi 1.1.3 (from koffice 1.6.3) is required.

vMovieDB project is a movies collection manager for GNOME desktop. Its GTK+ 2.x, application writen on C, created according to Gnome-HIG standarts, vMovieDB fits perfectly in GNOME Desktop Enviroment.
Main features:
- Play selected movie with your favorite video player.
- Manage various types of information for your movies: title, year, media type, quality, subtitles, location, genre and movie image.
- Genre editor.
- Export your movies to html document.
- Export movies to text document.
- Search for selected movie on ImDB.com.
vMovieDB have fast and light database based on XML.

openDICOM.NET software implements a new approach towards DICOM (Digital Imaging and Communications in Medicine) libraries. DICOM is a worldwide standard in Medical IT and is provided by the National Electrical Manufacturers Assocation (NEMA). This standard specifies the way medical images and meta data like study or patient related data is stored and communicated over different digital medias. Thus, DICOM is a binary protocol and data format.

The openDICOM# Class Libary, main part of the openDICOM.NET project, provides an API to DICOM in C# for Mono and the .NET Framework. It is a completely new implementation of DICOM. In contrast to other similar libraries the intention of this implementation is to provide a clean classification with support of unidirectional DICOM data streaming. Another implemented goal is the support of DICOM as XML. This is not standard conform but very use- and powerful within software development, storage and manipulation. Currently, full read support of DICOM output stream and full write support to XML is supposed to be provided. The entire DICOM content can be accessed as sequence or as tree of class instances. Latter is the default representation of DICOM content by the library.

The openDICOM.NET Utils are a collection of console tools for working with the needed data dictionaries in different data formats (binary and textual), query of ACR-NEMA (prior DICOM standard) and DICOM files and transcoding them into image formats like JPEG and XML files. These utils are written in C# for Mono and the .NET Framework and are using the openDICOM# API for processing.

Last but not least, the openDICOM.NET Navigator recapitulates the openDICOM.NET Utils in form of a GTK# GUI. It provides different views with focus on DICOM data sets and visualization. Connectivity to GIMP is also given for image processing purpose as well as the possibility to run through multi-frame images like a movie.

Encode::PerlIO is a detailed document on Encode and PerlIO.

Overview

It is very common to want to do encoding transformations when reading or writing files, network connections, pipes etc. If Perl is configured to use the new perlio IO system then Encode provides a "layer" (see PerlIO) which can transform data as it is read or written.

Here is how the blind poet would modernise the encoding:

use Encode;
open(my $iliad,:utf8,iliad.utf8);
my @epic = < $iliad >;
print $utf8 @epic;
close($utf8);
close($illiad);

In addition, the new IO system can also be configured to read/write UTF-8 encoded characters (as noted above, this is efficient):

open(my $fh,>:utf8,anything);
print $fh "Any x{0021} string N{SMILEY FACE}n";

Either of the above forms of "layer" specifications can be made the default for a lexical scope with the use open ... pragma. See open.

Once a handle is open, its layers can be altered using binmode.

Without any such configuration, or if Perl itself is built using the systems own IO, then write operations assume that the file handle accepts only bytes and will die if a character larger than 255 is written to the handle. When reading, each octet from the handle becomes a byte-in-a-character. Note that this default is the same behaviour as bytes-only languages (including Perl before v5.6) would have, and is sufficient to handle native 8-bit encodings e.g. iso-8859-1, EBCDIC etc. and any legacy mechanisms for handling other encodings and binary data.
In other cases, it is the programs responsibility to transform characters into bytes using the API above before doing writes, and to transform the bytes read from a handle into characters before doing "character operations" (e.g. lc, /W+/, ...).

You can also use PerlIO to convert larger amounts of data you dont want to bring into memory. For example, to convert between ISO-8859-1 (Latin 1) and UTF-8 (or UTF-EBCDIC in EBCDIC machines):

open(F, ":utf8", "data.utf") or die $!;
while (< F >) { print G }

# Could also do "print G < F >" but that would pull
# the whole file into memory just to write it out again.

More examples:

open(my $f, ":encoding(iso-8859-2)")
open(my $h, ">:encoding(latin9)") # iso-8859-15