gmane.comp.type-setting.lout

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{

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

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

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?

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

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

< at >NP in macros

Kevin Banjo — 2013-01-28T22:46:52

I try to put < at >NP in a macro and it doesn't error, there is no page eject,
and nothing after that even shows.  Is there a way to do it?


-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

Additional formatting inside < at >CP

Valeriy E. Ushakov — 2013-01-23T21:44:38

While we are on this topic...  I recently needed to highlight bits of
code inside < at >CP without manual editing of prg2lout output and without
additional filtering (corporate laptop with windows, so < at >Filter is a
problem). 

I came up with the following quick hack that someone might also find
useful (or at least it's archived for my own future reference :).

< at >CP < at >Begin
...
      do_stuff();
/*< at >< at >ShowBackground { < at >ASTRUT# */
#ifdef SPECIAL
      do_special_stuff();
#endif/*< at >#
< at >ZSTRUT}*/
      do_more_stuff();
...
< at >End < at >CP

Where

macro < at >ASTRUT { 0.8w < at >VShift 1f < at >High {} //0io "" }
macro < at >ZSTRUT { 0.3w < at >VShift 1f < at >High {} }

and < at >ShowBackground is bog standard < at >Graphics to fill background:

def < at >ShowBackground
  named < at >BG { 0.90 }
  right x
{
  { 0 0 moveto xsize 0 lineto xsize ysize lineto 0 ysize lineto
    closepath < at >BG setgray fill
  } < at >Graphic x
}

The /*< at > comments should be used *exactly* as shown, with embedded lout
comments (to deal with "lines" < at >Break vs. leading whitespace) and the
closing /*< at > comment spl

How do you set < at >Book { < at >Title{} } font size?

Jeff Kingston — 2013-01-23T21:16:12

Mark,


The < at >BookSetup setup file symbol has a < at >TitlePageFont option.  If
you don't like what you are getting on the admittedly very hard
wired front page, you can always switch to using the < at >OnTitlePage
option of < at >Book, which places an arbitrary object on the title page
instead of the usual arrangement of title, author, and so on.


The default value is 2.5f, which for an initial font of 12p is
30p.  Perhaps you didn't notice the 3p difference?  I tried

   < at >SysInclude { book }
   < at >Book
       < at >Title { 5p < at >Font { A Title } }
   //
   < at >Chapter
      < at >Title { First Chapter }
   < at >Begin
   < at >LP
   Stuff.
   < at >End < at >Chapter

just now and certainly got an unusually small title.  But I
don't think this is the right way to do it, mixing up format
with content always costs in the end.

Jeff

How do you set < at >Book { < at >Title{} } font size?

Mark Summerfield — 2013-01-23T11:15:47

Hi,

I have

    < at >Book
< at >Title{The Title}

but I can't see how to set the < at >Title's font size (and using, say, 
< at >Title{27p < at >Font{The Title}}
has no effect.

Thanks!

prg2lout raw mode

2013-01-21T21:43:57

Greetings,

I'm attempting to use prg2lout to convert pod input into man page style
documentation.  In the "SEE ALSO" section of the man page, there are
references to other tools.  I'd like to find a way to make those references
into links in my final product -- a pdf file.

I'm thinking that it may be possible to use prg2lout -r to generate
"Lout-readable source" which I then edit, save in a file, and < at >Include in
my document.  Does this sound like it should work?  And how do I use the
output of prg2lout -r?  When I try including (via < at >Include) the output, I
get errors like:

     1,1: symbol < at >PPG unknown or misspelt
     2,1: symbol < at >PPG unknown or misspelt
     4,1: symbol < at >PPG unknown or misspelt
     5,1: symbol < at >PHA unknown or misspelt

Thanks,
David

Inter-letter spacing

2013-01-01T23:40:05

 Hi there,

 after gaining some experience with Latex and groff I am curious about Lout. At
 first glance it looks very promising to me. I just stumbled about the issue of
 adjusting the inter-letter spacing of words. How is this done in Lout? 
 Basically, I want some characters to overlap and some to have larger then
 normal spacings within one word.

 Thanks in advance,
 Martin

CrossLink Question

Leon Hauck — 2012-11-04T08:51:59

I'm currently using Lout 3.38 (from Debian Squeeze) and can't seem to
get the CrossLink functionality to work.  Given the following input file
(named testme.lin on my system):

---------------------------------------

< at >SysInclude { doc }
< at >Doc < at >Text < at >Begin
< at >LLP < at >LeftNote { 1. }BY MS. asdfasfd:  { EX0000PG0000 } < at >CrossLink {
Exhibit < at >PageOf EX0000PG0000 }
< at >LLP < at >LeftNote { 2. }   Q.    Would you state your name for the record.
< at >LLP < at >LeftNote { 3. }   A.    asfasdf.
< at >LLP < at >LeftNote { 4. }   Q.    Mr.  I'm  and with me is
< at >LLP < at >LeftNote { 5. } and we represent regarding an`
< at >LLP < at >LeftNote { 6. }incident that happened at the back in April of
< at >LLP < at >LeftNote { 7. }2099.  So the questions I'm going to ask you today
relate
< at >LLP < at >LeftNote { 8. }to that and your knowledge about, that okay?
< at >NP
< at >NP
< at >NP
< at >PageMark { EX0000PG0000 }
< at >Place
    x { right - xsize }
    y { { foot }  }
{
    # < at >IncludeGraphic testme4.eps
}

----------------------------------------

I'm trying to trying to create a link on the first page that whe

table of contents on a regular doc document

Daniel Ajoy — 2012-10-26T03:20:25

Hi how do I add a table of content to a document with this structure:

< at >Include { doc }
< at >Doc < at >Text < at >Begin
< at >BeginSections
< at >Section ... < at >End < at >Section
< at >Section ... < at >End < at >Section
< at >Section ... < at >End < at >Section
< at >EndSections
< at >End < at >Text


I changed my personal "doc" include to have this line

< at >MakeContents{ Yes }

but when I run lout I get:

     27,1: no < at >ContentsPlace precedes or follows this < at >ContentsPlace&&foll_or_prec


Daniel

bookman base

Daniel Ajoy — 2012-09-05T01:41:15

Hi,

I have noticed that Bookman Base is more bold than Bookman Bold. (in version 3.36), is that normal?

Daniel

Arguments before or after command?

Cedric Sodhi — 2012-09-02T12:34:03

Hello, I just found out about Lout. Firstly, I'm more than amazed by it.
For years I've been using LaTeX, until I found out about GRoff, which
was much better than the former, but as a programmer, I could never
quite get to terms with how inconsistent the syntax itsself seemed to be
(which seems to be a common problem in Typesetting languages which need
to find a balance between being a programming language and being
efficiently typeable). I wish I had known about Lout earlier!

What doesn't quite seem to fit in with Lout being a clean, consistent
language is how arguments are passed to < at >Commands . By which logic do
commands take arguments { Before } < at >TheCommand or < at >TheCommand { And then
the Argument } or even

< at >TheCommand { And then } { multiple } { Arguments } ?

Sadly, this reminds me a bit of the problems I had with Groff and
especially LaTeX, where sometimes, there appears to be no rule for how
commands are called. Could you shed a bit of light onto that? For
example, why are not all commands constructe

Resources.

Weaver — 2012-08-19T11:35:32

Hello,

I'm about to start delving into Lout.

I'm running a Debian-based system, so already have some doc resources, but
am still chasing more in this initial stage.

I have joined this list and searched the archive on 'Lout Resources'
terminology, but come up with nix.

Google enquiry comes up with a little more, but I suspect there might be
other gems floating round in obscure corners and I don't mind purchasing a
book or two if they come recommended.

Grateful for any pointers.
Thanking you for your time and attention to this matter.
Regards,

Weaver.

Margin kerning, inter-sentence spacing and drawings

Matej Nanut — 2012-07-13T15:41:22

Hello again!

1. I've recently discovered the "margin kerning"/"character
protrusion" typographic feature and see that it is implemented in Lout
as a < at >Break parameter.

Here's my question: it doesn't seem to put hyphens into the margin. Is
this deliberate? LaTeX's microtype package does it, and I quite like
it. In Lout it seems to do it only for periods and commas (and I
haven't tried other similiar punctuation marks). Is it possible to add
hyphens to the list of margin-kernable characters somehow?

Also, is the feature in any way configurable? It seems like the whole
character protrudes into the margin. I would prefer it if only a
portion of it would (for the comma, for example).

2. As for the inter-sentence part: is it possible to configure its
extra spacing? It feels like a whole extra space is too much at times,
and I wouldn't want to add something like "&1.3s" into the code
wherever I end a sentence. I could change the meaning of "~~" but that
doesn't affect literal double spaces. Is my only choice wri

LaTeX "stretch" equivalent

Matej Nanut — 2012-07-06T23:05:00

Hello,

I'm afraid I've hit another snag. How would I go about getting two
rules to the left and right of a centred object?

Like this: [---------------- text ----------------].

I've tried using "|" and "&" with various combinations of
< at >FullWidthRule and < at >LocalWidthRule, but I can't figure it out.

Sorry for being so annoying. An answer in the form of the (obvious? :/
) page (or approximate section) in one of the guides would more than
suffice.

Thank you, Matej

Guillemets and Slovenian

Matej Nanut — 2012-07-05T00:51:13

Hello everyone,

I've just discovered Lout yesterday and will probably switch over from
{Xe,Lua,La,...}TeX, mainly for the organised documentation, the
interesting programming approach and for it being a lot more modern.

However I have hit an issue: if I set < at >InitialFont to SchoolbookCE (or
<anything>CE), I can't use ©Char guillemotright (or left) due to it
being unknown in the font. I have "fixed" this issue temporarily by
using "def ">>" { { Schoolbook Base } < at >Font < at >Char guillemotright{} }",
but if I change my mind about < at >InitialFont, I will have to correct
these definitions as well.

Is there a better way?

On a side note, what is the preferred way to write an ellipsis (...) in Lout?

Thanks for your time,
Matej.

LaTeX "stretch" equivalent

Matej Nanut — 2012-07-06T23:05:00

Hello,

I'm afraid I've hit another snag. How would I go about getting two
rules to the left and right of a centred object?

Like this: [---------------- text ----------------].

I've tried using "|" and "&" with various combinations of
< at >FullWidthRule and < at >LocalWidthRule, but I can't figure it out.

Sorry for being so annoying. An answer in the form of the (obvious? :/
) page (or approximate section) in one of the guides would more than
suffice.

Thank you, Matej