Re: source for hz algorithm

2003-01-29 Thread Sébastien Aperghis-Tramoni
On Wednesday, January 29, 2003, at 09:05 AM, Victor Mote wrote:


BTW, I looked for but did not find licensing information at tug  ctan
licensing information, as well as in my Norman Walsh book Making TeX 
Work.
Does it use a GPL? If it had a compatible licensing scheme, it would 
sure
seem to make sense to use as much of the TeX work as possible.

Information about the licenses used by the TeX related softwares
are available on this page:
  http://www.ctan.org/tex-archive/help/Catalogue/licenses.html

The core of TeX, the files written by Donald Knuth, doesn't seem to
be covered by a particular license apart from the README file
  http://www.ctan.org/tex-archive/systems/knuth/tex/README

The TeX FAQ confirms that TeX simply is free:
  http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree


Sébastien Aperghis-Tramoni
 -- - --- -- - -- - --- -- - --- -- - --[ http://maddingue.org ]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Getting FOP running on Mac OS X

2002-12-09 Thread Sébastien Aperghis-Tramoni
On Monday, December 9, 2002, at 11:54 PM, Victor Mote wrote:


Clay Leeds wrote:


The files were ZIP'd, and when they were unZIP'd using Stuffit 
Expander,
the avalon JAR file's long filename was changed from:

   avalon-framework-cvs-20020315.jar

to:

   avalon-framework-cvs-20020315.j

Adding ar at the end of that filename, resolved the problem, and I am
able to run FOP on my Mac. Unfortunately, it took a few days to
figure out this problem.

First, thanks for the input. I'll be glad to update the FAQ, but I am a
little confused about what to put into it. The file name was truncated 
after
31 characters, which is too odd of a number to seem to have been done on
purpose by StuffIt. What caused the filename truncation? Without
understanding that, I am not sure how to help.

This is because 31 characters was the file name limit under Mac OS 
Classic.
StuffIt Expander being a carbonized application, it may still contains 
code
that make sure filenames are truncated to 31 characters.

The Good Way to extract Unix archives under Mac OS X is to open the
Terminal and use gzip, gnutar and zip/unzip.

Java Home. Many Java applications require the identification of a Java
Home directory during installation. The equivalent on Mac OS X should
always be /Library/Java/Home. This is actually a symbolic link to the
current installed J2SE version, and allows access to the bin 
subdirectory
where command line tools such as java, javac, etc. exist as expected. 
The

I am not a Mac guy, so please excuse my ignorance. Is this something 
that
Mac people should already know? In other words, I wonder whether it is 
even
appropriate to address this in FOP doc as it is primarily a sysadmin 
issue,
or at least a Mac or Java issue. Also, what if /Library/Java/Home 
points to
a 1.1 or 1.2 java runtime? If we tell the user to use that, then FOP 
doesn't
work. Again, I am not sure what to recommend here.

Java under Mac OS X started with JDK 1.3. JDK 1.4 is in beta test.
The JAVA_HOME issue should already be known by most Java
programmers that work under Mac OS X, but it may be useful to
recall the trick.


Sébastien Aperghis-Tramoni
 -- - --- -- - -- - --- -- - --- -- - --[ http://maddingue.org ]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]