From: Bernd Kosubek <kosubek@sksatz.de>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with "packed" and "\space" / "broad" and "/nospace"
Date: Mon, 23 Feb 2009 22:35:26 +0100 [thread overview]
Message-ID: <200902232235.30147.kosubek@sksatz.de> (raw)
In-Reply-To: <42586F4A-1B1B-4583-B574-206A1F163716@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Montag, 23. Februar 2009 21:56 schrieb Wolfgang Schuster:
> Am 23.02.2009 um 21:52 schrieb Bernd Kosubek:
> > If I run "texexec" over this, the last three line are
> > longer than the first line AND they have the same
> > lengths.
> >
> > What have I not understand -- or is it a known problem
> > or a bug?
>
> You get what you write.
>
> 2. Sentence: \space{} = 2 spaces because of the {}
>
> 3. Sentence: Wide than the first sentence because of the
> disabled frenchspacing
>
> 4. Sentence: You write \nospace but insert a space with
> {}
>
> Wolfgang
Thank You for the quick answer.
I don't understand where the second space should be come
from.
I use the empty group "{}" always to separate optionless
commands.
I think it is the same whether I write:
xxxx. yyyy. or
xxxy.{} yyyy. or
xxxx.
yyyy. or
xxxx.{}
yyyy.
If I use
xxxx.\space yyyy or xxxx.\space{} yyyy
the first \space produce NO space (that is not what I wish)
I suppose, that the empty group has no effect.
The following space will be printed and THIS space should be
smaller in an broad-environment if I use \nospace or larger
in an packed-environment if I use \space.
- --
Bernd Kosubek
Unsigned eMail are not from me.
eMail: kosubek@sksatz.com
Fingerprint: C121 F3C2 A6DD 1ACD A9BC F0AF 1289 2AEC B7C4
D63B
URL: http://www.sksatz.com
Keyserver: blackhole.pca.dfn.de (oder andere)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQFJoxafEokq7LfE1jsRAjXLAKCHuX5TDHnEfKscgY02u+DoLSZXVgCffQRA
AncnhYSkHngDZV57RKRnPdQ=
=C9Pg
-----END PGP SIGNATURE-----
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-23 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 20:52 Bernd Kosubek
2009-02-23 20:56 ` Wolfgang Schuster
2009-02-23 21:35 ` Bernd Kosubek [this message]
2009-02-23 21:34 ` Wolfgang Schuster
2009-02-23 22:01 ` Bernd Kosubek
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=200902232235.30147.kosubek@sksatz.de \
--to=kosubek@sksatz.de \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.com \
/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).