1. Shlomi Fish
  2. Website Meta Language

Commits

shl...@7081e830-ea04-0410-ae62-fb6148e2d9db  committed 5dfe6bd

Various fixes and updates to get wml to compile on cygwin. The compiled
wml was tested by rendering the Israeli Welcome-to-Linux site. It worked.

  • Participants
  • Parent commits 6483b4c
  • Branches maintenance

Comments (0)

Files changed (19)

File 2.0.x/src/wml_aux/tidy/tidy.txt

-
-                     icon Clean up your Web pages
-                            with HTML TIDY
-                                   
-   This version 4th August 2000
-   
-   Copyright Š 1998-2000 W3C, see tidy.c for copyright notice.
-   
-     With many thanks to Hewlett Packard for financial support
-     during the development of this software!
-         _________________________________________________
-   
-   How to use Tidy | Downloading Tidy | Release Notes
-   Integration with other Software | Acknowledgements
-         _________________________________________________
-   
-   To get the latest version of Tidy please visit the original
-   version of this page at:
-   http://www.w3.org/People/Raggett/tidy/. Courtesy of Netmind,
-   you can register for email reminders when new versions of tidy
-   become available.
-   
-   Press Here to Register
-   
-   The public email list devoted to HTML Tidy is:
-   <html-tidy@w3.org>. 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.
-   Please use this list to report errors or enhancement requests.
-   See the release notes for information on recent changes. Your
-   feedback is welcome!
-   
-   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.
-   
-  Tutorials for HTML and CSS
-  
-   If you are just starting off and would like to know more about
-   how to author Web pages, you may find my guide to HTML and CSS
-   helpful. Please send me feedback on this, and I will do my
-   best to further improve it.
-   
-    Support for Word2000
-    
-   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 Tidy's "Word-2000"
-   config option! Of course Tidy does a good job on Word'97 files
-   as well!
-   
-  Introduction to TIDY
-  
-   When editing HTML it's easy to make mistakes. Wouldn't 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 Raggett's 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
-   won't generate a cleaned up version when there are problems
-   that it can't be sure of how to handle. These are logged as
-   "errors" rather than "warnings".
-   
-   Tidy features in a recent article on XHTML by webreview.com.
-   
-  Examples of TIDY at work
-  
-   Tidy corrects the markup in a way that matches where possible
-   the observed rendering in popular browsers from Netscape and
-   Microsoft. Here are just a few examples of how TIDY perfects
-   your HTML for you:
-     * Missing or mismatched end tags are detected and corrected
-   <h1>heading
-   <h2>subheading</h3>
-       is mapped to
-   <h1>heading</h1>
-   <h2>subheading</h2>
-     * End tags in the wrong order are corrected:
-   <p>here is a para <b>bold <i>bold italic</b> bold?</i> normal?
-       is mapped to
-   <p>here is a para <b>bold <i>bold italic</i> bold?</b> normal?
-     * Fixes problems with heading emphasis
-   <h1><i>italic heading</h1>
-   <p>new paragraph
-       In Netscape and Internet Explorer this causes everything
-       following the heading to be in the heading font size, not
-       the desired effect at all!
-       Tidy maps the example to
-   <h1><i>italic heading</i></h1>
-   <p>new paragraph
-     * Recovers from mixed up tags
-   <i><h1>heading</h1></i>
-   <p>new paragraph <b>bold text
-   <p>some more bold text
-       Tidy maps this to
-   <h1><i>heading</i></h1>
-   <p>new paragraph <b>bold text</b>
-   <p><b>some more bold text</b>
-     * Getting the <hr> in the right place:
-   <h1><hr>heading</h1>
-   <h2>sub<hr>heading</h2>
-       Tidy maps this to
-   <hr>
-   <h1>heading</h1>
-   <h2>sub</h2>
-   <hr>
-   <h2>heading</h2>
-     * Adding the missing "/" in end tags for anchors:
-   <a href="#refs">References<a>
-       Tidy maps this to
-   <a href="#refs">References</a>
-     * Perfecting lists by putting in tags missed out:
-   <body>
-   <li>1st list item
-   <li>2nd list item
-       is mapped to
-   <body>
-   <ul>
-   <li>1st list item</li>
-   <li>2nd list item</li>
-   </ul>
-     * Missing quotes around attribute values are added
-       Tidy inserts quote marks around all attribute values for
-       you. It can also detect when you have forgotten the
-       closing quote mark, although this is something you will
-       have to fix yourself.
-     * Unknown/Proprietary attributes are reported
-       Tidy has a comprehensive knowledge of the attributes
-       defined in the HTML 4.0 recommendation from W3C. This
-       often allows you to spot where you have mistyped an
-       attribute or value.
-     * Proprietary elements are recognized and reported as such.
-       Tidy will even work out which version of HTML you are
-       using and insert the appropriate DOCTYPE element, as per
-       the W3C recommendations.
-     * Tags lacking a terminating '>' are spotted
-       This is something you then have to fix yourself as Tidy is
-       unsure of where the > should be inserted.
-       
-  Layout style
-  
-   You can choose which style you want Tidy to use when it
-   generates the cleaned up markup: for instance whether you like
-   elements to indent their contents or not. Several people have
-   asked if Tidy could preserve the original layout. I am sorry
-   to say that this would be very hard to support due to the way
-   Tidy is implemented. Tidy starts by building a clean parse
-   tree from the source file. The parse tree doesn't contain any
-   information about the original layout. Tidy then pretty prints
-   the parse tree using the current layout options. Trying to
-   preserve the original layout would interact badly with the
-   repair operations needed to build a clean parse tree and
-   considerably complicate the code.
-   
-   Some browsers can screw up the right alignment of text
-   depending on how you layout headings. As an example, consider:
-<h1 align="right">
-  Heading
-</h1>
-
-<h1 align="right">Heading</h1>
-
-   Both of these should be rendered the same. Sadly a common
-   browser bug fails to trim trailing whitespace and misaligns
-   the first heading. HTML Tidy will protect you from this bug,
-   except when you set the indent option to "yes".
-   
-   Setting the indent option to yes can also cause problems with
-   table layout for some browsers:
-<td><img src="foo.gif"></td>
-<td><img src="foo.gif"></td>
-
-   will look slightly different from:
-<td>
-  <img src="foo.gif">
-</td>
-<td>
-  <img src="foo.gif">
-</td>
-
-   You can avoid such quirks by using indent: no or indent: auto
-   in the config file.
-   
-  Internationalization issues
-  
-   Tidy offers you a choice of character encodings: US ASCII, ISO
-   Latin-1, UTF-8 and the ISO 2022 family of 7 bit encodings. The
-   full set of HTML 4.0 entities are defined. Cleaned up output
-   uses HTML entity names for characters when appropriate.
-   Otherwise characters outside the normal range are output as
-   numeric character entities. Tidy defaults to assuming you want
-   the output to be in US ASCII. Tidy doesn't yet recognize the
-   use of the HTML meta element for specifying the character
-   encoding.
-   
-  Accessibility
-  
-   Tidy offers advice on accessibility problems for people using
-   non-graphical browsers. The most common thing you will see is
-   the suggestion you add a summary attribute to table elements.
-   The idea is to provide a summary of the table's role and
-   structure suitable for use with aural browsers.
-   
-  Cleaning up presentational markup
-  
-   Many tools generate HTML with an excess of FONT, NOBR and
-   CENTER tags. Tidy's -clean option will replace them by style
-   properties and rules using CSS. This makes the markup easier
-   to read and maintain as well as reducing the file size! Tidy
-   is expected to get smarter at this in the future.
-   
-   Some pages rely on the presentation effects of isolated <p> or
-   </p> tags.Tidy deletes empty paragraph and heading elements
-   etc. The use of empty paragraph elements is not recommended
-   for adding vertical whitespace. Instead use style sheets, or
-   the <br> element. Tidy won't discard paragraphs only
-   containing a nonbreaking space &nbsp;
-   
-  Teaching Tidy about new tags!
-  
-   You can teach Tidy about new tags by declaring them in the
-   configuration file, the syntax is:
-  new-inline-tags: tag1, tag2, tag3
-  new-empty-tags: tag1, tag2, tag3
-  new-blocklevel-tags: tag1, tag2, tag3
-  new-pre-tags: tag1, tag2, tag3
-
-   The same tag can be defined as empty and as inline or as empty
-   and as block.
-   
-   These declarations can be combined to define an a new empty
-   inline or empty block element, but you are not advised to
-   declare tags as being both inline and block!
-   
-   Note that the new tags can only appear where Tidy expects
-   inline or block-level tags respectively. This means you can't
-   (yet) place new tags within the document head or other
-   contexts with restricted content models. So far the most
-   popular use of this feature is to allow Tidy to be applied to
-   Cold Fusion files.
-   
-   I am working on ways to make it easy to customize the
-   permitted document syntax using assertion grammars, and hope
-   to apply this to a much smarter version of Tidy for release
-   later this year or early next year.
-   
-  Limited support for ASP, JSTE and PHP
-  
-   Tidy is somewhat aware of the preprocessing language called
-   ASP which uses a pseudo element syntax <% ... %> to include
-   preprocessor directives. ASP is normally interpreted by the
-   web server before delivery to the browser. JSTE shares the
-   same syntax, but sometimes also uses <# ... #>. Tidy can also
-   cope with another such language called PHP, which uses the
-   syntax <?php ... ?>
-   
-   Tidy will cope with ASP, JSTE and PHP pseudo elements within
-   element content and as replacements for attributes, for
-   example:
-  <option <% if rsSchool.Fields("ID").Value
-    = session("sessSchoolID")
-    then Response.Write("selected") %>
-    value='<%=rsSchool.Fields("ID").Value%>'>
-    <%=rsSchool.Fields("Name").Value%>
-    (<%=rsSchool.Fields("ID").Value%>)
-  </option>
-
-   Note that Tidy doesn't understand the scripting language used
-   within pseudo elements and attributes, and can easily get
-   confused. Tidy may report missing attributes when these are
-   hidden within preprocessor code. Tidy can also get things
-   wrong if the code includes quote marks, e.g. if the example
-   above is changed to:
-    value="<%=rsSchool.Fields("ID").Value%>"
-
-   Tidy will now see the quote mark preceding ID as ending the
-   attribute value, and proceed to complain about what follows.
-   Note you can choose whether to allow line wrapping on spaces
-   within pseudo elements or not using the wrap-asp option. If
-   you used ASP, JSTE or PHP to create a start tag, but placed
-   the end tag explicitly in the markup, Tidy won't be able to
-   match them up, and will delete the end tag for you. So in this
-   case you are advise to make the start tag explicit and to use
-   ASP, JSTE or PHP for just the attributes, e.g.
-   <a href="<%=random.site()%>">do you feel lucky?</a>
-
-   Tidy allows you to control whether line wrapping is enabled
-   for ASP, JSTE and PHP instructions, see the wrap-asp,
-   wrap-jste and wrap-php config options, respectively.
-   
-   I regret that Tidy does not support Tango preprocessing
-   instructions which look like:
-<@if variable_1='a'>
-    do something
-<@else>
-    do nothing
-</@if>
-
-<@include <@cgi><@appfilepath>includes/message.html>
-
-   Tidy supports another preprocessing syntax called "Tango", but
-   only for attribute values. Adding support for pseudo elements
-   written in Tango looks as if it would be quite tough, so I
-   would like to gauge the level of interest before committing to
-   this work.
-   
-  Limited support for XML
-  
-   XML processors compliant with W3C's XML 1.0 recommendation are
-   very picky about which files they will accept. Tidy can help
-   you to fix errors that cause your XML files to be rejected.
-   Tidy doesn't yet recognize all XML features though, e.g. it
-   doesn't understand CDATA sections or DTD subsets.
-   
-  Creating Slides
-  
-   The -slides option allows you to burst a single HTML file into
-   a number of linked slides. Each H2 element in the input file
-   is treated as delimiting the start of the next slide. The
-   slides are named slide1.html, slide2.html, slide3.html etc.
-   This is a relatively new feature and ideas are welcomed as to
-   how to improve it. In particular, I plan to add support to the
-   configuration file for setting the style sheet for slides and
-   for customizing the slides via a template.
-   
-   I would be interested in hearing from anyone who can offer
-   help with using JavaScript for adding dynamic effects to
-   slides, for instance similar to those available in Microsoft
-   PowerPoint.
-   
-  Indenting text for a better layout
-  
-   Indenting the content of elements makes the markup easier to
-   read. Tidy can do this for all elements or just for those
-   where it's needed. The auto-indent mode has been used below to
-   avoid indenting the content of title, p and li elements:
-<html>
-  <head>
-    <title>Test document</title>
-  </head>
-
-  <body>
-    <p>para which has enough text to cause a line break,
-    and so test the wrapping mechanism for long lines.</p>
-<pre>
-This is
-<em>genuine
-       preformatted</em>
-   text
-</pre>
-
-    <ul>
-      <li>1st list item</li>
-
-      <li>2nd list item</li>
-    </ul>
-    <!-- end comment -->
-  </body>
-</html>
-
-   Indenting the content does increase the size of the file, so
-   you may prefer Tidy's default style:
- <html>
- <head>
- <title>Test document</title>
- </head>
- <body>
- <p>para which has enough text to cause a line break,
- and so test the wrapping mechanism for long lines.</p>
-
- <pre>This is
- <em>genuine
-       preformatted</em>
-    text
- </pre>
-
- <ul>
- <li>1st list item </li>
-
- <li>2nd list item</li>
- </ul>
-
- <!-- end comment -->
- </body>
- </html>
-
-  How to run tidy
-  
-   tidy [[options] filename]*
-
-   HTML tidy is not (yet) a Windows program. If you run tidy
-   without any arguments, it will just sit there waiting to read
-   markup on the stdin stream. Tidy's input and output default to
-   stdin and stdout respectively. Errors are written to stderr
-   but can be redirected to a file with the -f filename option.
-   
-   I generally use the -m option to get tidy to update the
-   original file, and if the file is particularly bad I also use
-   the -f option to write the errors to a file to make it easier
-   to review them. Tidy supports a small set of character
-   encoding options. The default is ASCII, which makes it easy to
-   edit markup in regular text editors.
-   
-   For instance:
-   tidy -f errs.txt -m index.html
-
-   which runs tidy on the file "index.html" updating it in place
-   and writing the error messages to the file "errs.txt". Its a
-   good idea to save your work before tidying it, as with all
-   complex software, tidy may have bugs. If you find any please
-   let me know!
-   
-   Thanks to Jacek Niedziela, The Win32 executable for tidy is
-   now able to example wild cards in filenames. This utilizes the
-   setargv library supplied with VC++.
-   
-   Tidy writes errors to stderr, and won't be paused by the more
-   command. A work around is to redirect stderr to stdout as
-   follows. This works on Unix and Windows NT, but not on other
-   platforms. My thanks to Markus Wolf for this tip!
-   tidy file.html 2>&1 | more
-
-    Tidy's Options
-    
-   To get a list of available options use:
-   tidy -help
-
-   You may want to run it through more to view the help a page at
-   a time.
-   tidy -help | more
-
-   Input and Output default to stdin/stdout respectively. Single
-   letter options apart from -f may be combined as in: tidy -f
-   errs.txt -imu foo.html
-   
-   Matej Vela <vela@debian.org> has written a Unix man page for
-   Tidy, but for the latest details on config options and for the
-   release notes please visit this page:
-   http://www.w3.org/People/Raggett/tidy.
-   
-  Using a Configuration File
-  
-   Tidy now supports a configuration file, and this is now much
-   the most convenient way to configure Tidy. Assuming you have
-   created a config file named "config.txt" (the name doesn't
-   matter), you can instruct Tidy to use it via the command line
-   option -config config.txt, e.g.
-   tidy -config config.txt file1.html file2.html
-
-   Alternatively, you can name the default config file via the
-   environment variable named "HTML_TIDY". Note this should be
-   the absolute path since you are likely to want to run Tidy in
-   different directories. You can also set a config file at
-   compile time by defining CONFIG_FILE as the path string, see
-   platform.h.
-   
-   You can now set config options on the command line by
-   preceding the name of the option immediately (no intervening
-   space) by "--", for example:
-  tidy --break-before-br true --show-warnings false
-
-   The following options are supported:
-   
-   tidy-mark: bool
-          If set to yes (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 no. Tidy won't add a meta element if one
-          is already present.
-          
-   markup: bool
-          Determines whether Tidy generates a pretty printed
-          version of the markup. Bool values are either yes or
-          no. Note that Tidy won't generate a pretty printed
-          version if it finds unknown tags, or missing trailing
-          quotes on attribute values, or missing trailing '>' on
-          tags. The default is yes.
-          
-   wrap: number
-          Sets the right margin for line wrapping. Tidy tries to
-          wrap lines so that they do not exceed this length. The
-          default is 66. Set wrap to zero if you want to disable
-          line wrapping.
-          
-   wrap-attributes: bool
-          If set to yes, attribute values may be wrapped across
-          lines for easier editing. The default is no. This
-          option can be set independently of wrap-scriptlets
-          
-   wrap-script-literals: bool
-          If set to yes, this allows lines to be wrapped within
-          string literals that appear in script attributes. The
-          default is no. The example shows how Tidy wraps a
-          really really long script string literal inserting a
-          backslash character before the linebreak:
-          
-<a href="somewhere.html" onmouseover="document.status = '...some \
-really, really, really, really, really, really, really, really, \
-really, really long string..';">test</a>
-
-   wrap-asp: bool
-          If set to no, this prevents lines from being wrapped
-          within ASP pseudo elements, which look like: <% ... %>.
-          The default is yes.
-          
-   wrap-jste: bool
-          If set to no, this prevents lines from being wrapped
-          within JSTE pseudo elements, which look like:
-          <# ... #>. The default is yes.
-          
-   wrap-php: bool
-          If set to no, this prevents lines from being wrapped
-          within PHP pseudo elements. The default is yes.
-          
-   literal-attributes: bool
-          If set to yes, this ensures that whitespace characters
-          within attribute values are passed through unchanged.
-          The default is no.
-          
-   tab-size: number
-          Sets the number of columns between successive tab
-          stops. The default is 4. It is used to map tabs to
-          spaces when reading files. Tidy never outputs files
-          with tabs.
-          
-   indent: no, yes or auto
-          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.
-          
-   indent-spaces: number
-          Sets the number of spaces to indent content when
-          indentation is enabled. The default is 2 spaces.
-          
-   indent-attributes: bool
-          If set to yes, each attribute will begin on a new line.
-          The default is no.
-          
-   hide-endtags: bool
-          If set to yes, 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
-          no.
-          
-   input-xml: bool
-          If set to yes, Tidy will use the XML parser rather than
-          the error correcting HTML parser. The default is no.
-          
-   output-xml: bool
-          If set to yes, 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 no.
-          
-   add-xml-pi: bool
-   add-xml-decl: bool
-          If set to yes, Tidy will add the XML declatation when
-          outputting XML or XHTML. The default is no. Note that
-          if the input document includes an <?xml?> declaration
-          then it will appear in the output independent of the
-          value of this option.
-          
-   output-xhtml: bool
-          If set to yes, Tidy will generate the pretty printed
-          output writing it as extensible HTML. The default is
-          no. 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.
-          
-   doctype: omit, auto, strict, loose or <fpi>
-          This property controls the doctype declaration
-          generated by Tidy. If set to omit the output file won't
-          contain a doctype declaration. If set to auto (the
-          default) Tidy will use an educated guess based upon the
-          contents of the document. If set to strict, Tidy will
-          set the doctype to the strict DTD. If set to loose, the
-          doctype is set to the loose (transitional) DTD.
-          Alternatively, you can supply a string for the formal
-          public identifier (fpi) for example:
-          
-    doctype: "-//ACME//DTD HTML 3.14159//EN"
-
-          If you specify the fpi for an XHTML document, Tidy will
-          set the system identifier to the empty string. Tidy
-          leaves the document type for generic XML documents
-          unchanged.
-          
-   char-encoding: raw, ascii, latin1, utf8 or iso2022
-          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.
-          
-   numeric-entities: bool
-          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 no
-          
-   quote-marks: bool
-          If set to yes, this causes " characters to be written
-          out as &quot; as is preferred by some editing
-          environments. The apostrophe character ' is written out
-          as &#39; since many web browsers don't yet support
-          &apos;. The default is no.
-          
-   quote-nbsp: bool
-          If set to yes, this causes non-breaking space
-          characters to be written out as entities, rather than
-          as the Unicode character value 160 (decimal). The
-          default is yes.
-          
-   quote-ampersand: bool
-          If set to yes, this causes unadorned & characters to be
-          written out as &amp;. The default is yes.
-          
-   assume-xml-procins: bool
-          If set to yes, this changes the parsing of processing
-          instructions to require ?> as the terminator rather
-          than >. The default is no. This option is automatically
-          set if the input is in XML.
-          
-   fix-backslash: bool
-          If set to yes, this causes backslash characters "\" in
-          URLs to be replaced by forward slashes "/". The default
-          is yes.
-          
-   break-before-br: bool
-          If set to yes, Tidy will output a line break before
-          each <br> element. The default is no.
-          
-   uppercase-tags: bool
-          Causes tag names to be output in upper case. The
-          default is no resulting in lowercase, except for XML
-          input where the original case is preserved.
-          
-   uppercase-attributes: bool
-          If set to yes attribute names are output in upper case.
-          The default is no resulting in lowercase, except for
-          XML where the original case is preserved.
-          
-   word-2000: bool
-          If set to yes, 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
-          no. Note that Tidy doesn't yet know what to do with VML
-          markup from Word, but in future I hope to be able to
-          map VML to SVG.
-          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.
-          
-   clean: bool
-          If set to yes, 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 no.
-          
-   logical-emphasis: bool
-          If set to yes, 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 no. This option can now be set independently
-          of the clean and drop-font-tags options.
-          
-   drop-empty-paras: bool
-          If set to yes, empty paragraphs will be discarded. If
-          set to no, empty paragraphs are replaced by a pair of
-          br elements as HTML4 precludes empty paragraphs. The
-          default is yes.
-          
-   drop-font-tags: bool
-          If set to yes together with the clean option (see
-          above), Tidy will discard font and center tags rather
-          than creating the corresponding style rules. The
-          default is no.
-          
-   enclose-text: bool
-          If set to yes, this causes Tidy to enclose any text it
-          finds in the body element within a p element. This is
-          useful when you want to take an existing html file and
-          use it with a style sheet. Any text at the body level
-          will screw up the margins, but wrap the text within a p
-          element and all is well! The default is no.
-          
-   enclose-block-text: bool
-          If set to yes, 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 no.
-          
-   fix-bad-comments: bool
-          If set to yes, this causes Tidy to replace unexpected
-          hyphens with "=" characters when it comes across
-          adjacent hyphens. The default is yes. This option is
-          provided for users of Cold Fusion which uses the
-          comment syntax: <!--- --->
-          
-   add-xml-space: bool
-          If set to yes, 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 no.
-          
-   alt-text: string
-          This allows you to set the default alt text for img
-          attributes. This feature is dangerous as it suppresses
-          further accessibility warnings. YOU ARE RESPONSIBLE FOR
-          MAKING YOUR DOCUMENTS ACCESSIBLE TO PEOPLE WHO CAN'T
-          SEE THE IMAGES!!!
-          
-   write-back: bool
-          If set to yes, Tidy will write back the tidied markup
-          to the same file it read from. The default is no. You
-          are advised to keep copies of important files before
-          tidying them as on rare occasions the result may not
-          always be what you expect.
-          
-   keep-time: bool
-          If set to yes, Tidy won't alter the last modified time
-          for files it writes back to. The default is yes. This
-          allows you to tidy files without effecting which ones
-          will be uploaded to the Web server when using a tool
-          such as 'SiteCopy'. Note that this feature may not work
-          on some platforms.
-          
-   error-file: filename
-          Writes errors and warnings to the named file rather
-          than to stderr.
-          
-   show-warnings: bool
-          If set to no, warnings are suppressed. This can be
-          useful when a few errors are hidden in a flurry of
-          warnings. The default is yes.
-          
-   quiet: bool
-          If set to yes, Tidy won't output the welcome message or
-          the summary of the numbers of errors and warnings. The
-          default is no.
-          
-   gnu-emacs: bool
-          If set to yes, Tidy changes the format for reporting
-          errors and warnings to a format that is more easily
-          parsed by GNU Emacs. The default is no.
-          
-   split: bool
-          If set to yes Tidy will use the input file to create a
-          sequence of slides, splitting the markup prior to each
-          successive <h2>. You can see an example of the results
-          in a recent talk I made on XHTML. The slides are
-          written to "slide1.html", "slide2.html" etc. The
-          default is no.
-          
-   new-empty-tags: tag1, tag2, tag3
-          Use this to declare new empty inline tags. The option
-          takes a space or comma separated list of tag names.
-          Unless you declare new tags, Tidy will refuse to
-          generate a tidied file if the input includes previously
-          unknown tags. Remember to also declare empty tags as
-          either inline or blocklevel, see below.
-          
-   new-inline-tags: tag1, tag2, tag3
-          Use this to declare new non-empty inline tags. The
-          option takes a space or comma separated list of tag
-          names. Unless you declare new tags, Tidy will refuse to
-          generate a tidied file if the input includes previously
-          unknown tags.
-          
-   new-blocklevel-tags: tag1, tag2, tag3
-          Use this to declare new block-level tags. The option
-          takes a space or comma separated list of tag names.
-          Unless you declare new tags, Tidy will refuse to
-          generate a tidied file if the input includes previously
-          unknown tags. Note you can't change the content model
-          for elements such as table, ul, ol and dl. This is
-          explained in more detail in the release notes.
-          
-   new-pre-tags: tag1, tag2, tag3
-          Use this to declare new tags that are to be processed
-          in exactly the same way as HTML's pre element. The
-          option takes a space or comma separated list of tag
-          names. Unless you declare new tags, Tidy will refuse to
-          generate a tidied file if the input includes previously
-          unknown tags. Note you can't as yet add new CDATA
-          elements (similar to script).
-          
-    Sample Config File
-    
-   This is just an example to get you started.
-// sample config file for HTML tidy
-indent: auto
-indent-spaces: 2
-wrap: 72
-markup: yes
-output-xml: no
-input-xml: no
-show-warnings: yes
-numeric-entities: yes
-quote-marks: yes
-quote-nbsp: yes
-quote-ampersand: no
-break-before-br: no
-uppercase-tags: no
-uppercase-attributes: no
-char-encoding: latin1
-new-inline-tags: cfif, cfelse, math, mroot,
-  mrow, mi, mn, mo, msqrt, mfrac, msubsup, munderover,
-  munder, mover, mmultiscripts, msup, msub, mtext,
-  mprescripts, mtable, mtr, mtd, mth
-new-blocklevel-tags: cfoutput, cfquery
-new-empty-tags: cfelse
-
-  Using Tidy from scripts
-  
-   If you want to run Tidy from a Perl or other scripting
-   language you may find it of value to inspect the result
-   returned by Tidy when it exits: 0 if everything is fine, 1 if
-   there were warnings and 2 if there were errors. This is an
-   example using Perl:
-if (close(TIDY) == 0) {
-  my $exitcode = $? >> 8;
-  if ($exitcode == 1) {
-    printf STDERR "tidy issued warning messages\n";
-  } elsif ($exitcode == 2) {
-    printf STDERR "tidy issued error messages\n";
-  } else {
-    die "tidy exited with code: $exitcode\n";
-  }
-} else {
-  printf STDERR "tidy detected no errors\n";
-}
-
-  Downloadable Binaries
-  
-   If you are prepared to maintain a public URL for HTML Tidy
-   compiled for a specific platform, please let me know so that I
-   can add a link to your page. This will avoid the need for me
-   to update this page whenever you recompile.
-   
-Windows 95/98/NT/2000
-
-   tidy.exe. Windows 95/98/NT/2000 executable (32-bit Windows
-   console-mode program). This is the executable that I maintain
-   as part of the HTML Tidy distribution. The command line
-   parameters are described above, along with the extensive
-   configuration file options.
-   
-   HTML-Kit - a free HTML editor for Windows 95/98/NT/2000 with
-   integrated support for Tidy.
-   
-   TidyGUI. Windows front end for running Tidy, written by André
-   Blavier. André has also written a Windows COM wrapper for
-   Tidy. He describes how to use this from Visual Basic.
-   
-   Evrsoft's 1st Page 2000 - a free HTML editor for Windows
-   95/98/NT/2000 with integrated support for Tidy. 1st Page 2000
-   is a high-end authoring tool that makes it easy to add effects
-   based upon scripting.
-   
-   NoteTab - an award winning text and html editor for Windows
-   with built-in support for running HTML Tidy. NoteTab is
-   written by Eric Fookes.
-   
-Mac OS
-
-   Several versions of HTML Tidy for Mac OS are available,
-   including a standalone Macintosh application with a graphical
-   user interface, a BBEdit plugin, a MPW tool, or as a FilterTop
-   filter ( Screenshot). My thanks to Terry Teague for this port.
-   
-Atari
-
-   Arnaud Bercegeay's site for the Atari binary for Tidy.
-   
-Amiga
-
-   Keith Blakemore-Noble maintains a page for Tidy on Amiga.
-   
-BeOS
-
-   Peter Enzerink is maintaining HTML Tidy for BeOS. Link points
-   to download for HTML Tidy as well as HTML Tidy editor addons
-   for BeOS.
-   
-AIX
-
-   Ciaran Deignan maintains an AIX binary for Tidy. The link is
-   to a general download page. The executable is available for
-   AIX 4.3.2 and later.
-   
-Linux
-
-   Dimitri Papadopoulos maintains a Tidy RPM package for Redhat
-   Linux You may also be able to find Tidy on other Linux
-   distribution sites, e.g. http://rpmfind.net/.
-   
-UnixWare
-
-   Simon Trimmer <simon@ocston.org> maintains a Tidy binary for
-   Unixware.
-   
-HP-UX
-
-   You can get precompiled versions of Tidy for HPUX, from Olaf
-   Hopp, and from Ian Springer.
-   
-MSDOS
-
-   Nick B. maintains Tidy386 for DOS. This exploits the DPMI
-   mechanism for the memory management.
-   
-Solaris
-
-   Stephen Fuqua maintains a page for Tidy on Solaris.
-   
-OS/2
-
-   Kaz SHiMZ <kshimz@sfc.co.jp> maintains an OS/2 binary for
-   Tidy.
-   
-FreeBSD
-
-   Martin Fouts maintains Tidy on FreeBSD.
-   
-RISC OS
-
-   Alex Macfarlane Smith maintains a port of Tidy to the RISC OS.
-   
-MiNT (Atari) OS
-
-   Edgar Aichinger maintains a port of Tidy to the MiNT OS. MiNT
-   is a UNIX for m68k Atari computers and is nearly FHS compliant
-   (we don't use bootable OS images nor have any mounting
-   capabilities, so neither /boot nor /mnt are used). The binary
-   also runs on ordinary TOS, since the MiNT libraries cover all
-   GEMDOS/GEM functions.
-   
-  Integrating Tidy as part of other Software
-  
-   You can also incorporate Tidy as part of a larger program, for
-   instance in HTML editors or HTML transformation tools used for
-   import filters, or for when you want to customize Web content
-   to get the best out of different kinds of browsers. Imagine
-   authoring clean HTML with CSS and at a touch of a button
-   producing variants that look great and work reliably on a
-   large variety of different browsers, taking into account the
-   quirks of each. For instance, providing the ability to tune
-   content for different versions of Netscape and Internet
-   Explorer, and for browsers running on set-top boxes for
-   televisions, handheld and palmtop devices, cell phones, and
-   voice browsers. I am happy to quote for software development
-   for such tools.
-   
-   Sebastian Lange has contributed a perl wrapper for calling
-   Tidy from your perl scripts, see sl-tidy.pl.
-   
-    Using Tidy from emacs
-    
-   Pete Gelbman emailed this tip for using Tidy with the Unix
-   version of emacs. lets you highlight a region of text and run
-   Tidy on it. Tidy's "fixed" output will replace your
-   highlighted region right in place. The error/warnings output
-   will be directed into a separate mini-buffer below in your
-   main screen.
-   
-  Java port of HTML Tidy
-  
-   Andy Quick <ac.quick@sympatico.ca> maintains a Java port of
-   Tidy, so you can now integrate Tidy into your Java
-   applications. Andy is tracking the releases of Tidy in C (this
-   page). More information is available on Andy's home page.
-   
-  Source Code
-  
-   The code is in ANSI C and uses the C standard library for i/o.
-   The parser works top down, building a complete parse tree in
-   memory. Document text is held as Unicode represented as UTF-8
-   in a character buffer that expands as needed. The code has so
-   far been tested on Windows'95, Windows'98, Windows NT, Windows
-   2000, Linux, FreeBSD, NetBSD, Ultrix, OSF, OS/MP, IRIX,
-   NeXtStep, MacOS, BeOS, OS/2, AIX, Amiga, Atari, SunOS,
-   Solaris, IRIX and HP-UX, amongst others.
-   
-   Here is a link to the Open Source copyright notice and
-   license.
-   
-   tidy4aug00.tgz
-          gzipped tar file for source code (Unix line ends)
-          
-   tidy4aug00.zip
-          zipped source code (Windows line ends)
-          
-   platform.h, html.h
-          the include files with common definitions
-          
-   config.c
-          support for customizing Tidy via config files
-          
-   lexer.c
-          lexical analysis and buffer management
-          
-   parser.c
-          HTML and XML parsers
-          
-   tags.c
-          dictionary of tags and their properties
-          
-   attrs.c
-          dictionary of attributes and their properties
-          
-   istack.c
-          stack of active inline elements
-          
-   entities.c
-          dictionary of entities
-          
-   clean.c
-          smarts for cleaning up presentational markup
-          
-   pprint.c
-          pretty printing for HTML and XML
-          
-   localize.c
-          Change this file to localize tidy's messages
-          
-   tidy.c
-          main() and error reporting routines
-          
-   Makefile
-          Makefile for gcc
-          
-   Unix Man page
-          Maintained by Matej Vela <vela@debian.org>
-          
-   Conventions for whether lines end with CRLF, LF or CR vary
-   from one system to another. I have included the C source for a
-   utility tab2space which can be used to ensure that files use
-   the line end convention of your choice, and to expand tabs to
-   spaces.
-   tab2space -t4 -unix *.h *.c
-   tab2space -tabs -unix Makefile
-
-   Note use of "-tabs" to ensure that tabs are preserved in the
-   Makefile (it won't work without them!).
-   
-   For those of you on Unix, here is a script you can use to
-   strip carriage returns:
-#!/bin/sh
-echo Stripping Carriage Returns from files...
-for i
-do
-        # If a writable file
-        if [ -f $i ]
-        then
-                if [ -w $i ]
-                then
-                        echo $i
-                        # strip CRs from input and output to temp file
-                        tr -d '\015' < $i > toix.tmp
-                        mv toix.tmp $i
-                else
-                        echo $i: write-protected
-                fi
-        else
-                echo $i: not a file
-        fi
-done
-
-   Save this script to a file, e.g. "scripcr" and use "chmod +x
-   stripcr" to make it executable. You can then run it as
-   "stripcr *.c *.h Overview.html Makefile"
-   
-Acknowledgements
-
-   I would like to thank the many people who have written to me
-   with suggestions for improvements or reporting bugs. Your help
-   has been invaluable.
-   
-     Jonathan Adair, Drew Adams, Osma Ahvenlampi, Carsten
-     Allefeld, Richard Allsebrook, Jacob Sparre Andersen, Joe
-     D'Andrea, Jerry Andrews, Bruce Aron, Takuya Asada, Edward
-     Avis, Carlos Piqueres Ayela, Nick B, Chang Hyun Baek, Nick
-     B, Denis Barbier, Chuck Baslock, Christer Bernerus, David
-     J. Biesack, John Bigby, Yu Jian Bin, Alexander Biron, Keith
-     Blakemore-Noble, Eric Blossom, Berend de Boer, Ochen M.
-     Braun, Dave Bryan, David Brooke, Andy Brown, Keith B.
-     Brown, Andreas Buchholz, Maurice Buxton, Jelks Cabaniss,
-     John Cappelletti, Trevor Carden, Terry Cassidy, Mathew
-     Cepl, Kendall Clark, Rob Clark, Jeremy Clulow, Dan
-     Connolly, Larry Cousin, Ken Cox, Luis M. Cruz, John
-     Cumming, Ian Davey, Keith Davies, Ciaran Deignan, David
-     Duffy, Emma Duke-Williams, Tamminen Eero, Bodo Eing, Peter
-     Enzerink, Baruch Even, David Fallon, Claus André Färber,
-     Stephanie Foott, Darren Forcier, Martin Fouts, Frederik
-     Fouvry, Rene Fritz, Stephen Fuqua, Martin Gallwey, Pete
-     Gelbman, Francisco Guardiola, David Getchell, Michael
-     Giroux, Davor Golek, Guus Goos, Léa Gris, Rainer Gutsche,
-     Kai Hackemesser, Juha Häikiö, David Halliday,
-     Johann-Christian Hanke, Vlad Harchev, Shane Harrelson,
-     Andre Hinrichs, Bjoern Hoehrmann, G. Ken Holman, Bill
-     Homer, Olaf Hopp, Craig Horman, Jack Horsfield, Nigel
-     Horspool, Pao-Hsi Huang, Stuart Hungerford, Marc Jauvin,
-     Rick Jelliffe, Peter Jeremy, Craig Johnson, Charles
-     LaFountain, Steven Lobo, Zdenek Kabelac, Michael Kay,
-     Jeffery Kendall, Axel Kielhorn, Konstantinos Kleisouris,
-     Johannes Koch, Daniel Kohn, Rudy Kohut, Allan Kuchinsky,
-     Volker Kuhlmann, Michael LaStella, Johnny Lee, Steve Lee,
-     Tony Leneis, Nick Leverton, Todd Lewis, Dietmar Lippold,
-     Gert-Jan C. Lokhorst, Murray Longmore, John Love-Jensen,
-     Satwinder Mangat, Carole Mah, Anton Marsden, Bede McCall,
-     Shane McCarron, Thomas McGuigan, Ian McKellar, Al Medeiros,
-     Chris Nappin, Ann Navarro, Jacek Niedziela, Morten
-     Blinksbjerg Nielsen, Kenichi Numata, Allan Odgaard, Matt
-     Oshry, Gerald Oskoboiny, Paul Ossenbruggen, Ernst Paalvast,
-     Christian Pantel, Dimitri Papadopoulos, Rick Parsons,
-     Steven Pemberton, Daniel Persson, Lee Anne Phillips, Xavier
-     Plantefeve, Karl Prinz, Andy Quick, Jany Quintard, Julian
-     Reschke, Stephen Reynolds, Thomas Ribbrock, Ross L.
-     Richardson, Philip Riebold, Erik Rossen, Dan Rudman, Peter
-     Ruevski, Christian Ruetgers, Klaus Johannes Rusch, John
-     Russell, Eric Schindler, J. Schlauch, Christian Schüler,
-     Klaus Alexander Seistrup, Jim Seymour, Kazuyoshi Shimizu,
-     Geoff Sinclair, Jo Smith, Paul Smith, Steve Spilker, Rafi
-     Stern, Jacques Steyn, Michael J. Suzio, Zac Thompson, Eric
-     Thorbjornsen, Oren Tirosh, John Tobler, Omri Traub, Loďc
-     Trégan, Jason Tribbeck, Simon Trimmer, Steffen Ullrich,
-     Stuart Updegrave, Charles A. Upsdell, Jussi Vestman, Larry
-     W. Virden, Daniel Vogelheim, Nigel Wadsworth, Jez Wain,
-     Randy Waki, Paul Ward, Neil Weber, Bertilo Wennergren,
-     Yudong Yang, Jeff Young, Edward Zalta, Johannes Zellner,
-     Christian Zuckschwerdt
-     
-  Dave's Address
-  
-    73b Ground Corner
-    Holt
-    Wiltshire
-    BA14 6RT
-    United Kingdom
-
-   Dave Raggett <dsr@w3.org> is an engineer from Hewlett
-   Packard's UK Laboratories, and works on assignment to the
-   World Wide Web Consortium, where he is the W3C lead for HTML,
-   XForms and Voice Browsers and Math.

File 2.0.x/src/wml_backend/p2_mp4h/Makefile.in

-# Makefile.in generated by automake 1.6.3 from Makefile.am.
-# @configure_input@
-
-# Copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002
-# Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-@SET_MAKE@
-SHELL = @SHELL@
-
-srcdir = @srcdir@
-top_srcdir = @top_srcdir@
-VPATH = @srcdir@
-prefix = @prefix@
-exec_prefix = @exec_prefix@
-
-bindir = @bindir@
-sbindir = @sbindir@
-libexecdir = @libexecdir@
-datadir = @datadir@
-sysconfdir = @sysconfdir@
-sharedstatedir = @sharedstatedir@
-localstatedir = @localstatedir@
-libdir = @libdir@
-infodir = @infodir@
-mandir = @mandir@
-includedir = @includedir@
-oldincludedir = /usr/include
-pkgdatadir = $(datadir)/@PACKAGE@
-pkglibdir = $(libdir)/@PACKAGE@
-pkgincludedir = $(includedir)/@PACKAGE@
-top_builddir = .
-
-ACLOCAL = @ACLOCAL@
-AUTOCONF = @AUTOCONF@
-AUTOMAKE = @AUTOMAKE@
-AUTOHEADER = @AUTOHEADER@
-
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-INSTALL = @INSTALL@
-INSTALL_PROGRAM = @INSTALL_PROGRAM@
-INSTALL_DATA = @INSTALL_DATA@
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_SCRIPT = @INSTALL_SCRIPT@
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = @program_transform_name@
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-host_alias = @host_alias@
-host_triplet = @host@
-
-EXEEXT = @EXEEXT@
-OBJEXT = @OBJEXT@
-PATH_SEPARATOR = @PATH_SEPARATOR@
-AMTAR = @AMTAR@
-AS = @AS@
-AWK = @AWK@
-BUILD_INCLUDED_LIBINTL = @BUILD_INCLUDED_LIBINTL@
-CATOBJEXT = @CATOBJEXT@
-CC = @CC@
-CFLAGS = @CFLAGS@
-CPP = @CPP@
-DATADIRNAME = @DATADIRNAME@
-DEPDIR = @DEPDIR@
-DLLDFLAGS = @DLLDFLAGS@
-DLLTOOL = @DLLTOOL@
-ECHO = @ECHO@
-GENCAT = @GENCAT@
-GLIBC21 = @GLIBC21@
-GMSGFMT = @GMSGFMT@
-HAVE_LIB = @HAVE_LIB@
-INCLTDL = @INCLTDL@
-INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
-INSTOBJEXT = @INSTOBJEXT@
-INTLBISON = @INTLBISON@
-INTLINCL = @INTLINCL@
-INTLLIBS = @INTLLIBS@
-INTLOBJS = @INTLOBJS@
-INTL_LIBTOOL_SUFFIX_PREFIX = @INTL_LIBTOOL_SUFFIX_PREFIX@
-LIB = @LIB@
-LIBADD_DL = @LIBADD_DL@
-LIBICONV = @LIBICONV@
-LIBINTL = @LIBINTL@
-LIBLTDL = @LIBLTDL@
-LIBTOOL = @LIBTOOL@
-LN_S = @LN_S@
-LTLIB = @LTLIB@
-LTLIBICONV = @LTLIBICONV@
-LTLIBINTL = @LTLIBINTL@
-MAINT = @MAINT@
-MKINSTALLDIRS = @MKINSTALLDIRS@
-OBJDUMP = @OBJDUMP@
-PACKAGE = @PACKAGE@
-PACKAGE_DATE = @PACKAGE_DATE@
-POSUB = @POSUB@
-RANLIB = @RANLIB@
-STRIP = @STRIP@
-TIDY = @TIDY@
-U = @U@
-USE_INCLUDED_LIBINTL = @USE_INCLUDED_LIBINTL@
-USE_NLS = @USE_NLS@
-VERSION = @VERSION@
-am__include = @am__include@
-am__quote = @am__quote@
-install_sh = @install_sh@
-
-AUTOMAKE_OPTIONS = foreign
-
-DIST_SUBDIRS = intl pcre lib src po doc modules tests
-
-@LOADABLE_MODULES_TRUE@SUBDIRS = intl pcre lib src po doc modules tests
-@LOADABLE_MODULES_FALSE@SUBDIRS = intl pcre lib src po doc tests
-
-EXTRA_DIST = CREDITS README README.pcre bootstrap.sh shtool
-subdir = .
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
-CONFIG_HEADER = config.h
-CONFIG_CLEAN_FILES = intl/Makefile
-DIST_SOURCES =
-
-RECURSIVE_TARGETS = info-recursive dvi-recursive install-info-recursive \
-	uninstall-info-recursive all-recursive install-data-recursive \
-	install-exec-recursive installdirs-recursive install-recursive \
-	uninstall-recursive check-recursive installcheck-recursive
-DIST_COMMON = README ABOUT-NLS COPYING ChangeLog INSTALL Makefile.am \
-	Makefile.in acconfig.h acinclude.m4 aclocal.m4 config.guess \
-	config.h.in config.rpath config.sub configure configure.ac \
-	depcomp install-sh ltmain.sh missing mkinstalldirs
-all: config.h
-	$(MAKE) $(AM_MAKEFLAGS) all-recursive
-
-.SUFFIXES:
-
-am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
- configure.lineno
-$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am  $(top_srcdir)/configure.ac $(ACLOCAL_M4)
-	cd $(top_srcdir) && \
-	  $(AUTOMAKE) --foreign  Makefile
-Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in  $(top_builddir)/config.status
-	cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)
-
-$(top_builddir)/config.status: $(srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
-	$(SHELL) ./config.status --recheck
-$(srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(srcdir)/configure.ac $(ACLOCAL_M4) $(CONFIGURE_DEPENDENCIES)
-	cd $(srcdir) && $(AUTOCONF)
-
-$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.ac acinclude.m4
-	cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
-
-config.h: stamp-h1
-	@if test ! -f $@; then \
-	  rm -f stamp-h1; \
-	  $(MAKE) stamp-h1; \
-	else :; fi
-
-stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status
-	@rm -f stamp-h1
-	cd $(top_builddir) && $(SHELL) ./config.status config.h
-
-$(srcdir)/config.h.in: @MAINTAINER_MODE_TRUE@ $(top_srcdir)/configure.ac $(ACLOCAL_M4) $(top_srcdir)/acconfig.h
-	cd $(top_srcdir) && $(AUTOHEADER)
-	touch $(srcdir)/config.h.in
-
-distclean-hdr:
-	-rm -f config.h stamp-h1
-intl/Makefile: $(top_builddir)/config.status $(top_srcdir)/intl/Makefile.in
-	cd $(top_builddir) && $(SHELL) ./config.status $@
-
-mostlyclean-libtool:
-	-rm -f *.lo
-
-clean-libtool:
-	-rm -rf .libs _libs
-
-distclean-libtool:
-	-rm -f libtool
-uninstall-info-am:
-
-# This directory's subdirectories are mostly independent; you can cd
-# into them and run `make' without going through this Makefile.
-# To change the values of `make' variables: instead of editing Makefiles,
-# (1) if the variable is set in `config.status', edit `config.status'
-#     (which will cause the Makefiles to be regenerated when you run `make');
-# (2) otherwise, pass the desired values on the `make' command line.
-$(RECURSIVE_TARGETS):
-	@set fnord $$MAKEFLAGS; amf=$$2; \
-	dot_seen=no; \
-	target=`echo $@ | sed s/-recursive//`; \
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  echo "Making $$target in $$subdir"; \
-	  if test "$$subdir" = "."; then \
-	    dot_seen=yes; \
-	    local_target="$$target-am"; \
-	  else \
-	    local_target="$$target"; \
-	  fi; \
-	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
-	   || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
-	done; \
-	if test "$$dot_seen" = "no"; then \
-	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
-	fi; test -z "$$fail"
-
-mostlyclean-recursive clean-recursive distclean-recursive \
-maintainer-clean-recursive:
-	@set fnord $$MAKEFLAGS; amf=$$2; \
-	dot_seen=no; \
-	case "$@" in \
-	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
-	  *) list='$(SUBDIRS)' ;; \
-	esac; \
-	rev=''; for subdir in $$list; do \
-	  if test "$$subdir" = "."; then :; else \
-	    rev="$$subdir $$rev"; \
-	  fi; \
-	done; \
-	rev="$$rev ."; \
-	target=`echo $@ | sed s/-recursive//`; \
-	for subdir in $$rev; do \
-	  echo "Making $$target in $$subdir"; \
-	  if test "$$subdir" = "."; then \
-	    local_target="$$target-am"; \
-	  else \
-	    local_target="$$target"; \
-	  fi; \
-	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
-	   || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
-	done && test -z "$$fail"
-tags-recursive:
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
-	done
-
-ETAGS = etags
-ETAGSFLAGS =
-
-tags: TAGS
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
-	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
-	unique=`for i in $$list; do \
-	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
-	  done | \
-	  $(AWK) '    { files[$$0] = 1; } \
-	       END { for (i in files) print i; }'`; \
-	mkid -fID $$unique
-
-TAGS: tags-recursive $(HEADERS) $(SOURCES) config.h.in $(TAGS_DEPENDENCIES) \
-		$(TAGS_FILES) $(LISP)
-	tags=; \
-	here=`pwd`; \
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  if test "$$subdir" = .; then :; else \
-	    test -f $$subdir/TAGS && tags="$$tags -i $$here/$$subdir/TAGS"; \
-	  fi; \
-	done; \
-	list='$(SOURCES) $(HEADERS) config.h.in $(LISP) $(TAGS_FILES)'; \
-	unique=`for i in $$list; do \
-	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
-	  done | \
-	  $(AWK) '    { files[$$0] = 1; } \
-	       END { for (i in files) print i; }'`; \
-	test -z "$(ETAGS_ARGS)$$tags$$unique" \
-	  || $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
-	     $$tags $$unique
-
-GTAGS:
-	here=`$(am__cd) $(top_builddir) && pwd` \
-	  && cd $(top_srcdir) \
-	  && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
-	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-
-top_distdir = .
-distdir = $(PACKAGE)-$(VERSION)
-
-am__remove_distdir = \
-  { test ! -d $(distdir) \
-    || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \
-         && rm -fr $(distdir); }; }
-
-GZIP_ENV = --best
-distcleancheck_listfiles = find . -type f -print
-
-distdir: $(DISTFILES)
-	$(am__remove_distdir)
-	mkdir $(distdir)
-	$(mkinstalldirs) $(distdir)/intl $(distdir)/po
-	@list='$(DISTFILES)'; for file in $$list; do \
-	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
-	  dir=`echo "$$file" | sed -e 's,/[^/]*$$,,'`; \
-	  if test "$$dir" != "$$file" && test "$$dir" != "."; then \
-	    dir="/$$dir"; \
-	    $(mkinstalldirs) "$(distdir)$$dir"; \
-	  else \
-	    dir=''; \
-	  fi; \
-	  if test -d $$d/$$file; then \
-	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
-	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
-	    fi; \
-	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
-	  else \
-	    test -f $(distdir)/$$file \
-	    || cp -p $$d/$$file $(distdir)/$$file \
-	    || exit 1; \
-	  fi; \
-	done
-	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
-	  if test "$$subdir" = .; then :; else \
-	    test -d $(distdir)/$$subdir \
-	    || mkdir $(distdir)/$$subdir \
-	    || exit 1; \
-	    (cd $$subdir && \
-	      $(MAKE) $(AM_MAKEFLAGS) \
-	        top_distdir="$(top_distdir)" \
-	        distdir=../$(distdir)/$$subdir \
-	        distdir) \
-	      || exit 1; \
-	  fi; \
-	done
-	-find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \
-	  ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
-	  ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
-	  ! -type d ! -perm -444 -exec $(SHELL) $(install_sh) -c -m a+r {} {} \; \
-	|| chmod -R a+r $(distdir)
-dist-gzip: distdir
-	$(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
-	$(am__remove_distdir)
-
-dist dist-all: distdir
-	$(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
-	$(am__remove_distdir)
-
-# This target untars the dist file and tries a VPATH configuration.  Then
-# it guarantees that the distribution is self-contained by making another
-# tarfile.
-distcheck: dist
-	$(am__remove_distdir)
-	GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(AMTAR) xf -
-	chmod -R a-w $(distdir); chmod a+w $(distdir)
-	mkdir $(distdir)/=build
-	mkdir $(distdir)/=inst
-	chmod a-w $(distdir)
-	dc_install_base=`$(am__cd) $(distdir)/=inst && pwd` \
-	  && cd $(distdir)/=build \
-	  && ../configure --srcdir=.. --prefix=$$dc_install_base \
-	    --with-included-gettext \
-	    $(DISTCHECK_CONFIGURE_FLAGS) \
-	  && $(MAKE) $(AM_MAKEFLAGS) \
-	  && $(MAKE) $(AM_MAKEFLAGS) dvi \
-	  && $(MAKE) $(AM_MAKEFLAGS) check \
-	  && $(MAKE) $(AM_MAKEFLAGS) install \
-	  && $(MAKE) $(AM_MAKEFLAGS) installcheck \
-	  && $(MAKE) $(AM_MAKEFLAGS) uninstall \
-	  && (test `find $$dc_install_base -type f -print | wc -l` -le 1 \
-	      || { echo "ERROR: files left after uninstall:" ; \
-	           find $$dc_install_base -type f -print ; \
-	           exit 1; } >&2 ) \
-	  && $(MAKE) $(AM_MAKEFLAGS) dist-gzip \
-	  && rm -f $(distdir).tar.gz \
-	  && $(MAKE) $(AM_MAKEFLAGS) distcleancheck
-	$(am__remove_distdir)
-	@echo "$(distdir).tar.gz is ready for distribution" | \
-	  sed 'h;s/./=/g;p;x;p;x'
-distcleancheck: distclean
-	if test '$(srcdir)' = . ; then \
-	  echo "ERROR: distcleancheck can only run from a VPATH build" ; \
-	  exit 1 ; \
-	fi
-	test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
-	  || { echo "ERROR: files left after distclean:" ; \
-	       $(distcleancheck_listfiles) ; \
-	       exit 1; } >&2
-check-am: all-am
-check: check-recursive
-all-am: Makefile config.h
-installdirs: installdirs-recursive
-installdirs-am:
-
-install: install-recursive
-install-exec: install-exec-recursive
-install-data: install-data-recursive
-uninstall: uninstall-recursive
-
-install-am: all-am
-	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-recursive
-install-strip:
-	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
-	  INSTALL_STRIP_FLAG=-s \
-	  `test -z '$(STRIP)' || \
-	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
-	-rm -f Makefile $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
-	@echo "This command is intended for maintainers to use"
-	@echo "it deletes files that may require special tools to rebuild."
-clean: clean-recursive
-
-clean-am: clean-generic clean-libtool mostlyclean-am
-
-distclean: distclean-recursive
-	-rm -f $(am__CONFIG_DISTCLEAN_FILES)
-distclean-am: clean-am distclean-generic distclean-hdr distclean-libtool \
-	distclean-tags
-
-dvi: dvi-recursive
-
-dvi-am:
-
-info: info-recursive
-
-info-am:
-
-install-data-am:
-
-install-exec-am:
-
-install-info: install-info-recursive
-
-install-man:
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-recursive
-	-rm -f $(am__CONFIG_DISTCLEAN_FILES)
-	-rm -rf autom4te.cache
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-recursive
-
-mostlyclean-am: mostlyclean-generic mostlyclean-libtool
-
-uninstall-am: uninstall-info-am
-
-uninstall-info: uninstall-info-recursive
-
-.PHONY: $(RECURSIVE_TARGETS) GTAGS all all-am check check-am clean \
-	clean-generic clean-libtool clean-recursive dist dist-all \
-	dist-gzip distcheck distclean distclean-generic distclean-hdr \
-	distclean-libtool distclean-recursive distclean-tags \
-	distcleancheck distdir dvi dvi-am dvi-recursive info info-am \
-	info-recursive install install-am install-data install-data-am \
-	install-data-recursive install-exec install-exec-am \
-	install-exec-recursive install-info install-info-am \
-	install-info-recursive install-man install-recursive \
-	install-strip installcheck installcheck-am installdirs \
-	installdirs-am installdirs-recursive maintainer-clean \
-	maintainer-clean-generic maintainer-clean-recursive mostlyclean \
-	mostlyclean-generic mostlyclean-libtool mostlyclean-recursive \
-	tags tags-recursive uninstall uninstall-am uninstall-info-am \
-	uninstall-info-recursive uninstall-recursive
-
-
-deb:
-	if test -f ../mp4h_$(VERSION).orig.tar.gz; then \
-          :; \
-        else \
-          $(MAKE) dist && mv mp4h-$(VERSION).tar.gz ../mp4h_$(VERSION).orig.tar.gz; \
-        fi
-	-rm -rf config.log autom4te.cache
-	$(MAKE) distclean && dpkg-buildpackage -i'/CVS|/\.cvsignore|/\.scvsrc|/tags' -rfakeroot
-
-README: configure.ac src/readme.tmpl
-	@x='@'; sed -e "s/$${x}PACKAGE_VERSION$${x}/@PACKAGE_VERSION@/" -e "s/$${x}PACKAGE_DATE$${x}/@PACKAGE_DATE@/" src/readme.tmpl > $@
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT: