Revision: 18785
http://gar.svn.sourceforge.net/gar/?rev=18785&view=rev
Author: pfelecan
Date: 2012-07-17 11:49:43 +0000 (Tue, 17 Jul 2012)
Log Message:
-----------
tex4ht/trunk: migrated from a private recipe to a GAR based recipe.
Added Paths:
-----------
csw/mgar/pkg/tex4ht/
csw/mgar/pkg/tex4ht/Makefile
csw/mgar/pkg/tex4ht/branches/
csw/mgar/pkg/tex4ht/tags/
csw/mgar/pkg/tex4ht/trunk/
csw/mgar/pkg/tex4ht/trunk/Makefile
csw/mgar/pkg/tex4ht/trunk/checksums
csw/mgar/pkg/tex4ht/trunk/files/
csw/mgar/pkg/tex4ht/trunk/files/COPYING
csw/mgar/pkg/tex4ht/trunk/files/tex4ht.1
Added: csw/mgar/pkg/tex4ht/Makefile
===================================================================
--- csw/mgar/pkg/tex4ht/Makefile (rev 0)
+++ csw/mgar/pkg/tex4ht/Makefile 2012-07-17 11:49:43 UTC (rev 18785)
@@ -0,0 +1,2 @@
+%:
+ $(MAKE) -C trunk $*
Property changes on: csw/mgar/pkg/tex4ht/trunk
___________________________________________________________________
Added: svn:ignore
+ work
Added: csw/mgar/pkg/tex4ht/trunk/Makefile
===================================================================
--- csw/mgar/pkg/tex4ht/trunk/Makefile (rev 0)
+++ csw/mgar/pkg/tex4ht/trunk/Makefile 2012-07-17 11:49:43 UTC (rev 18785)
@@ -0,0 +1,148 @@
+# $Id$
+# TODO (release-critical prefixed with !, non release-critical with *)
+#
+NAME = tex4ht
+VERSION = 1.0.2009_06_11_1038
+GARTYPE = v2
+CATEGORIES = apps
+
+DESCRIPTION = LaTeX and TeX for Hypertext (HTML)
+define BLURB
+ TeX4ht is a highly configurable TeX-based authoring system dedicated mainly
+ to produce hypertext. It interacts with TeX-based applications through style
+ files and postprocessors, leaving the processing of the source files to the
+ native TeX compiler. Consequently, TeX4ht can handle the features of
+ TeX-based systems in general, and of the LaTeX and AMS style files in
+ particular.
+
+ Pre-tailored configurations are offered for different output formats,
+ including (X)HTML, MathML, OpenDocument, and DocBook.
+endef
+
+MASTER_SITES = http://tug.org/applications/tex4ht/
+DISTFILES = $(NAME).zip
+DISTFILES += COPYING
+DISTFILES += tex4ht.1
+
+PACKAGING_PLATFORMS = solaris10-sparc
+PACKAGING_PLATFORMS += solaris10-i386
+
+BUILD_DEP_PKGS += CSWtetex
+
+GARCOMPILER = GNU
+
+CONFIGURE_SCRIPTS =
+BUILD_SCRIPTS = custom
+TEST_SCRIPTS =
+INSTALL_SCRIPTS = custom
+
+PACKAGES +=
CSWtex4ht-common
+CATALOGNAME_CSWtex4ht-common = tex4ht_common
+SPKG_DESC_CSWtex4ht-common += $(DESCRIPTION),
architecture neutral components
+ARCHALL_CSWtex4ht-common = 1
+OBSOLETED_BY_CSWtex4ht-common = CSWtex4htcommon
+CATALOGNAME_CSWtex4htcommon =
tex4ht_common_stub
+RUNTIME_DEP_PKGS_CSWtex4ht-common += CSWimagemagick
+CHECKPKG_OVERRIDES_CSWtex4ht-common +=
surplus-dependency|CSWimagemagick
+RUNTIME_DEP_PKGS_CSWtex4ht-common += CSWnetpbm
+CHECKPKG_OVERRIDES_CSWtex4ht-common +=
surplus-dependency|CSWnetpbm
+RUNTIME_DEP_PKGS_CSWtex4ht-common += CSWperl
+CHECKPKG_OVERRIDES_CSWtex4ht-common +=
surplus-dependency|CSWperl
+RUNTIME_DEP_PKGS_CSWtex4ht-common += CSWpstoedit
+CHECKPKG_OVERRIDES_CSWtex4ht-common +=
surplus-dependency|CSWpstoedit
+RUNTIME_DEP_PKGS_CSWtex4ht-common += CSWtetex
+CHECKPKG_OVERRIDES_CSWtex4ht-common +=
surplus-dependency|CSWtetex
+
+PACKAGES +=
CSWtex4ht
+CATALOGNAME_CSWtex4ht = tex4ht
+SPKG_DESC_CSWtex4ht +=
$(DESCRIPTION)
+PKGFILES_CSWtex4ht +=
/opt/csw/bin/tex4ht
+PKGFILES_CSWtex4ht +=
/opt/csw/bin/t4ht
+RUNTIME_DEP_PKGS +=
CSWtex4ht-common
+CHECKPKG_OVERRIDES_CSWtex4ht +=
surplus-dependency|CSWtex4ht-common
+
+include gar/category.mk
+
+genBins = \
+ $(WORKSRC)/src/tex4ht \
+ $(WORKSRC)/src/t4ht
+
+envBase = $(NAME).env
+envFile = $(WORKSRC)/$(envBase)
+origEnvFile = $(WORKSRC)/texmf/$(NAME)/base/unix/$(envBase)
+
+build-custom: \
+ $(genBins) \
+ $(envFile)
+ $(MAKECOOKIE)
+
+confdir = $(sysconfdir)
+sharedir = $(sharedstatedir)
+libexecdir = $(sharedir)/$(NAME)
+docdir = $(sharedir)/doc/$(NAME)
+texdir = $(texmflocaldir)
+libdir = $(texdir)/$(NAME)
+
+LDFLAGS += -lkpathsea
+
+$(WORKSRC)/src/tex4ht: \
+ $(WORKSRC)/src/tex4ht.c
+ $(CC) $(CFLAGS) -DENVFILE='"$(confdir)/tex4ht.env"' -DKPATHSEA
-DHAVE_DIRENT_H $^ -o $@ $(LDFLAGS)
+
+$(WORKSRC)/src/t4ht: \
+ $(WORKSRC)/src/t4ht.c
+ $(CC) $(CFLAGS) -DENVFILE='"$(confdir)/tex4ht.env"' -DKPATHSEA
-DHAVE_DIRENT_H $^ -o $@ $(LDFLAGS)
+
+$(envFile): \
+ $(origEnvFile)
+ gsed \
+ -e
's:^tpath/tex/texmf/fonts/tfm/!$$:t$(sharedir)/texmf-dist/fonts/tfm/!:' \
+ -e 's:^i~/tex4ht.dir/texmf/tex4ht:i$(libdir):' \
+ $^ > $@
+
+install-custom: pkgmandir = $(mandir)/man1
+install-custom:
+ ginstall --directory $(DESTDIR)/$(bindir)
+ ginstall $(genBins) $(DESTDIR)/$(bindir)
+ ginstall \
+ $(WORKSRC)/bin/ht/unix/htlatex \
+ $(WORKSRC)/bin/ht/unix/httex \
+ $(WORKSRC)/bin/unix/ht \
+ $(WORKSRC)/bin/unix/httexi \
+ $(WORKSRC)/bin/unix/mk4ht \
+ $(DESTDIR)/$(bindir)
+ ginstall --directory $(DESTDIR)/$(confdir)
+ ginstall $(envFile) $(DESTDIR)/$(confdir)
+ ginstall --directory $(DESTDIR)/$(libexecdir)
+ ginstall $(WORKSRC)/bin/unix/mk4ht $(DESTDIR)/$(libexecdir)
+ ginstall $(WORKSRC)/texmf/tex4ht/bin/tex4ht.jar $(DESTDIR)/$(libexecdir)
+ find $(WORKSRC)/bin/ht/unix -type f -exec ginstall {}
$(DESTDIR)/$(libexecdir) \;
+ ginstall --directory $(DESTDIR)/$(libdir)
+ gtar \
+ --directory $(WORKSRC)/texmf/tex4ht \
+ --create \
+ --file=- \
+ ht-fonts \
+ xtpipes \
+ | \
+ gtar \
+ --directory $(DESTDIR)/$(libdir) \
+ --extract \
+ --file=-
+ gtar \
+ --directory $(WORKSRC)/texmf \
+ --create \
+ --file=- \
+ tex \
+ | \
+ gtar \
+ --directory $(DESTDIR)/$(texdir) \
+ --extract \
+ --file=-
+ ginstall --directory --mode=u=rwx,go=rx $(DESTDIR)/$(pkgmandir)
+ ginstall --preserve-timestamps --mode=u=rwx,go=r $(FILEDIR)/tex4ht.1
$(DESTDIR)/$(pkgmandir)
+ $(MAKECOOKIE)
+
+# this is private and not available publicly
+mydependencies:
+ for package in $(PACKAGES); do echo '___' $${package};
$(HOME)/bin/ocswdeplist --depth 1 --dependencies --packaging --csw --prototype
$(HOME)/opencsw/$(NAME)/trunk/work/build-global/$${package}.prototype --target
$(HOME)/opencsw/$(NAME)/trunk/work/pkgroot; done
Property changes on: csw/mgar/pkg/tex4ht/trunk/Makefile
___________________________________________________________________
Added: svn:keywords
+ Id
Added: csw/mgar/pkg/tex4ht/trunk/checksums
===================================================================
--- csw/mgar/pkg/tex4ht/trunk/checksums (rev 0)
+++ csw/mgar/pkg/tex4ht/trunk/checksums 2012-07-17 11:49:43 UTC (rev 18785)
@@ -0,0 +1 @@
+a3449f7e81a917d6d80073a687448b3f tex4ht.zip
Added: csw/mgar/pkg/tex4ht/trunk/files/COPYING
===================================================================
--- csw/mgar/pkg/tex4ht/trunk/files/COPYING (rev 0)
+++ csw/mgar/pkg/tex4ht/trunk/files/COPYING 2012-07-17 11:49:43 UTC (rev
18785)
@@ -0,0 +1,416 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c 2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+ Everyone is allowed to distribute verbatim copies of this
+ license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute. This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but
+it is written in such a way that you can use it even if your work is
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work. If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+ `Work'
+ Any work being distributed under this License.
+
+ `Derived Work'
+ Any work that under any applicable law is derived from the Work.
+
+ `Modification'
+ Any procedure that produces a Derived Work under any applicable
+ law -- for example, the production of a file containing an
+ original file associated with the Work or a significant portion of
+ such a file, either verbatim or with modifications and/or
+ translated into another language.
+
+ `Modify'
+ To apply any procedure that produces a Derived Work under any
+ applicable law.
+
+ `Distribution'
+ Making copies of the Work available from one person to another, in
+ whole or in part. Distribution includes (but is not limited to)
+ making any electronic components of the Work accessible by
+ file transfer protocols such as FTP or HTTP or by shared file
+ systems such as Sun's Network File System (NFS).
+
+ `Compiled Work'
+ A version of the Work that has been processed into a form where it
+ is directly usable on a computer system. This processing may
+ include using installation facilities provided by the Work,
+ transformations of the Work, copying of components of the Work, or
+ other activities. Note that modification of any installation
+ facilities provided by the Work constitutes modification of the Work.
+
+ `Current Maintainer'
+ A person or persons nominated as such within the Work. If there is
+ no such explicit nomination then it is the `Copyright Holder' under
+ any applicable law.
+
+ `Base Interpreter'
+ A program or process that is normally needed for running or
+ interpreting a part or the whole of the Work.
+
+ A Base Interpreter may depend on external components but these
+ are not considered part of the Base Interpreter provided that each
+ external component clearly identifies itself whenever it is used
+ interactively. Unless explicitly specified when applying the
+ license to the Work, the only applicable Base Interpreter is a
+ `LaTeX-Format' or in the case of files belonging to the
+ `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1. Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope. In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2. You may distribute a complete, unmodified copy of the Work as you
+received it. Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3. You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4. If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work. You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work. Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5. If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6. If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition. Only
+the Current Maintainer is allowed to add such statements of exemption
+to a component of the Work.
+
+ a. If a component of this Derived Work can be a direct replacement
+ for a component of the Work when that component is used with the
+ Base Interpreter, then, wherever this component of the Work
+ identifies itself to the user when used interactively with that
+ Base Interpreter, the replacement component of this Derived Work
+ clearly and unambiguously identifies itself as a modified version
+ of this component to the user when used interactively with that
+ Base Interpreter.
+
+ b. Every component of the Derived Work contains prominent notices
+ detailing the nature of the changes to that component, or a
+ prominent reference to another file that is distributed as part
+ of the Derived Work and that contains a complete and accurate log
+ of the changes.
+
+ c. No information in the Derived Work implies that any persons,
+ including (but not limited to) the authors of the original version
+ of the Work, provide any support, including (but not limited to)
+ the reporting and handling of errors, to recipients of the
+ Derived Work unless those persons have stated explicitly that
+ they do provide such support for the Derived Work.
+
+ d. You distribute at least one of the following with the Derived Work:
+
+ 1. A complete, unmodified copy of the Work;
+ if your distribution of a modified component is made by
+ offering access to copy the modified component from a
+ designated place, then offering equivalent access to copy
+ the Work from the same or some similar place meets this
+ condition, even though third parties are not compelled to
+ copy the Work along with the modified component;
+
+ 2. Information that is sufficient to obtain a complete,
+ unmodified copy of the Work.
+
+7. If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8. The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9. Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+
+10. a. A Derived Work may be distributed under a different license
+ provided that license itself honors the conditions listed in
+ Clause 6 above, in regard to the Work, though it does not have
+ to honor the rest of the conditions in this license.
+
+ b. If a Derived Work is distributed under a different license, that
+ Derived Work must provide sufficient documentation as part of
+ itself to allow each recipient of that Derived Work to honor the
+ restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12. Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work. Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose. The entire risk as to the quality and performance
+of the Work is with you. Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1. Make a reasonable attempt to trace the Current Maintainer (and
+ the Copyright Holder, if the two differ) through the means of
+ an Internet or similar search.
+
+ 2. If this search is successful, then enquire whether the Work
+ is still maintained.
+
+ a. If it is being maintained, then ask the Current Maintainer
+ to update their communication data within one month.
+
+ b. If the search is unsuccessful or no action to resume active
+ maintenance is taken by the Current Maintainer, then announce
+ within the pertinent community your intention to take over
+ maintenance. (If the Work is a LaTeX work, this could be
+ done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+ maintenance of the Work to you, then this takes effect
+ immediately upon announcement.
+
+ b. If the Current Maintainer is not reachable and the Copyright
+ Holder agrees that maintenance of the Work be passed to you,
+ then this takes effect immediately upon announcement.
+
+ 4. If you make an `intention announcement' as described in 2b. above
+ and after three months your intention is challenged neither by
+ the Current Maintainer nor by the Copyright Holder nor by other
+ people, then you may arrange for the Work to be changed so as
+ to name you as the (new) Current Maintainer.
+
+ 5. If the previously unreachable Current Maintainer becomes
+ reachable once more within three months of a change completed
+ under the terms of 3b) or 4), then that Current Maintainer must
+ become or remain the Current Maintainer upon request provided
+ they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer. You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license. These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license. You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license. It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate. Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component. While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community. It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one. Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified. Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+ %% pig.dtx
+ %% Copyright 2005 M. Y. Name
+ %
+ % This work may be distributed and/or modified under the
+ % conditions of the LaTeX Project Public License, either version 1.3
+ % of this license or (at your option) any later version.
+ % The latest version of this license is in
+ % http://www.latex-project.org/lppl.txt
+ % and version 1.3 or later is part of all distributions of LaTeX
+ % version 2005/12/01 or later.
+ %
+ % This work has the LPPL maintenance status `maintained'.
+ %
+ % The Current Maintainer of this work is M. Y. Name.
+ %
+ % This work consists of the files pig.dtx and pig.ins
+ % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+ The LPPL requires that distributions of the Work contain all the
+ files of the Work. It is therefore important that you provide a
+ way for the licensee to determine which files constitute the Work.
+ This could, for example, be achieved by explicitly listing all the
+ files of the Work near the copyright notice of each file or by
+ using a line such as:
+
+ % This work consists of all files listed in manifest.txt.
+
+ in that place. In the absence of an unequivocal list it might be
+ impossible for the licensee to determine what is considered by you
+ to comprise the Work and, in such a case, the licensee would be
+ entitled to make reasonable conjectures as to which files comprise
+ the Work.
+
Added: csw/mgar/pkg/tex4ht/trunk/files/tex4ht.1
===================================================================
--- csw/mgar/pkg/tex4ht/trunk/files/tex4ht.1 (rev 0)
+++ csw/mgar/pkg/tex4ht/trunk/files/tex4ht.1 2012-07-17 11:49:43 UTC (rev
18785)
@@ -0,0 +1,500 @@
+.\" Written by Andrew Gray <a...@debian.org>, 12 March 1999
+.\" Revised Tue, 22 Jun 1999 09:53:47 +0100
+.\" Revised Sun, 16 Jul 2000 14:08:07 +0100
+.\" Revised Sat, 3 May 2003 22:41:20 +0100
+.\" Revised by Kapil Hari Paranjape Tue, 5 Apr 2005 08:51:27 +0530
+.\" Revised Thu, 11 Sep 2008 12:40:50 +0530
+.TH TEX4HT 1 "5 Apr 2005"
+.SH NAME
+TeX4ht \- a system for authoring hypertext with TeX and friends
+.SH SYNOPSIS
+.BR mk4ht
+.I command
+.I file
+.RI "[ " "options1" " ]"
+.RI "[ " "options2" " ]"
+.RI "[ " "options3" " ]"
+.LP
+.BR httex | htlatex | httexi
+.I file
+.RI "[ " "options1" " ]"
+.RI "[ " "options2" " ]"
+.RI "[ " "options3" " ]"
+.LP
+.B ht
+tex|latex
+.IR file " [ " "t4ht options" " ]"
+.LP
+.B tex4ht
+[
+.BI \-f dir-char
+]
+.I file[.dvi]
+[
+.BI \-c tag-name
+] [
+.BI \-e env-file
+] [
+.BI \-g bitmap-file-ext
+] [
+.BR \-h ( e|f|F|g|s|v|V )
+] [
+.BI \-i htf-font-dir
+] [
+.BI \-l bookkeeping-file
+] [
+.BR \-P ( * | \fIfilter\fP )
+] [
+.BI \-t tfm-font-dir
+] [
+.B \-u10
+] [
+.B \-utf8
+] [
+.B \-xs
+]
+.LP
+.B t4ht
+[
+.BI \-f dir-char
+]
+.I file[.lg]
+[
+.BI \-c tag-name
+] [
+.BI \-d out-dir
+] [
+.BI \-e env-file
+] [
+.B \-i
+] [
+.BI \-m mode
+] [
+.BI \-M mode
+] [
+.B \-p
+] [
+.B \-r
+] [
+.BR \-S ( * | \fIfilter\fP )
+] [
+.BI \-X field-content
+] [
+.BI \-. field-content
+]
+.LP
+.SH "DESCRIPTION"
+(This manual page was written for the Debian GNU/Linux distribution because the
+original program does not have a manual page. Instead, it is
+documented in detail at the author's website; see below. Please refer to
+that documentation for more details or up to date information.)
+.PP
+This page documents briefly
+the portmanteau perl script
+.BR mk4ht ",
+the more specific shell scripts
+.BR httex ", "htlatex ", "httexi ",
+and others like them, the lower level shell script interface
+.BR ht ",
+and the commands
+.BR tex4ht " and "t4ht "
+that all these scripts invoke. Together these programs constitute
+TeX4ht; a highly configurable TeX-based authoring system for producing
hypertext.
+.PP
+TeX4ht interacts with TeX-based applications through a style file
+.I tex4ht.sty
+and other files which are loaded by this style file,
+leaving the processing of the source files to the native TeX
+compiler. The output of the TeX compiler is then post-processed by
+.BR tex4ht " and "t4ht ".
+Consequently, TeX4ht can handle most features of TeX-based systems in
+general, and of LaTeX in particular.
+.PP
+The shell scripts
+.BR " httex ", " htlatex " and " httexi
+convert TeX (respectively LaTeX and texinfo) into HTML. Typical user
+requirements should be satisfied by these scripts which can generally
+convert typical TeX source
+.IR without
+requiring any modifications.
+.PP
+To convert from a one of the other dialects of TeX (like ConTeXt),
+.IR or
+to convert into one of the other variants of hypertext
+(MathML, XML, OO and so on), it is
+.IR recommended
+that you use the perl script
+.BR "mk4ht".
+Most common usage of the
+system can be covered by the appropriate use of this command with its options.
+.PP
+The shell script
+.BR " ht
+is a much more elementary script which is provided for more complicated
+needs. Its correct use depends on a better understanding of the system.
+.PP
+All these scripts begin with suitable invocations of
+.BR tex (1)
+or
+.BR latex (1)
+or other dialects of TeX as required. The post-processing of the
+.I .dvi
+output is handled by
+.BR "tex4ht".
+Anything that cannot be rendered using HTML (or its chosen hypertext variant),
such
+as the creation of bitmap images or CSS (Cascade Style Sheet) files is handled
by
+the auxiliary program
+.BR "t4ht".
+The method used for generating the images can be configured.
+.PP
+.SH OPTIONS
+The following is only a very brief summary of the main program options.
+For more details of the command-line and configuration options, see the HTML
+documentation (see below).
+.SS Options for httex, htlatex and httexi
+.BR httex ", " htlatex " and " httexi
+are shell scripts that can be used to convert a file in the TeX/LaTeX/texinfo
format
+into HTML. This TeX source file should be like any other TeX source file
+normally used to produce a
+.I .dvi
+file by processing with TeX and friends. The name of such a file is the
mandatory file argument
+for each script. This is followed by up to three optional arguments (delimited
with
+quotation marks). These arguments, which are
+.B not
+required for typical usage, are as follows:
+.IP 1.
+The first argument is a list of options for the
+.I tex4ht.sty
+style file (used with tex or latex), separated with commas.
+See the HTML documentation for the list of options available. The
+.I .log
+file generated by tex/latex also includes summaries of some of the options
available.
+If not empty, this argument must start with
+.B html
+or
+.BR xhtml .
+Additional options could be
+.B mathml
+or
+.B docbook
+to indicate appropriate style of output.
+.IP 2.
+This argument is used to select tagged sections of
+.I tex4ht.env
+that specifies the font files (*.htf) to use. This corresponds to the
+.BI \-c
+option for the command
+.I tex4ht
+as explained below. Examples include
+.B unicode
+or
+.BR mozilla .
+.IP 3.
+This argument lists options for the
+.I t4ht
+program as explained below.
+.LP
+See the HTML documentation for more details and examples.
+.LP
+Similar scripts are
+available within the directory
+.I /opt/csw/share/tex4ht
+for generating other kinds of hypertext output. It is also possible
+to use the perl script
+.BR mk4ht
+as explained below.
+.SS Options for mk4ht
+.BR mk4ht
+is a perl script that can be used to convert TeX source files from
+numerous dialects of TeX into different hypertext variants. This script
+takes two mandatory arguments: the name of the command to run and the
+file to run it on. Each possible command is of the form
+"<variant><dialect>": so for example
+.IR xhmlatex
+denotes a LaTeX source that needs to be converted to XHTML with
+MathML extensions. The possible names for commands can be found by
+listing the directory
+.I /opt/csw/share/tex4ht.
+The three optional arguments to
+.BR mk4ht
+are identical to those outlined above for
+.BR httex ", "htlatex " and " httexi ".
+In fact, the command
+.BR htlatex " "foo "
+is identical to
+.BR mk4ht " "htlatex " "foo "
+except that the former is shorter to type! However,
+.BR mk4ht
+can be configured to shorten the command line as follows.
+.PP
+Each user can create the configuration file
+.IR mk4ht.cfg
+or
+.IR .mk4ht
+in the home or working directory to configure commonly used options
+for mk4ht; in addition options to clean up temporary files can also
+be added to this configuration file. Running the command
+.BR mk4ht
+without any arguments will summarise the use of this user configuration
+file.
+.SS Options for ht
+.B ht
+is a small shell script that is used to run the tex4ht programs. It has two
+compulsory arguments, as follows:
+.IP 1.
+The TeX command name to run, usually either
+.B tex
+or
+.BR latex .
+.IP 2.
+The input file name (with or without extension).
+.PP
+It may take any additional options, which will be passed on to the call to
+.BR t4ht .
+.SS General directory/file search options
+Several of the options detailed below relate to setting directory paths to
+find particular kinds of files. Note the following when specifying
+directories for the programs:
+.IP 1.
+There must be no space between the option letter (eg,
+.BR \-t )
+and the directory/file name.
+.IP 2.
+The directory name must end with a trailing slash
+.RB ( / ,
+or
+.B /!
+\- see below).
+.IP 3.
+You can add an exclamation mark
+.RB ( ! )
+to the end of the directory name, to enable sub-directory searching.
+.IP 4.
+Only one directory can be specified at a time. To search multiple
+directories, either use the sub-directory searching facility or repeat the
+option. (The directory search options can be repeated as often as required.)
+.IP 5.
+When compiled with
+.B kpathsea
+(as in the OpenCSW package), the path-searching is in part taken over by
+kpathsea. On a OpeCSW system see
+.I /opt/csw/share/doc/tex4ht/README.kpathsea
+for more information on path-searching in a kpathsea-enabled tex4ht.
+.LP
+As well as command-line options, most of these options can (and normally
+should) be set in the configuration file
+.IR tex4ht.env .
+The format within this file is similar, but without using a hyphen before the
+option letter. See the HTML documentation for more details on the
+configuration options available. The file
+.IR tex4ht.env
+can be superseded on a per-directory and/or a per-user basis as
+explained in the HTML documentation.
+as well.
+.SS Options for tex4ht
+.TP
+.BI \-c tag-name
+Certain lines within the
+.I tex4ht.env
+configuration file can be marked with tags. These lines (typically
+.I htf-font-dir
+search lines)
+will be omitted unless specifically requested by specifying the tag name on
+the tex4ht command line. If not used, a command-line option of
+.BI \-c default
+is assumed. (See the supplied tex4ht.env file for examples of tagged
+sections.)
+.TP
+.BI \-e env-file
+Specify address of the tex4ht configuration file
+.IR tex4ht.env .
+.TP
+.BI \-g bitmap-file-ext
+Set the extension of bitmap images to
+.I bitmap-file-ext
+instead of the default
+.IR .png .
+Note that the extension should begin with a dot
+.RB ( . ).
+Note also that this option only affects images generated automatically for
+symbol fonts, and not images generated with the
+.B \(rsPicture
+macro of tex4ht.
+.TP
+.B \-he
+Trace errors and warnings (produces verbose output).
+.TP
+.B \-hg
+Trace groups
+.TP
+.B \-hs
+Trace
+.BR \(rsspecial s.
+.TP
+.B \-hV
+Trace search path for tex4ht.env configuration file
+.TP
+.B \-hF
+Trace search path for
+.I .htf
+font files
+.TP
+.B \-hv
+Dump contents of found tex4ht.env configuration file to stderr (for debugging)
+.TP
+.B \-hf
+Dump contents of each
+.I .htf
+font file found to stderr (for debugging)
+.TP
+.BI \-i htf-font-dir
+Set directory for HTF font files (used by tex4ht) to
+.IR htf-font-dir .
+.TP
+.BI \-l bookkeeping-file
+Specify name of the file listing cache used to speed up filename lookups
+(ignored if compiled with kpathsea support)
+.TP
+.BI \-P filter
+Restrict system calls requested in the source (La)TeX files to utilities whose
+names have
+.I filter
+as a prefix. Use a single asterisk as
+.I filter
+to allow any system calls.
+.TP
+.BI \-t tfm-font-dir
+Set directory for TFM font files to
+.I tfm-font-dir
+(ignored if compiled with kpathsea support).
+.TP
+.BI \-u10
+Use base 10 encoding for unicode characters.
+.TP
+.BI \-utf8
+Use utf-8 encoding for unicode characters.
+.TP
+.BI \-xs
+Use 8.3 (MSDOS style) file names for the generated PNG files.
+.SS Options for t4ht
+.TP
+.BI \-c tag-name
+Certain lines within the
+.I tex4ht.env
+configuration file can be marked with tags. These lines (typically scripts
+for post-processing files) will be omitted unless specifically requested by
+specifying the tag name on the tex4ht command line. If not used, a
+command-line option of
+.BI \-c default
+is assumed. (See the supplied tex4ht.env file for examples of tagged
+sections.)
+.TP
+.BI \-d out-dir
+Output files to directory
+.IR out-dir ,
+instead of to the current directory.
+.TP
+.BI \-e env-file
+Specify address of the tex4ht configuration file
+.IR tex4ht.env .
+.TP
+.B \-i
+Generate verbose debugging output.
+.TP
+.BI \-m mode
+Create any new output files with access mode as indicated by
+.IR mode .
+The
+.I mode
+should be a numeric mode, as used by the
+.BR chmod (1)
+command.
+.TP
+.BI \-M mode
+As
+.I -m
+but change all mode of all output files (including reused bitmaps).
+.TP
+.B \-p
+Do not convert pictures (ie, images generated with macros like
+.BR \(rsPicture ,
+not characters in symbol fonts that will be automatically converted into a
+graphic file).
+.TP
+.B \-r
+Do not resuse existing bitmaps of glyphs (for characters in symbol fonts etc),
+but instead generate all bitmaps anew.
+.TP
+.BI \-S filter
+Restrict system calls requested in the source (La)TeX files to utilities whose
+names have
+.I filter
+as a prefix. Use a single asterisk as
+.I filter
+to allow any system calls.
+.TP
+.BI \-X field-content
+Scripts for post-processing of files can be specified in tex4ht.env. If these
+scripts refer to a field %%3, content for that field can be set with this
+command-line option.
+.TP
+.BI \-. field-content
+Scripts for post-processing of groups of files with a particular extension can
+be specified in tex4ht.env. If these scripts refer to a field %%2, content
+for that field can be set with this command-line option.
+.SH FILES
+.TP
+.I /opt/csw/etc/tex4ht.env
+Configuration file for tex4ht. This file is commented within the file, and
+some additional notes are in
+.I /opt/csw/share/doc/tex4ht/README.kpathsea
+on a OpenCSW system. Further explanation is available in the HTML
+documentation.
+.TP
+.I /opt/csw/share/texmf/web2c/texmf.cnf
+Global configuration file for all TeX-related programs using the kpathsea path
+searching library. The variables
+.IR TEX4HTINPUTS ,
+.I T4HTINPUTS
+and
+.I TEX4HTFONTSET
+within this file relate to file searching within
+.B tex4ht
+and
+.BR t4ht.
+These variables may also be set in the environment, outwith
/opt/csw/texmf/web2c/texmf.cnf.
+.TP
+.I /opt/csw/share/texmf/tex4ht/ht-fonts/*.htf
+Hypertext font files used by tex4ht.
+.TP
+.IR /opt/csw/share/texmf-local/tex/generic/tex4ht/tex4ht.sty " and "
/opt/csw/share/texmf-local/tex/generic/tex4ht/*.4ht
+Macro files used by tex or latex when using tex4ht to generate HTML output.
+.TP
+.I /opt/csw/share/tex4ht/*
+Shell scripts for generating different kinds of hypertext output from tex or
+latex sources.
+.SH "SEE ALSO"
+The use of the tex4ht macros is documented in the HTML documentation.
+.PP
+.BR tex (1),
+.BR latex (1),
+.BR amstex (1),
+.BR kpsewhich (1),
+.I http://tug.org/tex4ht/
+.SH BUGS
+This manual page is not complete. Users should refer to the HTML
+documentation for fuller details of the
+configuration options and for details of the use of the tex4ht style files.
+.B tex4ht
+is still a work in progress, so bug reports
+and requests are very welcome.
+.SH AUTHOR
+This manual page was originally written by Andrew Gray <a...@debian.org>
+(and then modified by Kapil Paranjape),
+for the Debian GNU/Linux system (but it may be used by others).
+Adapted for OpenCSW by Peter Felecan.
+.PP
+The
+.B tex4ht
+programs and macro files were written by Eitan Gurari.
+.
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
_______________________________________________
devel mailing list
devel@lists.opencsw.org
https://lists.opencsw.org/mailman/listinfo/devel
