On Sat, Mar 27, 2010 at 11:43:58AM +0100, luigi scarso wrote:
> On Sat, Mar 27, 2010 at 11:36 AM, Arthur Reutenauer
> wrote:
> >> may we can be package them in an otf format
> >
> > Right, OpenType can embed bitmap fonts (even TrueType could, if I'm
> > not mistaken);
> true
> > if the font is on
On 29-3-2010 0:45, Wolfgang Werners-Lucchini wrote:
I have it found!
In chapter 4.1.1.10 of the luatex reference one can read:
The argument name is a bit special in this case. Its form is
dpi/.pk
well, i could turn
600dpi/manfnt.720pk
into
manfnt.720pk
No, no! That makes sens
> > I have it found!
> >
> > In chapter 4.1.1.10 of the luatex reference one can read:
> >
> > The argument name is a bit special in this case. Its form is
> >
> > dpi/.pk
>
> well, i could turn
>
> 600dpi/manfnt.720pk
>
> into
>
> manfnt.720pk
>
No, no! That makes sense this way.
--
On 28-3-2010 22:59, Wolfgang Werners-Lucchini wrote:
Hallo,
I have it found!
In chapter 4.1.1.10 of the luatex reference one can read:
The argument name is a bit special in this case. Its form is
dpi/.pk
well, i could turn
600dpi/manfnt.720pk
into
manfnt.720pk
and then assume that
On 28-3-2010 22:53, Wolfgang Werners-Lucchini wrote:
Hallo Hans,
so it would be nice, if a user could see (from a log) what and
where luatex is searching. Isn't there any switch?
--track=resolvers.locating,resolvers.detail
Hmm! luatex ignores this and luatex --help does not list an option
n
Hallo,
I have it found!
In chapter 4.1.1.10 of the luatex reference one can read:
The argument name is a bit special in this case. Its form is
dpi/.pk
Wolfgang
___
If your question is of interest to others as well,
Hallo Hans,
> > so it would be nice, if a user could see (from a log) what and
> > where luatex is searching. Isn't there any switch?
>
> --track=resolvers.locating,resolvers.detail
Hmm! luatex ignores this and luatex --help does not list an option
named --track nor does it context.
Wolfgang
_
> I thought luatex does not use kpathsearch anymore?
You're right, Mark IV doesn't, so my piece of advice wasn't really
useful, sorry :-) But it is still there in LuaTeX (the engine).
Arthur
___
If your que
On 28-3-2010 15:39, Wolfgang Werners-Lucchini wrote:
Hallo Taco,
Dumping a ready-made pk file in the local directory worked last
time I tried it.
No success! Neiter *.pk nor *.600pk
and not with a local subdir /dpi600
What extension have you used?
.600pk (but that was ages ago, when I sti
Hallo Taco,
> >> Dumping a ready-made pk file in the local directory worked last
> >> time I tried it.
> >
> >
> > No success! Neiter *.pk nor *.600pk
> > and not with a local subdir /dpi600
> >
> > What extension have you used?
>
> .600pk (but that was ages ago, when I still cared about pk f
> > Is there a debug-switch which informs the user what and where
> > luatex is searching?
>
> If you're working in a shell, try setting the KPATHSEA_DEBUG
> environment variable to -1, you will get tons of information about
> path lookups and directory searches.
>
> Arthur
I thought lua
> No, neither OpenType or TrueType support bitmap-only, they can embed
> bitmaps besides the regular outlines
Thanks for the precision, Khaled. I have to admit I never looked into
the details, I only knew one could embed bitmaps, but it seems I
extrapolated a bit.
Arthur
__
On Sat, Mar 27, 2010 at 11:36:22AM +0100, Arthur Reutenauer wrote:
> > may we can be package them in an otf format
>
> Right, OpenType can embed bitmap fonts (even TrueType could, if I'm
> not mistaken); if the font is only available as PK, it should be
> possible to make it into an OpenType fon
Wolfgang Werners-Lucchini wrote:
On 27 Mar 2010 at 12:00, ntg-context-requ...@ntg.nl wrote:
That being said, I realize that it means Metafont fonts can't be
used in Mark IV, am I right?
Dumping a ready-made pk file in the local directory worked last
time I tried it.
No success! Neiter *.pk
On Fri, Mar 26, 2010 at 11:16 PM, Hartmut Henkel wrote:
> On Fri, 26 Mar 2010, Wolfgang Werners-Lucchini wrote:
>> On 26 Mar 2010 at 22:09, Hartmut Henkel wrote:
>> > On Fri, 26 Mar 2010, Hans Hagen wrote:
>> > > On 26-3-2010 21:30, Wolfgang Werners-Lucchini wrote:
>> > > >
>> > > > how should the
> Is there a debug-switch which informs the user what and where luatex
> is searching?
If you're working in a shell, try setting the KPATHSEA_DEBUG
environment variable to -1, you will get tons of information about path
lookups and directory searches.
Arthur
___
On 27 Mar 2010 at 12:00, ntg-context-requ...@ntg.nl wrote:
> > That being said, I realize that it means Metafont fonts can't be
> > used in Mark IV, am I right?
>
> Dumping a ready-made pk file in the local directory worked last
> time I tried it.
No success! Neiter *.pk nor *.600pk
and not wi
Arthur Reutenauer wrote:
may we can be package them in an otf format
Right, OpenType can embed bitmap fonts (even TrueType could, if I'm
not mistaken); if the font is only available as PK, it should be
possible to make it into an OpenType font, using FontForge, for example.
The chance of th
On Sat, Mar 27, 2010 at 11:36 AM, Arthur Reutenauer
wrote:
>> may we can be package them in an otf format
>
> Right, OpenType can embed bitmap fonts (even TrueType could, if I'm
> not mistaken);
true
> if the font is only available as PK, it should be
> possible to make it into an OpenType font,
> may we can be package them in an otf format
Right, OpenType can embed bitmap fonts (even TrueType could, if I'm
not mistaken); if the font is only available as PK, it should be
possible to make it into an OpenType font, using FontForge, for example.
That being said, I realize that it means
On Sat, Mar 27, 2010 at 10:37 AM, Hans Hagen wrote:
> On 27-3-2010 0:45, Taco Hoekwater wrote:
>>
>> Wolfgang Werners-Lucchini wrote:
>>>
>>> Hallo,
>>>
>>> how should the directory be named where a 600 dpi pk-font is searched
>>> for by luatex?
>>
>> Context mkiv does not support pk files (the lu
On 27-3-2010 0:45, Taco Hoekwater wrote:
Wolfgang Werners-Lucchini wrote:
Hallo,
how should the directory be named where a 600 dpi pk-font is searched
for by luatex?
Context mkiv does not support pk files (the luatex executable itself
does, but context mkiv overrules all search paths and does
Wolfgang Werners-Lucchini wrote:
Hallo,
how should the directory be named where a 600 dpi pk-font is searched
for by luatex?
Context mkiv does not support pk files (the luatex executable itself
does, but context mkiv overrules all search paths and does not support
searching for pk files).
Be
On Fri, 26 Mar 2010, Wolfgang Werners-Lucchini wrote:
> On 26 Mar 2010 at 22:09, Hartmut Henkel wrote:
> > On Fri, 26 Mar 2010, Hans Hagen wrote:
> > > On 26-3-2010 21:30, Wolfgang Werners-Lucchini wrote:
> > > >
> > > > how should the directory be named where a 600 dpi pk-font is
> > > > searched
On 26 Mar 2010 at 22:09, Hartmut Henkel wrote:
> On Fri, 26 Mar 2010, Hans Hagen wrote:
> > On 26-3-2010 21:30, Wolfgang Werners-Lucchini wrote:
> > >
> > > how should the directory be named where a 600 dpi pk-font is
> > > searched for by luatex?
> >
> > i'm not so sure if luatex does pk fonts (i
On Fri, 26 Mar 2010, Hans Hagen wrote:
> On 26-3-2010 21:30, Wolfgang Werners-Lucchini wrote:
> >
> > how should the directory be named where a 600 dpi pk-font is
> > searched for by luatex?
>
> i'm not so sure if luatex does pk fonts (i havent't included pk fonts
> in 15 years)
it does, with the
On 26-3-2010 21:30, Wolfgang Werners-Lucchini wrote:
Hallo,
how should the directory be named where a 600 dpi pk-font is searched
for by luatex?
i'm not so sure if luatex does pk fonts (i havent't included pk fonts in
15 years)
Hans
Hallo,
how should the directory be named where a 600 dpi pk-font is searched
for by luatex?
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@nt
28 matches
Mail list logo
