LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Mime-Version:
1.0 (Apple Message framework v1084)
Content-Type:
text/plain; charset=us-ascii
Date:
Mon, 1 Aug 2011 08:24:38 -0400
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
Re: future
From:
William Adams <[log in to unmask]>
Message-ID:
<[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-Transfer-Encoding:
8bit
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (20 lines) 
On Aug 1, 2011, at 8:01 AM, William Adams wrote:

> So I guess this has two questions:
> 
> 1 - what is the optimal way to get non-standard characters like that into a text stream?

There's an obvious corollary to this:

1b - Do we have a list of characters which are replaced by vector elements? If so, what should be done about them?

I believe that in any instance of the user issuing a command to output character(s) matching character(s) need to show up in the output.

William

-- 
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.

ATOM RSS1 RSS2