Free tidy software for linux

HTML TIDY is a free utility to fix mistakes made while editing HTML and to automatically tidy up sloppy editing into nicely layed out markup. It also works great on the atrociously hard to read markup generated by specialized HTML editors and conversion tools, and can help you identify where you need to pay further attention on making your pages more accessible to people with disabilities.
When editing HTML its easy to make mistakes. Wouldnt it be nice if there was a simple way to fix these mistakes automatically and tidy up sloppy editing into nicely layed out markup? Well now there is! Dave Raggetts HTML TIDY is a free utility for doing just that. It also works great on the atrociously hard to read markup generated by specialized HTML editors and conversion tools, and can help you identify where you need to pay further attention on making your pages more accessible to people with disabilities.
Tidy is able to fix up a wide range of problems and to bring to your attention things that you need to work on yourself. Each item found is listed with the line number and column so that you can see where the problem lies in your markup. Tidy wont generate a cleaned up version when there are problems that it cant be sure of how to handle. These are logged as "errors" rather than "warnings".
Dave Raggett has now passed the baton for maintaining Tidy to a group of volunteers working together as part of the open source community at Source Forge. The source code continues to be available under an open source license, and you are encouraged to pass on bug reports and enhancement requests at http://tidy.sourceforge.net.
If you find HTML Tidy useful and you would like to say thanks, then please send me a (paper) postcard or other souvenir from the area in which you live along with a few words on what you are using Tidy for. It will be fun to map out where Tidy users are to be found! My postal address is given at the end of this file.
The W3C public email list devoted to HTML Tidy is: . To subscribe send an email to html-tidy-request@w3.org with the word subscribe in the subject line (include the word unsubscribe if you want to unsubscribe). The archive for this list is accessible online. If you would like to contact the developers, or you just want to submit an enhancement request or a bug report, please visit http://tidy.sourceforge.net.
Tidy can now perform wonders on HTML saved from Microsoft Word 2000! Word bulks out HTML files with stuff for round-tripping presentation between HTML and Word. If you are more concerned about using HTML on the Web, check out Tidys "Word-2000" config option! Of course Tidy does a good job on Word97 files as well!
Main features:
- Missing or mismatched end tags are detected and corrected
- End tags in the wrong order are corrected
- Fixes problems with heading emphasis
- Recovers from mixed up tags
- Getting the

---

in the right place
- Adding the missing "/" in end tags for anchors
- Perfecting lists by putting in tags missed out
- Missing quotes around attribute values are added
- Unknown/Proprietary attributes are reported
- Proprietary elements are recognized and reported as such
- Tags lacking a terminating > are spotted

TkHTMLtidy is a Tcl/Tk front-end for tidy, the W3C utility to clean up and pretty print HTML/XHTML/XML. It includes support for most of tidys options.

atropine is a screen-scraping library built on top of BeautifulSoup.
atropine helps programmers make assertions about document structure while getting at the data they are interested in.
atropine library was developed under Python.
Special thanks to Piet Delport for the resolver, null resolver, chain-of-resolvers ideas.
Please note, using this library is not as complicated as it sounds, it consists of only 275 lines of python.
It is better to get no data than to get the wrong data.
The key to screen-scraping the right data is to make a painful amount of assertions about document structure
Enhancements:
- Some unused imports were removed.
- A text only version of the reference was added.
- Things were generally tidied up.

smtpfilter is a filter for an SMTP session which passes the session through transparently in real time, except for the DATA command which is intercepted in order to scan the data for spam and/or viruses with the scanner of your choice.

If you are reading this source, it is what should have been an internal release and consequently has a few comments at the head of the file which would not normally be here. Most likely I must have released this in a hurry because someone needed some
recent feature that has been added, before I had time to do a periodic code review and tidy-up. If this is your first time looking at or installing this code you should probably get in
touch with the author (gtoal@gtoal.com) and ask for a cleaner version before you start.

The descriptive comments which explain what this program does, and how, have slowly migrated from being at the top of the file to being lost half way down. That is something which will be done in the next maintenance release.

But this version *does* work, and works very well now. It is in service at the University of Texas Pan American, with 2000 staff and 15,000 students (although not all of those are active emailers -maybe only 2000-3000 are in heavy use. It sometimes looks like
AOL and MSN and Yahoo are the official campus mailers.

fid-graphics project is a simple toolkit for the Frigand Imperial Desktop.
It is probably the easiest toolkit to write a display engine for, but it does not support any widgets.
Enhancements:
- src/Desktop/Fid/Window.lhs (displayWaitRedisplay): New function.
- (requestRedisplay): Tidy up.
- src/Desktop/Fid/Main.lhs (data WinCapLine): New type.
- (data WindowType): Use it.
- (&&*, ||*, isnt, haveEnvVar, haveOpt): Deleted.
- (lookupFeature, lookupProtocol, lookupKeywords): New functions.
- (windowTypes): Use WindowCapLine.
- (forkProcess): Unused; deleted.
- (data FidOpt): Unused; deleted.
- (fidMain): Dont consider forking.
- Only call getOpt to sort out verbose options.
- src/Desktop/Fid/Control.lhs (PrimKey): New type.
- (instance Eq PrimKey, instance Ord PrimKey)
- (instance Show PrimKey, instance Arbitrary PrimKey): Instances for t.
- (data Key): Use it.
- (charKey, control, keyToChar): Do the right thing with PrimKey.
- (symbolKey): New function.
- (instance Arbitrary Key): Use instance Arbitrary PrimKey.
- (instance Arbitrary Char): New Instance.

File::Wildcard is a Perl module for enhanced glob processing.

SYNOPSIS

use File::Wildcard;
my $foo = File::Wildcard->new(path => "/home/me///core");
while (my $file = $foo->next) {
unlink $file;
}

When looking at how various operating systems do filename wildcard expansion (globbing), VMS has a nice syntax which allows expansion and searching of whole directory trees. It would be nice if other operating systems had something like this built in. The best Unix can manage is through the utility program find.

This module provides this facility to Perl. Whereas native VMS syntax uses the ellipsis "...", this will not fit in with POSIX filenames, as ... is a valid (though somewhat strange) filename. Instead, the construct "///" is used as this cannot syntactically be part of a filename, as you do not get three concurrent filename separators with nothing between (three slashes are used to avoid confusion with //node/path/name syntax).

You dont have to use this syntax, as you can do the splitting yourself and pass in an arrayref as your path.

The module also forms a regular expression for the whole of the wildcard string, and binds a series of back references ($1, $2 etc.) which are available to construct new filenames.

new

File::Wildcard-new( $wildcard, [,option => value,...]);>
my $foo = File::Wildcard->new( path => "/home/me///core");
my $srcfnd = File::Wildcard->new( path => "src///*.cpp",
match => qr(^src/(.*?).cpp$),
derive => [src/$1.o,src/$1.hpp]);

This is the constructor for File::Wildcard objects. At a simple level, pass a single wildcard string as a path.

For more complicated operations, you can supply your own match regexp, or use the derive option to specify regular expression captures to form the basis of other filenames that are constructed for you.

The $srcfnd example gives you object files and header files corresponding to C++ source files.

Here are the options that are available:

path

This is the input parameter that specifies the range of files that will be looked at. This is a glob spec which can also contain the ellipsis /// (it could contain more than one ellipsis, but the benefit of this is questionable, and multiple ellipsi would cause a performance hit).

Note that the path can be relative or absolute. new will do the right thing, working out that a path starting with / is absolute. In order to recurse from the current directory downwards, specify .///foo.

As an alternative, you can supply an arrayref with the path constituents already split. If you do this, you need to tell new if the path is absolute. Include an empty string for an ellipsis. For example:

foo///bar/*.c is equivalent to [foo,,bar,*.c]

You can also construct a File::Wildcard without a path. A call to next will return undef, but paths can be added using the append and prepend methods.
absolute

This is ignored unless you are using a pre split path. If you are passing a string as the path, new will work out whether the path is absolute or relative. Pass a true value for absolute paths.

If your original filespec started with / before you split it, specify absolute => 1. absolute is not required for Windows if the path contains a drive specification, e.g. C:/foo/bar.

case_insensitive

By default, the module will use Filesys::Type to determine whether the file system of your wildcard is defined. This is an optional module (see Module::Optional), and File::Wildcard will guess at case sensitivity based on your operating system. This will not always be correct, as the file system might be VFAT mounted on Linux or ODS-5 on VMS.

Specifying the option case_insensitive explicitly forces this behaviour on the wildcard.

Note that File::Wildcard will use the file system of the current working directory if the path is not absolute. If the path is absolute, you should specify the case_sensitivity option explicitly.

exclude

You can provide a regexp to apply to any generated paths, which will cause any matching paths not to be processed. If the root of a directory tree matches, no processing is done on the entire tree.

This option can be useful for excluding version control repositories, e.g.

exclude => qr/.svn/
match

Optional. If you do not specify a regexp, you get all the files that match the glob; in addition, new will set up a regexp for you, to provide a capture for each wildcard used in the path.

If you do provide a match parameter, this will be used instead, and will filter the results.

derive

Supply an arrayref with a list of derived filenames, which will be constructed for each matching file. This causes next to return an arrayref instead of a scalar.
follow

If given a true value indicates that symbolic links are to be followed. Otherwise, the symbolic link target itself is presented, but the ellipsis will not traverse the link.

This module detects a looping symlink that points to a directory higher up, and will only present the tree once.

ellipsis_order

This can take one of the following values: normal, breadth-first, inside-out. The default option is normal. This controls how File::Wildcard handles the ellipsis. The default is a normal depth first search, presenting the name of each containing directory before the contents.

The inside-out order presents the contents of directories first before the directory, which is useful when you want to remove files and directories (all O/S require directories to be empty before rmdir will work). See t/03_absolute.t as this uses inside-out order to tidy up after the test.

Breadth-first is rarely needed (but I do have an application for it). Here, the whole directory contents is presented before traversing any subdirectories.
Consider the following tree: a/ a/bar/ a/bar/drink a/foo/ a/foo/lish
breadth-first will give the following order: qw(a/ a/bar/ a/foo/ a/bar/drink a/foo/lish). normal gives the order in which the files are listed. inside-out gives the following: qw(a/bar/drink a/bar/ a/foo/lish a/foo/ a/).

sort

By default, globbing returns the list of files in the order in which they are returned by the dirhandle (internally). If you specify sort => 1, the files are sorted into ASCII sequence (case insensitively if we are operating that way). If you specify a CODEREF, this will be used as a comparison routine. Note that this takes its operands in @_, not in $a and $b.

debug and debug_output

You can enable a trace of the internal states of File::Wildcard by setting debug to a true value. Set debug_output to an open filehandle to get the trace in a file. If you are submitting bug reports for File::Wildcard, attaching debug trace files would be very useful.

debug_output defaults to STDERR.
match
my $foo_re = $foo->match;
$foo->match(bar/core);

This is a get and set method that gives access to the match regexp that the File::Wildcard object is using. It is possible to change the regex on the fly in the middle of a search (though I dont know why anyone would want to do this).

append

$foo->append(path => /home/me///*.tmp);

appends a path to an objects todo list. This will be globbed after the object has finished processing the existing wildcards.

prepend
$srcfnd->prepend(path => $include_file);

This is similar to append, but prepends the path to the todo list. In other words, the current wildcard operation is interrupted to serve the new path, then the previous wildcard operation is resumed when this is exhausted.

next
while (my $core = $foo->next) {
unlink $core;
}
my ($src,$obj,$hdr) = @{$srcfnd->next};

The next method is an iterator, which returns successive files. Returns matching files if there was no derive option passed to new. If there was a derive option, returns an arrayref containing the matching filespec and all derived filespecs. The derived filespecs do not have to exist.

Note that next maintains an internal cursor, which retains context and state information. Beware if the contents of directories are changing while you are iterating with next; you may get unpredictable results. If you are intending to change the contents of the directories you are scanning (with unlink or rename), you are better off deferring this operation until you have processed the whole tree. For the pending delete or rename operations, you could always use another File::Wildcard object - see the spike example below:

all
my @cores = $foo->all;

all returns an array of matching files, in the simple case. Returns an array of arrays if you are constructing new filenames, like the $srcfnd example.

Beware of the performance and memory implications of using all. The method will not return until it has read the entire directory tree. Use of the all method is not recommended for traversing large directory trees and whole file systems. Consider coding the traversal using the iterator next instead.

reset

reset causes the wildcard context to be set to re-read the first filename again. Note that this will cause directory contents to be re-read.

Note also that this will cause the path to revert to the original path specified to new. Any additional paths appended or prepended will be forgotten.

close

Release all directory handles associated with the File::Wildcard object. An object that has been closed will be garbage collected once it goes out of scope. Wildcards that have been exhausted are automatically closed, (i.e. all was used, or c< next > returned undef).

Subsequent calls to next will return undef. It is possible to call reset after close on the same File::Wildcard object, which will cause it to be reopened.

DisSent (short for "Distribute Sent Mails") is a program for separating your sent mail from a single folder into different folders based on properties of the individual messages in the folder.
DisSent scans your mail storage and proposes a set of actions to tidy up your sent mail folders.
Almost all mail user agents (MUA, "mail clients") Ive encountered implement a standard way of handling outgoing messages by placing a copy of every sent message into a certain special folder.
While this might be a fail-safe approach, it is not very useful for you if you belong to those people who work with mail folders and rules to sort incoming mails. Usually, youll have your rules setup so that an incoming mail from John Doe will be moved into a separate folder, lets say "INBOX.Friends.JDoe". Now if you reply to this mail, your answer is moved to an entirely different folder, and if you want to look up your answer some time later, youll have to browse through all the mails you sent in the meantime. This is ugly.
Enters DisSent (short for "Distribute Sent Mails"). DisSent scans your mail storage and proposes a set of actions to tidy up your sent mail folders. More precisely, it gives you a list of messages along with proposals on where to move these messages. You can then select the mails you want to move and let DisSent do the actual work.
Known Issues
- The progress monitors should be modal so you cant execute other actions while DisSent is busy.
- The protocol SMTP in the login window doesnt really make sense.