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>
Subject: Re: New module - mkiv font loading
Date: Mon, 11 May 2009 16:33:17 +0200	[thread overview]
Message-ID: <4A08372D.9020800@wxs.nl> (raw)
In-Reply-To: <68bfdc900905110658p6294e07fu71be47f3fbb0a1f6@mail.gmail.com>

Yue Wang wrote:
> On Mon, May 11, 2009 at 9:48 PM, Hans Hagen <pragma@wxs.nl> wrote:
>> Wolfgang Schuster wrote:
>>
>>> possible yes but it's a lot of work because the complete fallback
>>> mechanism
>>> needs to be written for XeTeX which is available for MkIV since a while.
>> this is unlikely to happen (unless we add lots of optional code to mkii to
>> deal with xetex which then probably results in a lot of other code hooked
>> into other mechanisms as well) as mkii is kind of frozen
>>
>> if we have to port all sophisticated (upcoming) mkiv features back to mkiv
>> we might wonder why we started with mkiv in the first place; the whole idea
>> is to have less (complex) code
> 
> 
> not like that complicated (we do not need font fallback).
> 
> it is only something about:
> 
> save the current font style (like \ss, \it ,10pt) to a macro . then
> apply the macro to a group.
> for example
> 
> aa { \anotherfont bb}
> we should save the style for aa when \anotherfont is called, and apply
> that style to bb.
> 
> that should be enough. but we don't know how to get the font style.

see \pushcurrentfont

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-05-11 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 12:23 Wolfgang Schuster
2009-05-11 12:41 ` Yue Wang
2009-05-11 13:00   ` Wolfgang Schuster
2009-05-11 13:44     ` Yue Wang
2009-05-11 13:48     ` Hans Hagen
2009-05-11 13:58       ` Yue Wang
2009-05-11 14:33         ` Hans Hagen [this message]
2009-05-11 14:38           ` Yue Wang
2009-05-11 17:32       ` Wolfgang Schuster
2009-05-12  7:47   ` Wolfgang Schuster
2009-05-11 13:18 ` Mohamed Bana
2009-05-11 13:31   ` Wolfgang Schuster
2009-05-11 13:32   ` Yanrui Li
2009-05-15 19:36 ` Mohamed Bana
2009-05-16  6:49   ` Wolfgang Schuster
2009-05-16 16:23 ` Mohamed Bana
2009-05-16 16:30   ` Hans Hagen
2009-05-16 16:36   ` 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=4A08372D.9020800@wxs.nl \
    --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).