RE: About XMLifequalelse

RE: About XMLifequalelse

[Hans Hagen]

At 11:25 AM 4/8/2002 +0200, Martin Kolarik wrote:
>I really like software,
>
>thank you -- after I installed last beta (I have installed stable version) I
>get immediately \XMLown... :-) and after aplying the patch all works fine.
>
>I have a few next questions (maybe something was answered in the discussion
>group sooner, but I cannot find it):
>
>1. XML + \startcombination...\stopcombination
>
>I tried to define XML environment <env> containing <item>(s) represented in
>ConTeXt with \startcombination...\stopcombination. As it takes arguments in
>{} I stored items of <env> in token register (directly or using a
>special-named macro for each <item>) and at the end of </env> I flushed this
>tokens using \startcombination[...]\the\tokens\stopcombination.

\expanded{\startcombination[...]\the\tokens}\stopcombination

What exactly do you want do achieve? Combinations are meant for figures, so 
maybe a tabulate is better

>But, using this method does not respect explicit \par (or \engraf) placed
>inside the stored stream. If I use \startitemize inside
><env><item>there</item></env> the list is badly formated -- whole in one
>line until I insert \par between the list items implicitly (directly to the
>XML). The list is still not fully correct, but at least the items are
>formatted/displayed in separate paragraphs.
>
>Thus I tried to use for storing <item> \startbuffer..\stopbuffer. But this
>failed, because (I think) this environment in this (my) case collides with
>XML -- there is (after \tracingmacros=1) correctly seen argument of <item>
>(e.g. "data 1") but incorrectly data for startbuffer "data 1 and next text
>until the end of the file" in the log file. The \startbuffer is incomplete
>and TeX fails.
>
>Now the question -- I there some solution to format XML input (<env>) into
>the \start,stopcombination? and allow inside <item> paragraphs and other
>nested environments?

i need a minimal example file of what you want

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

RE: About XMLifequalelse

[Hans Hagen]

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