Henning Sannemann | 4 Dec 2003 09:45
Picon

rel-0-7-8; error LaTeX found no preview images

To: preview-latex-bugs <at> lists.sourceforge.net
Subject: rel-0-7-8; error LaTeX found no preview images
X-Reporter-Void-Vars-Found: image-types
--text follows this line--

Remember to cover the basics.  Including a minimal LaTeX example
file exhibiting the problem might help.

Hallo,
inzwischen läuft Preview-Latex ziemlich gut und ich bin begeistert!!
Der Hinweis, dass durch make wahrscheinlich Dateien für den Emacs und
nicht für den XEmacs gebaut worden waren, war goldrichtig.
In dem Beispieldokument circ.tex gibt es aber noch ein paar Stellen,
mit denen preview latex nicht klar kommt.
1. Es wird keine Vorschau der itemize Umgebung erstellt
2. Referenzen /ref{irgendwas} bleiben unverändert.
3. Der Versuch, Fussnoten einzufügen und die Vorschau zu starten,führt
   zur Fehlermeldung: ,,error LaTeX found no preview images''
4. In Section 2 (Die gerade Linie) erscheint statt
    ,,Wird nun f >= 0.5, wie sich durch den Vergleich...''
    von Preview Latex der Text
    ,,Wird nun $\ifPreview\special{ps: junk}\fi f \geq 0.5$, wie sich durch
    den Vergleich...''

Muss ich noch irgendwas konfigurieren oder nachinstallieren?
Über Hilfe würde ich mich sehr freuen.

Viele Gruesse und vielen Dank
Henning Sannemann

(Continue reading)

David Kastrup | 4 Dec 2003 12:17
Picon
Picon

Re: [preview-latex-devel] rel-0-7-8; error LaTeX found no preview images

Henning Sannemann <hsannem <at> mi.uni-koeln.de> writes:

> To: preview-latex-bugs <at> lists.sourceforge.net
> Subject: rel-0-7-8; error LaTeX found no preview images
> X-Reporter-Void-Vars-Found: image-types
> --text follows this line--
> 
> Remember to cover the basics.  Including a minimal LaTeX example
> file exhibiting the problem might help.
> 
> Hallo,
> inzwischen läuft Preview-Latex ziemlich gut und ich bin begeistert!!

Uh, reverting you to the bug report list has the main purpose that it
does not remain my sole responsibility to answer to problems.  This
purpose is defeated if you choose a language in which few people may
be proficient here.

> dem Beispieldokument circ.tex gibt es aber noch ein paar Stellen,
> mit denen preview latex nicht klar kommt.  1. Es wird keine Vorschau
> der itemize Umgebung erstellt

The itemize environment is not previewed by default.  If you want it
previewed, use \PreviewEnvironment{itemize} in the preamble.  Since
it can be of arbitrary size, the result in most cases is a graphic
that is so large that handling it with Emacs/XEmacs is unwieldy.

> 2. Referenzen /ref{irgendwas} bleiben unverändert.

Why should references change in any manner?
(Continue reading)

Henning Sannemann | 4 Dec 2003 16:52
Picon

rel-0-7-8; \footnote{footnotetext} is not previewed

To: preview-latex-bugs <at> lists.sourceforge.net
Subject: rel-0-7-8; \footnote{footnotetext} is not previewed
X-Reporter-Void-Vars-Found: image-types
--text follows this line--

Remember to cover the basics.  Including a minimal LaTeX example
file exhibiting the problem might help.

Hello,
sorry for asking again. Preview latex works fine, but does not preview
footnotes as in the following modified abstract-part of circ.tex:

\begin{abstract}
Es sollen hier einfache Methoden vorgestellt werden, um auf einer
Rastereinheit verschiedene Kurven darzustellen. Vorgestellt werden
Zeichenalgorithmen für Linien, Kreise und Hyperbeln. Die hier
hergeleiteten Gleichungen sind auch unter dem Namen {\tt DDA}s
bekannt.\footnote{Just a footnote.}
\end{abstract}

The rest of circ.tex remained unchanged and preview works fine on it.

Thanks a lot for any ideas.
Henning Sannemann

Emacs  : XEmacs 21.4 (patch 13) "Rational FORTRAN" [Lucid] 
(i586-pc-win32) of Sun May 25 2003 on TSUNAMI
Package: rel-0-7-8

current state:
(Continue reading)

David Kastrup | 4 Dec 2003 17:05
Picon
Picon

Re: [preview-latex-devel] rel-0-7-8; \footnote{footnotetext} is not previewed

Henning Sannemann <hsannem <at> mi.uni-koeln.de> writes:

> To: preview-latex-bugs <at> lists.sourceforge.net
> Subject: rel-0-7-8; \footnote{footnotetext} is not previewed
> X-Reporter-Void-Vars-Found: image-types
> --text follows this line--
> 
> Remember to cover the basics.  Including a minimal LaTeX example
> file exhibiting the problem might help.
> 
> Hello,
> sorry for asking again. Preview latex works fine, but does not preview
> footnotes as in the following modified abstract-part of circ.tex:
> 
> \begin{abstract}
> Es sollen hier einfache Methoden vorgestellt werden, um auf einer
> Rastereinheit verschiedene Kurven darzustellen. Vorgestellt werden
> Zeichenalgorithmen für Linien, Kreise und Hyperbeln. Die hier
> hergeleiteten Gleichungen sind auch unter dem Namen {\tt DDA}s
> bekannt.\footnote{Just a footnote.}
> \end{abstract}

circ.tex explicitly invokes the preview package, and the invocation
does not specify the `footnotes' option.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
(Continue reading)

William H. Wheeler | 6 Dec 2003 05:37
Picon
Favicon

Bugs in dvipng: enc.c Version 0.7

Dear Jan-Ake,

I'm writing to mention two changes I had to make
to  enc.c  in versions 0.7  of dvipng  in order to get dvipng
to work, e.g., to process test-dvipng.dvi .

My environment is  a Sun SunBlade 2000 running  Solaris 9

The changes are:

------------------ Change 1  ---------------------------

struct encoding* InitEncoding(char* encoding)
{
  char *pos,*max,*buf,*enc_file =
/*    kpse_find_file(encoding,kpse_dvips_config_format,false); */
    kpse_find_file(encoding,kpse_tex_ps_header_format,false);
                            ^^^^^^^^^^^^^^^^^^^^^^^^^

===========================================================

------------------ Change 2  ------------------------------

struct encoding* FindEncoding(char* encoding)
{
  struct encoding *temp=encodingp;

  while(temp!=NULL && strcmp(encoding,temp->name)!=0)
    temp=temp->next;
  if (temp==NULL)
(Continue reading)

Jan-Åke Larsson | 7 Dec 2003 21:39
Picon
Picon
Favicon

Re: [preview-latex-devel] Bugs in dvipng: enc.c Version 0.7

Hi William,

> I'm writing to mention two changes I had to make
> to  enc.c  in versions 0.7  of dvipng  in order to get dvipng
> to work, e.g., to process test-dvipng.dvi .
> 
> My environment is  a Sun SunBlade 2000 running  Solaris 9

Let me guess, you have a complicated font installation (more
complicated than mine, that is), and your encodings are not in the
same path as the dvips config files (as they are here).

> ------------------ Change 1  ---------------------------
> 
> struct encoding* InitEncoding(char* encoding)
> {
>   char *pos,*max,*buf,*enc_file =
> /*    kpse_find_file(encoding,kpse_dvips_config_format,false); */
>     kpse_find_file(encoding,kpse_tex_ps_header_format,false);
>                             ^^^^^^^^^^^^^^^^^^^^^^^^^

Right. This will be in CVS in a few minutes, as it compiles and runs
straight on my configuration(s) too. The kpathsea info pages are not
really very informative on this, but _ps_header_ does seem more
fitting.

> ------------------ Change 2  ------------------------------

This is a case of forgotten braces. Sorry. This change is already in
CVS (minus the comments, was reported earlier off-list). The bug only
(Continue reading)

Unknown | 9 Dec 2003 11:03

°µ§AÀ³¸Ó°µªº¨Æ

¡ <at>

¡ <at>

°Ó·~¦Û¥D¡AÅý±z¸õ²æ¶Ç²Î°Ó·~©Ò­±Á{ªº§xÃø¦]¬°§Ú­Ì°í«ù¡§¤­¤£¡¨

¡¯ ¤£»Ý§ë¸ê¤j¶qªºª÷¿ú¡A§Y¥i³Ð·~¡C

¡¯ ¤£»Ý¾Ö¦³¥ô¦ó¾Ç¡B¸g¾ú¤Î±M·~§Þ¯à¡C

¡¯ ¤£¶·©Ó¾á¥ô¦óªº¸gÀç­·ÀI¡C
¡¯ ¤£±±¨î±zªº®É¶¡¡B¥i¦Û¥Ñ½Õ°t®É¶¡ ¡C

¡¯ ¤£¶·¥|³B¦V¤H±À¾P²£«~ ¡C

 ¥i­Ý®t¡B¥i±M¾¡A»P²{¦³¤u§ <at> ¤£½Ä¬ð,Åý±z²³æ¦a¾Ö¦³¤ <at> ¶µ¨ã¦³¥H¤U¦¨¥\¯S¦âªº¦Û¥D¨Æ·~¡G

¤£¥Î¶±­û
¤£¥Î¦s³f
¤£¥Î¤å®Ñ§ <at> ·~

¨S¦³®É¶¡­­¨î
¤£¥Î¥¨ÃB¸êª÷
¨S¦³¤H±¡À£¤O

±j«l¬¡°Ê
¶RªÌ·~ªÌ¤¬´f
¥þ²y³s½uµo®i

¤£½×§A¬O­Ó±M·~¤H¤h¡B®a®x¥D°ü¡B¤½¥q¾­û¡A±z»{¬°§A±N¤ <at> ½ú¤l±q¨Æ³o­Ó¦æ·~¦Ó¨S¦³¿ò¾Ñ¶Ü¡H

±z²{¦b±q¨Æªº¤u§ <at> ±N·|±aµ¹§A¤ <at> ½ú¤l§A¹Ú·Q¤¤ªº¥Í¬¡¶Ü¡H

¤£½×§A¬O¤°»ò±Ú¸s....BTOC´£¨Ñµ¹±z¤ <at> ­Ó¹F¦¨¹Ú·Qªº¾÷·|!§Ú­Ì­nªº¥u¬O§Aªº«i®ð¸ò¨M¤ß..

À˵ø§A¥Ø«eªºª¬ªp

§A¥i¥H§¤¦b¨Fµo¤W¬Ý¹qµø¡A§Ñ°O§Aªº¹Ú·Q¡A©Î¬O¦A«×À˵ø§A¥Ø«eªºª¬ªp..............
¡´ §Aı±o§A¥Ø«eªº¤u§ <at> ©Ò±o¦X²zªº¶Ü¡H ¡´ §AÄ <at> ·N¦AÄ~Äò°µ¥Ø«eªº¤u§ <at> 20¦~¶Ü¡H
¡´  §A¹ï¥Ø«eªº¤u§ <at> ı±o¨S¦³¥¼¨Ó©Î«D±`¹½´c¶Ü¡H ¡´ §A·|­n«Ä¤lªø¤j«á¤]°µ§A²{¦bªº¤u§ <at> ¶Ü¡H
¡´ §Aªº¥t¤ <at> ¥b¦Ñ¬O©ê«è®a¸Ì¨S¦³¨¬°÷ªº¿ú¥i¥H¥h°µ·Q°µªº¨Æ¶Ü¡H ¡´ §A¥Ø«eªº¤u§ <at> ¥O§Aı±o¥R¹ê¥B¤Þ¥H¬°¶Æ¶Ü¡H
¡´ §Aı±o²{¦b¾Ö¦³ªº¥Í¬¡¬O§A·Q­nªº¤è¦¡¶Ü¡H ¡ <at>
§A¥i¥H¼È®É¤£¥h·Ð´o...............
©Î¬O²{¦b´N·Q§ïÅÜ!

¤ <at> «Êemail©Î³\·|§ïÅܤF§Aªº¤ <at> ¥Í.....


¡ <at>

Thomas Klausner | 12 Dec 2003 23:40
Picon

dvipng-0.8 bugs

Hi!

Two problems in dvipng-0.8:
The configure script copies kpsewhich, but doesn't
ignore its permissions when trying to delete it (usually
it will be r-xr-xr-x and rm might ask); patch attached.

dvipng gives _lots_ of warnings:
	free(): warning: junk pointer, too high to make sense.
This usually means freeing unallocated space, or double-freeing
space.
Log of one run attached.

dvipng-0.6 didn't give these warnings on the same file.
[0.7 didn't work for me.]

Cheers,
 Thomas
$NetBSD: patch-aa,v 1.3 2003/12/12 22:36:14 wiz Exp $

--- configure.orig	Tue Dec  9 22:42:51 2003
+++ configure
 <at>  <at>  -6237,7 +6237,7  <at>  <at>  echo "${ECHO_T}$TEXMF_CNF" >&6
 echo $ECHO_N "checking for psfonts.map... $ECHO_C" >&6
   cp `which kpsewhich` .
   PSFONTS_MAP=`./kpsewhich psfonts.map`
-  rm ./kpsewhich
+  rm -f ./kpsewhich
   if test -n "$PSFONTS_MAP"; then
     echo "$as_me:$LINENO: result: $PSFONTS_MAP" >&5
 echo "${ECHO_T}$PSFONTS_MAP" >&6
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
This is dvipng 0.8 Copyright 2002-2003 Jan-Åke Larsson
[1dvipng warning: at (0,0) unimplemented \special{header=psfrag.pro}.
dvipng in free(): warning: junk pointer, too high to make sense.
dvipng in free(): warning: junk pointer, too high to make sense.
] [2] [3<pattern.eps>] [4dvipng warning: at (123,393) unimplemented \special{ps: /PSfrag
where{pop(pattern)[[0()1 0]](a)[[1()1 0]](b)[[2()1 0]]3 0 -1/Begin PSfrag}{userdict /PSfrag{pop}put}ifelse}.
<plantedmatch.eps>dvipng warning: at (123,393) unimplemented \special{ps: /End PSfrag}.
dvipng warning: at (123,328) unimplemented \special{ps: /Hide PSfrag}.
dvipng warning: at (123,343) unimplemented \special{ps: /Unhide PSfrag}.
dvipng warning: at (101,354) unimplemented \special{ps:  { }.
dvipng warning: at (101,354) unimplemented \special{ps:  } 0/Place PSfrag}.
dvipng warning: at (120,373) unimplemented \special{ps:  { }.
dvipng warning: at (120,373) unimplemented \special{ps:  } 1/Place PSfrag}.
dvipng warning: at (120,388) unimplemented \special{ps:  { }.
dvipng warning: at (120,388) unimplemented \special{ps:  } 2/Place PSfrag}.
] [5<plantedpatterns.eps>] [6<pp-splitting.eps>dvipng warning: at (140,583) unimplemented
\special{ps: /PSfrag where{pop(T1)[[0()1 0]](T2)[[1()1 0]](T3)[[2()1 0]]3 0 -1/Begin
PSfrag}{userdict /PSfrag{pop}put}ifelse}.
<pp-splitting2.eps>dvipng warning: at (140,583) unimplemented \special{ps: /End PSfrag}.
dvipng warning: at (140,518) unimplemented \special{ps: /Hide PSfrag}.
dvipng warning: at (140,533) unimplemented \special{ps: /Unhide PSfrag}.
dvipng warning: at (135,544) unimplemented \special{ps:  { }.
dvipng warning: at (135,544) unimplemented \special{ps:  } 0/Place PSfrag}.
dvipng warning: at (135,561) unimplemented \special{ps:  { }.
dvipng warning: at (135,561) unimplemented \special{ps:  } 1/Place PSfrag}.
dvipng warning: at (135,578) unimplemented \special{ps:  { }.
dvipng warning: at (135,578) unimplemented \special{ps:  } 2/Place PSfrag}.
dvipng warning: at (167,837) unimplemented \special{ps: /PSfrag where{pop(P)[[0()1 0]](T1)[[1()1
0]](T2)[[2()1 0]](T3)[[3()1 0]]4 0 -1/Begin PSfrag}{userdict /PSfrag{pop}put}ifelse}.
<pp-parts.eps>dvipng warning: at (167,837) unimplemented \special{ps: /End PSfrag}.
dvipng warning: at (167,755) unimplemented \special{ps: /Hide PSfrag}.
dvipng warning: at (167,770) unimplemented \special{ps: /Unhide PSfrag}.
dvipng warning: at (164,783) unimplemented \special{ps:  { }.
dvipng warning: at (164,783) unimplemented \special{ps:  } 0/Place PSfrag}.
dvipng warning: at (162,798) unimplemented \special{ps:  { }.
dvipng warning: at (162,798) unimplemented \special{ps:  } 1/Place PSfrag}.
dvipng warning: at (162,815) unimplemented \special{ps:  { }.
dvipng warning: at (162,815) unimplemented \special{ps:  } 2/Place PSfrag}.
dvipng warning: at (162,832) unimplemented \special{ps:  { }.
dvipng warning: at (162,832) unimplemented \special{ps:  } 3/Place PSfrag}.
dvipng in free(): warning: junk pointer, too high to make sense.
] [7] [8] [9] [10] dvipng in free(): warning: junk pointer, too high to make sense.
[11dvipng warning: at (123,272) unimplemented \special{ps: /PSfrag where{pop(a)[[0()1 0]](b)[[1()1
0]](c)[[2()1 0]]3 0 -1/Begin PSfrag}{userdict /PSfrag{pop}put}ifelse}.
<rootpattern.eps>dvipng warning: at (123,272) unimplemented \special{ps: /End PSfrag}.
dvipng warning: at (123,207) unimplemented \special{ps: /Hide PSfrag}.
dvipng warning: at (123,222) unimplemented \special{ps: /Unhide PSfrag}.
dvipng warning: at (119,236) unimplemented \special{ps:  { }.
dvipng warning: at (119,236) unimplemented \special{ps:  } 0/Place PSfrag}.
dvipng warning: at (120,251) unimplemented \special{ps:  { }.
dvipng warning: at (120,251) unimplemented \special{ps:  } 1/Place PSfrag}.
dvipng warning: at (120,269) unimplemented \special{ps:  { }.
dvipng warning: at (120,269) unimplemented \special{ps:  } 2/Place PSfrag}.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: page is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
dvipng in free(): warning: chunk is already free.
] [12] [13] [14] [15] [16] [17] [18] [19] 
Jan-Åke Larsson | 15 Dec 2003 10:03
Picon
Picon
Favicon

Re: [preview-latex-devel] dvipng-0.8 bugs

Thomas Klausner wrote:
> Hi!
> 
> Two problems in dvipng-0.8:
> The configure script copies kpsewhich, but doesn't
> ignore its permissions when trying to delete it (usually
> it will be r-xr-xr-x and rm might ask); patch attached.

Very good, will patch configure.ac

> dvipng gives _lots_ of warnings:
> 	free(): warning: junk pointer, too high to make sense.
> This usually means freeing unallocated space, or double-freeing
> space.

Odd. Real odd. And while running too (no problems when freeing at
close, it seems). That only leaves free() calls in font.c, hmmm...
These are free's of pointers returned by kpathsea. Except that one,
which shouldn't be there. Oh no. Well, whatdoyouknow. Try the
included patch.

Thanks. 

Perhaps it would be best to do 0.9 soon. Please respond as soon as
possible.

Anything more, guys? ISTR there was a problem with the -pp option that
I wanted to fix. Might as well do that.
/JÅ

--

-- 
Win95: What do you want to crash today?

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
Thomas Klausner | 15 Dec 2003 12:32
Picon

Re: [preview-latex-devel] dvipng-0.8 bugs

On Mon, Dec 15, 2003 at 10:03:24AM +0100, Jan-Åke Larsson wrote:
> Odd. Real odd. And while running too (no problems when freeing at
> close, it seems). That only leaves free() calls in font.c, hmmm...
> These are free's of pointers returned by kpathsea. Except that one,
> which shouldn't be there. Oh no. Well, whatdoyouknow. Try the
> included patch.

Patch missing.
 Thomas

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

Gmane