Free html documents software for linux

XML::DOM::Document is an XML document node in XML::DOM.

XML::DOM::Document extends XML::DOM::Node.

It is the main root of the XML document structure as returned by XML::DOM::Parser::parse and XML::DOM::Parser::parsefile.

Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document, the Document interface also contains the factory methods needed to create these objects. The Node objects created have a getOwnerDocument method which associates them with the Document within whose context they were created.

METHODS

getDocumentElement

This is a convenience method that allows direct access to the child node that is the root Element of the document.

getDoctype

The Document Type Declaration (see DocumentType) associated with this document. For HTML documents as well as XML documents without a document type declaration this returns undef. The DOM Level 1 does not support editing the Document Type Declaration.

Not In DOM Spec: This implementation allows editing the doctype. See XML::DOM::ignoreReadOnly for details.

getImplementation

The DOMImplementation object that handles this document. A DOM application may use objects from multiple implementations.

createElement (tagName)

Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.

DOMExceptions:

INVALID_CHARACTER_ERR

Raised if the tagName does not conform to the XML spec.

createTextNode (data)

Creates a Text node given the specified string.

createComment (data)

Creates a Comment node given the specified string.

createCDATASection (data)

Creates a CDATASection node given the specified string.

createAttribute (name [, value [, specified ]])

Creates an Attr of the given name. Note that the Attr instance can then be set on an Element using the setAttribute method.

Not In DOM Spec: The DOM Spec does not allow passing the value or the specified property in this method. In this implementation they are optional.

Parameters: value The attributes value. See Attr::setValue for details. If the value is not supplied, the specified property is set to 0. specified Whether the attribute value was specified or whether the default value was used. If not supplied, its assumed to be 1.

DOMExceptions:

INVALID_CHARACTER_ERR

Raised if the name does not conform to the XML spec.

createProcessingInstruction (target, data)

Creates a ProcessingInstruction node given the specified name and data strings.

Parameters: target The target part of the processing instruction. data The data for the node.

DOMExceptions:

INVALID_CHARACTER_ERR

Raised if the target does not conform to the XML spec.

createDocumentFragment

Creates an empty DocumentFragment object.

createEntityReference (name)

Creates an EntityReference object.

Auto Save Document is an extension used to store the currently shown document in a separate directory automatically.

Autosave is a small extension, which can be used to store the currently shown document in a seperate directory automatically when browsing a certain site. You may configure the sites, where all pages will be stored to cache, by adding them to a list. The documents are stored as html-text only (no embedded objects like pictures etc.)

The files are cyclic reused, e.g. if you set the cache size to 100, Autosave will store the document contents to X:/MyCache/Autosave_0.html ... AutoSave_100.html and start again with AutoSave_0.htm when the 101st page is browsed. A small Icon in the statusbar will change its colour each time to indicate a page was written.

If you click this small icon, the current page will be dumped, regardless if the site is in the autosave list or not.

NOTE: this extension is really, really simple! Only plain text is saved, no external .css,.js => the result may look ugly! The one and only intention for this extension is, to save the text for external parsing or similar! Look for Scrapbook etc. in case you want to store more than the plain text!

HTML::EP is a system for embedding Perl into HTML.
SYNOPSIS
< html >< head >< title >CGI-Env< /title >< /head >
< ep-comment >
This is an HTML document. You see. Perhaps you wonder about
the unknown HTML tags like ep-comment above? They are part
of the EP system. For example, this comment section will
be removed and you wont see it in your browser.
< /ep-comment >
< ep-perl >
# This is an example of embedding Perl into the page.
# We create a variable called time, containing the current
# time. This variable will be used below.
my $self = $_;
$self->{time} = localtime(time());
; # Return an empty string; result becomes embedded into the
# HTML page
< /ep-perl >
< body >< h1 >The current time< /h1 >
Your HTML::EP system is up and running: The current time is $time$.
< /body >
< /html >
NEWS
HTML::EP does now have a homepage, a CVS repository and a bug tracking system. Try
http://html-ep.sourceforge.net/
Have you ever written a CGI binary? Easy thing, isnt it? Was just fun!
Have you written two CGI binaries? Even easier, but not so much fun.
How about the third, fourth or fifth tool? Sometimes you notice that you are always doing the same:
- Reading and parsing variables
- Formatting output, in particular building tables
- Sending mail out from the page
- Building a database connection, passing CGI input to the database and vice versa
- Talking to HTML designers about realizing their wishes
You see, its soon to become a pain. Of course there are little helpers around, for example the CGI module, the mod_perl suite and lots of it more. Using them make live a lot easier, but not so much as you like. CGI(3). mod_perl(3).
On the other hand, there are tools like PHP or WebHTML. Incredibly easy to use, but not as powerfull as Perl. Why not get the best from both worlds? This is what EP wants to give you, similar to ePerl or HTML::EmbPerl. I personally believe that EP is simpler and better extendible than the latter two. ePerl(1). HTML::EmbPerl(3).
In short, its a single, but extensible program, that scans an HTML document for certain special HTML tags. These tags are replaced by appropriate output generated by the EP. What remains is passed to the browser. Its just like writing HTML for an enhanced browser!

The RTF to HTML convertor converts RTF files (in Windows-1250 encoding) to HTML file (in ISO-8859-2 encoding).
Main features:
- Bullets
- Superscript and subscript look bad in html document.
- Subscript is transformed to number. Superscript is transformed to "[number]".
- Text: bold, italic and underline
- Footnotes
- Alignments: left, center and right. "Justify" alignment
- looks bad - program use left alignment. Centered text is greater.
- Tables
- Links: text "aaa@bbb.cz" and "http://www.aaaaaa.cz" convert
- to html links.
- Unicode: Commentary with the character
- name is added to the non ISO Latin2 characters. The program htm2htm will
- convert html with commentaries to the unicode.
- Rtf commands sa and sb.
- (sa>0) or (sb>0) New paragraph - "p" html command
- (sa=0) and (sb=0) New paragraph (left aligned text) "< br >"
Enhancements:
- Processing was fixed in the RTF commands "fldinst", "fldrslt", "plain", "bkmkstart", and "bkmend".

HTMLab is a tool for demonstrating and experimenting with HTML markup. It runs within a web browser, using JavaScript and CGI. HTML documents may be created or marked up on-the-fly, and the results immediately displayed or validated.

The Interactive HTMLab is implemented by the htmlab.cgi CGI script. This script requires perl version 5 and the LWP::UserAgent module.

Do not even consider retrieving this unless you are reasonably competent with perl. All you are getting is a bare script with no documentation. You will almost certainly need to tailor it to work in your environment.

For instance, the do-validate.sh script (launched by the VALIDATE button) almost certainly wont run as-is in your environment.

Top Downloads provides a script that counts how many times a file has been downloaded.

It keeps statistics of your downloads and can generate a TOP10 of your downloaded files. The administration function of this script allows you to delete, rename or change count numbers for your downloads.

It can check a directory that you specify for new files and add it to a database. Count numbers and TOP10 can be included into a HTML document.

Most web servers require SSI documents to have the extension .shtml or .shtm

For Apache web servers:
- AddType text/html .shtml
- AddHandler server-parsed .shtml

HTML::StripScripts can strip scripting constructs out of HTML.

SYNOPSISM

use HTML::StripScripts;

my $hss = HTML::StripScripts->new({ Context => Inline });

$hss->input_start_document;

$hss->input_start(< i >);
$hss->input_text(hello, world!);
$hss->input_end(< /i >);

$hss->input_end_document;

print $hss->filtered_document;

This module strips scripting constructs out of HTML, leaving as much non-scripting markup in place as possible. This allows web applications to display HTML originating from an untrusted source without introducing XSS (cross site scripting) vulnerabilities.

You will probably use HTML::StripScripts::Parser rather than using this module directly.

The process is based on whitelists of tags, attributes and attribute values. This approach is the most secure against disguised scripting constructs hidden in malicious HTML documents.

As well as removing scripting constructs, this module ensures that there is a matching end for each start tag, and that the tags are properly nested.

Previously, in order to customise the output, you needed to subclass HTML::StripScripts and override methods. Now, most customisation can be done through the Rules option provided to new().

The HTML document must be parsed into start tags, end tags and text before it can be filtered by this module. Use either HTML::StripScripts::Parser or HTML::StripScripts::Regex instead if you want to input an unparsed HTML document.