ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 'kern': TrueType table and GPOS lookup feature
Date: Sat, 1 Dec 2012 20:22:36 +0100	[thread overview]
Message-ID: <CAG5iGsA1Z8DxQApYXanbkX3-AKt=9S9PVrz8m4QpH5KNkXvntg@mail.gmail.com> (raw)
In-Reply-To: <CAEmWKkScj0OerZED2kCpV4825ufTkJvaygcg2LfqDrYuycAKEQ@mail.gmail.com>

On Sat, Dec 1, 2012 at 5:22 PM, Steve White <stevan.white@gmail.com> wrote:
> Hi Luigi,
>
> I got ConTeXt installed and running, but the install was very choppy.
>
> FYI the script you gave me had several problems, which I'll detail here.
>
> 1) Throughout you want
>        freefont-ttf-20120503
>     rather than
>        freefont-src-20120503
yes, sorry  (btw  It would be nice to support the sfd format ...)

>
> 2) This line has a stray backslash character
>        bash /first-setup.sh --modules=simplefonts
yes again sorry --  bash  first-setup.sh --modules=simplefonts
or
bash ./first-setup.sh --modules=simplefonts
>
> 3) The command
>       mtxrun --script font --reload
>     searches a bunch of directories for fonts, but not the directory
>       texmf-project/fonts/
>     My work-around was just to copy the *.ttf files to
>       texmf-fonts/
>     and then re-do the mtxrun line.
Hm, no, this is strange --- are you sure ?
If I remove the files from texmf-project/fonts/
and make
mtxrun --script font --reload
I have
mtxrun --script font --list --all|grep Free
But when I copy them again in
texmf-project/fonts/
and
mtxrun --script font --reload
then
mtxrun --script font --list --all|grep Free
then I see

freemono                             freemono
FreeMono.ttf
freemonobold                         freemonobold
FreeMonoBold.ttf
freemonoboldoblique                  freemonoboldoblique
FreeMonoBoldOblique.ttf
freemononormal                       freemonooblique
FreeMonoOblique.ttf
freemonooblique                      freemonooblique
FreeMonoOblique.ttf
freesans                             freesans
FreeSans.ttf
freesansbold                         freesansbold
FreeSansBold.ttf
freesansboldoblique                  freesansboldoblique
FreeSansBoldOblique.ttf
freesansdemi                         freesansbold
FreeSansBold.ttf
freesansnormal                       freesansoblique
FreeSansOblique.ttf
freesansoblique                      freesansoblique
FreeSansOblique.ttf
freeserif                            freeserif
FreeSerif.ttf
freeserifbold                        freeserifbold
FreeSerifBold.ttf
freeserifbolditalic                  freeserifbolditalic
FreeSerifBoldItalic.ttf
freeserifitalic                      freeserifitalic
FreeSerifItalic.ttf
freeserifnormal                      freeserifitalic
FreeSerifItalic.ttf

I also see

fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for otf files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for OTF files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for ttf files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for TTF files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for ttc files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for TTC files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for dfont files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for DFONT files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for afm files
fonts           | names | scanning
/opt/luatex/standalone-mkiv/tex/texmf-project for AFM files

The problem with texmf-fonts/
is that is keep in sync with the original source, and hence the files
can be deleted.

>
> 4) You might want to explain that the
>       source /opt/luatex/standalone-new/tex/setuptex
>     has to be done once at the start of each session, or else bad things
> happen.
Hm , nothing bad:  you use the default pdftex/xetex/luatex --- nothing
of catastrophic, this  doesn't touch your mkiv in anyway.
Given that mkiv require some experience, the default is to leave the
distro to manage the TeX installation
and the user to setup the appropriate environment.


> 5) Generally it would be good to dilineate what should be done as root,
>     and where normal user stuff starts.
Hm, to be root is not required -- have you found some problem ?


--
luigi
___________________________________________________________________________________
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:[~2012-12-01 19:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  7:06 Pablo Rodríguez
2012-11-30  9:13 ` Hans Hagen
2012-11-30  9:58   ` Steve White
2012-11-30 10:18     ` luigi scarso
2012-11-30 11:40       ` Steve White
2012-11-30 12:24         ` luigi scarso
2012-11-30 14:25           ` Steve White
2012-11-30 15:30             ` luigi scarso
2012-11-30 15:38               ` Hans Hagen
2012-11-30 18:12                 ` Steve White
2012-11-30 18:22                   ` Hans Hagen
2012-11-30 19:37                   ` luigi scarso
2012-11-30 21:25                     ` Steve White
2012-11-30 22:02                       ` Hans Hagen
2012-11-30 23:57                         ` Pablo Rodríguez
2012-12-01 16:22                       ` Steve White
2012-12-01 19:22                         ` luigi scarso [this message]
2012-12-01 19:38                           ` Aditya Mahajan
2012-12-01 19:46                             ` luigi scarso
2012-12-01 19:58                               ` Aditya Mahajan
2012-12-01 21:09                                 ` luigi scarso
2012-12-02  9:58                                   ` Steve White
2012-12-02 13:12                                     ` Khaled Hosny
2012-12-02 14:32                                       ` Steve White
2012-12-02 14:49                                         ` Khaled Hosny
2012-12-02 10:10                           ` Steve White
2012-12-02 10:24                             ` luigi scarso
2012-12-02 10:43                               ` Wolfgang Schuster
2012-12-02 11:08                               ` Steve White
2012-12-02 11:48                                 ` luigi scarso
2012-11-30 15:43         ` Hans Hagen
2012-11-30 14:13     ` Khaled Hosny
2012-11-30 15:41       ` Hans Hagen
2012-11-30 16:05     ` Hans Hagen
2012-11-30 16:39       ` Bill Meahan
2012-11-30 18:08         ` Steve White
2012-11-30 19:07           ` Bill Meahan
2012-11-30 21:24             ` Steve White
2012-11-30 18:34       ` Steve White

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='CAG5iGsA1Z8DxQApYXanbkX3-AKt=9S9PVrz8m4QpH5KNkXvntg@mail.gmail.com' \
    --to=luigi.scarso@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).