ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Small caps?
Date: Wed, 25 Jul 2012 09:53:32 +0200	[thread overview]
Message-ID: <500FA5FC.30407@wxs.nl> (raw)
In-Reply-To: <CALBOmsYiN1iR6pNNu=PMf-+aBGo1Fc6XX8h-ZrE8gA4NVAA0KQ@mail.gmail.com>

On 25-7-2012 09:41, Mojca Miklavec wrote:
> On Wed, Jul 25, 2012 at 9:35 AM, Hans Hagen wrote:
>> On 25-7-2012 04:33, Shriramana Sharma wrote:
>>
>>> Basically I'm trying to move away from wordprocessors, and while I'm
>>> not looking for meaningless effects like "walking ants" (from MS Word)
>>> to be provided by TeX macro packages, faux smallcaps (and oblique and
>>> bold) is not an unreasonable thing to expect IMO. Not everyone is a
>>> typographer to produce the appropriate fine-typography glyphs for
>>> their favourite font to cater to a particular style. Why should the
>>> system impose "super-duper" typography on users when they are willing
>>> to settle for less?
>>
>> Sure, but one problem with a mkii fake approach is that it is fragile when
>> something else than 8 bit characters shows up in the content stream.
>
> Is that also true for XeTeX? (What is an 8-bit character when talking of XeTeX?)

On the one hand less, as a token can be an utf character, but fo rother 
bits and pieces of the input it is still tricky. Given the earlier 
posted code:

     \smallcaps{àáâãäå Watch out for returns.}

That works, but the next doesn't:

     \smallcaps{àáâãäå Watch out for \TEX\ returns.}

So, a parser would have to deal with things like this:

\TEX
{\bold test}
\hbox{test}

There are some token processors in mkii that deal with some of these 
aspects.

> But it lacks Indic scripts, so it's not an option for him, at least not yet.

Indic scripts will be supported in mkiv some day soon (at the ntg 
meeting there has been a presentation about devanagari etc using the 
context font machinery and that will be integrated once it's stable).

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2012-07-25  7:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 19:11 Shriramana Sharma
2012-07-24 19:25 ` Wolfgang Schuster
2012-07-24 19:29   ` Shriramana Sharma
2012-07-24 21:21     ` Hans Hagen
2012-07-24 21:52       ` Khaled Hosny
2012-07-24 19:34 ` Marco
2012-07-25  2:33   ` Shriramana Sharma
2012-07-25  3:08     ` Aditya Mahajan
2012-07-25  4:39       ` Shriramana Sharma
2012-07-25  4:59     ` Rogers, Michael K
2012-07-25  5:06       ` Shriramana Sharma
2012-07-25  7:04         ` Marco
2012-07-25  7:43           ` Mojca Miklavec
2012-07-25 13:12             ` Wolfgang Schuster
2012-07-25 12:34         ` Rogers, Michael K
2012-07-25  7:35     ` Hans Hagen
2012-07-25  7:41       ` Mojca Miklavec
2012-07-25  7:53         ` Hans Hagen [this message]
2012-07-25  8:16           ` Shriramana Sharma
2012-07-25  8:22             ` luigi scarso
2012-07-25  8:24             ` Hans Hagen

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=500FA5FC.30407@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mojca.miklavec.lists@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).