ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Uwe Koloska" <uwe.koloska@mailbox.tu-dresden.de>
Subject: experimenting metafun: problems with funnyframe
Date: Tue, 19 Dec 2000 03:02:23 +0100	[thread overview]
Message-ID: <00121903022302.01990@bilbo> (raw)

Hello,

I have just tried to gain a deeper insight into document preparation with 
context because in january I want to make a journal with it.

So I work through the metafun manual (27.10.2000) and have some question 
for the FunnyFrames example (4.6 Enhancing the layout):

1. What is the reason, the framed text does not span the whole line?  In 
core-rul I found that the width is derived from textwidth advanced 
-2\@@localoffset.  But where is this offset defined?

2. The lower space between text and frame is greater than the upper one.  
(this is the case in the manual, too)  Should I use \startlinecorrection? 
And how?  (just inside StartFrame, I cannot see a difference)

3. There are some funny hyphenations inside the frame (but they are right!) 
like "knowl-edge" ...  Anyway before I know that this is right, I looked 
into the .log from making the format (to find out wether the right 
hyphenation patterns are there).  And I found a great load of

language       : patterns en for en loaded (n=3)
(/usr/local/teTeX/texmf/tex/generic/hyphen/ushyph1.tex)
language       : no hyphenations en for en (n=3)
language       : patterns uk for uk loaded (n=4)
(/usr/local/teTeX/texmf/tex/generic/hyphen/ukhyphen.tex)
language       : no hyphenations uk for uk (n=4)
language       : patterns de for de loaded (n=5)

are this real problems?

4. How comes I cannot copy the _formatted_ sources from the pdf? Neither 
interactive nor print version worked.  I know (but not for sure) I have 
copied code with linebreaks from another pdf but don't know what file this 
was.

I am using Acrobat 4.05 and XEmacs on Linux.  But it seems it has to do 
with XEmacs, since I can copy with linebreaks to this mail (kmail2) ...

Is there someone on this list who has prepared some journal (no formal / 
scientific one, so maybe I should say magazine) and can give me some hints? 
I need illutrating titles, pictures, columns and normally a page centric 
layout.  Yes I know this is a task for a DTP program, but since this 
magazine is my playground (the last two issues are produced with vivapress 
professional and pagemaker) I am curious to see how context takes the 
challenge ;-))

Uwe

-- 
mailto:koloska@rcs.urz.tu-dresden.de
http://rcswww.urz.tu-dresden.de/~koloska/
--                                    --
right now the web page is in german only
but this will change as time goes by ;-)


             reply	other threads:[~2000-12-19  2:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-19  2:02 Uwe Koloska [this message]
2000-12-19  8:51 ` Berend de Boer
2000-12-19 12:26   ` S2P development
2000-12-20  2:06     ` Uwe Koloska
2000-12-19 11:10 ` Hans Hagen
2000-12-20  2:22   ` Uwe Koloska
2000-12-20  8:33     ` Hans Hagen
2000-12-20 16:54       ` Uwe Koloska
2000-12-21  8:06         ` Hans Hagen
2000-12-21 12:52           ` Uwe Koloska
2000-12-21 15:42             ` Hans Hagen
2000-12-20 17:52       ` Uwe Koloska
2000-12-21  8:16         ` Hans Hagen
2000-12-21 12:55           ` Uwe Koloska

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00121903022302.01990@bilbo \
    --to=uwe.koloska@mailbox.tu-dresden.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).