ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Subject: Re: Spacing after defined word: beginner's question
Date: Mon, 25 Dec 2006 19:04:33 +0100	[thread overview]
Message-ID: <20061225190433.58e3ce07.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <862F542D-05D3-4BE7-8EE8-421E845F55DB@mac.com>

On Mon, 25 Dec 2006 16:45:15 +0000
cormullion@mac.com wrote:

> This must be a beginner's question, but I can't find the answer to it  
> in the manuals...
> 
> Take this ConTeXt source:
> 
> --
> \def\Acme{%
> 	{\ss\sc ACME}}
> 
> Welcome from \Acme. \Acme make fine products.
> --
> 
> When this is made into a PDF, it looks like this:
> 
> --
> Welcome from ACME. ACMEmake fine products.
> --
> 
> - because I didn't have a space in the definition, I don't get a  
> space in the second sentence, but the period didn't interfere with  
> the execution of the first occurrence. But if I put a space in the  
> definition after the 'E', I get this:
> 
> --
> Welcome from ACME . ACME make fine products.
> --
> 
> - and there's a space after the first 'E', which I don't want, even  
> though there is now a space after the second...
> 
> What am I doing wrong?

Hi ???,

TeX ignores spaces after commands. This is now problem when your
command is before an period, comma ...,but it will it up the next space
in a sentence.

You can write you sentence in the following ways:
  Welcome from \Acme. \Acme\ make fine products.
  Welcome from \Acme. \Acme{} make fine products.
  Welcome from \Acme. {\Acme} make fine products.

There is also a predefined command to define and setup your own
abbreviations and syonyms. You can find an example at page 55 in the
beginners manual (ma-cb-en.pdf).

Wolfgang

      parent reply	other threads:[~2006-12-25 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-25 16:45 cormullion
2006-12-25 17:42 ` Aditya Mahajan
2006-12-25 18:04 ` Wolfgang Schuster [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=20061225190433.58e3ce07.schuster.wolfgang@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).