- From: Joris van der Hoeven <address@hidden>
- To: Magnus Rohde <address@hidden>
- Cc: <address@hidden>, Joris van der Hoeven <address@hidden>
- Subject: Re: [TeXmacs] More troubles with 1.0.3.8: crashes, pictures and papersizes
- Date: Fri, 14 May 2004 15:02:27 +0200 (CEST)
OK, I looked once more into the problems.
On Fri, 14 May 2004, Magnus Rohde wrote:
>
>> 1:
>
>> When I try to move the insertion mark into a floating element that is
>
>> included from another document, TeXmacs crashes (exits). This happens
>
>> when using either the mouse or the arrowkeys.
>
>
The document I had open when I discovered this worked flawlessly under
>
1.0.3.7. I have not retested under 1.0.3.7, maybe I will during the
>
weekend. In the meantime can someone else try to replicate this?
As I said before, I expect this problem to be solved in the CVS version.
If not, then please send me the erroneous document and a precise procedure
of how to reproduce this bug.
>
>> 2:
>
>> Whenever I try to open a document with pictures (png or jpeg) it looks
>
>> like the picture data is damaged. If it's jpeg, it says: "Bad Huffman
>
>> code" or somthing like that and displays a garbled picture. If it's
>
>> png, it says "png damaged by ASCII conversion" and displays a
>
>> questionmark. This happend when opening both old an new documents.
>
>> Workaround: only use linked pictures.
>
>
This is definetly something new, as I have used pictures in several
>
documents with 1.0.3.7 with no problems. This also occurs with new
>
document created under 1.0.3.8.
I made the system to save incorporated binary data more robust.
The problem should be solved in the CVS version.
>
>> 3:
>
>> When I export to PostScript or pdf the resulting document always uses
>
>> 11*8.5 as papersize, eventhough the paper size is set to a4 in both
>
>> TeXmacs and ghostscript. Has anybody experienced this, and how do
>
>> change the papersize in pdf's and .ps's?
>
>
This is also a problem with older documents (made with the current
>
TeXmacs version 3 - 4 months ago). Maybe this particular problem is
>
ghostscripts fault?
I have the impression that it is indeed ghostscripts fault.
There are lines
%%DocumentPaperSizes: a4
%%BoundingBox: 0 0 596 842
in the generated Postscript. I checked a few other programs and
it seems that (my) Ghostscript is not able to handle default
paper size information (nor for TeXmacs, nor for other programs) ;^(
Archive powered by MHonArc 2.6.19.