ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "P. Hanák" <hanak@wpb.cz>
To: ntg-context@ntg.nl
Subject: Re: Example from FAQ not working
Date: Wed, 06 Feb 2013 17:46:42 +0100	[thread overview]
Message-ID: <83pq0dcrv1.fsf@alfik.habrovka.xx> (raw)

Hi,

  >> Hi,
  >> 
  >> now I noticed that I can even use some non-existing alignment:
  >> 
  >> 
  >>   \setuppapersize[A5]
  >> 
  >>   \setuplayout[location=middle,
  >>                header=0pt,
  >>                footer=0pt,
  >>                height=fit,
  >>                width=109mm
  >>                ]
  >> 
  >>   \setupindenting[next,\baselineskip]
  >> 
  >>   \indenting[yes]
  >> 
  >>   \setupalign[nonexisting]
  >> 
  >>   \starttext
  >> 
  >>   Today, automated typesetting is quite popular, which is partly due to the fact that
  >>   document coding standards have evolved, in particular XML. For instance, when you
  >>   navigate the internet, a typesetting engine is at work to render the pages. When you
  >>   ask for a print preview, you often get a different rendering. So, one document source
  >>   can result in different views.
  >> 
  >>   The vehicle that we use for automated typesetting of books is called CONTEXT. This
  >>   system is based on the well known typesetting engine and language TEX and the
  >>   graphic programming environment METAPOST.
  >> 
  >>   \stoptext
  >> 
  >> This example is processed without errors although there is no definition
  >> of the alignment "nonexisting". Is it not strange?
  > 
  > When ConTeXt parses the \setupalign command it looks if the keyword is defined
  > and executes it but when the keyword isn?t defined its just ignored.
  > 
  > Wolfgang

thank you for your explanation. So probably my definition of new
alignment "block" was not successful and when using \setupalign the
alignment with the keyword "block" is simply ignored.

Is there any possibility to find out if the new alignment was really
defined and exists?

\installalign
   {block}
   {\parfillskip=\hsize
    \advance\parfillskip by -1.5\parindent
    \advance\parfillskip by 0pt minus \parfillskip
    \advance\parfillskip by 0pt minus -1em}

% Next command is probably ignored? Can I test if the alignment "block"
% really exists?

\setupalign[block]

Best regards

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


             reply	other threads:[~2013-02-06 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 16:46 P. Hanák [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-06 14:04 P. Hanák
2013-02-06 14:09 ` Wolfgang Schuster

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=83pq0dcrv1.fsf@alfik.habrovka.xx \
    --to=hanak@wpb.cz \
    --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).