ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Reimplementing xspace
Date: Sun, 20 Jan 2002 20:50:51 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20020120203537.02bfefb0@server-1> (raw)
In-Reply-To: <20020117220337.GB762@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 2085 bytes --]

At 07:03 AM 1/18/2002 +0000, Marco Kuhlmann wrote:
><file://f:\mail\eudora\attach\Re Reimplementing xspace.ems 
><0880.0002>>501f5.jpg<file://f:\mail\eudora\attach\Re Reimplementing 
>xspace.ems <0880.0002>> Re Reimplementing xspace.ems

^^^^ those pgp messages cannot be quoted, only painfully copied ^^^^

 >> so the problem is rather on how to integrate this with the rest of
 >> ConTeXt: there are some features of ConTeXt (e.g. logos,
 >> abbreviations) for which obeying spaces should be an option.
 >
 >I think this definitely needs consideration. It belongs to a
 >broader topic "programmable typography", to which I would add

programmable typo depends on extensive tagging; the outcome of minimal 
tagging as in the following items depends much on the availability of 
trigger points; complications arrise when content is hidden in capsules 
(macros, boxxes) since this breaks lookahead and lookback. As a result, 
having such features available will definitely lead to suboptimal output 
unless each instance is visually tested.

 >issues like
 >
 >  - dotted abbreviations (normally, you want a dot after them,
 >    but not at the end of a sentence),

can be a feature, but never be default; a user should turn it on thereby 
knowing that checking is needed; an important question to answer is: how 
does this relate to languages.

 >  - capitals (it would be great if ConTeXt could automatically
 >    detect sequences of capitals and optionally typeset them a
 >    little smaller than the rest of the text),

can only be done with active chars and fuzzy logic; can of worms; however, 
a macro based solution is already available in \Words; tricky point: there 
is no real watertight grabbing / mapping for arbitrary chars other than 
bytecoded ones.

 >  - hanging punctuation (does not work for all punctuation yet,
 >    and does not? work for left margins),

this is already there in protruding characters in pdftex, highy 
configurable for *all* characters, left and right

 >and some others.

[supp-box and syst-* and supp-fun already provide some trickery]

Hans

[-- Attachment #1.2: 501f5.jpg --]
[-- Type: image/jpeg, Size: 2443 bytes --]

[-- Attachment #2: Type: text/plain, Size: 523 bytes --]

-------------------------------------------------------------------------
                                   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-pod.nl
-------------------------------------------------------------------------

  parent reply	other threads:[~2002-01-20 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 12:43 Giuseppe Bilotta
2002-01-17 22:03 ` Marco Kuhlmann
2002-01-17 23:05   ` Re[2]: " Giuseppe Bilotta
2002-01-17 23:12     ` Marco Kuhlmann
2002-01-18 11:23       ` Re[2]: " Giuseppe Bilotta
2002-01-20 20:12         ` Hans Hagen
2002-01-20 20:09       ` Hans Hagen
2002-01-20 19:50   ` Hans Hagen [this message]
2002-01-20 20:35 ` Hans Hagen
2002-01-21 14:37   ` Re[2]: " Giuseppe Bilotta

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=5.1.0.14.1.20020120203537.02bfefb0@server-1 \
    --to=pragma@wxs.nl \
    --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).