> Works as expected now
That's great news, but now that's because Hans has fixed the old
behaviour in today's (yesterday's) release ;-)
Arthur
___
If your question is of interest to others as well, please a
On Jan 11, 2008 7:15 PM, Arthur Reutenauer
<[EMAIL PROTECTED]> wrote:
> > If you mean simple rename to Unicode.ttf, copy into appropriate dir,
> > luatools --generate, well ,
> > this did not work last night.
>
> This can be caused by a number of things:
>
> 1. The original font file name was s
> (Am I wrong if I said that 'BOX DRAWINGS UP LIGHT AND LEFT HEAVY' is
> normative ?)
No, you're right, Unicode names are absolutely normative. So
normative, actually, that Unicode and ISO guarantee that they will never
change, ever (they're among the very few so-called stable properties).
But,
> wel, we can make a characters.context.descriptions but i'm not sure if
> it will really be used, because when one knows this rather verbose
> string (has looked it up), one could as well use the (also found)
> unicode directly
That's what I thought at first, but then I realized it could be
luigi scarso wrote:
> On Jan 11, 2008 4:29 PM, Hans Hagen <[EMAIL PROTECTED]> wrote:
>> Arthur Reutenauer wrote:
Is there another solution other than fontforge ?
>>> Sure, just rename the font to Unicode.ttf. And the problem should be
>>> fixed now, so try the next beta with the original na
> If you mean simple rename to Unicode.ttf, copy into appropriate dir,
> luatools --generate, well ,
> this did not work last night.
This can be caused by a number of things:
1. The original font file name was still stored in the cache.
2. You kept Unicode.otf along with Unicode.ttf, and Co
On Jan 11, 2008 4:29 PM, Hans Hagen <[EMAIL PROTECTED]> wrote:
> Arthur Reutenauer wrote:
> >> Is there another solution other than fontforge ?
> >
> > Sure, just rename the font to Unicode.ttf. And the problem should be
> > fixed now, so try the next beta with the original name as well.
> >
> >
On Jan 11, 2008 4:22 PM, Arthur Reutenauer
<[EMAIL PROTECTED]> wrote:
> > Is there another solution other than fontforge ?
>
> Sure, just rename the font to Unicode.ttf. And the problem should be
> fixed now, so try the next beta with the original name as well.
If you mean simple rename to Unico
Arthur Reutenauer wrote:
>> Is there another solution other than fontforge ?
>
> Sure, just rename the font to Unicode.ttf. And the problem should be
> fixed now, so try the next beta with the original name as well.
>
>> I mean using by using characters.data in char-def.lua:
>>
>> [0x25C9] =
> Is there another solution other than fontforge ?
Sure, just rename the font to Unicode.ttf. And the problem should be
fixed now, so try the next beta with the original name as well.
> I mean using by using characters.data in char-def.lua:
>
> [0x25C9] = { unicodeslot=0x25C9, category='so'
On Jan 11, 2008 5:03 AM, Arthur Reutenauer
<[EMAIL PROTECTED]> wrote:
> This seems to be a slight misfeature in Mark IV: I take that when
> opening a font file with an .otf extension, it assumes it is an OpenType
> font with PostScript outlines (cubic splines); when the file has a .ttf
> extensio
This seems to be a slight misfeature in Mark IV: I take that when
opening a font file with an .otf extension, it assumes it is an OpenType
font with PostScript outlines (cubic splines); when the file has a .ttf
extension, it supposes there are TrueType outlines (quadratic splines).
Both types of
>There is a better font if you need only symbols, choose the "Unicode
> Symbols" link on the following page.
>
> http://users.teilar.gr/~g1951d/
>
I'm trying to use Unicode.otf from http://users.teilar.gr/~g1951d
I just copied it into
texmf/fonts/opentype/unicodesymbols/Unicode.otf
run
luatools --
13 matches
Mail list logo
