Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

hxref(1) [debian man page]

HXREF(1)							  HTML-XML-utils							  HXREF(1)

NAME
hxref - generate cross-references inside and between HTML files SYNOPSIS
hxref [ -x ] [ -l ] [ -b base ] [ -i index ] [ -- ] [ input [ output ] ] DESCRIPTION
The hxref command links inline elements to DFN elements with the same content. It adds ID attributes where necessary. If the content of a DFN or other element isn't suitable, the TITLE attribute may be used to provide the term to use for comparisons. Here is an example: <p>A <dfn>b-box</dfn> is defined to be... <p>For every b there is a <em>b-box</em>... The output of hxref will be similar to this: <p>A <dfn id="b-box">b-box</dfn> is defined to be... <p>For every b there is a <a href="#b-box"><em>b-box</em></a>... OPTIONS
The following options are supported: -x Use XML conventions: empty elements are written with a slash at the end: <IMG /> -b base Sets the prefix for the generated URLs. By default base is empty, which generates URLs like "#b-box" above. If base is set to, e.g., "http://xyz/", the URLs will look like "http://xyz/#b-box". -i index Directs hxref to read terms from a database file before looking for them in the document and afterwards store the terms that were found in the same file. DFN element in the document override terms found in index. This allows hxref to be run multiple times on different files, to make the files refer to each other. It may be necessary to run the commands twice, to resolve all cross-ref- erences. -l Try to use language-specific information to match instances to their definitions. Currently, only English is supported and the only rules applied are to search without a final "s" ("trees" matches "tree"), without a final "es" ("bosses" matches "boss") and with a "y" replacing a final "ies" ("bounties" matches "bounty"). hxref determines the language from "lang" and "xml:lang" attributes in the document. OPERANDS
The following operands are supported: input The name of an HTML file. If absent, standard input is read instead. The special name "-" also indicates standard input. The input may be an URL. output The file to write to. If absent, standard output is used. This may not be a URL. DIAGNOSTICS
The following exit values are returned: 0 Successful completion. > 0 An error occurred in the parsing of the HTML file. hxref will try to correct the error and produce output anyway. SEE ALSO
asc2xml(1), hxindex(1), hxnormalize(1), hxnum(1), hxtoc(1), xml2asc(1) BUGS
The error recovery for incorrect HTML is primitive. The program generates ID attributes, but doesn't generate <a name=...> tags, so the links only work in browsers that recognize ID attributes. The rules for matching English plurals are primitif. No dictionary is used. E.g., "bees" will be considered a plural of "be". There is currently no way to set the default language for a document for when the root element has no "lang" or "xml:lang" attribute. 6.x 10 Jul 2011 HXREF(1)

Check Out this Related Man Page

HXNORMALIZE(1)							  HTML-XML-utils						    HXNORMALIZE(1)

NAME
hxnormalize - pretty-print an HTML file SYNOPSIS
hxnormalize [ -x ] [ -e ] [ -d ] [ -s ] [ -L ] [ -i indent ] [ -l line-length ] [ -c commentmagic ] [ file-or-URL ] DESCRIPTION
The hxnormalize command pretty-prints an HTML file, and also tries to fix small errors. The output is the same HTML, but with a maximum line length and with optional indentation to indicate the nesting level of each line. OPTIONS
The following options are supported: -x Use XML conventions: empty elements are written with a slash at the end: <IMG />. Implies -e. -e Always insert endtags, even if HTML does not require them (for example: </p> and </li>). -d Omit the DOCTYPE from the output. -i indent Set the number of spaces to indent each nesting level. Default is 2. Not all elements cause an indent. In general, elements that can occur in a block environment are started on a new line and cause an indent, but inline elements, such as EM and SPAN do not cause an indent. -l line-length Sets the maximum length of lines. hxnormalize will wrap lines so that all lines are as long as possible, but no longer than this length. Default is 72. Words that are longer than the line length will not be broken, and will extend past this length. A content of the STYLE, SCRIPT and PRE elements will not be line-wrapped. -s Omit <span> tags that don't have any attributes. -L Remove redundant "lang" and "xml:lang" attributes. (I.e., those whose value is the same as the language inherited from the parent element.) -c commentmagic Comments are normally placed right after the preceding text. That is usually correct for short comments, but some comments are meant to be on a separate line. commentmagic is a string and when that string occurs inside a comment, hxnormalize will output an empty line before that comment. E.g. -c "====" can be used to put all comments that contain "====" on a separate line, pre- ceded by an empty line. By default, no comments are treated that way. OPERANDS
The following operand is supported: file-or-URL The name or URL of an HTML file. If absent, standard input is read instead. EXIT STATUS
The following exit values are returned: 0 Successful completion. > 0 An error occurred in the parsing of the HTML file. hxnormalize will try to correct the error and produce output anyway. ENVIRONMENT
To use a proxy to retrieve remote files, set the environment variables http_proxy and ftp_proxy. E.g., http_proxy="http://localhost:8080/" BUGS
The error recovery for incorrect HTML is primitive. hxnormalize will not omit an endtag if the white space after it could possibly be significant. E.g., it will not remove the first </p> from "<div><p>text</p> <p>text</p></div>". hxnormalize can currently only retrieve remote files over HTTP. It doesn't handle password-protected files, nor files whose content depends on HTTP "cookies." SEE ALSO
asc2xml(1), xml2asc(1), UTF-8 (RFC 2279) 6.x 10 Jul 2011 HXNORMALIZE(1)
Man Page