headers
Sébastien Pierre | 6 Sep 2004 11:47

Re: Lout website

Hi Tatyana,

Le 23 août 04, à 19:47, Tatyana Alexeyev a écrit :

> Hello,
>
> I tryed to write to the group, but got no response.
>
> Do you know if lout support coloring option when
> creating PDF documents.
>
> Paint option does not work.

Actually, Lout direct PDF support is quite outdated, so that it does 
not work as well as PostScript. The solution I would recommend is to 
generate your document in PostScript, then include fonts with 
PostScript utilities (psutils) if you have non-standard fonts, then 
convert it into PDF 1.4 with ghostscript.

This makes things a little bit more complex, but you can be sure to 
have the best result. BTW, if you are planning to use color images, 
have a look at the website for optimal usage of images in Lout.

Cheers,

  -- Sébastien
Permalink | Reply | 15 comments |
headers
Jason Whittle | 9 Sep 2004 01:35
Picon

Import?

Given the error: "symbol  <at> SubSection unknown or misspelt" occurring in
mydefs, I assume there is an import command I need to prefix that line
with. However, I can't identify what it is that exports  <at> SubSection.
Is there something I missed in the references?

Cheers, 
Jason Whittle
Permalink | Reply | 0 comments |
headers
Jason Whittle | 10 Sep 2004 04:39
Picon

Re: Import?

On Thu, 09 Sep 2004 13:22:27 -0600, Joe Beach <jbeach <at> mines.edu> wrote:
> I'm not exactly sure. It might help if you posted your mydefs and a copy
> of the full error output. Also, what are you including ( <at> SysInclude,
>  <at> Include) at the beginning of your document file? It might be that you
> are correctly defining the mydefs, but you you aren't using a document
> type that defines the  <at> SubSection tag. Or, it isn't enclosed by
>  <at> BeginSubSections ...  <at> EndSubSections.

I've pared down the mydefs file to two lines, to make sure that
nothing else is interacting; mydefs is down to two lines:

import  <at> BasicSetup
def  <at> Charm {  <at> SubSection }

I know I should be using a macro for a simple substitution, but I
eliminated all of the functionality of the definition in order to make
sure it was really a scope problem. In addition, Basser Lout fails on
the third line of my source file, with the first three lines reading:

 <at> SysInclude{ diag }
 <at> SysInclude{ tbl }
 <at> SysInclude{ doc }

Also, I've tried the same thing with other symbols, like
 <at> BeginSubSection,  <at> Section, and  <at> BeginSection, and none of them are
recognized either. I don't have a copy of the error in front of me,
but with the above mydefs, the "unknown or misspelt" error is the only
one that occurs, other than a notice stating that the pass terminated
on line 3 of ma.lt. As a final caveat, I should note that I'm using
the Win32 binary distribution.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Edgar Toernig | 10 Sep 2004 06:35
Picon
Picon

Re: Import?

Jason Whittle wrote:
>
>  <at> SysInclude{ diag }
>  <at> SysInclude{ tbl }
>  <at> SysInclude{ doc }
> 
> import  <at> BasicSetup
> def  <at> Charm {  <at> SubSection }
>
> [gives: symbol  <at> SubSection unknown or misspelt]

extend  <at> Text  <at> Section
  def  <at> Charm {  <at> SubSection }

puts SubSection in scope but now you'll get an error for
the missing body of SubSection.  Possible[1] solution:

extend  <at> Text  <at> Section
  def  <at> Charm body x {  <at> SubSection { x } }

> I know I should be using a macro for a simple substitution

Indeed :-)

Ciao, ET.

[1] At least it'll parse.  I'm not an Lout expert...
Permalink | Reply | 4 comments |
headers
Edgar Toernig | 10 Sep 2004 23:35
Picon
Picon

Re: Import?

Jason Whittle wrote:
>
> > import/export  <at> BasicSetup  <at> DocumentSetup  <at> OrdinarySetup  <at> Text  <at> Section
> >   def  <at> Charm body x {  <at> SubSection { x } }
> 
> Excellent, thank you. I didn't know about  <at> OrdinarySetup. Is there
> somewhere I can find the various Setup scopes?

Use the source, Luke ;-)

I just took it out of the docf file:  <at> SubSection is defined in  <at> Section
which is defined in  <at> Text which is defined in  <at> OrdinarySetup which is
an "extend  <at> BasicSetup  <at> DocumentSetup".

Ciao, ET.
Permalink | Reply | 0 comments |
headers
Jason Whittle | 10 Sep 2004 16:16
Picon

Re: Import?

On Fri, 10 Sep 2004 06:35:24 +0200, Edgar Toernig <froese <at> gmx.de> wrote:
> Jason Whittle wrote:
> >  <at> SysInclude{ diag }
> >  <at> SysInclude{ tbl }
> >  <at> SysInclude{ doc }
> > 
> > import  <at> BasicSetup
> > def  <at> Charm {  <at> SubSection }
> >
> > [gives: symbol  <at> SubSection unknown or misspelt]
> 
> extend  <at> Text  <at> Section
>   def  <at> Charm {  <at> SubSection }

Copying this into mydefs (and nothing else) gives: 

lout file "mydefs" (from "doc" line 29, from "ma" line 3): 
     1,8: extend symbol  <at> Text not in scope
    1,14: extend symbol  <at> Section not in scope
 not in scopeend symbol
    1,37: fatal error: exiting now

Is there something wrong with my installation, do you think? 

Cheers, 
Jason Whittle
Permalink | Reply | 3 comments |
headers
Edgar Toernig | 10 Sep 2004 22:03
Picon
Picon

Re: Import?

Jason Whittle wrote:
>
> Edgar Toernig wrote:
> >
> > Jason Whittle wrote:
> > >
> > >  <at> SysInclude{ diag }
> > >  <at> SysInclude{ tbl }
> > >  <at> SysInclude{ doc }
> > >
> > > import  <at> BasicSetup
> > > def  <at> Charm {  <at> SubSection }
> > >
> > > [gives: symbol  <at> SubSection unknown or misspelt]
> >
> > extend  <at> Text  <at> Section
> >   def  <at> Charm {  <at> SubSection }
>
> Copying this into mydefs (and nothing else) gives: 
>
> lout file "mydefs" (from "doc" line 29, from "ma" line 3): 
>      1,8: extend symbol  <at> Text not in scope
>     1,14: extend symbol  <at> Section not in scope
>  not in scopeend symbol
>     1,37: fatal error: exiting now
> 
> Is there something wrong with my installation, do you think?

No, I get the same if I put the two lines in mydefs[1].  When I wrote
the mail I'd put the def in the main file just after the SysIncludes.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jason Whittle | 10 Sep 2004 22:41
Picon

Re: Import?

On Fri, 10 Sep 2004 22:03:35 +0200, Edgar Toernig <froese <at> gmx.de> wrote:
> Jason Whittle wrote:
> > Edgar Toernig wrote:
> > > Jason Whittle wrote:
> > > >  <at> SysInclude{ diag }
> > > >  <at> SysInclude{ tbl }
> > > >  <at> SysInclude{ doc }
> > > >
> > > > import  <at> BasicSetup
> > > > def  <at> Charm {  <at> SubSection }
> > > >
> > > > [gives: symbol  <at> SubSection unknown or misspelt]
> > >
> > > extend  <at> Text  <at> Section
> > >   def  <at> Charm {  <at> SubSection }
> >
> > Copying this into mydefs (and nothing else) gives:
> >
> > lout file "mydefs" (from "doc" line 29, from "ma" line 3):
> >      1,8: extend symbol  <at> Text not in scope
> >     1,14: extend symbol  <at> Section not in scope
> >  not in scopeend symbol
> >     1,37: fatal error: exiting now
> >
> > Is there something wrong with my installation, do you think?
> 
> No, I get the same if I put the two lines in mydefs[1].  When I wrote
> the mail I'd put the def in the main file just after the SysIncludes.
> The difference is that doc reads mydefs before it has exported all
> those Setup symbols.  So you would have to supply the complete
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jason Whittle | 15 Sep 2004 21:44
Picon

<at> Cell source question

As Edgar suggested, I've been becoming more acquainted with the
source, so when I wanted to make a macro that used the  <at> Cell symbol
from within  <at> Tbl, I grepped through the include directory, and found
that all the references to  <at> Cell are in tblf. However,  <at> Cell is never
defined, that I can tell. It's always given as a named parameter of a
named parameter of a symbol. How does one construct an extend path for
that?

Cheers, 
Jason Whittle
Permalink | Reply | 0 comments |
headers
Tatyana Alexeyev | 15 Sep 2004 21:15
Picon
Favicon

escaping " character in a string

Hello,

I am trying to print the string which contains some
special characters, like " ...

I do not know how to escape " and the following option
does not work (enclosing in double quotes "s):
B{{Helvetica Base 9p}  <at> Font  <at> HContract  <at> HAdjust { <at> Font
 <at> B  {Product:   08"""}}

It gives me an error message when I try to create a
postscript document:

lout -s try.lout > a.ps
 16,78: unterminated string
    16,2: unmatched { (inserted })
    13,1: unmatched { (inserted })

Does anybody know how to escape single or double
quotes when creating a lout document.

Please let me know.

Tanya

		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
(Continue reading)

Permalink | Reply | 2 comments |

Gmane