--- jsmath-fonts-sprite-1.0.orig/debian/control
+++ jsmath-fonts-sprite-1.0/debian/control
@@ -0,0 +1,19 @@
+Source: jsmath-fonts-sprite
+Section: web
+Priority: optional
+Maintainer: Yaroslav Halchenko <debian@onerussian.com>
+Build-Depends: debhelper (>= 4.1.16), unzip
+Standards-Version: 3.7.2
+
+Package: jsmath-fonts-sprite
+Architecture: all
+Depends: jsmath
+Description: raster fonts for jsMath plugin spriteImageFonts
+ Rasterized fonts saved in separate image files -- 1 image per font to
+ enable viewing of jsMath pages by a web-browser which is missing
+ access to TeX fonts. Sprite organization of raster fonts elivates the
+ problem of jsmath-fonts, which is a tremendous number of images since
+ each character has a separate image file. But such advantage comes at
+ speed and compatibility cost.
+ .
+ Homepage: http://www.math.union.edu/~dpvc/jsMath
--- jsmath-fonts-sprite-1.0.orig/debian/copyright
+++ jsmath-fonts-sprite-1.0/debian/copyright
@@ -0,0 +1,218 @@
+This package was debianized by Yaroslav Halchenko
+<debian@onerussian.com> on Thu, 19 Oct 2006 20:58:52 -0400.
+
+It was downloaded from
+http://www.math.union.edu/~dpvc/jsMath/download/jsMath.html
+
+Upstream Author: Davide P. Cervone <dpvc@union.edu>
+
+Copyright: 2004-2006 Davide P. Cervone
+
+License:
+
+                               Apache License
+                         Version 2.0, January 2004
+                      http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction,
+    and distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by
+    the copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all
+    other entities that control, are controlled by, or are under common
+    control with that entity. For the purposes of this definition,
+    "control" means (i) the power, direct or indirect, to cause the
+    direction or management of such entity, whether by contract or
+    otherwise, or (ii) ownership of fifty percent (50%) or more of the
+    outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity
+    exercising permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation
+    source, and configuration files.
+
+    "Object" form shall mean any form resulting from mechanical
+    transformation or translation of a Source form, including but
+    not limited to compiled object code, generated documentation,
+    and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or
+    Object form, made available under the License, as indicated by a
+    copyright notice that is included in or attached to the work
+    (an example is provided in the Appendix below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object
+    form, that is based on (or derived from) the Work and for which the
+    editorial revisions, annotations, elaborations, or other modifications
+    represent, as a whole, an original work of authorship. For the purposes
+    of this License, Derivative Works shall not include works that remain
+    separable from, or merely link (or bind by name) to the interfaces of,
+    the Work and Derivative Works thereof.
+
+    "Contribution" shall mean any work of authorship, including
+    the original version of the Work and any modifications or additions
+    to that Work or Derivative Works thereof, that is intentionally
+    submitted to Licensor for inclusion in the Work by the copyright owner
+    or by an individual or Legal Entity authorized to submit on behalf of
+    the copyright owner. For the purposes of this definition, "submitted"
+    means any form of electronic, verbal, or written communication sent
+    to the Licensor or its representatives, including but not limited to
+    communication on electronic mailing lists, source code control systems,
+    and issue tracking systems that are managed by, or on behalf of, the
+    Licensor for the purpose of discussing and improving the Work, but
+    excluding communication that is conspicuously marked or otherwise
+    designated in writing by the copyright owner as "Not a Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity
+    on behalf of whom a Contribution has been received by Licensor and
+    subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    copyright license to reproduce, prepare Derivative Works of,
+    publicly display, publicly perform, sublicense, and distribute the
+    Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    (except as stated in this section) patent license to make, have made,
+    use, offer to sell, sell, import, and otherwise transfer the Work,
+    where such license applies only to those patent claims licensable
+    by such Contributor that are necessarily infringed by their
+    Contribution(s) alone or by combination of their Contribution(s)
+    with the Work to which such Contribution(s) was submitted. If You
+    institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work
+    or a Contribution incorporated within the Work constitutes direct
+    or contributory patent infringement, then any patent licenses
+    granted to You under this License for that Work shall terminate
+    as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+    Work or Derivative Works thereof in any medium, with or without
+    modifications, and in Source or Object form, provided that You
+    meet the following conditions:
+
+    (a) You must give any other recipients of the Work or
+        Derivative Works a copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices
+        stating that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works
+        that You distribute, all copyright, patent, trademark, and
+        attribution notices from the Source form of the Work,
+        excluding those notices that do not pertain to any part of
+        the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its
+        distribution, then any Derivative Works that You distribute must
+        include a readable copy of the attribution notices contained
+        within such NOTICE file, excluding those notices that do not
+        pertain to any part of the Derivative Works, in at least one
+        of the following places: within a NOTICE text file distributed
+        as part of the Derivative Works; within the Source form or
+        documentation, if provided along with the Derivative Works; or,
+        within a display generated by the Derivative Works, if and
+        wherever such third-party notices normally appear. The contents
+        of the NOTICE file are for informational purposes only and
+        do not modify the License. You may add Your own attribution
+        notices within Derivative Works that You distribute, alongside
+        or as an addendum to the NOTICE text from the Work, provided
+        that such additional attribution notices cannot be construed
+        as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and
+    may provide additional or different license terms and conditions
+    for use, reproduction, or distribution of Your modifications, or
+    for any such Derivative Works as a whole, provided Your use,
+    reproduction, and distribution of the Work otherwise complies with
+    the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+    any Contribution intentionally submitted for inclusion in the Work
+    by You to the Licensor shall be under the terms and conditions of
+    this License, without any additional terms or conditions.
+    Notwithstanding the above, nothing herein shall supersede or modify
+    the terms of any separate license agreement you may have executed
+    with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+    names, trademarks, service marks, or product names of the Licensor,
+    except as required for reasonable and customary use in describing the
+    origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+    agreed to in writing, Licensor provides the Work (and each
+    Contributor provides its Contributions) on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+    implied, including, without limitation, any warranties or conditions
+    of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+    PARTICULAR PURPOSE. You are solely responsible for determining the
+    appropriateness of using or redistributing the Work and assume any
+    risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+    whether in tort (including negligence), contract, or otherwise,
+    unless required by applicable law (such as deliberate and grossly
+    negligent acts) or agreed to in writing, shall any Contributor be
+    liable to You for damages, including any direct, indirect, special,
+    incidental, or consequential damages of any character arising as a
+    result of this License or out of the use or inability to use the
+    Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all
+    other commercial damages or losses), even if such Contributor
+    has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+    the Work or Derivative Works thereof, You may choose to offer,
+    and charge a fee for, acceptance of support, warranty, indemnity,
+    or other liability obligations and/or rights consistent with this
+    License. However, in accepting such obligations, You may act only
+    on Your own behalf and on Your sole responsibility, not on behalf
+    of any other Contributor, and only if You agree to indemnify,
+    defend, and hold each Contributor harmless for any liability
+    incurred by, or claims asserted against, such Contributor by reason
+    of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+    To apply the Apache License to your work, attach the following
+    boilerplate notice, with the fields enclosed by brackets "[]"
+    replaced with your own identifying information. (Don't include
+    the brackets!)  The text should be enclosed in the appropriate
+    comment syntax for the file format. We also recommend that a
+    file or class name and description of purpose be included on the
+    same "printed page" as the copyright notice for easier
+    identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+
+The Debian packaging is (C) 2006, Yaroslav Halchenko
+<debian@onerussian.com> and is licensed under the GPL, see
+`/usr/share/common-licenses/GPL'.
--- jsmath-fonts-sprite-1.0.orig/debian/changelog
+++ jsmath-fonts-sprite-1.0/debian/changelog
@@ -0,0 +1,12 @@
+jsmath-fonts-sprite (1.0-2) unstable; urgency=low
+
+  * Fixed debian/watch
+
+ -- Yaroslav Halchenko <debian@onerussian.com>  Fri, 09 Nov 2007 08:52:30 -0500
+
+jsmath-fonts-sprite (1.0-1) unstable; urgency=low
+
+  * Initial release
+
+ -- Yaroslav Halchenko <debian@onerussian.com>  Thu, 19 Oct 2006 20:58:52 -0400
+
--- jsmath-fonts-sprite-1.0.orig/debian/README.Debian
+++ jsmath-fonts-sprite-1.0/debian/README.Debian
@@ -0,0 +1,9 @@
+jsmath-fonts-sprite for Debian
+------------------------------
+
+jsmath-fonts-sprite is a preferable way to handle rasterized fonts for
+jsMath since it does not require huge number of small files, but
+stores all symbols in 1 image. Advantages and drawbacks of sprite
+method are highlighted in /usr/share/doc/jsmath-fonts-sprite/README
+
+ -- Yaroslav O. Halchenko <debian@onerussian.com>, Fri, 20 Oct 2006 00:54:32 -0400
--- jsmath-fonts-sprite-1.0.orig/debian/README
+++ jsmath-fonts-sprite-1.0/debian/README
@@ -0,0 +1,122 @@
+From
+http://www.math.union.edu/~dpvc/jsMath/authors/spriteImageFonts.html
+
+The spriteImageFonts plugin
+
+    This is an experimental plugin designed to address some of the
+    important drawbacks to the traditional implementation of the
+    image-font fallback method in jsMath. Currently, each character in
+    each size in each font is a separate image, so there are tens of
+    thousands of tiny images. That means that there is a lot of
+    overhead both in terms of network traffic when the image fonts are
+    used and in storage space on the server to make image fonts
+    available. For those who must use FTP to move individual files to
+    the server, it can be quite painful to install the image fonts.
+
+    The spriteImageFonts plugin uses an alternative approach in which
+    one larger file stores the images of all the characters in a given
+    font, and only a small portion of that file is displayed when one
+    of its characters is needed. This has the advantage of reducing
+    the number of needed files by a factor of 128 (the number of
+    characters in each font), so they take up far less space on the
+    server, and there is less network activity needed when a user
+    requests image fonts.
+
+    To use this plugin, you need to download the sprite font images
+    (available on the jsMath download page) and put them in the jsMath
+    directory on your server. They are stored in a directory called
+    fonts-sprite, and can be used without replacing the existing fonts
+    directory, if desired. If you always use the spriteImageFonts, you
+    can remove (or not download in the first place) the fonts
+    directory and just use the fonts-sprite directory. If you are
+    using any of the extra fonts, you should download sprite-based
+    versions of those fonts as well and place them in the fonts-sprite
+    directory.
+
+    Then, on those pages where you want to use the sprite-based image
+    fonts, add the command:
+
+    <SCRIPT SRC="path-to-jsMath/plugins/spriteImageFonts.js"></SCRIPT>
+
+    before loading jsMath.js or the autoload plugin, but after setting
+    the jsMath variable (if you are customizing jsMath in other
+    ways). This will cause jsMath's image mode to use the new
+    sprite-based image fonts rather than the traditional image fonts.
+
+    Note that this is considered an experimental plugin, and so you
+    should use it with caution. The image-fonts are the main fallback
+    method for when the TeX fonts are not available, so you need to be
+    sure the benefits are worth the costs that are outlined in the
+    next section. Also, there is no guarantee that this plugin will be
+    maintained in later versions of jsMath. (If it turns out to be too
+    problematic, it may be dropped.)
+
+Known Problems with the spriteImageFonts plugin
+
+    The main reason to use sprite-based images is that they should
+    transfer to the user's browser faster (they should generate less
+    network traffic), and because they take up less room and fewer
+    files on the server.
+
+    Unfortunately, these benefits come at a cost. One problem is that
+    the clipping required to obtain the small images from within the
+    larger file is very delicate, and even a one-pixel error can be
+    disastrous, especially for fonts at smaller point sizes. While the
+    on-screen rendering works reasonably well, some browsers introduce
+    slight spacing errors in the printed versions of their pages, most
+    likely due to the changes in font metrics between the screen and
+    printer versions of the fonts. These errors can lead to slight
+    clipping of characters in the printed output.
+
+    A more serious problem is that some browsers render the clipped
+    images slower than they do the individual images (presumably they
+    are rendering the whole image even though most of it is not
+    shown). This is particularly noticable in MSIE on the PC, which is
+    already the slowest browser that handles jsMath, making it even
+    slower. Indeed, the images that use alpha-channel transparency are
+    so slow in MSIE on the PC (due to the rediculous apppraoch used to
+    handle alpha-channel transparency in MSIE) that the non-alpha
+    images are used by default (in MSIE only) unless the user
+    specifically requests alpha transparency.
+
+    Speed also seems to be an issue with Firefox on the PC when the
+    high-resolution images for printing are used. This causes Firefox
+    to run unexpectedly slowly, though it does not seem to affect the
+    normal screen resolution images. In addition, Firefox's print
+    preview on the PC will show the images located in the wrong
+    positions, but they will print properly anyway.
+
+    Opera on both the PC and the Mac has significant problems with the
+    sprite-based image fonts. Due to a serious alignment bug in Opera,
+    the sprite images can't be handled as standard images, so are
+    implemented using background images instead. This means they can't
+    be scaled by jsMath, and so the scaling and hi-res printing
+    options are disabled in Opera. Since Opera automatically scales
+    images when you zoom the page, this is not really much of a
+    problem, though it does mean you can't get high-resolution
+    printing. Since background images are not printed by default,
+    however, in order for Opera users to print pages containing
+    mathematics, they need to turn on printing of background images in
+    the print dialog box. This works fine on the Mac, but on the PC,
+    the images don't print properly, even though they show up
+    correctly in the print preview. (It looks like the positioning of
+    the background image is not being adjusted correctly for the
+    resolution of the printer, and so the font image is positioned
+    incorrectly and the wrong characters are printed.)
+
+    Finally, some older browsers do not implement the clipping that is
+    required to make the sprite-based fonts work, and so the image
+    modes are disabled for these. That means that if the user does not
+    have the TeX fonts installed, the only option will be unicode
+    fonts. These are not as effective as the traditional image fonts,
+    so changing to sprite-based fonts will cause a reduciton in
+    quality for users of these older browsers.
+
+    All of these problems make the sprite-based image fonts less
+    reliable than the individual-image fonts, and so the sprite images
+    have not been incorporated into jsMath.js directly. You may choose
+    to use the sprite fonts if the reduction in storage space or
+    number of files is critical enough to compensate for the problems
+    that using them introduces, but it is a decision that should not
+    be taken lightly, as it will inconvenience some of your users,
+    perhaps significantly.
--- jsmath-fonts-sprite-1.0.orig/debian/watch
+++ jsmath-fonts-sprite-1.0/debian/watch
@@ -0,0 +1,11 @@
+# Watch control file for uscan
+# See uscan(1) for format
+
+# Compulsory line, this is a version 3 file
+version=3
+
+# Uncommment to examine a FTP server
+http://sf.net/jsmath \
+ jsMath-fonts-sprite-([0-9].*)\.zip debian dh_wraporig
+
+
--- jsmath-fonts-sprite-1.0.orig/debian/rules
+++ jsmath-fonts-sprite-1.0/debian/rules
@@ -0,0 +1,55 @@
+#!/usr/bin/make -f
+# -*- makefile -*-
+# Sample debian/rules that uses debhelper.
+# This file was originally written by Joey Hess and Craig Small.
+# As a special exception, when this file is copied by dh-make into a
+# dh-make output file, you may use that output file without restriction.
+# This special exception was added by Craig Small in version 0.37 of dh-make.
+
+# Uncomment this to turn on verbose mode.
+#export DH_VERBOSE=1
+
+DESTDIR=$(CURDIR)/debian/jsmath-fonts-sprite
+JSMDIR=$(DESTDIR)/usr/share/jsmath
+
+build: build-stamp
+
+build-stamp:
+	dh_testdir
+	unzip -q -d jsMath jsMath-*.zip
+	touch build-stamp
+
+clean:
+	dh_testdir
+	dh_testroot
+	rm -f build-stamp
+	rm -rf jsMath
+	dh_clean
+
+install:
+	dh_testdir
+	dh_testroot
+	dh_clean -k
+	dh_installdirs
+
+	install -m 755 -d $(JSMDIR)
+	cp -rp jsMath/* $(JSMDIR)/
+
+# Build architecture-independent files here.
+binary-indep: build install
+	dh_testdir
+	dh_testroot
+	dh_installchangelogs
+	dh_installdocs debian/README
+	dh_compress
+	dh_fixperms
+	dh_installdeb
+	dh_gencontrol
+	dh_md5sums
+	dh_builddeb
+
+# Build architecture-dependent files here.
+binary-arch: build install
+
+binary: binary-indep
+.PHONY: build clean binary-indep binary-arch binary install configure
--- jsmath-fonts-sprite-1.0.orig/debian/compat
+++ jsmath-fonts-sprite-1.0/debian/compat
@@ -0,0 +1 @@
+4
