gmane.comp.type-setting.lout

Re: Everything on a single page

Jeff Kingston — 2013-06-12T06:45:28

Dear Lout users,

I'm pretty sure I've worked out what is going on here.  As
Uwe discovered, there is a partially uninitialized array.  The
uninitialized bits have a flag saying "don't use me", but the
array of flags is being shared between two fonts, which was
fine long ago when it was constant, but broke when it became
non-constant during an enhancement.  Things started to happen
when the TOC was added because it is at that time that two
sizes of TimesCE Bold are first present; these are the two
fonts that erroneously share the array of flags.

At present the only workaround is to not use composite
characters in fonts that appear in two sizes.  So a new
release is called for, and I'll get to work on that more
or less right away.  It will take a little while because I
have to look through all the mail since the last release.

There is no problem with the apparently missing information
in the font metrics file.  Lout substitutes information from
the corresponding unaccented character when information for
an

Re: Everything on a single page

Valery Ushakov — 2013-06-12T02:01:07


Luck with good enoguh values in the uninitialized part of the array?
I summarized how it fails in a mail up-thread (linux/amd64).  You can
try running lout under valgrind on MacOS.  The bug hits on the thrid
iteration, when TOC manifests.

Why it doesn't happen earlier, with the chapter title itself - is a
mistery.

-uwe

Re: Everything on a single page

2013-06-12T01:40:21

Perhaps i'm missing something obvious...  As far as i can tell, the
original Lout source attachment (with // added before the preface) compiles
fine for me both with Lout 3.39 compiled under Cygwin on Win7 and Lout 3.38
on my Mac.  I've attached the pdf that I get after converting with ps2pdf.
 Let me know if more details are useful.

Thanks,
David

Re: Everything on a single page

Valery Ushakov — 2013-06-12T01:20:28

[...]

To work around this problem you need to expand lout font metrics with
information for the missing Polish characters.  As I said, currently
it's present only for two fonts.  You should be able to use AFM files
from Ghostscript or OpenOffice directly, or just fetch necessary
metrics from them and add it to lout's font/Ti-Bd+ etc.

Long ago I wrote an overview of font handling in Lout that might still
be useful:

http://www.stderr.spb.ru/~uwe/lout/essays/1365.fonts.txt

The part about fontdef is out of date, as Lout now uses a < at >FontDef
database, but that's only a surface syntactic change.

-uwe

Re: Everything on a single page

Kamil Rytarowski — 2013-06-12T00:34:34

Hello,

I have reproduced this behaviour locally for the given eogonek.lt example.

Changing {< at >Char eogonek} from "Wst{< at >Char eogonek}p" to [of course in 
ISO-Latin2] one of ź/ć/ń produces the internal error,changing to one of 
ą/ś/ż results with: "437,24: 668.2c object too high for 24.7c space; 
will try elsewhere" and the ó/ł are accepted as a valid character.

Regards,

Re: Everything on a single page

Valery Ushakov — 2013-06-11T22:33:52


Hmm, interesting.  The first error that valgrind tells me about is
that lout is confused by egonek in "Wste,p" (in the chapter title)
when table of contents is produced on the thrid run:

  Conditional jump or move depends on uninitialised value(s)
     at 0x4F7B6C: FontWordSize (z37.c:1683)
     by 0x47B096: MinSize (z12.c:1093)
     [...]
   Uninitialised value was created by a heap allocation
     at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
     by 0x4F2FD8: FontRead (z37.c:729)
     by 0x4F5876: FontChange (z37.c:1347)
     [...]

and many more.  Depending on the garbage you've got in the
uninitialised memory you either get that error or a crash.

A quick kludge to change z37.c:729 from malloc to calloc (that zeroes
the memory):

--- z37.c~  2010-09-10 00:55:04.000000000 +0400
+++ 37.c   2013-06-12 01:11:42.317596802 +0400
< at >< at > -726,7 +726,7 < at >< at >
   /* initialise font metrics table for the new font */
   ifdebug(DMA, D,
       DebugRegisterUsage(MEM_FONTS, 1, MAX_CHARS * s

Re: Everything on a single page

Jeff Kingston — 2013-06-11T21:27:56

Kamil,

This is quite an unusual error.  It means that your document
contains something that is not officially wrong but is not what
most people would have.

To fix it, you will need to comment out parts of your
document until you have narrowed down the problem to
a small area of it.  At that point the problem will
either be obvious, or else you will be able to post
a small example to the list for us to work on.

Jeff

On Tue, Jun 11, 2013 at 07:50:34PM +0200, Kamil Rytarowski wrote:

Re: Everything on a single page

Kamil Rytarowski — 2013-06-11T17:50:34

Thank you, I was looking for styles, page types, fonts for 2 weeks.. and 
those 2 characters are supposed to fix it!

The new problem came in my work (with applied '//' patch) and in the 
given example (as well with the '//' patch):

internal error: assert failed in MinSize: fwd(x, dim) < 0!

What it may be, how to resolve it?

Many thanks!

On 11.06.2013 18:41, slomium< at >att.net wrote:

Re: Everything on a single page

2013-06-11T16:41:33

Kamil,

Everything is printed on a single page, and therefore document is neither

Here's a section of your book attachment.  Note the // that I added below,
just before the Preface.  I think that's what you're missing.  See the
section in the Lout manual on Books for more info -- it's just a required
symbol.

< at >Book
< at >Title { Tytu? pracy }
< at >Author { Autor pracy }
< at >Publisher { Wydawca }
//
#
-----------------------------------------------------------------------------
# Przedmowa

Hope that helps!

David

Everything on a single page

Kamil Rytarowski — 2013-06-11T16:25:07

Hello!

I've got a serious problem with lout. I'm going to write a book-style 
document, but I'm struggling with the invalid output.

Everything is printed on a single page, and therefore document is 
neither readable, nor usable at all. After ps2pdf I can just see the 
last page...

I'm attaching my document - with randomized content.

Please help.
# -*- coding: latin-2;-*-

< at >SysInclude { latin2 }
< at >SysInclude { langdefs }
< at >SysInclude { bsf }
< at >SysInclude { dsf }
< at >SysInclude { bookf }

< at >Use { < at >BasicSetup
    < at >InitialFont { TimesCE Base 12p }
    < at >InitialLanguage { Polish }
}

< at >Use { < at >DocumentSetup
    < at >MakeContents { Yes }
    < at >MakeIndex { Yes }
    < at >PageHeaders { Titles }
    < at >PageType { A4 }
    < at >PageWidth { 80s }
    < at >PageHeight { 66f }
    < at >PageBackground { < at >Scale 60d < at >Rotate lightgrey < at >Colour SZKIC }
}

< at >Use { < at >BookSetup
    < at >SubSectionInContents { Yes }
}

< at >SysDatabase < at >FontDef { fontdefs }
< at >SysDatabase < at >RefStyle { refstyle }

< at >Book
< at >Title { Tytu

Re: space before lists

Jeff Kingston — 2013-05-13T21:42:43

Like this, using "< at >OneCol D" and "< at >RawBulletList":

< at >LP < at >Tbl
width { expand }
rule { yes }
aformat {
< at >Cell indentvertical {ctr} indent { ctr } < at >B clines < at >Break A |
< at >Cell width {1c} indent { ctr } indentvertical {foot} 90d < at >Rotate < at >B B |
< at >Cell width {1c} indent { ctr } indentvertical {foot} 90d < at >Rotate < at >B C |
< at >Cell indentvertical {ctr} indent { ctr } < at >B clines < at >Break D |
< at >Cell width {1.5i} indentvertical {ctr} indent { ctr } < at >B clines < at >Break
E }
bformat { < at >Cell A | < at >Cell width {1c} B | < at >Cell width {1c} C | < at >Cell
< at >OneCol D | < at >Cell width {1.5i} E }
{
< at >Rowa
A { Componente del Proyecto }
B { Estudiante }
C { Profesor }
D { Recursos Disponibles }
E { Notas }

< at >Rowb
A { Hacer nuevas carpetas }
D {
< at >RawBulletList
< at >ListItem { Cartilla Organizando Carpetas }
< at >EndList
}

< at >Rowb
A { Selecciona un grupo de fotos }
D {
< at >RawBulletList
< at >ListItem { Investigacin en Internet }
< at >ListItem { Manual de la Cmara }
< at >EndList
}

}

Jeff

space before lists

Daniel Ajoy — 2013-05-13T20:00:18

Hi,

How do I remove the red vertical space? (image attached)


My table code is:

< at >LP < at >Tbl
width { expand }
rule { yes }
aformat {
< at >Cell indentvertical {ctr} indent { ctr } < at >B clines < at >Break A |
< at >Cell width {1c} indent { ctr } indentvertical {foot} 90d < at >Rotate < at >B B |
< at >Cell width {1c} indent { ctr } indentvertical {foot} 90d < at >Rotate < at >B C |
< at >Cell indentvertical {ctr} indent { ctr } < at >B clines < at >Break D |
< at >Cell width {1.5i} indentvertical {ctr} indent { ctr } < at >B clines < at >Break E }
bformat { < at >Cell A | < at >Cell width {1c} B | < at >Cell width {1c} C | < at >Cell D | < at >Cell width {1.5i} E }
{
< at >Rowa
A { Componente del Proyecto }
B { Estudiante }
C { Profesor }
D { Recursos Disponibles }
E { Notas }

< at >Rowb
A { Hacer nuevas carpetas }
D {
< at >BulletList
< at >ListItem { Cartilla Organizando Carpetas }
< at >EndList
}

< at >Rowb
A { Selecciona un grupo de fotos }
D {
< at >BulletList
< at >ListItem { Investigación en Internet }
< at >ListItem { Manual de la Cámara }
< at >EndList
}

}


My "doc" says

   < at >ListOuterGap{ 0.00v} # gap before, after lists
   < at >ListGap{

Re: < at >BookSetup chapters - how to prevent chapter title page?

Jeff Kingston — 2013-05-10T22:27:14

Paul,

The book package does not insert an entire page devoted to
the title.  It inserts a large title at the top of the
first page containing "Chapter 1.  Whatever-the-title-is",
but the remainder of that page contains chapter text.

If you are getting a page with nothing on it but the title,
the problem must be something else.  I suggest you do the
following:

(1) If you are using your own setup file, the first step is
to return to the default setup file.  If that fixes the
problem, then the problem is somewhere in your setup file
and you can work it out by reinstating your setup file
one option at a time.

(2) If the problem is still there, then it's in your
text.  The first thing would be to try a chapter like
this:

    < at >Chapter
       < at >Title { First Chapter }
    < at >Begin
    This is the first chapter.
    < at >End < at >Chapter

which ought to come out completely on one page.  If
that still does not work, let me know.  If it does
work, again you can work gradually back towards your
actual chapter and find the pr

< at >BookSetup chapters - how to prevent chapter title page?

Paul Zarucki — 2013-05-08T23:37:12

Hi,

The < at >BookSetup extension inserts a 'title' page at the start of each 
chapter containing text like "Chapter 1" in large print. I would like to 
prevent this page from appearing but can't see how to do it. I have 
tried adjusting parameters in the 'book' setup and have looked at the 
code in bookf but can't see how the extra page is generated.

I have tried adding

< at >Book
    < at >PageHeaders { None }
//

to the start of my document. This disables the title text but a page, 
which is now blank, is still inserted at the start of the chapter.

Any help would be appreciated.

TIA

Paul Zarucki.

Re: Experiences with Lout

Pierre — 2013-04-16T04:22:12



I for one mostly use the ps output, but I think the -p output is just
plain necessary (for generating, well, text output. Text is neat. Text
is universal. Text is needed).
I also think that the -Z option should be kept, pretty much as is. It
doesn't make Lout much heavier, and it is useful for basic doc
generation. 
I do like lout's most advanced features, but I also used to use Todd
Coram's AFT quite extensively, and the -p and -Z options are needed
AFAIC. Or I could just keep using AFT for "simple" output, but that
means re-writing stuff. Re-writing is bad, m'kay*?

Cheers

Re: Experiences with Lout

Joerg Jung — 2013-04-15T14:06:24

Hi,

Am 15.04.2013 um 00:55 schrieb Jeff Kingston <jeff< at >it.usyd.edu.au>:


Yes. :)


That is what I expected and what makes sense. 
Hence, my list contains only minor issues and as far as 
possible  only small features/options. I think Lout does not 
need major features, as it is mostly perfect already.


Thank you!

Regards,
Joerg

Re: Experiences with Lout

Joerg Jung — 2013-04-15T13:59:34

Hi,

Am 14.04.2013 um 22:36 schrieb Valery Ushakov <uwe< at >stderr.spb.ru>:


Thanks, for looking into both issues, maybe someone (Jeff?) can fix them 
with  the next release? 
Is there a bug tracking somewhere or can I send patches/diffs somewhere
to help, getting things fixed?


Rash, no.
Harsh, yes absolutely. That is why I wrote: "I personally" (IMHO) to 
reflect my personal view (which is probably not common).


I wrote this, _after_ I worked with both exports for a while, hence I
used them intensely. My very *personal* conclusion is: both are 
too limited and introduce bloat, e.g. additional cases in include
configs for Plain case and additional case for drawing primitives
adding "case pdf" in several places. *I* prefer software not bloated
with such limited options.


This is a good point, but I'm pretty sure there are better options 
for debugging from Lout developers point of view (e.g. gdb) and
from users point of view Lout error output is great and 
provides everything required for definitions debugg

Re: Experiences with Lout

Jeff Kingston — 2013-04-14T22:55:03

Joerg,

Thanks for the list of issues.  Looks like you gave Lout a pretty
thorough workout.

I don't see major new features being added to Lout at this late
stage in its life cycle, but I'm still happy to fix bugs.  I'll
look at your list again when I prepare the next release.

Jeff Kingston

Re: Experiences with Lout

Valery Ushakov — 2013-04-14T20:36:00


There's a typo in slidesf in def < at >Overhead invocation of
< at >LargeScaleStructure, the at-sign is lost in:

  indisplays { OverheadNumInDisplays }



Looks like unedited copy-paste in bsf.



Isn't it a bit rash to dismiss a feature that you don't use as
universally useless?

I personally find plain text extremely useful for debugging
definitions or doing a quick test (lout -p -s | cat -s).

Other people find PDF useful because when you need to generate simple
PDFs well within limitations of the pdf backend, you save time/space
on not having ghostscript around.

-uwe

Experiences with Lout

Joerg Jung — 2013-04-14T18:20:05

Hi,

in the following I would like to share my experiences with Lout from the
last six months. I'm writing my PhD thesis and started with LaTeX. I want
a rather 'stylish' thesis with nice headers, customized fonts and framed
and colored content. After I wasted hours searching the net, digging into
the source, adding several hacks, fighting with version incompatibilities

Re: Equation with condition

Matej Nanut — 2013-03-18T18:00:15

Turns out I did more or less the same thing as Pierre, so probably use that. :)

Matej