Free xml version 1.0 encoding utf 8 software for linux

XMLSysInfo is a system monitoring daemon that replies to network queries with XML-encoded system information and statistics. This data can then be analyzed, graphed or otherwise presented by a front-end. It is BSD-licensed and free for anyone to use for any purpose.
Or, because it sounds so much better:
XSI is an agile, vertical XML application for mission-critical enterprise environments that leverages collective synergy to drive "outside of the box" thinking and formulate key objectives into a win-win game plan with a quality-driven approach that focuses on empowering key players to drive-up their core competencies and increase expectations with an all-around initiative to drive up the bottom-line.
It is currently under heavy development and in its "alpha" stage. The XML output grammar may still change a bit, but all in all, "beta" is approaching fast.
Main features:
System information:
- Hardware
- CPUs and load distribution on CPU states
- Interrupts
- Memory and swap space
- Operating system
Sensors:
- Temperature
- Fan RPM
- Voltage
- Disk drives
- Indicators
- ...
Storage devices:
- Filesystems
- Disk (I/O)
- RAID arrays (optional)
Network:
- Information and statistics per interface
- Packet filter statistics (optional)

Right Encoding allows you to select the Character Encoding from the context menu.
Adds the Character Encoding menu to the context menu.
Main features:
- Allows you to set the character encoding of a whole page.
- Allows you to set the character encoding of a certain frame.
Supports:
- Firefox 0.9 - 2.0.0.*
- Thunderbird 1.0 - 1.5.0.*
Enhancements:
- Supports Firefox 2.0.0.*

XML::IODEF is a Perl module for building/parsing IODEF messages.

QUICK START

Below is an example of an Incident IODEF message.
< ?xml version="1.0" encoding="UTF-8"?>
< !DOCTYPE IODEF-Message PUBLIC "-//IETF//DTD RFC XXXX IODEF v1.0//EN" "IODEF-Document.dtd">
< IODEF-Document>
< Incident purpose="handling">
< IncidentID>
#12345
< /IncidentID>
< AdditionalData meaning="data2" type="string">value2< /AdditionalData>
< AdditionalData meaning="data1" type="string">value1< /AdditionalData>
< /Incident>
< /IODEF-Document>
The previous IODEF message can be built with the following code snipset:
use XML::IODEF;

my $iodef = new XML::IODEF();

$iodef->add("Incidentpurpose", "handling");
$iodef->add("IncidentAdditionalData", "value1", "data1");
$iodef->add("IncidentAdditionalData", "value2", "data2");
$iodef->add("IncidentIncidentID", "#12345");

print $iodef->out();
To automatically insert an the ReportTime class to the current time, add the 2 lines:
$iodef->create_time();
and you will get (for example):
< ?xml version="1.0" encoding="UTF-8"?>
< !DOCTYPE IODEF-Message PUBLIC "-//IETF//DTD RFC XXXX IODEF v1.0//EN" "IODEF-Document.dtd">
< IODEF-Document>
< Incident purpose="handling">
< IncidentID>
#12345
< /IncidentID>
< IncidentData>
< ReportTime ntpstamp="0xc28859cf.0x0">2003-06-04-T11:43:11Z">2003-06-04-T11:43:11Z< /ReportTime>
< AdditionalData meaning="data2" type="string">value2
< AdditionalData meaning="data1" type="string">value1
< /Incident>
< /IODEF-Document>

Svnmailer is a tool to post subversion repository commit information by mail, news or XML (to a CIA tracker).
The svnmailer package is derived from the script mailer.py distributed with subversion. Svnmailer arose from the idea to add some features to the original mailer script.
But Ive found the script not as extensible as it could be, so the svnmailer package was redeveloped from scratch with clearer design and extensibility in mind.
Now there are additional features like property diffs, MIME encoding, configurable handling of huge mails and news postings, subject templates, consistent unicode handling and even a better extensible command line.
Enhancements:
- This release enables the possibility to send mails as BCC and allows cia_rpc_server to be configured per notification group.

ETTERLOG is a utility for Network Lan (SWITCH) for file .ECI and .ECP.
(Ettercap program).

Etterlog is the log analyzer for logfiles created by ettercap. It can handle both compressed (created with -Lc) or uncompressed logfiles. With this tool you can manipulate binary files as you like and you can print data in different ways all the times you want (in contrast with the previous logging system which was used to dump in a single static manner).

You will be able to dump traffic from only one connection of your choice, from only one or more hosts, print data in hex, ascii, binary etc... TIP: All unuseful messages are printed to stderr, so you can save the output from etterlog with the following command:

etterlog [options] logfile > outfile Thus you can dump for example a binary file from an ftp connection if you print the data in binary mode, without headers and selecting only the ftp server as the source of the communication.

GENERAL OPTIONS

-a, --analyze Analyze a log file and display some interesting statistics.

-c, --connections Parse the log file and print a table of unique connections (port to port). This option can be used only on LOG_PACKET logfiles. On LOG_INFO logfiles it is useless. TIP: you can search for a particular host by using the following command: etterlog -c logfile.ecp | grep 10.0.0.1

-f, --filter < TARGET > Print only packets coming from or going to TARGET. The TARGET specification is the same as in ettercap.
TARGET is in the form MAC/IPs/PORTs. Omitting one or more of its parts will be equivalent to set them to ANY. If the log type is LOG_INFO the target is used to display hosts matching the mac, ip and having the specified port(s) open. For example the target //80 will display only information about hosts with a running web server.

-r, --reverse Reverse the matching in the TARGET selection. It means not(TARGET). All but the selected TARGET.

-t, --proto < PROTO > Sniff only PROTO packets (default is TCP + UDP). This option is only useful in "simple" mode. If you start ettercap in interactive mode both TCP and UDP are sniffed.
PROTO can be "tcp", "udp" or "all" for both.

-F, --filcon < CONNECTION > Print packets belonging only to this CONNECTION.
CONNECTION is in the form PROTO:SOURCE:DEST. SOURCE and DEST are in the form IP:PORT. example: etterlog -F TCP:10.0.0.23:3318:198.182.196.56:80

-s, --only-source Display only packets that are sent by the source of the selected CONNECTION. This option makes sense only in conjunction with the -F option. TIP: if you want to save a file transferred in an HTTP or FTP connection, you can use the following command: etterlog -B -s -n -F TCP:10.0.0.1:20:10.0.0.2:35426 logfile.ecp > example.tar.gz

-d, --only-dest Same as --only-source but it filters on the destination host.

-n, --no-headers Do not print the header of each packet. This option is useful if you want to save a file in binary format (-B option). Without the headers you can redirect the output to a file and you will get the original stream. NOTE: the time stamp in the header is in the form: Thu Mar 27 23:03:31 2003 [169396], the value in the square brackets is expressed in microseconds

-m, --show-mac In the headers show also the mac addresses corresponding to the ip addresses.

-k, --color If used in conjunction with -F it displays the source and dest of the connection using different colors. If used with a LOG_INFO file it prints LAN hosts in green, REMOTE hosts in blue and GATEWAYS in red.

-l, --only-local Used displaying an INFO file, it displays information only about local hosts.

-L, --only-remote Used displaying an INFO file, it displays information only about remote hosts.

SEARCH OPTIONS

-e, --regex < REGEX > Display only packets matching the regex < REGEX >.
If this option is used agains a LOG_PACKET logfile, the regex is executed on the payload of the packet. If the type is LOG_INFO, the regex is executed on all the fields of the host profile (OS, banners, service and ethernet adapter).
NOTE: the regex is compiled with the REG_ICASE flag (case insensitive).

-u, --user < USER > Display information about this user. The search is performed over all the user/pass couples collected across all hosts.

-p, --passwords Print only the collected account information for each host. This prevents the huge profile output. It can be used in conjunction with the -u option to filter the users. An asterisk * used in front of an account represents a failed login attempt.

-i, --show-client Show the client ip address when displaying the collected users and passwords. It may be useful when ACLs are in place.

-I, --client < IP > Show passwords only coming from a specific < IP >. This is useful to view all the usernames and passwords of a client.


EDITING OPTIONS

-C, --concat Use this option to concatenate two (or more) files into one single file. This is useful if you have collected ettercap log files from multiple sources and want to have an unified report. The output file must be specified with the -o option and the input files are listed as normal arguments. example:
etterlog -C -o outfile input1 input2 input3

-o, --outfile < FILE > specifies the output file for a concatenation.


VISUALIZATION METHOD


-B, --binary Print data as they are, in binary form. Useful to dump binary data to a file (as described above).

-X, --hex Print the packets in hex format. example: the string "HTTP/1.1 304 Not Modified" becomes: 0000: 4854 5450 2f31 2e31 2033 3034 204e 6f74 HTTP/1.1 304 Not
0010: 204d 6f64 6966 6965 64 Modified

-A, --ascii Print only "printable" characters, the others are displayed as dots .

-T, --text Print only the "printable" characters and skip the others.

-E, --ebcdic Convert an EBCDIC text to ASCII.

-H, --html Strip all html tags from the text. A tag is every string between < and >. example: < title >This is the title< /title >, but the following < string > will not be displayed. This is the title, but the following will not be displayed.

-U, --utf8 < encoding > Print the packets in UTF-8 format. The < encoding > parameter specifies the encoding to be used while performing the conversion. Use the `iconv --list` command to obtain a list of all supported encodings.

-Z, --zero Print always the void string. i.e. print only header information and no packet content will be printed.

-x, --xml Print the host information in xml form, so you can parse it with your favourite program. The DTD associated with the xml output is in share/etterlog.dtd

STANDARD OPTIONS

-v, --version Print the version and exit.

-h, --help Print the help screen with a short summary of the available options.


EXAMPLES

Here are some examples of using etterlog.

etterlog -k -l dump.eci
Displays information about local hosts in different colors.

etterlog -X dump.ecp
Prints packets in HEX mode with full headers.

etterlog -c dump.ecp
Displays the list of connections logged in the file.

etterlog -Akn -F TCP:10.0.0.1:13423:213.203.143.52:6666 dump.ecp
Displays the IRC traffic made by 10.0.0.1 in ASCII mode, without headers information and in colored mode.

etterlog -H -t tcp -f //80 dump.ecp
Dumps all HTTP traffic and strips html tags.

etterlog -Z -r -f /10.0.0.2/22 dump.ecp
Displays only the headers of all connections except ssh on host 10.0.0.2

etterlog -A -e user -f //110 dump.ecp
Displays only POP packets containing the user regexp (case insensitive).

etterlog -u root dump.eci
Displays information about all the accounts of the user root.

etterlog -e Apache dump.eci
Displays information about all the hosts running Apache.

etterlog -e Linux dump.eci
Displays information about all the hosts with the Linux operating system.

etterlog -t tcp -f //110 dump.eci
Displays information about all the hosts with the tcp port 110 open.

etterlog -t udp dump.eci
Displays information about all the hosts with at least one UDP port open.

etterlog -B -s -n -F TCP:10.0.0.1:20:10.0.0.2:35426 logfile.ecp > example.tar.gz
Dumps in binary form the data sent by 10.0.0.1 over the data port of FTP. Since the headers are omitted, you will get the file as it was.

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

MP3::Info is a Perl module that can manipulate / fetch info from MP3 audio files.

SYNOPSIS

#!perl -w
use MP3::Info;
my $file = Pearls_Before_Swine.mp3;
set_mp3tag($file, Pearls Before Swine, q"77s",
Sticks and Stones, 1990,
q"(c) 1990 77s LTD.", rock & roll);

my $tag = get_mp3tag($file) or die "No TAG info";
$tag->{GENRE} = rock;
set_mp3tag($file, $tag);

my $info = get_mp3info($file);
printf "$file length is %d:%dn", $info->{MM}, $info->{SS};
my $mp3 = new MP3::Info $file;
$mp3->title(Perls Before Swine);
printf "$file length is %s, title is %sn",
$mp3->time, $mp3->title;

$mp3 = MP3::Info->new(FILE)

OOP interface to the rest of the module. The same keys available via get_mp3info and get_mp3tag are available via the returned object (using upper case or lower case; but note that all-caps "VERSION" will return the module version, not the MP3 version).

Passing a value to one of the methods will set the value for that tag in the MP3 file, if applicable.

use_mp3_utf8([STATUS])

Tells MP3::Info to (or not) return TAG info in UTF-8. TRUE is 1, FALSE is 0. Default is TRUE, if available.

Will only be able to turn it on if Encode is available. ID3v2 tags will be converted to UTF-8 according to the encoding specified in each tag; ID3v1 tags will be assumed Latin-1 and converted to UTF-8.

Function returns status (TRUE/FALSE). If no argument is supplied, or an unaccepted argument is supplied, function merely returns status.

This function is not exported by default, but may be exported with the :utf8 or :all export tag.

use_winamp_genres()

Puts WinAmp genres into @mp3_genres and %mp3_genres (adds 68 additional genres to the default list of 80). This is a separate function because these are non-standard genres, but they are included because they are widely used.

You can import the data structures with one of:
use MP3::Info qw(:genres);
use MP3::Info qw(:DEFAULT :genres);
use MP3::Info qw(:all);

remove_mp3tag (FILE [, VERSION, BUFFER])

Can remove ID3v1 or ID3v2 tags. VERSION should be 1 for ID3v1 (the default), 2 for ID3v2, and ALL for both.

For ID3v1, removes last 128 bytes from file if those last 128 bytes begin with the text TAG. File will be 128 bytes shorter.

For ID3v2, removes ID3v2 tag. Because an ID3v2 tag is at the beginning of the file, we rewrite the file after removing the tag data. The buffer for rewriting the file is 4MB. BUFFER (in bytes) ca change the buffer size.

Returns the number of bytes removed, or -1 if no tag removed, or undef if there is an error.

set_mp3tag (FILE, TITLE, ARTIST, ALBUM, YEAR, COMMENT, GENRE [, TRACKNUM])

set_mp3tag (FILE, $HASHREF)

Adds/changes tag information in an MP3 audio file. Will clobber any existing information in file.

Fields are TITLE, ARTIST, ALBUM, YEAR, COMMENT, GENRE. All fields have a 30-byte limit, except for YEAR, which has a four-byte limit, and GENRE, which is one byte in the file. The GENRE passed in the function is a case-insensitive text string representing a genre found in @mp3_genres.

Will accept either a list of values, or a hashref of the type returned by get_mp3tag.
If TRACKNUM is present (for ID3v1.1), then the COMMENT field can only be 28 bytes.

ID3v2 support may come eventually. Note that if you set a tag on a file with ID3v2, the set tag will be for ID3v1[.1] only, and if you call get_mp3tag on the file, it will show you the (unchanged) ID3v2 tags, unless you specify ID3v1.

get_mp3tag (FILE [, VERSION, RAW_V2])

Returns hash reference containing tag information in MP3 file. The keys returned are the same as those supplied for set_mp3tag, except in the case of RAW_V2 being set.
If VERSION is 1, the information is taken from the ID3v1 tag (if present). If VERSION is 2, the information is taken from the ID3v2 tag (if present). If VERSION is not supplied, or is false, the ID3v1 tag is read if present, and then, if present, the ID3v2 tag information will override any existing ID3v1 tag info.

If RAW_V2 is 1, the raw ID3v2 tag data is returned, without any manipulation of text encoding. The key name is the same as the frame ID (ID to name mappings are in the global %v2_tag_names).

If RAW_V2 is 2, the ID3v2 tag data is returned, manipulating for Unicode if necessary, etc. It also takes multiple values for a given key (such as comments) and puts them in an arrayref.

If the ID3v2 version is older than ID3v2.2.0 or newer than ID3v2.4.0, it will not be read.

Strings returned will be in Latin-1, unless UTF-8 is specified (use_mp3_utf8), (unless RAW_V2 is 1).

Also returns a TAGVERSION key, containing the ID3 version used for the returned data (if TAGVERSION argument is 0, may contain two versions).
get_mp3info (FILE)

Returns hash reference containing file information for MP3 file. This data cannot be changed. Returned data:

VERSION MPEG audio version (1, 2, 2.5)
LAYER MPEG layer description (1, 2, 3)
STEREO boolean for audio is in stereo

VBR boolean for variable bitrate
BITRATE bitrate in kbps (average for VBR files)
FREQUENCY frequency in kHz
SIZE bytes in audio stream
OFFSET bytes offset that stream begins

SECS total seconds
MM minutes
SS leftover seconds
MS leftover milliseconds
TIME time in MM:SS

COPYRIGHT boolean for audio is copyrighted
PADDING boolean for MP3 frames are padded
MODE channel mode (0 = stereo, 1 = joint stereo,
2 = dual channel, 3 = single channel)
FRAMES approximate number of frames
FRAME_LENGTH approximate length of a frame
VBR_SCALE VBR scale from VBR header
On error, returns nothing and sets $@.

Verbiste is a French conjugation system. Verbiste project contains a C++ library, two programs that can be run from the command line or from another program, and a GNOME applet.
This applet shows a text field in the GNOME Panel where the user can enter a conjugated verb and obtain its complete conjugation. The knowledge base is represented in XML and contains over 6800 verbs.
The current version is 0.1.13 (2005-10-10). An error in the present conditional tense of the conjugation template men:tir has been fixed.
Verbiste is free software distributed under the GNU General Public License. Please note that this means that proprietary software linked with this library cannot be distributed legally.
Enhancements:
- This release a --utf8 option for the commands french-conjugator and french-deconjugator to force them to assume that the terminal uses the UTF-8 encoding instead of Latin-1.