LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Transfer-Encoding:
8bit
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
From:
"J.Fine" <[log in to unmask]>
Date:
Fri, 1 Dec 2006 17:15:42 -0000
Content-Type:
text/plain; charset="us-ascii"
MIME-Version:
1.0
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (17 lines)
Frank wrote:

> in other words, somewhere there has to be a knowledgeable 
> instance that decides
> what to do when a current font selection doesn't work for the 
> requested
> characters because it is not part of the supported glyph set 
> of that resource
> --- you can consider that part of the font selection 
> intelligence and it is
> not resolved with a naming standard for characters eg unicode

Is that not what virtual fonts are for?

-- 
Jonathan

ATOM RSS1 RSS2