ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: <josephcanedo@gmail.com>
To: "Alan BRASLAU" <alan.braslau@cea.fr>
Cc: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: Simple font size changes command
Date: Mon, 13 Jun 2016 07:30:04 +0000	[thread overview]
Message-ID: <63a352d244c24b34a3c524e6c56d9f03@gmail.com> (raw)
In-Reply-To: <20160612211954.03c0b5de@cea.fr>


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

It is (very) limited to few words only to reproduce how an old Bible I am trying to typeset  (words added in the text to ease the understand were printed in smaller size).


Thanks a lot

Regards


Joseph





From: Alan BRASLAU
Sent: ‎Monday‎, ‎June‎ ‎13‎, ‎2016 ‎5‎:‎19‎ ‎AM
To: josephcanedo@gmail.com
Cc: ntg-context@ntg.nl





On Sun, 12 Jun 2016 16:57:26 +0000
<josephcanedo@gmail.com> wrote:

> I was also a bit surprised with \tf<size> behaviour when used inside
> a scope of another one leading to 2 different sizes in output, as in
> 
> {\tfd Foo {\tfx Bar1}} {\tfx Bar2} Baz.
> 
> For the sake of knowledge I would be interested in knowing if this is
> expected eventually.

Yes, and this appears to me to be the most logical behavior.

By the way, the use of such "low-level" font changes is not very good
style in any case, and should be limited to special cases. In
particular, this will not export well in tagged output to xml, for
example, which is why I suggest the use of styles and "highlight".

Alan

[-- Attachment #1.2: Type: text/html, Size: 3154 bytes --]

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

___________________________________________________________________________________
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:[~2016-06-13  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 21:47 josephcanedo
2016-06-12 15:19 ` Alan BRASLAU
2016-06-12 16:57   ` josephcanedo
2016-06-13  3:19     ` Alan BRASLAU
2016-06-13  7:30       ` josephcanedo [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=63a352d244c24b34a3c524e6c56d9f03@gmail.com \
    --to=josephcanedo@gmail.com \
    --cc=alan.braslau@cea.fr \
    --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).