From: Andrea Valle <valle@di.unito.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: fonts (in luatex) (again)
Date: Mon, 30 Jun 2008 22:42:17 +0200 [thread overview]
Message-ID: <82AFE03A-ADC3-452A-9D96-5E4877B52C9E@di.unito.it> (raw)
In-Reply-To: <1214675743.7122.23.camel@elbereth>
[-- Attachment #1.1: Type: text/plain, Size: 4758 bytes --]
Thanks Charles
A praise from the heart to the devs.
Wouldn't be possibile to support font selection like in XeTeX?
This would make thing really a lot easier for sublunar users like me.
Really, the whole process it's damn' complicated: no one a part 2 or
3 seems to know the details :)
Best
-a-
On 28 Jun 2008, at 19:55, Charles P. Schaum wrote:
> This first bit differentiates a "backend" that refers to your font
> and a
> "frontend" that you normally work with. Why?
>
> Macros, macros, macros. Let's put it this way: You could have a myriad
> of styles. That's what many in the WYSIWYG world do. Then ... they
> have
> to keep track of them all.
>
> But TeX, as a Turing-complete programming language that could
> theoretically be used for lots of things, has the design of local
> redefinition, so that "sans" within a group or a macro can be
> redefined
> to something other than delicious without you needing to worry about
> keeping track of global style changes.
>
> In short, like the Unix "small is beautiful" philosophy (and good
> programming) you make parts of your document that work, you put the
> working parts together, and the whole thing should have a good shot at
> working. It will also be remarkably consistent and behave in a manner
> that is more regular than, for example, Word's typesetting engine.
>
> And if you are working on a source for different outputs or even
> different possibilities of publication, you can switch out a font
> without having to muck about through every font reference in your
> document, saving hours of labor.
>>
>> \starttypescript [sans] [delicious]
>> \setups[font:fallback:sans]
>> \definefontsynonym [Sans] [Delicious-Regular]
>> \definefontsynonym [SansItalic] [Delicious-Italic]
>> \definefontsynonym [SansBold] [Delicious-Bold]
>> \definefontsynonym [SansBoldItalic] [Delicious-BoldItalic]
>> \definefontsynonym [SansCaps] [Delicious-Caps]
>> \stoptypescript
>>
>
> As I understand, this next bit maps the "expectations" of the
> typesetting engine to the capabilities of the font. For example, when
> working with InDesign/InCopy and importing things from Word, there's a
> difference between character style mappings and local overrides.
>
> Word processors usually employ local overrides. That means usually the
> typesetting engine picks from the alternative of a font face for bold,
> italic, and so on, or it takes the default face and changes its
> rasterization to create a faux bold, italic, and so on. In good
> typesetting, however, you actually link character styles with actual
> fonts, just like you would when hand-compositing blocks of type in a
> typecase with lots of clamps and so on.
>
> This bit looks like what character styles do in InDesign. The more
> I get
> into InDesign and work with my designers, the more I understand the
> basic typographical principles that make TeX and ConTeXt elegant.
>>
>> \starttypescript [sans] [delicious]
>> \definefontsynonym [Delicious-Regular] [name:Delicious-Roman]
>> [features=default]
>> \definefontsynonym [Delicious-Italic] [name:Delicious-Italic]
>> [features=default]
>> \definefontsynonym [Delicious-Bold] [name:Delicious-Bold]
>> [features=default]
>> \definefontsynonym [Delicious-BoldItalic]
>> [name:Delicious-BoldItalic] [features=default]
>> \definefontsynonym [Delicious-Caps] [name:Delicious-SmallCaps]
>> [features=default]
>> \stoptypescript
>>
>>
>
> The following is not in the Ubuntu-distributed manual, so I am not
> sure
> about it.
>
>> \starttypescript [delicious]
>> \definetypeface [delicious] [ss] [sans] [delicious] [default]
>> \stoptypescript
>>
>
>
>
> ______________________________________________________________________
> _____________
> 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
> ______________________________________________________________________
> _____________
--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - DAMS
Università degli Studi di Torino
--> http://www.cirma.unito.it/andrea/
--> http://www.myspace.com/andreavalle
--> andrea.valle@unito.it
--------------------------------------------------
"
Think of it as seasoning
. noise [salt] is boring
. F(blah) [food without salt] can be boring
. F(noise, blah) can be really tasty
"
(Ken Perlin on noise)
[-- Attachment #1.2: Type: text/html, Size: 18425 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-30 20:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 15:34 Andrea Valle
2008-06-28 17:55 ` Charles P. Schaum
2008-06-30 20:42 ` Andrea Valle [this message]
2008-06-30 21:06 ` Hans Hagen
2008-07-02 13:25 ` Andrea Valle
2008-07-02 15:41 ` Hans Hagen
2008-07-02 17:22 ` Andrea Valle
2008-07-02 22:09 ` Hans Hagen
2008-07-02 23:40 ` Andrea Valle
2008-07-03 7:55 ` Hans Hagen
2008-07-03 7:57 ` Mojca Miklavec
2008-07-03 8:48 ` Wolfgang Schuster
2008-07-03 9:28 ` Mojca Miklavec
2008-07-03 9:40 ` Wolfgang Schuster
2008-07-03 9:22 ` Khaled Hosny
2008-07-03 9:51 ` Hans Hagen
2008-07-03 6:47 ` Wolfgang Schuster
2008-07-02 23:30 ` Diego Depaoli
2008-06-30 6:56 ` Wolfgang Schuster
2008-06-30 20:37 ` Andrea Valle
2008-07-15 13:14 ` Andrea Valle
2008-07-15 13:22 ` Mojca Miklavec
2008-07-15 13:34 ` Andrea Valle
2008-07-15 14:16 ` Mojca Miklavec
2008-07-15 14:18 ` Mojca Miklavec
2008-07-15 15:10 ` Andrea Valle
2008-07-15 15:35 ` Mojca Miklavec
2008-07-15 15:41 ` Taco Hoekwater
2008-07-15 16:22 ` Arthur Reutenauer
2008-07-15 15:59 ` Andrea Valle
2008-07-15 16:27 ` Mojca Miklavec
2008-07-15 19:19 ` Thomas A. Schmitz
2008-07-15 20:53 ` Charles P. Schaum
2008-07-15 21:58 ` Taco Hoekwater
2008-07-15 21:30 ` Andrea Valle
2008-07-16 0:42 ` Diego Depaoli
2008-07-16 7:15 ` Andrea Valle
2008-07-16 11:26 ` Wolfgang Schuster
2008-07-17 8:05 ` Andrea Valle
2008-07-15 20:36 ` Hans Hagen
2008-07-15 20:54 ` Hans Hagen
2008-07-15 21:04 ` Andrea Valle
2008-07-15 14:39 ` Andrea Valle
2008-07-15 14:50 ` Aditya Mahajan
2008-07-15 15:53 ` Mojca Miklavec
2008-07-15 15:57 ` Andrea Valle
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=82AFE03A-ADC3-452A-9D96-5E4877B52C9E@di.unito.it \
--to=valle@di.unito.it \
--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).