From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: align and location in \setupcombination
Date: Mon, 29 Oct 2012 13:59:58 +0100 [thread overview]
Message-ID: <FF31A44A-A76D-4D24-BD5C-4B7E8F8FEBF0@gmail.com> (raw)
In-Reply-To: <8704AD50-BCB3-46FE-8743-9FE2DFE57B73@me.com>
Am 29.10.2012 um 13:31 schrieb Jeong Dal <haksan@me.com>:
> Dear Marco and Wolfgang,
>
> Thank you for solutions.
>
> I have tried \startalignment … \stopalignment, but it is not working.
> Does it work as same as \midaligned?
No, both commands work different. With \startalignment you can set a different \setupalign
setting for a certain part of your document and it does work for longer text but \midaligned
works only for content which fits on a single line. In the following example you can see
the text in the alignment environment is broken across line but the text in \midaligned is
placed in one long line which exceeds the page dimensions.
\starttext
\startalignment[middle]
\input ward
\stopalignment
\blank
\midaligned{\input ward }
\stoptext
> \startcontent … \stopcontent, \startcaption … \stopcaption seem to me a new commands.
> Is every command in ConTeXt changed as a form of "\start … \stop"?
No, not all commands are available in a start/stop form and even when it doesn’t
mean you can replace a command with a environment, e.g. \quotation{…} is
different from \startquotation … \stopquotation but there will be more commands
in the future which can be used as \start… and \stop…
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-10-29 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 12:31 Jeong Dal
2012-10-29 12:59 ` Wolfgang Schuster [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-27 11:38 Jeong Dal
2012-10-28 14:59 ` Marco Patzer
2012-10-28 15:24 ` Wolfgang Schuster
2012-10-30 12:01 ` Wolfgang Schuster
2012-10-30 12:36 ` Marco Patzer
2012-10-30 17:57 ` Wolfgang Schuster
2012-10-30 18:39 ` Hans Hagen
2012-10-30 19:04 ` Wolfgang Schuster
2012-10-30 20:49 ` Hans Hagen
2012-10-31 10:31 ` Alan BRASLAU
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=FF31A44A-A76D-4D24-BD5C-4B7E8F8FEBF0@gmail.com \
--to=wolfgang.schuster@gmail.com \
--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).