ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Aíre Funvake" <aire.funvake@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX-Plain and OTF/TTF Fonts
Date: Tue, 06 May 2014 21:51:53 +0200	[thread overview]
Message-ID: <53693D59.4040905@gmail.com> (raw)
In-Reply-To: <53693467.5060805@wxs.nl>

On Tue May  6 21:13:43 2014, Hans Hagen wrote:
> On 5/6/2014 4:49 PM, Aire Funvake wrote:
>> Dear Group,
>>
>> Thank you for your time. I'm starting out with TeX/ConTeXt, but
>> want to arrive via LuaTeX (`luatex-plain.tex/fmt`). Managed to
>> build, move and use `luatex-plain`. Have the same problem under
>> MacOSX & Win7 (here is the Win-specific decription -- `%CTX%` is
>> my ConTeXt root):
>>
>> ....
>> Setting `OSFONTDIR` before font update and/or before running
>> `luatex-plain`, have no observable effect.
>>
>> So, I do have a manual fix/solution. But is there an easier way?
>
> I assume you made a plain format with:
>
>   mtxrun --script plain --make
>
> Then, does this work:
>
>   mtxrun --script plain luatex-test
>
> okay?
>
> Hans
> 8<-----------------------------------------------------------------

Hi Hans,

No, I made it with `luatex --ini luatex-plain.fmt` and copied
the resulting `.fmt` file. But, I executed the first command
just now, just to be sure, and then ran the next command:
`mtxrun --script plain luatex-test`. Result:

\write18 enabled.
...
tex/texmf-cache/luatex-cache/generic/fonts/data/luatex-fonts-names.luc)(load 
luc
: 
c:/ctx/tex/texmf-cache/luatex-cache/generic/fonts/otf/lmroman10-bold.luc)<unkn
own font in database, run: mtxrun --script fonts --reload --simple>
! LuaTeX error 
...ntext/tex/generic/context/luatex/luatex-fonts-merged.lua:6213:
 attempt to index field 'known' (a nil value).
<to be read again>
\par
l.33

?R<enter>

After `R`, it did produced `luatex-test.pdf`. Not sure if it
looks the way it should ... couple of overfull boxes, narrow
third page.

Either way, I updated the fonts again as above, checked that
it recreated the `luatex-fonts-names.lua` file like before.
If I delete the old `luatex-fonts-names.luc`, the next run of
`luatex-plain hello.tex` produces the same result. Added the
paths to the fonts in `luatex-fonts-names.lua` (minion &
myriad), ran `luatex-plain hello.tex` again ... and all is fine.

Further experimentation: Copied the "Source Sans Pro" fonts to
a subdirectory alongside the `minion` and `myriad` directories,
(`%CTX%\tex\texmf-fonts\otf\sourcesans`), and again updated the
fonts database(s). Upon inspection of `luatex-fonts-names.lua`,
the Source Sans fonts and files are listed, but they *did* have
the path prefixed to the font file names, and consequently, I
could use them without modifying `luatex-fonts-names.lua`.

Thank you for your reply. I'm convinced this is no bug, just my
inexperience at play. This is not a crippling problem. I can
tackle The TeXbook now.

Regards,
Aíre Funvake.


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2014-05-06 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 14:49 Aire Funvake
2014-05-06 19:13 ` Hans Hagen
2014-05-06 19:51   ` Aíre Funvake [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53693D59.4040905@gmail.com \
    --to=aire.funvake@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).