From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: fonts with luatex
Date: Thu, 10 Jul 2008 09:15:12 +0200 [thread overview]
Message-ID: <326847810807100015q4d6e87c4x9ba230a921544545@mail.gmail.com> (raw)
In-Reply-To: <4875B078.1050306@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 831 bytes --]
>cleaned up ... i'll upload a beta
Thanks a lot Hans.
Where from will the beta be uploadable ?
Alan
On Thu, Jul 10, 2008 at 8:47 AM, Hans Hagen <pragma@wxs.nl> wrote:
> Taco Hoekwater wrote:
> >
> > Hans Hagen wrote:
> >> Alan Stone wrote:
> >>>> are there really two dots there? ..tma
> >>> Yes indeed Hans.
> >> that's weird, i'm stymied
> >
> > I'm not :) You got that from a bug in the warning message, not
> > the actual file name.
> >
> > input.luasuffix = '.tma'
> > input.report("unable to save %s in %s.%s",dataname,name,input.luasuffix)
> >
> > So that the string format reduces to
> >
> > ("unable to save %s in %s..tma",dataname,name)
>
> ah, ok, cleaned up ... i'll upload a beta
>
> i now save as binary .. maybe it helps otherwise there's realy a write /
> permission problem in Alan's machine
>
> Hans
>
[-- Attachment #1.2: Type: text/html, Size: 1326 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-07-10 7:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 14:00 Alan Stone
2008-07-08 15:02 ` Hans Hagen
2008-07-08 18:23 ` Alan Stone
2008-07-09 8:16 ` Hans Hagen
2008-07-09 8:24 ` Alan Stone
2008-07-09 8:40 ` Hans Hagen
2008-07-09 10:03 ` Alan Stone
2008-07-09 11:19 ` Alan Stone
2008-07-09 11:42 ` Hans Hagen
2008-07-09 14:15 ` Arthur Reutenauer
2008-07-09 14:25 ` Alan Stone
2008-07-09 15:04 ` Arthur Reutenauer
2008-07-09 15:13 ` Taco Hoekwater
2008-07-09 15:18 ` Arthur Reutenauer
2008-07-09 17:00 ` Alan Stone
2008-07-09 18:26 ` Alan Stone
2008-07-10 6:21 ` Hans Hagen
2008-07-10 6:54 ` Alan Stone
2008-07-10 6:47 ` Hans Hagen
2008-07-10 7:15 ` Alan Stone [this message]
2008-07-10 7:21 ` Wolfgang Schuster
2008-07-10 7:45 ` Alan Stone
2008-07-10 7:25 ` Mojca Miklavec
2008-07-10 8:12 ` Alan Stone
2008-07-10 8:52 ` Wolfgang Schuster
2008-07-10 9:00 ` Alan Stone
2008-07-10 8:55 ` Alan Stone
2008-07-10 9:13 ` Alan Stone
2008-07-10 9:36 ` Alan Stone
2008-07-10 9:49 ` Mojca Miklavec
2008-07-10 10:02 ` Alan Stone
2008-07-10 9:52 ` Mojca Miklavec
2008-07-10 11:39 ` Diego Depaoli
2008-07-10 12:16 ` Mojca Miklavec
2008-07-10 13:50 ` Diego Depaoli
2008-07-10 14:05 ` Mojca Miklavec
2008-07-10 14:38 ` Diego Depaoli
2008-07-10 8:14 ` Hans Hagen
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=326847810807100015q4d6e87c4x9ba230a921544545@mail.gmail.com \
--to=software.list.1es9s@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).