hyperlatex-users — For developers and users of hyperlatex

Re: [hlx] \image and ps2image

[Ralf H. <hem...@ri...>]

Hello, maybe I should also say something here.

Jay is right. The modification does not add any functionality that
hyperlatex did not have before.

Hyperlatex cannot deal with directories in filenames. And my suggested
modifications did not mess with that.

 >>> \begin{image}{directory/name} ... \end{image} Hyperlatex couldn't
 >>>  deal with that before and it can't deal with it now.

Well, with hyperlatex-relative-prefix it is easy. Only the line
following ;rhx: has been added to the hyperlatex 2.7 code.
(Of course one has to do this also for hyperlatex-format-gif and
hyperlatex-format-img.)

(defun hyperlatex-format-image ()
   (let* ((opt (hyperlatex-parse-optional-argument))
	 (tags (if opt opt ""))
	 (resolution (hyperlatex-parse-optional-argument))
	 (dpi (hyperlatex-parse-optional-argument))
	 (url (hyperlatex-parse-required-argument)))
     ;rhx: added the following line
     (setq url (concat (hyperlatex-relative-prefix) url))
     (delete-region hyperlatex-command-start
		   (progn (search-forward "\\end{image}") (point)))
     (hyperlatex-delete-whitespace)
     (hyperlatex-pop-stacks)
     (hyperlatex-gen
      (format (concat "img src=" hyperlatex-meta-dq "%s."
                      hyperlatex-imagetype hyperlatex-meta-dq " %s /")
	     url tags))))
}

If I am not wrong then everything works fine if htmldir is ".".

 > It would be easy enough to have ps2image create the necessary
 > directory, but another problem is that file.ps will be created as
 > ./dir/file.ps.

Well, Jay, you are again right. I did not think of this because my
htmldir is ".". But again, hyperlatex is not supposed to handle things
like \begin{image}{directory/name} ... \end{image}. So at least we have 
not introduced a bug that wasn't there before.

 > This would occur (in texfile.makeimage) before ps2image is called,
 > and if htmldirectory isn't ".", then the png file will be
 > htmldir/dir/file.png.  So both directories ./dir and htmldir/dir
 > would have to exist.  It would be nice if file.ps were just
 > ./file.ps, but the ps file name is made by TeX based on the image
 > name dir/file, and I don't know how to (reasonably) strip off the
 > directory name in TeX.

Hmmm, I cannot think of a quick solution to strip off the directory part 
with latex, but it should work somehow.

But let me ask you about a change. At the moment I have to write some 
html page that has several places where some math occurs. Having learnt 
about \begin{image}{file}..\end{image}, I now simply put the math there 
and let hyperlatex generate a .png for the html document. What bothers 
me most is that I have to give a file name for every image environment 
and additionally these filenames have to be unique over the document.

In the \endimage code in hyperlatex.sty appears \the\@imagecount. So why 
not replace the line

\jobname.dvi\space>\space\im...@na...^^J%

by

\jobname.dvi\space>\space\jobname\the\@imagecount.ps^^J%

and the same with

ps2image\space -res\space \image@resolution\space \im...@na...%

replaced by

ps2image\space -res\space \image@resolution\space
   \jobname\the\@imagecount.ps%

I would then even add code to ps2image to remove the .ps file.
Who would ever need the .ps file?

Maybe, I do not understand the initial intention, but approximately that 
would be my suggestion to
1) Overcome the directory problem in the image environment and
2) the tedious work of always having to invent a new filename.



------------------------------------------------------------------
Just some other thoughts about directories in arguments.

Tom maybe you remember that I modified the \xname command in my 
rhxhlx/rhxxname.hlx package to deal with the issue of having something like

\xname{dir/file}

and correctly creating the following section into

htmldir/dir/file.html

In case the rhxpanel is active, it will also take the panel icons from
htmldir/pics/../dir
if there appears \renewcommand{\HlxIcons}{pics} in the .tex file.

Via rhxxname.hlx I modify certain command of hyperlatex.el in order to
make the directory relative to the target place of the html file.

All arguments to pictures (actually to \htmlicon) should be understood
relative to htmldirectory (even if the current node will be generated in
a subdirectory of htmldir).

The code (from rhxxname.hlx)

(defun hyperlatex-relative-prefix ()
   (setq hyperlatex-rel-prefix "")
   (setq rhx-tmp (hyperlatex-fullname hyperlatex-node-number))
   (while (string-match "/" rhx-tmp)
     (setq rhx-tmp (replace-match "" t t rhx-tmp))
     (setq hyperlatex-rel-prefix (concat hyperlatex-rel-prefix "../" )))
   hyperlatex-rel-prefix)

(defun hyperlatex-relative-fullname (node-number)
   (concat (hyperlatex-relative-prefix)
           (hyperlatex-fullname node-number)))

simply takes the directory part of the current node (which is identical
to the directory part of the corresponding \xname command) and generates
the corresponding directory string that must be prepended to reach
htmldir from the current node.

Example: \xname{dir1/dir2/file}
html-relative-prefix --> ../../
So ../../dir1/dir2 should be equal to htmldirectory.
Note that I do not handle absolute paths, because I think that every
generated stuff should go below htmldirectory.


Best

Ralf

Re: [hlx] \image and ps2image

[Jay B. <bel...@tr...>]

tom sgouros <to...@as...> writes:

>  >On Wed, 25 Aug 2004 22:09:12 -0500, Jay Belanger wrote:
>
>>> Wait a minute.  I think I've been asleep.  So the change, intended to
>>> deal with a warning (not an error), has introduced the possibility of
>>> an error in the default case?
>
>> No; I was terribly unclear.
>> No new errors (that I'm aware of) were added; I was responding to
>> Ralf's musings about adding other functionality.
>
> Yes, but there was a warning, when hyperlatex got to the line that
> read 'mv file.gif .', and now there's an error when a directory
> doesn't exist to store the output file.

Right, but there would have been before, too.
Given \begin{image}{imagename},
before Hyperlatex would try
 1)  dvips ... file.dvi -o imagename.ps
 2)  ps2image ... imagename.ps imagename.png
 3)  mv imagename.png htmldirectory/imagename.png
and 3) would give an error if htmldirectory was "."
Now, Hyperlatex will try
 1) dvips ... file.dvi -o imagename.ps
 2) ps2image ... imagename.ps htmldirectory/imagename.png
and there's no need for 3).
If the htmldirectory is ".", then what happens now is just like
before, without the now unnecessary move.
If htmldirectory is something else, then all the new behavior does is
(effectively) roll steps 2) and 3) into step 2).
In both cases there will be problems if imagename is of the form
imagedirectory/name.  If ./imagedirectory doesn't exist, both will
fail at step 1).  If htmldirectory/imagedirectory doesn't exist, then
before Hyperlatex would fail at step 3, now it will fail at step 2)
(because step 3) has been rolled into step 2)).

> Or perhaps I'm missing something.

Or maybe I am.

> This was only to move files from the source to the html directory, but
> it's more or less the same problem you're dealing with.  Wouldn't it
> be better to have an \imagepath command instead of messing with the
> command syntax?  Plus that does away with the confusion about what the
> directory is supposed to mean.

If you want the images in a different directory than the html files,
that sounds like a good idea.

>> \begin{image}{directory/name}
>> ...
>> \end{image}
>> Hyperlatex couldn't deal with that before and it can't deal with it
>> now.
>
> In this case, it's not really clear what the right behavior should
> be.  That's the real hurdle.  It's not possible from this syntax to
> tell what is intended: is this directory where the file comes from or
> where it's going?  The meaning simply isn't clear, to a person or a
> sophisticated text editing program.

Since Hyperlatex is creating the image files, I'm not sure how this
could indicate where the file is coming from.
I've been satisfied with the current behavior (the imagename can't
be of the form imagedirectory/name) so I haven't thought
about this a whole lot, so I may well be missing something.

Jay

Re: [hlx] \image and ps2image

[tom s. <to...@as...>]

 >On Wed, 25 Aug 2004 22:09:12 -0500, Jay Belanger wrote:

>> Wait a minute.  I think I've been asleep.  So the change, intended to
>> deal with a warning (not an error), has introduced the possibility of
>> an error in the default case?

> No; I was terribly unclear.
> No new errors (that I'm aware of) were added; I was responding to
> Ralf's musings about adding other functionality.

Yes, but there was a warning, when hyperlatex got to the line that
read 'mv file.gif .', and now there's an error when a directory
doesn't exist to store the output file.  Or perhaps I'm missing
something.  

> I don't think that Hyperlatex used to be able to deal with directories
> in the image names (I just double checked --- it couldn't), it can't
> now, either.  My unclear, long-winded message was only meant to say I
> didn't know of a good way of dealing with things like

No, it didn't.  TeX doesn't do so well here, either.  But that's why
packages like psfig.sty have a \psfigurepath command, to specify the
source file.  I put this in my siteinit to deal with more-or-less the
same problem when I was making a psfig parallel for hyperlatex:

\HlxEval{ 
(put 'figpath        'hyperlatex 'hyperlatex-ts-set-figurepath)
(put 'figuremove     'hyperlatex 'hyperlatex-ts-figuremove)

(defvar hyperlatex-ts-figurepath)

(defun hyperlatex-ts-set-figurepath ()
  (setq hyperlatex-ts-figurepath
  (hyperlatex-parse-required-argument))) 

(defun hyperlatex-ts-figuremove ()
  (if hyperlatex-final-pass 
    (let ((file (hyperlatex-parse-required-argument)))
      (let ((infile  (concat hyperlatex-ts-figurepath "/" file))
            (outfile (concat hyperlatex-html-directory "/" file)))
        (message "Copying %s to %s" infile outfile)
        (copy-file infile outfile t)))))
}
\newcommand{\figureplace}[7][\relax]{
\begin{figure}[#3]
  \label{#4}
  \begin{center}\xmlattributes{img}{border="0"}
    \EmptyP{#7}{\xlink{\htmlimage{#6}}{#7}}{\htmlimage{#6}}
    \caption{#2}
  \end{center}
\end{figure}
\figuremove{#6}}


This was only to move files from the source to the html directory, but
it's more or less the same problem you're dealing with.  Wouldn't it
be better to have an \imagepath command instead of messing with the
command syntax?  Plus that does away with the confusion about what the
directory is supposed to mean.


> \begin{image}{directory/name}
> ...
> \end{image}
> Hyperlatex couldn't deal with that before and it can't deal with it
> now. 

In this case, it's not really clear what the right behavior should
be.  That's the real hurdle.  It's not possible from this syntax to
tell what is intended: is this directory where the file comes from or
where it's going?  The meaning simply isn't clear, to a person or a
sophisticated text editing program.

-tom

 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net

Re: [hlx] \image and ps2image

[Jay B. <bel...@tr...>]

tom sgouros <to...@as...> writes:

> Wait a minute.  I think I've been asleep.  So the change, intended to
> deal with a warning (not an error), has introduced the possibility of
> an error in the default case?

No; I was terribly unclear.
No new errors (that I'm aware of) were added; I was responding to
Ralf's musings about adding other functionality.
I don't think that Hyperlatex used to be able to deal with directories
in the image names (I just double checked --- it couldn't), it can't
now, either.  My unclear, long-winded message was only meant to say I
didn't know of a good way of dealing with things like
\begin{image}{directory/name}
...
\end{image}
Hyperlatex couldn't deal with that before and it can't deal with it
now. 

Next time I'll try to get more sleep before I write.
Or maybe more caffeine....

Jay

Re: [hlx] \image and ps2image

[tom s. <to...@as...>]

Wait a minute.  I think I've been asleep.  So the change, intended to
deal with a warning (not an error), has introduced the possibility of
an error in the default case?  I'm not sure that's progress.  Wouldn't
it have been easier to make the Makefile (the original source of the
problem) behave?

-tom

 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net

Re: [hlx] \image and ps2image

[Jay B. <bel...@tr...>]

Ralf HEMMECKE <ra...@he...> writes:
...
> The only problem that remains is the following.
> It is now possible to say
>
> \begin{image}{dir/file} ... \end{image}
>
> and the picture file.png (or file.gif) will be generated in the
> subdirectory 'dir', but only if 'dir' already exists. There is no code
> at the moment, that would generate such a missing directory.

It would be easy enough to have ps2image create the necessary
directory, but another problem is that file.ps will be created as
./dir/file.ps.  This would occur (in texfile.makeimage) before 
ps2image is called, and if htmldirectory isn't ".", then the png file
will be htmldir/dir/file.png.  So both directories ./dir and
htmldir/dir would have to exist.  It would be nice if file.ps were just
./file.ps, but the ps file name is made by TeX based on the image name
dir/file, and I don't know how to (reasonably) strip off the directory
name in TeX.

For those who haven't looked at the TeX code recently, the TeX code
itself creates a shell script to call dvips and ps2image to create
file.png.  The shell script looks roughly like
  dvips ... texfile.dvi > \im...@na...
  ps2image .... \im...@na... htmldirectory\im...@na...g
The TeX command \image@name is given the value imagename from
\begin{image}{imagename}.  So if imagename contains a directory, the
the ps file will be created in that directory relative to ".", but 
the png file will be put in that directory relative to htmldirectory.

One possibility is to add the htmldirectory to the ps file name in
TeX, and then, assuming that "hyperlatex texfile" is run before
"hyperlatex -image texfile", have the necessary directories created by
emacs.

(I'm not sure how clear I'm being....)

Jay

Re: [hlx] \image and ps2image

[Jay B. <bel...@tr...>]

tom sgouros <to...@as...> writes:
...
> If you've tested it, go ahead.  It sounds like a good idea to me.

Okay; it's been committed.

Jay

Re: [hlx] \image and ps2image

[tom s. <to...@as...>]

 >On Wed, 25 Aug 2004 08:17:46 -0500, Jay Belanger wrote:

> This seems to work pretty well for me.
> Would there be any problems with commiting it?

Jay:

If you've tested it, go ahead.  It sounds like a good idea to me.

-tom

 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net

Re: [hlx] \image and ps2image

[Jay B. <bel...@tr...>]

Ralf HEMMECKE <ra...@he...> writes:

> Hello,
>
> I had a problem when using
>
>     hyperlatex -image
>
> in conjunction with the default \htmldirectory{.}.
>
> hyperlatex produces a file.makeimage with the command
>
>     mv file.png .
>
> Of course this results in an error since the file is already there and
> cannot be moved to itself.
>
> Yes, it would be possible to convince my Makefile to ignore such an
> error, but I think I have another solution. See the modified files in
> the attachment.

This seems to work pretty well for me.
Would there be any problems with commiting it?

Jay

[hlx] \image and ps2image

[Ralf H. <ra...@he...>]

Hello,

I had a problem when using

    hyperlatex -image

in conjunction with the default \htmldirectory{.}.

hyperlatex produces a file.makeimage with the command

    mv file.png .

Of course this results in an error since the file is already there and
cannot be moved to itself.

Yes, it would be possible to convince my Makefile to ignore such an
error, but I think I have another solution. See the modified files in
the attachment.

hyperlatex.sty:
    I have modified \endimage to produce a command suitable for the
    modified ps2image. So instead of

    ps2image -png ... file.ps > file.png
    mv file.png .

    it will produce

    ps2image ... file.ps htmldir/file.png

ps2image:
    This script recognises the target filetype from a parameter that ends
    in .png or .gif. The extension .ps is always assumed to be the input
    filename.
    Since the target filename includes the targed directory, an additional
    move of the file is unnecessary.

    It even seems ps2image is a bit shorter. ;-)


The only problem that remains is the following.
It is now possible to say

\begin{image}{dir/file} ... \end{image}

and the picture file.png (or file.gif) will be generated in the
subdirectory 'dir', but only if 'dir' already exists. There is no code
at the moment, that would generate such a missing directory.

Maybe I could think about putting some extension code into my rhxxname
package, but this will take some more spare time.

Best regards
Ralf

Re: [hlx] \image???

[tom s. <to...@as...>]

 >On Fri, 20 Aug 2004 16:09:34 -0500, Jay Belanger wrote:

>> Unfortunately, I cannot find anything about that command in
>> the documentation. Without a proper documentation it is useless.
>> 
>> Is there someone who could document it into the manual?

> It's in the manual that comes with hyperlatex, just not the online
> manual.  That should be changed, of course.

Quite right.  Here I was apologizing for not putting it in the manual,
but I did.  (Or you did.  Is my memory going?  Maybe it's just too hot
around here.)  I'll fix the online version.

-tom


 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net

Re: [hlx] \image???

[Jay B. <bel...@tr...>]

Hi Ralf,

> I am just looking through hyperlatex.el (version 2.7). I've found that
> there is now
>
> (put 'image     	'hyperlatex 'hyperlatex-format-image)
>
> Seemingly, I could use the command \image in an hyperlatex document.

Actually, it's the environment
\begin{image}{name}
...
\end{name}

> From the code I would guess that it does something similar to the gif
> environment. 

Yes; it's a replacement for the gif environment.

> Unfortunately, I cannot find anything about that command in
> the documentation. Without a proper documentation it is useless.
>
> Is there someone who could document it into the manual?

It's in the manual that comes with hyperlatex, just not the online
manual.  That should be changed, of course.

> The same for \imagetype.

Also in the manual, but not the index.
I commited a change to hyperlatex.ind to fix that (but something
went weird when I was supposed to make a changelog entry.)

Jay

[hlx] \image???

[Ralf H. <ra...@he...>]

Hello,

I am just looking through hyperlatex.el (version 2.7). I've found that 
there is now

(put 'image     	'hyperlatex 'hyperlatex-format-image)

Seemingly, I could use the command \image in an hyperlatex document.
 From the code I would guess that it does something similar to the gif 
environment. Unfortunately, I cannot find anything about that command in 
the documentation. Without a proper documentation it is useless.

Is there someone who could document it into the manual?

The same for \imagetype.

Thanks

Ralf

Re: [hlx] How to generate <P> tags ?

[<to...@as...>]

------- Forwarded Message

Date: Thu, 3 Jun 2004 04:15:53 +0800
From: Yajun Wang <ya...@cs...>
To: tom sgouros <to...@as...>
Subject: Re: [hlx] How to generate <P> tags ?

Hi Tom:

I found the problem.

Whenever I use:

\htmlheading[2]{Section}
blablabla..........

It will not generate <p> for the "blabla...."

I have to insert an empty line that hyperlatex will treat
the following as a paragraph...


anyway, thanks


regards,
yalding


On Wed, Jun 02, 2004 at 04:01:42PM -0400, tom sgouros wrote:
>
> Yajun:
>
> The default behavior is to generate <p> tags.  Perhaps you could post
> the smallest file that is giving you trouble?  (The </p> tags are not
> generated.)
>
> -tom
>
>  ------------------------
>  tomfool at as220 dot org
>  http://sgouros.com =20
>  http://whatcheer.net

------- End of Forwarded Message



 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net

[hlx] How to generate <P> tags ?

[Yajun W. <ya...@cs...>]

Hi all:

I found that hyperlatex do not generate <P> tag by default.
But I want to use <P> because it is helpful in css files.

Is there anyone know how to do it?

thanks.

regards,
yalding

[hlx] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

Re: [hlx] Hyperlatex 2.7 on Emacs 21.3.50.1 on Mac OS X 10.3... not?

[tom s. <to...@as...>]

Uli:

Can you post or send me the smallest fraction of the file you can make
that re-creates the problem?

-tom

 ------------------------
 tomfool at as220 dot org
 http://sgouros.com  
 http://whatcheer.net

Re: [hlx] Hyperlatex 2.7 on Emacs 21.3.50.1 on Mac OS X 10.3... not?

[Uli W. <ul...@sl...>]

Tom,

You are right, the trailing "/" is required. This got me so far with 
translating the manual:

--------- Begin Hyperlatex output
Parsing ...
Package "siteinit" inserted
Package "init" not found...
Package "article" inserted
Reading site init file for Hyperlatex version 2.7:
Package "english" inserted

Hyperlatex ERROR: Unknown command: htmltopname
Hint: Try running Latex, it may give a better error message.

Error discovered here:
 >>>{Top}
\htmlmathitalic{1}

\renewcommand{\HlxSeqPrevUrl}{\HlxPrevUrl}
\renewcommand{\HlxSeqNextUrl}{\HlxNextUrl}
\renewcommand{\HlxSeqPrevTitle}{\HlxPrevTitle}
\renewcommand{\HlxSeqNextTitle}{\HlxNextT ...
----- End Hyperlatex output

The package loading is correct, there is no "init" package (i never 
made one).
The offending "htmltopname" is in siteinit.hlx.

I can comment that one out but then get stuck later on, so that is not 
an option.

I should maybe mention that I don't have a (La)TeX installation on this 
computer.
I don't think I need one for Hyperlatex to work (right?)

I do not have Babel and the corresponding line in the manual source is 
commented out (as per the readme).

Uli

On May 17, 2004, at 10:10, tom sgouros wrote:

>
>> On Mon, 17 May 2004 09:37:31 -0700, Uli Wienands wrote:
>
>> My hyperlatex-extension-dirs variable looks like this
>> (describe-variable):
>
>> hyperlatex-extension-dirs's value is
>> ("~/" "/Applications/Emacs/Hyperlatex-2.7/hlx")
>
> Try it like this:
>
> ("~/" "/Applications/Emacs/Hyperlatex-2.7/hlx/")
>
> I think the following slash is significant.
>
> -tom
>
>  ----------------------------------------
>  tomfool at as220 dot org    401-861-2831
>  http://sgouros.com

Re: [hlx] Hyperlatex 2.7 on Emacs 21.3.50.1 on Mac OS X 10.3... not?

[tom s. <to...@as...>]

 >On Mon, 17 May 2004 09:37:31 -0700, Uli Wienands wrote:

> My hyperlatex-extension-dirs variable looks like this 
> (describe-variable):

> hyperlatex-extension-dirs's value is
> ("~/" "/Applications/Emacs/Hyperlatex-2.7/hlx")

Try it like this:

("~/" "/Applications/Emacs/Hyperlatex-2.7/hlx/")

I think the following slash is significant.

-tom

 ----------------------------------------
 tomfool at as220 dot org    401-861-2831
 http://sgouros.com

[hlx] Hyperlatex 2.7 on Emacs 21.3.50.1 on Mac OS X 10.3... not?

[Uli W. <ul...@sl...>]

I have been using Hyperlatex 2.5 on Emacs 18.59 on Mac OS 8.6 for 
years. Now I switched to Mac OS X and am running Andrew Choi's Emacs 
21.3.50 and am trying to get Hyperlatex 2.7 to work.

The way I am using HL is from within Emacs, i.e. I am editing my source 
file and then say hyperlatex-format-buffer to compile the source into 
html. This always worked in my previous setup.

Doing as preescribed in the head of hyperlatex.el I get the autoload to 
work, i.e. hyperlatex-format-buffer starts up. However, trying to 
compile the manual it hangs when it hits \htmlpanelfield{}. Moreover, 
it does not find *any* of the packages it wants to load. The failure to 
load packages is where I am mystified: I have left hyperlatex.el where 
it is in the distro (hlx folder in Hyperlatex-2.7 folder) and moved the 
whole thing into the Emacs directory where Emacs also resides.

Here is the error I get:
----------------------------
Parsing ...
Package "siteinit" not found...
Package "init" not found...
Package "article" not found...
Package "verbatim" not found...
Package "longtable" not found...
Package "makeidx" not found...
Package "frames" not found...
Package "simplepanels" not found...

Hyperlatex ERROR: Unknown command: htmlpanelfield
Hint: Try running Latex, it may give a better error message.

Error discovered here:
 >>>{Contents}{hlxcontents}
\htmlpanelfield{Index}{hlxindex}
------------------------------------

My hyperlatex-extension-dirs variable looks like this 
(describe-variable):

hyperlatex-extension-dirs's value is
("~/" "/Applications/Emacs/Hyperlatex-2.7/hlx")

which is as intended, and most packages are in the 2nd directory, 
specifically site-init, longtable, ....
I assume the htmlpanelfield fails because it is def'd in a local 
package that is not found.

Any help would be appreciated.

Uli Wienands

Re: [hlx] release of Hyperlatex 2.7

[Roland S. <st...@an...>]

On Sun, 2004-05-02 at 23:11, to...@as... wrote:
>   Hyperlatex version 2.7 is available at hyperlatex.sourceforge.net, 
>   to those who would like it.

Thanks, Tom!

I integrated it into Debian/unstable (which will automatically migrate
to testing and hopefully the next stable release) to be available for
you shortly.

All reports are appreciated.

bye,
  Roland

[hlx] release of Hyperlatex 2.7

[<to...@as...>]

Rather than wait for me to figure out the ins and outs of writing
configure and install scripts, I've forged ahead and would like to
announce that

  Hyperlatex version 2.7 is available at hyperlatex.sourceforge.net, 
  to those who would like it.

The thumbnail version of release notes:

This version:

  o Removes dependency on GIF images, replacing them with PNG.  (This
    is relevant both to the documentation and to the bitmaps generated
    for the "image" environment.
  o Includes some new contributed code, notably Ralf Hemmecke's work.

That's all, except that a bug fix submitted in 1999 for version 2.4
was somehow either incompletely applied to that version, or partially
backed out of version 2.5.  (I don't have the records to determine
what went wrong.)  The bug was related to the sequential.hlx package,
and would cause hyperlatex to fail when it was encountered.  The fix
has been re-applied for version 2.7.

Thanks for your attention,

-tom

 ----------------------------------------
 tomfool at as220 dot org    401-861-2831
 http://sgouros.com

Re: [hlx] GIFs and PNGs

[Roland S. <st...@an...>]

On Wed, 2004-04-28 at 23:44, Steven Augart wrote:
> Is there any way I can help make such a release happen?  I am packing 
> up Jikes RVM for Debian.  The user's guide is written using 
> Hyperlatex.  Because "hyperlatex" is still not in "main" on Debian, 
> including the Hyperlatex-formatted user's manual would keep us from 
> being in main on Debian.  And I would really like to ship with a 
> working user's manual.

You can decide to (temporarily) put the precompiled manual (and the
sources) into the package. Then, it doesn't need to build-depend on
hyperlatex. That's what the python maintainers in Debian did when I had
to move latex2html to non-free.

> Alternatively, Roland, would you be willing to put a snapshot into 
> Debian/testing, as a stopgap?

Unfortunately, since the release of Debian "sarge" is near (supposedly
some weeks ahead), and Debian is known for rather staying with "stable"
packages than with latest releases, I certainly can't do that right now.

This doesn't mean that I won't incorporate new versions of packages into
Debian, but at this point in the release cycle, we prefer putting the
latest versions of upstream (i.e. Tom's hyperlatex :) rather to the
"experimental" distribution. When after some time the bug reports don't
overwhelm, we can decide on a case by case basis to move it to
unstable/testing.

After the release of the next stable Debian version, it is no problem
anymore.

bye,
  Roland

[hlx] next release

[<to...@as...>]

Will happen within the next week, or at least that's my plan.

-tom

 ----------------------------------------
 tomfool at as220 dot org    401-861-2831
 http://sgouros.com

[hlx] GIFs and PNGs

[Steven A. <au...@wa...>]

I read in the message 
http://www.mail-archive.com/hyp...@li.../msg00001.html
that Hyperlatex can now use PNGs, but that we are waiting on a release.

Is there any way I can help make such a release happen?  I am packing 
up Jikes RVM for Debian.  The user's guide is written using 
Hyperlatex.  Because "hyperlatex" is still not in "main" on Debian, 
including the Hyperlatex-formatted user's manual would keep us from 
being in main on Debian.  And I would really like to ship with a 
working user's manual.

Alternatively, Roland, would you be willing to put a snapshot into 
Debian/testing, as a stopgap?

Thanks,

--Steve Augart

-- 
Steven Augart

Jikes RVM, a free, open source, Virtual Machine:
http://oss.software.ibm.com/jikesrvm