ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: RE: About XMLifequalelse
Date: Mon, 08 Apr 2002 17:38:11 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20020408173047.0316abe8@server-1> (raw)
In-Reply-To: <004601c1dedf$603d2de0$2197fac3@mii.cz>

At 11:25 AM 4/8/2002 +0200, Martin Kolarik wrote:

>4. relationships between TeX primitives and ConTeXt
>
>Being software developer is difficult for me to combine different layers of
>system without full understanding what happens (or can happen). Such thins
>(now) in ConTeXt are (I can explore ConTeXt sources, but the quick look into
>did not help me...)
>
>-- relationship between \setuptolerance[horizontal] and \emergencystretch

core-spa.tex is the fiel to look into (search for \process)

>-- relationship between \setupinterlinespacing and \lineskip,
>\lineskiplimit -- I noticed some piece of text is typeset corectly for
>\setupinterlinespacing[line=1.3em] but badly (baselines are not equidistant)
>for [line=1.2em] and I cannot influence this (it was strange, the same lines
>of text typeset later were correct)

you should not make the height too small, otherwise tex starts inserting 
lineskips

>Q: the relationships
>
>5. grid + default caption (chapter, section, title, sibject), itemize and
>description
>
>I want to have lines of text placed on the grid. If I use ConTeXt as is
>(with minimal own definitions and setups) the default line/paragraph spacing
>does not respects grid (I do not think I is bad...). For itemize (and for
>descriptions I hope too) I influence this using e.g. "style=joinedup", for
>captions probably using \startlinecorrections too.

no, \setuplayout[grid=on]

>Q: Is not there some built way to achieve proper grid positioning in
>ConTeXt? I would prefer ConTeXt way if exists to mine (proprietal).

grid snapping is available; i'm currently extending the snapper (precise 
control in for instance section headers, but this is still unofficial); it 
will be available in the next beta version; i'm also working on a manual 
that explains these things (and a few more); some 15 pages finished.

>6. hanging + and more common question
>
>My favourite :-) -- it is not functional now, but I must look where I have
>error...
>
>Q: isn't there some documentation to ConTeXt inside? E.g. how the font
>mechanism is working, how and when each of setup command takes effect,
>logical layering of function of commands, etc.? I am sure, it is NOT
>necessary for normal, mainstream ConTeXt users, but it would be very
>interesting for me :-) (and maybe some others too...)

texexec --modu --pdf font-ini
texexec --modu --pdf type-ini

>7. XML + UTF8
>
>Q: can ConTeXt handle UTF8 coded XMLs? I know it is rather complicated for
>TeX to realize it...

the machinery is there (Was needed for chinese) but i still have to add the 
definition files

>8. tilde
>
>If I use ~ in XML, it is not (of course) handled in the TeX way. I tried to
>change \defineXMLentity [tex-tilde] to the \lettertilde or simple ~, but TeX

you can define the XML entity to things like {\space\nobreak} and alike

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                                   fall-back web server: 
www.pragma-ade.nl
-------------------------------------------------------------------------


      parent reply	other threads:[~2002-04-08 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.1.0.14.1.20020405192017.02b84eb0@server-1>
     [not found] ` <004601c1dedf$603d2de0$2197fac3@mii.cz>
2002-04-08 15:30   ` Hans Hagen
2002-04-08 15:38   ` Hans Hagen [this message]

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=5.1.0.14.1.20020408173047.0316abe8@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /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).