On 24 Oct 2013, at 07:41, Pierre Bovet pierr...@me.com wrote:
Hi all!
It seems that Luatex (0.76 2013/04/05) don't works with Mavericks?
Thank's in advanced for your help and testimonies
Best wishes
I’m afraid you’re right! I installed Mavericks yesterday; trying to build the
format,
Am 24.10.2013 um 07:41 schrieb Pierre Bovet pierr...@me.com:
Hi all!
It seems that Luatex (0.76 2013/04/05) don't works with Mavericks?
Thank's in advanced for your help and testimonies
There are no problems for me with the last version of the context suite and OS
10.9.
This is
On 24 Oct 2013, at 09:01, Schmitz Thomas A. thomas.schm...@uni-bonn.de wrote:
But so far, I have not been able to unset OSFONTDIR and make context ignore
this directory. (Unlike some people in a recent discussion, my preference
would be to NOT include any system fonts by default: it slows
On 24 Oct 2013, at 09:04, Wolfgang Schuster wolfgang.schus...@gmail.com wrote:
There are no problems for me with the last version of the context suite and
OS 10.9.
This is LuaTeX, Version beta-0.76.0-2013040508 (TeX Live 2013/dev)(rev 4627)
Wolfgang
not on my system. I have this
Context (luatex) works without problem under Mavericks, but it don't works with
external font:
\usetypescript[lucida][ec] \setupbodyfont[lucida,12pt]
\starttext
Hello world!
\stoptext
Pierre
Le 24 oct. 2013 à 09:24, Wolfgang Schuster wolfgang.schus...@gmail.com a
écrit :
Am 24.10.2013
Am 24.10.2013 um 09:30 schrieb Pierre Bovet pierr...@me.com:
Context (luatex) works without problem under Mavericks, but it don't works
with external font:
\usetypescript[lucida][ec] \setupbodyfont[lucida,12pt]
\starttext
Hello world!
\stoptext
This is unrelated to the problem.
OK, that was not a good example…
But the the message above is coming with any other otf fonts:
fontsnames globbing path '/Library/Fonts/**.ttf'
mtx-context | fatal error: no return code, message: luatex: execution
interrupted
Pierre
Le 24 oct. 2013 à 09:36, Wolfgang Schuster
Am 24.10.2013 um 09:45 schrieb Pierre Bovet pierr...@me.com:
OK, that was not a good example…
But the the message above is coming with any other otf fonts:
fontsnames globbing path '/Library/Fonts/**.ttf'
mtx-context | fatal error: no return code, message: luatex:
On 24 Oct 2013, at 10:00, Wolfgang Schuster wolfgang.schus...@gmail.com wrote:
Can you remove the Skia.ttf (copy it to another directory) font from
/Library/Fonts,
this helped on my system to get rid of the error message.
Wolfgang
Yes, that helped, and I can at least compile my documents
Oh yes, thank you very much!
I can compile again with Myriad Pro and all other otf fonts!
Thank you!
Pierre
Le 24 oct. 2013 à 10:08, Schmitz Thomas A. thomas.schm...@uni-bonn.de a écrit
:
On 24 Oct 2013, at 10:00, Wolfgang Schuster wolfgang.schus...@gmail.com
wrote:
Can you remove the
Hi Pierre,
I have Mavericks installed and no problems.
But, I did a clean install, migrated User Folder from a TM-Backup, and
my ConTeXt Suite (latest beta) work fine.
Since I did a clean install I had to install MacTeX.
-- Tried an older LuaLaTeX and got an error
-- Ran TeXLive Utility
Hi All, Wolfgang,
The PROBLEM is that Skia.ttf has the wrong permissions!
Everyone is set to none. meaning this file can not be read!
Solution copy to somewhere else, remove from /Library/Fonts and reinstall.
This suggest to me that when scanning the fonts and building the support files
there
Hello ConTeXist.
I tried convert plainTeX source code into ConTeXt source code so that
the output PDF gave the same (or approximately the same) result. I did
it for one of plainTEX developers (Mr. Olšák), which compared results of
PlainTeX, LaTeX and ConTeXt. However, I encountered the
Hello,
I was looking into simplefonts
(http://wiki.contextgarden.net/simplefonts) and noticed the clause
if you’re running ConTeXt Standalone
http://wiki.contextgarden.net/ConTeXt_Standalone (which is a better
option)
Well I'm using TeXLive, but am happy to take good advice, so I looked at
Hi Jarda and all,
I tested it on my computer using CTX from TL 2010 and 2013 and I have got
the same result in both cases. It seems that the content of the option before
is completely ignored. I tested another values for this option
(\page,\vskip,\godown...), no result.
The only one way which
Thanx Tomas.
Of course I know about the possibility of solving the problem by
directly entering a space before internal environment. However, I prefer
setting off the source text, so I wonder how it can be solved.
Jarda Hajtmar
Dne 24.10.2013 14:21, Tomas Hala napsal(a):
Hi Jarda and all,
On Thu, Oct 24, 2013 at 2:13 PM, Lars Huttar wrote:
The other issue for me with Standalone is that the only version listed
for Windows is W32TeX. When I go to the web page for that platform, I
don't see any information about what W32TeX is; just how to install it.
It sounds like it's specific
On Thu, 24 Oct 2013 14:57:35 +0200
Mojca Miklavec mojca.miklavec.li...@gmail.com wrote:
On Thu, Oct 24, 2013 at 2:13 PM, Lars Huttar wrote:
The other issue for me with Standalone is that the only version
listed for Windows is W32TeX. When I go to the web page for that
platform, I don't
On Thu, 24 Oct 2013, Lars Huttar wrote:
Hello,
I was looking into simplefonts
(http://wiki.contextgarden.net/simplefonts) and noticed the clause
if you’re running ConTeXt Standalone
http://wiki.contextgarden.net/ConTeXt_Standalone (which is a better
option)
Well I'm using TeXLive, but am
On 10/24/2013 4:12 PM, Schmitz Thomas A. wrote:
On 24 Oct 2013, at 09:01, Schmitz Thomas A. thomas.schm...@uni-bonn.de wrote:
But so far, I have not been able to unset OSFONTDIR and make context ignore
this directory. (Unlike some people in a recent discussion, my preference would
be to
The problem with Standalone is that the full range of fonts found with
Texlive is not available. Standalone has 258 otf fonts and TexLive
has 508 otf fonts. So I am opting for TeXLive, although I have both.
I use standalone in parallel with texlive (which I need for latex). In the
Arch
On Thu, 24 Oct 2013 23:17:13 +0900
Hans Hagen pra...@wxs.nl wrote:
Hm. The problem is that we get some oscillation (with a few year cycle)
between the 'demand' for os fonts support vs tree only (as far as
remember os font support was mostly requested by osx users). Anyhow, we
can make it
On 24 Oct 2013, at 16:17, Hans Hagen pra...@wxs.nl wrote:
Hm. The problem is that we get some oscillation (with a few year cycle)
between the 'demand' for os fonts support vs tree only (as far as remember os
font support was mostly requested by osx users). Anyhow, we can make it an
On Thu, 24 Oct 2013, Schmitz Thomas A. wrote:
On 24 Oct 2013, at 16:17, Hans Hagen pra...@wxs.nl wrote:
Hm. The problem is that we get some oscillation (with a few year cycle) between
the 'demand' for os fonts support vs tree only (as far as remember os font
support was mostly requested by
After installing Mavericks and attempting to update to the latest
Standalone—
Problem 1: with sh ./first-setupsh I get Context current version:
2013.10.15 13:52. though it should. I think, be version 2013-10-20 07:11.
Problem 2: (noted before?) compiling with this Standalone (ConTeXt ver:
Am 24.10.2013 um 22:48 schrieb Alan Bowen bowenala...@gmail.com:
After installing Mavericks and attempting to update to the latest Standalone—
Problem 1: with sh ./first-setupsh I get Context current version: 2013.10.15
13:52. though it should. I think, be version 2013-10-20 07:11.
Am 24.10.2013 um 16:18 schrieb Aditya Mahajan adit...@umich.edu:
Another dfficulty is that many of the examples for simplefonts
are apparently developed on a Windows system and I use Linux. Font
names are different.
I haven't had any trouble with using simplefonts in Linux (but then, I
On 10/24/2013 11:39 PM, Schmitz Thomas A. wrote:
On 24 Oct 2013, at 16:17, Hans Hagen pra...@wxs.nl wrote:
Hm. The problem is that we get some oscillation (with a few year cycle) between
the 'demand' for os fonts support vs tree only (as far as remember os font
support was mostly requested
On 24 Oct 2013, at 16:44, Aditya Mahajan adit...@umich.edu wrote:
You need to set it to a dummy directory! See:
http://tex.stackexchange.com/a/136073/323
No, even that doesn’t help:
echo $OSFONTDIR
/tmp/dummy
and then on a first run (after regnerating the format with this variable set),
I
On 10/25/2013 7:01 AM, Schmitz Thomas A. wrote:
On 24 Oct 2013, at 16:44, Aditya Mahajan adit...@umich.edu wrote:
You need to set it to a dummy directory! See:
http://tex.stackexchange.com/a/136073/323
No, even that doesn’t help:
echo $OSFONTDIR
/tmp/dummy
and then on a first run (after
Hi,
Concerning unix: Norbert Preining (tex live maintainer) found out that
when font directories are symlinks, file access is much slower due to
more lookups (esp with long names as then the lookup is indirect which
means more disk access). Of course on a modern machine with ssd this is
On 10/24/2013 2:46 PM, H. Özoguz wrote:
\setupbodyfont [dejavu,12pt]
\starttext
$a/b$
$1/2$
$π/3$
\stoptext
Is this indeed the desired spacing? What do others think?
Thanks.
I think you are right, I don't know if this is really desired, but I
don't think so. Escpecially one gets problems
On Fri, 25 Oct 2013, Hans Hagen wrote:
On 10/25/2013 7:01 AM, Schmitz Thomas A. wrote:
On 24 Oct 2013, at 16:44, Aditya Mahajan adit...@umich.edu wrote:
You need to set it to a dummy directory! See:
http://tex.stackexchange.com/a/136073/323
No, even that doesn’t help:
echo $OSFONTDIR
Any ideas ... ? :)
___
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 :
34 matches
Mail list logo
