On Tue, Apr 8, 2008 at 12:50 AM, Mojca Miklavec
[EMAIL PROTECTED] wrote:
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm wrote:
Oh? I thought uc encoding would magically enhance my type1 fonts with
full unicode range...
;-)
I almost forgot ... to be honest, I wanted to say:
2008/4/8, Wolfgang Schuster [EMAIL PROTECTED]:
On Tue, Apr 8, 2008 at 12:50 AM, Mojca Miklavec
[EMAIL PROTECTED] wrote:
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm wrote:
Oh? I thought uc encoding would magically enhance my type1 fonts with
full unicode range...
;-)
On Tue, Apr 8, 2008 at 9:11 AM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
2008/4/8, Wolfgang Schuster [EMAIL PROTECTED]:
On Tue, Apr 8, 2008 at 12:50 AM, Mojca Miklavec
[EMAIL PROTECTED] wrote:
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm wrote:
Oh? I thought uc encoding
Mojca Miklavec wrote:
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm wrote:
Oh? I thought uc encoding would magically enhance my type1 fonts with
full unicode range...
;-)
I almost forgot ... to be honest, I wanted to say: LuaTeX does
exactly that, but then I have remembered that
Mojca Miklavec wrote:
Hello Hraban,
thanks for pointing this out.
To Hans: the \typescriptthree indeed needs to go out of those
definitions (line 300 in type-otf).
hm, can you post the line? i have this
\starttypescript [serif] [adventor,bonum,cursor,heros,pagella,schola,termes]
To
On Tue, Apr 8, 2008 at 10:13 AM, Hans Hagen wrote:
Mojca Miklavec wrote:
Hello Hraban,
thanks for pointing this out.
To Hans: the \typescriptthree indeed needs to go out of those
definitions (line 300 in type-otf).
hm, can you post the line? i have this
300-311 (301-310),
Mojca Miklavec wrote:
300-311 (301-310), this are the fixed ones, but probably broken across lines:
ok, fixed
To Hraban: oh, I did not understand you joke at first :-) Now I see
what you were trying to say with extending the font to the full
unicode range :-) And sure enough - LuaTeX
Am 2008-04-08 um 13:41 schrieb Hans Hagen:
To Hraban: oh, I did not understand you joke at first :-) Now I see
what you were trying to say with extending the font to the full
unicode range :-) And sure enough - LuaTeX doesn't do that either.
Sorry, I should know since a few years that my
Hello Hraban,
thanks for pointing this out.
To Hans: the \typescriptthree indeed needs to go out of those
definitions (line 300 in type-otf).
To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
you will be able to extract any more than (theoretical limit of) 256
glyphs from
Am 2008-04-07 um 12:58 schrieb Mojca Miklavec:
To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
you will be able to extract any more than (theoretical limit of) 256
glyphs from the Type1 font with XeTeX - character slots and font
glyphs are in one-to-one correlation, so I
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
Am 2008-04-07 um 12:58 schrieb Mojca Miklavec:
To Hraban: encoding=uc has *zero* effect. To be honest - I doubt that
you will be able to extract any more than (theoretical limit of) 256
glyphs from the Type1
On Mon, Apr 7, 2008 at 8:22 PM, Henning Hraban Ramm wrote:
Oh? I thought uc encoding would magically enhance my type1 fonts with
full unicode range...
;-)
I almost forgot ... to be honest, I wanted to say: LuaTeX does
exactly that, but then I have remembered that you have explicitely
asked
Am 2008-04-06 um 13:35 schrieb Henning Hraban Ramm:
(2)
This seems wrong to me (i.e. I don't understand it):
\starttypescript [serif]
[adventor,bonum,cursor,heros,pagella,schola,termes]
\definefontsynonym
[\typescriptprefix{n:\typescripttwo}-Regular]
13 matches
Mail list logo
