gmane.comp.type-setting.lout

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{ 0.50v} # gap between list items
   # < at >ListIndent{ 0s} # indent of list items
   # < at >ListRightIndent{ 0s} # right indent of list items
   < at >ListLabelWidth{ 1.00f< at >OrIfPlain 5s} # width allowed for list tags
   # < at >ListLabelRight{ No} # right-adjust list labels
   # < at >ListLabelRightGap{ 2s} # gap when right-adjusting
   # < at >ListFont{ } # font of list items
   < at >ListBreak{ ragged } # break style of list items


Daniel

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 problem that way.

Jeff

On Thu, May 09, 2013 at 12:37:12AM +0100, Paul Zarucki wrote:

< 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 debugging.

For debugging things in my thesis, I ended up in setting up a 
"test" document with the same 'template' configuration (headers, 
fonts, etc.) but no 'content'. If I setup a new larger Diag for example,
I do this in the test environment as compiling takes a second here.
Afterwards I copy it over to the production document.

My production thesis document is a rather large document (about 
180 pages, hundreds of cross references,  several Diags, a lot of 
Graphs (with larger input from < at >Pipe awk/grep/sed) and several
Listings. It takes several minutes and about 16 runs to build the ps 
and even some more minutes to create the final PDF. So for me, 
no option to debug something directly there without wasting hours 
of time.



*IMHO* not a reason to bloat Lout.

But anyway! Not so important... this was just a suggestion.
I'm fine if that suggestion does not match the view of the 
project (developers).

Regards,
Joerg

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

Re: Equation with condition

Pierre Lesimple — 2013-03-18T15:50:50

Le Mon, 18 Mar 2013 11:23:01 -0400,
Pierre Lesimple <pierre.lesimple< at >mcgill.ca> a écrit :


As a precision,

< at >CenteredNumberedDisplay < at >Tag {profound123} {< at >Eq {x=y} |1c  for < at >Eq
{x>0}} 
< at >CenteredNumberedDisplay < at >Tag {profound124}  < at >Eq {y=az+b}

seems to do what you want to do, if you don't mind the "centered" look
of it.

Re: Equation with condition

Pierre Lesimple — 2013-03-18T15:23:01

Le Mon, 18 Mar 2013 01:23:37 -0700,
Daren Scot Wilson <darenw< at >darenscotwilson.com> a écrit :


I would go for 2 columns (horizontal concatenation, two < at >Math{} objects)
in that particular case, but I don't know how the "flow" of equations
would look like as a whole...

Re: Equation with condition

Matej Nanut — 2013-03-18T15:02:50

I used to do something like this for cases in maths, but I'm at work
now so I don't have my "mydefs" file at hand.

I'll post it when I get home.

Matej

On 18 March 2013 09:23, Daren Scot Wilson <darenw< at >darenscotwilson.com> wrote:

Equation with condition

Daren Scot Wilson — 2013-03-18T08:23:37

I've gone temporarily dense or something, not seeing this in the User's 
Guide.  I know how to write an equation on a line of its own, for example

      x = y

using
< at >CenteredNumberedDisplay < at >Tag {profound123} < at >Math {x=y}

But how would I add a condition following the equation,  something like

      x = y     for x>0

but of course looking good?

Re: About < at >Eq and double integral

Dominique Crétel — 2013-02-08T06:56:35

Thanks for your help Ludo.
I've tried, but it's not much better !

Are there any lout users who can provide links to mathematics paper as example ?

Dominique

Le 7 févr. 2013 à 23:21, ludo< at >gnu.org (Ludovic Courtès) a écrit :

Re: About < at >Eq and double integral

Ludovic Courtès — 2013-02-07T22:21:38

Hi,

Dominique Crétel <dc.geslain< at >free.fr> skribis:


Using < at >Math might give you a slightly better result, but TeX remains
unequaled in that area...

Ludo’.

About < at >Eq and double integral

Dominique Crétel — 2013-02-06T17:18:47

Hi all,

How to get a beautiful double integral symbol ?

Here is what I've done :
< at >Eq { big int big int sub Sigma f(x) dx }
but the result is not so pretty !

I'd like something like here : http://personal.maths.surrey.ac.uk/st/S.Gourley/double_int.pdf

Thanks

Dominique Cretel

Re: < at >NP in macros

Jeff Kingston — 2013-01-28T23:45:40

Kevin,

The problem is not the macro, it is the context in which
you are using it.

Jeff

On Mon, Jan 28, 2013 at 02:46:52PM -0800, Kevin Banjo wrote:

Re: fill/page justify in macros

Pierre — 2013-01-28T23:46:44

About that and your previous message about < at >NP: both should work if done
properly, can you post the code you tried?

Le lundi 28 janvier 2013 à 14:51 -0800, Kevin Banjo a écrit :

fill/page justify in macros

Kevin Banjo — 2013-01-28T22:51:39

When I put text in a macro, it does not fill nor justify, however text
passed in < at >Body does.  Any idea how to fix?

-Kevin
------------
To be or not to be.
        -- Shakespeare
To do is to be.
        -- Nietzsche
To be is to do.
        -- Sartre
Do be do be do.
        -- Sinatra