mxTidy - Interface to HTML Tidy (HTML/XML cleanup tool)
| HTML Tidy Options : Interface ( Functions : Constants ) : Examples : Structure : Support : Download : Copyright & License : History : Home | Version 0.3.0 |
Introduction
mxTidy provides a Python interface to a thread-safe, library version of the HTML Tidy command line tool.
HTML Tidy helps you to cleanup coding errors in HTML and XML files and produce well-formed HTML, XHTML or XML as output. This allows you to preprocess web-page for inclusion in XML repositories, prepare broken XML files for validation and also makes it possible to write converters from well-known word processing applications such as MS Word to other structured data representations by using XML as intermediate format.
During the development of this interface, the original HTML Tidy version was significantly modified to turn it from a single run, command line tool into a thread-safe C library which not only interfaces to files, but also to memory buffers.
Most of mxTidy's operations are automatic or can be manipulated by large number of configuration options. It also provides you with access to the error and warning information generated by HTML Tidy.
Speed and Memory
HTML Tidy is very good at trying to restructure the HTML or XML input, but unfortunately not too fast at it. The main reason for this is the single character input/output strategy used in the code which causes quite a few C function calls.
Changing the code to use a buffer and pointer strategy would enhance the performance, but requires a lot of work.
The memory requirements in string to string mode amount to about twice the size of the input string in addition to the parser tree overhead. In file to file mode, only the tree overhead is introduced.
Note that the current releases reconfigure HTML Tidy for every run which causes additional overhead.
Interface
add_xml_decl (0)-
If set to 1, Tidy will add the XML declatation when
outputting XML or XHTML. The default is 0.
Note that if the input document includes an <?xml?> declaration then it will appear in the output independent of the value of this option.
add_xml_space (0)-
If set to 1, this causes Tidy to add
xml:space="preserve" to elements such as pre, style and
script when generating XML.
This is needed if the whitespace in such elements is to be parsed appropriately without having access to the DTD. The default is 0.
assume_xml_procins (0)-
If set to 1, this changes the parsing of
processing instructions to require ?> as the terminator
rather than >.
The default is 0. This option is automatically set if the input is in XML.
break_before_br (0)- If set to 1, Tidy will output a line break before each <br> element. The default is 0.
clean (0)- If set to 1, causes Tidy to strip out surplus presentational tags and attributes replacing them by style rules and structural markup as appropriate. It works well on the html saved from Microsoft Office'97. The default is 0.
drop_empty_paras (1)-
If set to 1, empty paragraphs will be
discarded. If set to no, empty paragraphs are replaced by
a pair of
brelements as HTML4 precludes empty paragraphs. The default is 1. drop_font_tags (0)- If set to 1 together with the clean option (see above), Tidy will discard font and center tags rather than creating the corresponding style rules. The default is 0.
enclose_block_text (0)- If set to 1, this causes Tidy to insert a p element to enclose any text it finds in any element that allows mixed content for HTML transitional but not HTML strict. The default is 0.
fix_backslash (1)- If set to 1, this causes backslash characters "\" in URLs to be replaced by forward slashes "/". The default is 1.
fix_bad_comments (1)- If set to 1, this causes Tidy to replace unexpected hyphens with '=' characters when it comes across adjacent hyphens. The default is 1. This option is provided for users of Cold Fusion which uses the comment syntax: <!--- --->
gnu_emacs (0)- If set to 1, Tidy changes the format for reporting errors and warnings to a format that is more easily parsed by GNU Emacs. The default is 0.
hide_endtags (0)- If set to 1, optional end-tags will be omitted when generating the pretty printed markup. This option is ignored if you are outputting to XML. The default is 0.
indent_attributes (0)- If set to 1, each attribute will begin on a new line. The default is 0.
input_xml (0)- If set to 1, Tidy will use the XML parser rather than the error correcting HTML parser. The default is 0.
literal_attributes (0)- If set to 1, this ensures that whitespace characters within attribute values are passed through unchanged. The default is 0.
logical_emphasis (0)- If set to 1, causes Tidy to replace any occurrence of i by em and any occurrence of b by strong. In both cases, the attributes are preserved unchanged. The default is 0. This option can now be set independently of the clean and drop-font-tags options.
numeric_entities (0)- Causes entities other than the basic XML 1.0 named entities to be written in the numeric rather than the named entity form. The default is 0.
output_error (1)- Generate error information. Default if 1.
output_markup (1)- Generate markup output. Turning this off is useful for checking for errors only. Default if 1.
output_xhtml (0)- If set to 1, Tidy will generate the pretty printed output writing it as extensible HTML. The default is 0. This option causes Tidy to set the doctype and default namespace as appropriate to XHTML. If a doctype or namespace is given they will checked for consistency with the content of the document. In the case of an inconsistency, the corrected values will appear in the output. For XHTML, entities can be written as named or numeric entities according to the value of the "numeric-entities" property. The tags and attributes will be output in the case used in the input document, regardless of other options.
output_xml (0)- If set to 1, Tidy will use generate the pretty printed output writing it as well-formed XML. Any entities not defined in XML 1.0 will be written as numeric entities to allow them to be parsed by an XML parser. The tags and attributes will be in the case used in the input document, regardless of other options. The default is 0.
quiet (0)- If set to 1, Tidy won't output the welcome message or the summary of the numbers of errors and warnings to the error stream. The default is 0.
quote_ampersand (1)- If set to 1, this causes unadorned & characters to be written out as &. The default is 1.
quote_marks (0)- If set to 1, this causes " characters to be written out as " as is preferred by some editing environments. The apostrophe character ' is written out as ' since many web browsers don't yet support '. The default is 0.
quote_nbsp (1)- If set to 1, this causes non-breaking space characters to be written out as entities, rather than as the Unicode character value 160 (decimal). The default is 1.
raw (0)- Avoid mapping values > 127 to entities. Default is 0.
show_warnings (0)- If set to 0, warnings are suppressed. This can be useful when a few errors are hidden in a flurry of warnings. The default is 1.<
tidy_mark (0)- f set to 1 (the default) Tidy will add a meta element to the document head to indicate that the document has been tidied. To suppress this, set tidy-mark to 0. Tidy won't add a meta element if one is already present.
uppercase_attributes (0)- If set to 1 attribute names are output in upper case. The default is 0 resulting in lowercase, except for XML where the original case is preserved.
uppercase_tags (0)- Causes tag names to be output in upper case. The default is 0 resulting in lowercase, except for XML input where the original case is preserved.
word_2000 (0)-
If set to 1, Tidy will go to great pains to
strip out all the surplus stuff Microsoft Word 2000
inserts when you save Word documents as "Web pages". The
default is 0.
Microsoft has developed its own optional filter for exporting to HTML, and the 2.0 version is much improved. You can download the filter free from the Microsoft Office Update site.
wrap_asp (1)- If set to 0, this prevents lines from being wrapped within ASP pseudo elements, which look like: <% ... %>. The default is 1.
wrap_attributes (0)- If set to 1, attribute values may be wrapped across lines for easier editing. The default is 0. This option can be set independently of wrap-scriptlets.
wrap_jste (1)- If set to 0, this prevents lines from being wrapped within JSTE pseudo elements, which look like: <# ... #>. The default is 1.
wrap_php (1)- If set to 0, this prevents lines from being wrapped within PHP pseudo elements. The default is 1.
wrap_script_literals (0)- If set to 1, this allows lines to be wrapped within string literals that appear in script attributes. The default is 0.
wrap_sections (1)- Wrap within <![ ... ]> section tags. Default is 1.
indent_spaces (2)- Sets the number of spaces to indent content when indentation is enabled. The default is 2 spaces.
tab_size (8)- Sets the number of columns between successive tab stops. The default is 8. It is used to map tabs to spaces when reading files. Tidy never outputs files with tabs.
wrap (72)- Sets the right margin for line wrapping. Tidy tries to wrap lines so that they do not exceed this length. The default is 72. Set wrap to 0 if you want to disable line wrapping.
alt_text (None)- This allows you to set the default alt text for img attributes. This feature is dangerous as it suppresses further accessibility warnings.
indent ("no")- If set to "yes", Tidy will indent block-level tags. The default is "no". If set to "auto" Tidy will decide whether or not to indent the content of tags such as title, h1-h6, li, td, th, or p depending on whether or not the content includes a block-level element. You are advised to avoid setting indent to yes as this can expose layout bugs in some browsers.
char_encoding ("ascii")- Determines how Tidy interprets character streams. For "ascii", Tidy will accept Latin-1 character values, but will use entities for all characters whose value > 127. For "raw", Tidy will output values above 127 without translating them into entities. For "latin1" characters above 255 will be written as entities. For "utf8", Tidy assumes that both input and output is encoded as UTF-8. You can use "iso2022" for files encoded using the ISO2022 family of encodings e.g. ISO 2022-JP. The default is "ascii".
tidy(input, output=None, errors=None, **options)-
Beautify the HTML/XML input and return a tuple
(nerrors, nwarnings, outputdata, errordata).inputmay be a string or a file open for reading data.If
outputis given as file open for writing, the generated markup is written to this file andoutputdatais set to None. Otherwise, output is written to a string which is returned by the function inoutputdata.The same is true for error information which Tidy generates. This is either written to
errorsor returned via errordata.nerrorsandnwarningsare integers which are set to the number of errors/warnings which TIDY generated.Tidy options can be passed to the function using keyword parameters, e.g.
output_xhtml=1. Configuration files are not supported by the interface. Error- This exception will be raised for problems related to the Tidy interface.
The mxTidy package defines the following interfaces. Most
important are the HTML Tidy options which the interface
functions allow you to pass to the underlying HTML Tidy
engine.
Most of the original HTML Tidy options are also
available in the mxTidy interface; some options have
been removed, though, since they don't map well to an
embedded module, e.g. there is no configuration file
support and the slide bursting options have also been
removed.
The following options are available. The default values
used in mxTidy are given in parenthesis. Note that some
options have different defaults than in the command line
version of HTML Tidy.
For more information about the background and workings
of HTML Tidy, please see the HTML Tidy Overview which is
also included in the package.
These descriptions were extracted from the HTML Tidy documentation and
fall under the HTML Tidy copyright.
The package defines these functions:
The package defines these constants:
If you find any bugs, please report them to me so that
I can fix them for the next release.
HTML Tidy Options
Functions
Constants
Submodules
The package currently does not expose any submodules.
Examples of Use
TBD
This snippet demonstrates some of the possible interactions
of mxTidy types and Python number types:
>>> from mx.Tidy import *
>>> # To be written...
More examples will appear in the Examples subdirectory of the package.
Package Structure
[Tidy]
Doc/
[Examples]
[mxTidy]
libtidy/
test.py
Tidy.py
Names with trailing / are plain directories, ones with []-brackets are Python packages, ones with ".py" extension are Python submodules.
The package imports all symbols from the extension module and also registers the types so that they become compatible to the pickle and copy mechanisms in Python.
eGenix.com is providing commercial support for this
package. If you are interested in receiving information
about this service please see the eGenix.com
Support Conditions.
© 2001, Copyright by eGenix.com Software, Skills and
Services GmbH, Langenfeld, Germany; All Rights Reserved.
mailto: info@egenix.com
The mxTidy software and the modifications to the HTML Tidy
source code are covered by the eGenix.com Public License
Agreement. The text of the license is also included
as file "LICENSE" in the package's main directory.
The included HTML Tidy software is covered by the following
license:
By downloading, copying, installing or otherwise using
the software, you agree to be bound by the terms and
conditions of the eGenix.com
Public License Agreement and the above HTML Tidy
license.
Things that still need to be done:
Things that changed from 0.2.0 to 0.3.0:
Things that changed from 0.1.0 to 0.2.0:
Version 0.1.0 was the first public release.
Support
What I'd like to hear from you...
Copyright & License
Copyright (c) 1998-2000 World Wide Web Consortium
(Massachusetts Institute of Technology, Institut National de
Recherche en Informatique et en Automatique, Keio University).
All Rights Reserved.
Contributing Author(s):
Dave Raggett, dsr@w3.org
The contributing author(s) would like to thank all those who
helped with testing, bug fixes, and patience. This wouldn't
have been possible without all of you.
COPYRIGHT NOTICE:
This software and documentation is provided "as is," and
the copyright holders and contributing author(s) make no
representations or warranties, express or implied, including
but not limited to, warranties of merchantability or fitness
for any particular purpose or that the use of the software or
documentation will not infringe any third party patents,
copyrights, trademarks or other rights.
The copyright holders and contributing author(s) will not be
liable for any direct, indirect, special or consequential damages
arising out of any use of the software or documentation, even if
advised of the possibility of such damage.
Permission is hereby granted to use, copy, modify, and distribute
this source code, or portions hereof, documentation and executables,
for any purpose, without fee, subject to the following restrictions:
1. The origin of this source code must not be misrepresented.
2. Altered versions must be plainly marked as such and must
not be misrepresented as being the original source.
3. This Copyright notice may not be removed or altered from any
source or altered source distribution.
The copyright holders and contributing author(s) specifically
permit, without fee, and encourage the use of this source code
as a component for supporting the Hypertext Markup Language in
commercial products. If you use this source code in a product,
acknowledgment is not required but would be appreciated.
History & Future