to use Python
instead of Lua, but I suppose I should ask that as a new question.
It is easy to do this in TeX, so no need to go to lua (or python).
Call
\getfiguredimensions[filename]
It seems that this is broken with the newest beta – at least for me. Can
someone confirm?
Greeting
that as a new question.
It is easy to do this in TeX, so no need to go to lua (or python).
Call
\getfiguredimensions[filename]
Then you can use
\noffigurepages
\figurenaturalwidth \figurenaturalheight
to place each page of the figure. Something like:
\getfiguredimensions[filename
On 2011-02-23 Andreas Harder ahar...@uni-koblenz.de wrote:
\getfiguredimensions[filename]
It seems that this is broken with the newest beta – at least for me. Can
someone confirm?
Confirmed on solaris x86
LuaTeX ver: beta-0.65.0-2010121317
ConTeXt ver: 2011.02.18 17:17 and
ConTeXt ver
make sense to convince --purgeall to be more grabby and to
remove all .tmp files in the working dir + all files in the »directory« dir
(here tmp). But I'm not sure about possible displeasing side effects, though.
I am not sure what you want. Do you want
context --purge filename
to remove all
directory
tree has to be scanned to find xyz-externalfilter-abc-X.___ remains. However
context --purgeall filename
should remove all temporary files belonging to the document like
filename-externalfilter-CON-0.tmp % not removed
filename-externalfilter-CON-0.tmp.md5 % not removed
filename
extension in the current directory. Only the .vimout files remain.
However
context --purgeall filename
should remove all temporary files belonging to the document like
filename-externalfilter-CON-0.tmp % not removed
filename-externalfilter-CON-0.tmp.md5 % not removed
filename
and execute context --purgeall afterwards, the files
t-externalfilter-CON-0.tmp.md5 and
t.tex.md5
still remain.
Why not simply run `context --purgeall` (no filename)?
See above.
Regards
Marco
___
If your question
in the originator's post.
i'll patch lpdf-wid but somehow I get the impression that it's more a
viewer issue (the list shown seems to be a merge of filename as well as
symbolic names while a clever list builder should look at the referred
objects) ... but maybe no one else usesvdifferent symbolic names (we had
, as well as for MacOS.
See, http://en.wikipedia.org/wiki/Filename
Microsoft Windows: Windows kernel forbids the use of characters in range 1-31
(i.e., 0x01-0x1F) and characters * : ? \ / |. Although NTFS allows each
path component (directory or filename) to be 255 characters long and paths up
never be 100% sure what you
get so in critical long term projects you can best use names or filename
(and keep the files someplace backed up). It all depends on the situation.
Hans
-
Hans
then
table.sort(document.files)
end
for _, filename in ipairs(document.files) do
if not string.find(filename,^mtx%-context%-) then
context.filterpages (
{ filename },
{ selection },
{ width
is that \filename{core-lst.tex} contains an explicit
%D \type|\hfill|.
\def\!!ieee@brackets#1%
{\hbox \ifdim\!!widtha\zeropoint to \!!widtha \fi
{\hss[#1]\hskip 0.5em}}
\setuppublications
[\c!sorttype=cite,
\c!criterium=,
\c!refcommand=num,
\c!numbering=\v!yes,
\c
as a string.)
I hope that's the correct answer and not a hack.
There are mechanisms for embedding files, like
backends.codeinjections.embedfile(filename)
However, a nametree is not constructed (as with forms these are not
mandate, but with forms they are better be there due to initialization
with \pdfbackendsetname/catalog,
the second argument is taken as a string.)
I hope that's the correct answer and not a hack.
There are mechanisms for embedding files, like
backends.codeinjections.embedfile(filename)
However, a nametree is not constructed (as with forms these are not
mandate, but with forms
normalized base url + md5sum of url + extension). I am not sure how if
extensions can be calculated reliably in urls. In particular imaging
something like
http://www.bing.com/search?q=check+.extension+long+url+so+that+os+filename+limit+exceeds+
A simple algorithm with assume that everything
On 18-1-2011 10:04, Peter Münster wrote:
Renaud AUBINau...@nibua-r.org writes:
It would be nice to think of those like me who use dot into their naming
scheme… ;)
See also http://www.ntg.nl/pipermail/ntg-context/2010/052339.html ;)
well, having a * in a filename is a bad idea anyway
Hans
/052339.html ;)
well, having a * in a filename is a bad idea anyway
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip
Hi,
While downloading urls, context santizes the filename but does not check
the length of the url. So, one can end up with a situation where the
filename is too long for the operating system to handle. For example, the
following fails on 32bit linux.
\enabletrackers[resolvers.schemes
somename_followed_by_space
we need:
context.environment(false, foo.tex )
a false will omit the {} for the next argument. and the space is after
the filename. Sorry that it looks so hackerish.
I think that it makes sense to patch \environment to accept [filename]
as well. (It's an old command)
Hans
On 14-1-2011 6:58, Khaled Hosny wrote:
On Fri, Jan 14, 2011 at 06:52:25PM +0100, Peter Münster wrote:
Khaled Hosnykhaledho...@eglug.org writes:
context.environment(foo.tex) -- throws an error
context(\\environment foo )
btw, you can also use \useenvironment[filename], so
, you can also use \useenvironment[filename], so
context.environment { foo.tex }
context.useenvironment { foo.tex } you mean, that is fine with me,
much cleaner.
Regards,
Khaled
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font developer
pdftex.map
which certainly lacks the information about lmmi font. But I wonder
why it only reads from pdftex.map ... I could fix pdftex.map, but I
would like to figure out what exactly is going on ...
Just some more information ... Looking into the filename.1 makes me
very suspicious:
%!PS
\placepublications seems to reset linespacing as well.
Can you make a example.
BTW: \startproduct takes the filename as argument, please add it.
Wolfgang
___
If your question is of interest to others as well, please add
Hi Wolfgang,
the next beta will provide
\xmltofile{#1}{.}{filename}
so that one can avoid a buffer.
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
version='1.0' standalone='yes' ?
!-- input filename : xml_test_export --
!-- processing date : 01/03/11 12:43:00 --
!-- context version : 2010.12.31 08:59 --
!-- exporter version : 0.10 --
document language='en' file='xml_test_export' date='01/03/11 12:43:01'
context
the newest luatex from the minimals I
don't see how it should be able to see the roots of miktex without
manipulating the texmf.cnf first, or use the filename database of
miktex (FNDB) at all, or use the tools of miktex (like on-the-fly
installation, or format generation through miktex settings
luatex from the minimals I
don't see how it should be able to see the roots of miktex without
manipulating the texmf.cnf first, or use the filename database of
miktex (FNDB) at all, or use the tools of miktex (like on-the-fly
installation, or format generation through miktex settings).
Barney
)!!!
Has to do with the rewrite of the verbatim code in mkiv.
Here is a minimal example which can be run with “context filename”
to generate the error:
\usemodule[mod-01]
\startmodule[type=tex]
\startdefinition
\TeX
\stopdefinition
\stopmodule
The problem is \startmodule[type=tex] produce
at line 4
system : cont-err loaded
...
What does the file-parameter do? I'm somehow lost now, sorry!
The file: tries to find a font by file name. In your case,
it fails because the font is not called 'snowdusted.ttf',
it is 'plymouthsnowdusted.ttf' (the filename is lowercased
automatically). So
. in a filename). After
running context foo.11.tex a bunch of files get created with the
names such as
foo.11.log
foo.11.pdf
foo.11.tex
foo.11.tuc
In addition there is a file named foo.top but NO foo.11.top.
Inspecting the file foo.11.log I noticed the line:
systems : no foo.11.top
Please, correct
history to provide more
insight. What pfb files exactly do you have on your system?
I would try to completely remove texmf-cache and then regenerate the
filename database again (mtxrun --generate).
This works:
\starttypescript[lucida]
\definetypeface[\typescriptone][rm][serif]
[lucida
that are absolutely needed for Math, it probably won't
work anyway. I don't know enough of Lucida's history to provide more
insight. What pfb files exactly do you have on your system?
I would try to completely remove texmf-cache and then regenerate the
filename database again (mtxrun --generate
insight. What pfb files exactly do you have on your system?
now I renamed all files to teh yy ones.
I would try to completely remove texmf-cache and then regenerate the
filename database again (mtxrun --generate).
also done. The font files are now found, but I always get a
luatex error
for otf in type-otf.mkiv,
but using type1 instead of otf?
type-otf.mkiv is just a filename. The otf is partially there for
historic reasons and doesn't imply that only OpenType fonts should be
defined there, even though this is true for almost all fonts listed
there.
Typescripts for Lucida define
. But seems that I was wrong or this will be in future
of the backend?
---
WBR, Vladimir Lomov
--
If you make people think they're thinking, they'll love you; but if you
really make them think they'll hate you.
?xml version='1.0' standalone='yes' ?
!-- input filename : ex1
.
I do not need any fancy stuff, just simple things: ordered,
unordered lists, verbatim, tables etc.
\setupbackend[export=yes]
\starttext
\section{Some section}
\startitemize[1]
\item bla bla
\stopitemize
\stoptext
Run context filename. This will create a filename.export file in your
\par.
sure, you are right, I'g fogotten it. However, I suppose,
I did more wrong, because I get now:
Your second \stopitemize is missing an i.
Oh my dear ... I was blinded by the light .. looked 10 times
over the code ...
texmfstart concheck filename
It gives false alarms, but definitely
On Sat, Oct 16, 2010 at 11:09 PM, Aditya Mahajan adit...@umich.edu wrote:
Hi,
In MkII, I can say
\ReadFile{/tmp/filename}
to read a file in /tmp directory. However, in MkIV, that fails because
ReadFile is defined as
\unexpanded\def\ReadFile #1{\doreadfile{any}
{.}{#1}\donothing
On Sun, 17 Oct 2010, luigi scarso wrote:
On Sat, Oct 16, 2010 at 11:09 PM, Aditya Mahajan adit...@umich.edu wrote:
Hi,
In MkII, I can say
\ReadFile{/tmp/filename}
to read a file in /tmp directory. However, in MkIV, that fails because
ReadFile is defined as
\unexpanded\def\ReadFile
On Sun, 17 Oct 2010, Aditya Mahajan wrote:
I am just looking for macro that takes the filename as a (brace delimited)
parameter and typesets it.
Err.. I mean \inputs it.
Aditya
___
If your question is of interest
will be really ugly.
I am just looking for macro that takes the filename as a (brace delimited)
parameter and typesets it. I can define one on my own; but I thought that
\ReadFile is already supposed to do that.
It is straight forward to fix \ReadFile so that absolute paths work:
\unexpanded
]
and have all the tmp files created in $TEMP. Having to set this as a
relative path will be really ugly.
I am just looking for macro that takes the filename as a (brace
delimited) parameter and typesets it. I can define one on my own; but
I thought that \ReadFile is already supposed to do
Hi,
In MkII, I can say
\ReadFile{/tmp/filename}
to read a file in /tmp directory. However, in MkIV, that fails because
ReadFile is defined as
\unexpanded\def\ReadFile #1{\doreadfile{any} {.}{#1}\donothing\donothing}
so it explicitly searches in the . (current) directory.
Bug
= img.scan{ filename = cow.jpg }
print(xsize = ,f.xsize,, ysize = ,f.ysize)
Best wishes, Peter
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http
to customer OS for embedded devices
Maybe we should restrict our coding as well to ascii...
As long as you impose the filename to follow the ascii 8.3 convention
the OS should be ok.
ConTeXt mkii is already able to manage utf-8 bytestreams (it's not a
OS issue, becuse it's a binary file
..., 4096) =
4096
[pid 14119] read(3, = \Hans Hagen, PRAGMA-ADE, Ha..., 4096) =
4096
[pid 14119] brk(0xa8c7000) = 0xa8c7000
[pid 14119] read(3, )\,\%1:\))) or filename\nend\n\nfunc...,
4096) = 4096
[pid 14119] read(3, = root .. path\nl..., 4096) =
4096
[pid
read(3, = \Hans Hagen, PRAGMA-ADE, Ha..., 4096) = 4096
brk(0x1c205000) = 0x1c205000
read(3, )\,\%1:\))) or filename\nend\n\nfunc..., 4096) = 4096
read(3, = root .. path\nl..., 4096) = 4096
read(3, function dir.expandname(str) -- ..., 4096) = 4096
read(3
of a
filename-font mapping, right? I assume that somewhere there is a statement like
\usetypescript [sans] [corbel] [name]
after saying
\definetypeface [mainface] [ss] [sans] [corbel] [default] [rscale=auto]
Is this the way this is done internally?
What exactly is rscale=auto ?
Patrick
Am 29.09.2010 um 15:25 schrieb Patrick Gundlach:
I guess [name] is just a default classifier for defining the base level of a
filename-font mapping, right?
It’s a leftover from mkii where you had [name] and [texnansi,ec,...], the first
was to map from “Serif” etc. to the symbolic name (e.g
,
before=\startsolutionbackground,
after=\stopsolutionbackground
]
%D The \filename{exam.cls} class in \LATEX\ allows you to put a frame around
%D the solution and the frame breaks across pages. I wanted to put a frame
%D around the solution, but something more informal than
, that it's not possible at the moment. There is a tracker item
for this feature: http://tracker.luatex.org/view.php?id=475
Not hard to do, just no interface. We can change buffers.range so that it
accepts {1,-4} to mean from first to last-4 lines, and then just set
\typefile[lines={1,-4}]{filename
first to last-4 lines, and then just set
\typefile[lines={1,-4}]{filename}
In any case, it is easy to define a lua function that does this.
\startluacode
function buffers.stripfromend(name, count)
local str = buffers.loaddata(name)
if str and str~= then
local lines
Hi Hans,
It can load cid fonts rightly now. But I found it can not generate
MetaPost figure.
For example,
%filename: test.tex
\setmplibformat{plain}
\mplibcode
beginfig(1);
draw fullcircle scaled 10cm withcolor red withpen pencircle;
endfig;
\endmplibcode
\end
luatex output
are recognized by mtxrun, but, again, the font names don't
enable simplefonts to load them correctly.
4. This somehow seems to work. This is the font name (at least it's
not the filename) and the font is TrueType. However, trying to load a
different font here, like Sazanami Mincho, does *not* work
] you'll get the cow.
So the question is:
- bug?
- or don't ever use * in a filename?
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
If your question is of interest to others as well, please add
On Sun, Sep 12 2010, Hans Hagen wrote:
On 12-9-2010 8:41, Peter Münster wrote:
- or don't ever use * in a filename?
in all our projects we normalize to a-z and a dash, otherwise you
always get into problems esp when graphics come from a third party
... multiple spaces in names, funny case
On 12-9-2010 3:10, Peter Münster wrote:
On Sun, Sep 12 2010, Hans Hagen wrote:
On 12-9-2010 8:41, Peter Münster wrote:
- or don't ever use * in a filename?
in all our projects we normalize to a-z and a dash, otherwise you
always get into problems esp when graphics come from a third party
{mkdir testdir}
\executesystemcommand{move /Y pdf-pages.pdf testdir/28.pdf}
\starttext
\setupexternalfigures[directory={./testdir}]
\externalfigure[28][page=3]
\stoptext
so, no * in the filename
however, you can do this
\starttext
\startbuffer[pdf-pages]
\starttext
page 1 \page page 2
On Fri, Sep 10 2010, Hans Hagen wrote:
\starttext
\setupexternalfigures[directory={./testdir}]
\externalfigure[28][page=3]
\stoptext
so, no * in the filename
Does this mean, that you can reproduce the problem, or not?
I just want to know, how to compile the context manual, see
On 10-9-2010 6:12, Peter Münster wrote:
On Fri, Sep 10 2010, Hans Hagen wrote:
\starttext
\setupexternalfigures[directory={./testdir}]
\externalfigure[28][page=3]
\stoptext
so, no * in the filename
Does this mean, that you can reproduce the problem, or not?
i get empty pages
On Fri, Sep 10 2010, Hans Hagen wrote:
i get empty pages in the case of a * but that can be simply because
a * might not be in a filename on windows
Ok, I can rename the file.
But I think, the behaviour is so strange, that there is somewhere a hidden
bug.
Strange, because 2*8 is the only
On Fri, 10 Sep 2010, Peter Münster wrote:
On Fri, Sep 10 2010, Hans Hagen wrote:
i get empty pages in the case of a * but that can be simply because
a * might not be in a filename on windows
Ok, I can rename the file.
But I think, the behaviour is so strange, that there is somewhere
On Fri, Sep 10, 2010 at 21:27, Peter Münster pmli...@free.fr wrote:
On Fri, Sep 10 2010, Hans Hagen wrote:
i get empty pages in the case of a * but that can be simply because
a * might not be in a filename on windows
Ok, I can rename the file.
But I think, the behaviour is so strange
[whatever]
\unexpanded\def\PAGENUMBER%
{\incrementnumber[whatever]%
\getnumber[whatever]}
\usemodule[cut-n-paste]
\starttext
\processcutNpaste
[%option=test,
text={Page~\PAGENUMBER},
location={(OverlayWidth/2, 1cm)},
name=file]
\stoptext
Here name=filename that you want to include
the tex file and both log files.
The on-the-fly generation of metapost images is off because
the setting for shell_escape in your texmf.cnf does not allow
execution of system commands.
The reason why the original filename worked is because in thatcase
the image (ConTeXtWikiLogo-mpgraph.1) has
/correspondence-letter-examples.tex
--- a/manual/correspondence-letter-examples.tex Sat Aug 28 12:40:15 2010 +0200
+++ b/manual/correspondence-letter-examples.tex Sat Aug 28 13:42:26 2010 +0200
@@ -82,7 +82,7 @@
\section[letter:example:dinb]{DIN 676 B}\index{DIN 676 B}
-The letter style \filename{dinb
--script context filename work instead?
Aditya
___
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
wrote:
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans, I think it would be nice to be able to load
fonts by either font name or file name regardless of where they reside
(I'm not sure how easy is that, though, with luaotfload and kpse setting
Khaled,
a while ago I was getting strange results: wanted to use roman font got bold
italic, etc. Font listing roman name and italic filename, all with several
fonts.
I just deleted the font cache folder Did the trick for the time being.
./tex/texmf-cache/luatex-cache/context/hexnumber
with name xits-regular is not found
define fonts unknown font xits-regular, loading aborted
define fonts unable to define xits-regular.otf as \*xits11ptrmtfc*
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans, I think it would be nice to be able
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans, I think it would be nice to be able to load
fonts by either font name or file name regardless of where they reside
(I'm not sure how easy is that, though
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans, I think it would be nice to be able to load
fonts by either font name or file name regardless
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans, I think it would be nice to be able to load
fonts by either
On Tue, Aug 17, 2010 at 05:26:19PM +0200, Hans Hagen wrote:
On 17-8-2010 4:53, Khaled Hosny wrote:
On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
On 17-8-2010 3:00, Khaled Hosny wrote:
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans
not load system
fonts by filename. Hans, I think it would be nice to be able to load
fonts by either font name or file name regardless of where they reside
(I'm not sure how easy is that, though, with luaotfload and kpse setting
OSFONTDIR is all what I need, since kpathsea appends it to its font
:
The typescript uses file names, however ConTeXt can not load system
fonts by filename. Hans, I think it would be nice to be able to load
fonts by either font name or file name regardless of where they
reside
(I'm not sure how easy is that, though, with luaotfload and kpse
setting
OSFONTDIR is all what I
Hi all,
in an interface xml definition, what is the notation for an argument value
that is a filename? I'm just unsure whether to specify it as “cd:text”
or “cd:name”. Example:
···8··
cd:parameter name=file
cd:constant
Am 16.08.10 14:50, schrieb Philipp Gesang:
Hi all,
in an interface xml definition, what is the notation for an argument value
that is a filename? I'm just unsure whether to specify it as “cd:text”
or “cd:name”.
It’s “cd:name”.
Also, is there a way to specify conditioned arguments (apart
On 08/16/2010 02:58 PM, Wolfgang Schuster wrote:
Am 16.08.10 14:50, schrieb Philipp Gesang:
Hi all,
in an interface xml definition, what is the notation for an argument
value
that is a filename? I'm just unsure whether to specify it as “cd:text”
or “cd:name”.
It’s “cd:name”.
Also
Am 16.08.10 14:58, schrieb Wolfgang Schuster:
Am 16.08.10 14:50, schrieb Philipp Gesang:
Hi all,
in an interface xml definition, what is the notation for an argument
value
that is a filename? I'm just unsure whether to specify it as “cd:text”
or “cd:name”.
It’s “cd:name”.
I forgot
the new file \filename{t-correspondence.tex}
which holds now the low level code. As a result of this the new file
-\filename{t-resume.tex} became part of the package with it’s own setup commands
+\filename{t-resume.tex} became part of the package with its own setup commands
and external style
generated the zips), so that luatools --generate
should run automatically when no filename database is found. (But you
cannot test it unless we re-run the script to rebuild the zips.)
Mojca
___
If your question
.
All best
Thomas
On Jul 19, 2010, at 10:51 AM, Li Yanrui (李延瑞) wrote:
Hi all,
I have the following problems when I use the bib module.
1. For the cite of 'authoryear', how to make it being clickable link?
This is a minimum example:
%%%
%% filename: test.tex
Hi all,
I have the following problems when I use the bib module.
1. For the cite of 'authoryear', how to make it being clickable link?
This is a minimum example:
%%%
%% filename: test.tex
\setupinteraction[state=start]
\setupbibtex[database=ref]
\setupcite[authoryear
:
\startluacode
function palapatch (data,filename)
-- to be filled in
end
fonts.otf.enhancers.patches[^pala] = palapatch
\stopluacode
The two arguments to the patch function are the data table from the
luafontloader and the font file name, respectively. The function
should patch the data table to our
it is
possible to deduce that something like this is the correct program
structure, theoretically:
\startluacode
function palapatch (data,filename)
-- to be filled in
end
fonts.otf.enhancers.patches[^pala] = palapatch
\stopluacode
The two arguments to the patch function are the data table
in the output!
The existing font patches are in font-pat.lua, and from that file it is
possible to deduce that something like this is the correct program
structure, theoretically:
\startluacode
function palapatch (data,filename)
-- to be filled in
end
fonts.otf.enhancers.patches[^pala
On Fri, 25 Jun 2010, Hans Hagen wrote:
On 25-6-2010 9:48, Martin 'golodhrim' Scholz wrote:
Hi Hans, Mojca, Aditya and List,
just tried to use the vim Syntax Highlighting module in ConTeXt MKIV, but
if running the documents complains it searches a file called
filename-vimsyntax.tmp
Hi,
After finding out that line numbering works different in Mark IV I tried using
this version on Mac OS X via MacTeX 2009. I modified TeXworks to use texexec
--lua $filename as for ConTeXt. I have updated MacTeX to latest version and
actually I still cant' make it work. I tried following
On 25-6-2010 9:06, David Abdurachmanov wrote:
After finding out that line numbering works different in Mark IV I tried using this
version on Mac OS X via MacTeX 2009. I modified TeXworks to use texexec --lua
$filename as for ConTeXt. I have updated MacTeX to latest version and actually I
Hi Hans, Mojca, Aditya and List,
just tried to use the vim Syntax Highlighting module in ConTeXt MKIV, but
if running the documents complains it searches a file called
filename-vimsyntax.tmp-vimsyntax.tmp
sure that file not exists but there is a file called
filename
On 25-6-2010 9:48, Martin 'golodhrim' Scholz wrote:
Hi Hans, Mojca, Aditya and List,
just tried to use the vim Syntax Highlighting module in ConTeXt MKIV, but
if running the documents complains it searches a file called
filename-vimsyntax.tmp-vimsyntax.tmp
sure that file not exists
On 23-6-2010 1:39, Mojca Miklavec wrote:
when processing it with
texexec --xtx filename
so ... xetex ... you're sure xetex is run?
(/Users/mojca/soft/texlive/2010/texmf-dist/tex/context/base/spec-xet.mkii)
(/Users/mojca/soft/texlive/2010/texmf-dist/tex/context/third/gentium/type-genti
On Wed, Jun 23, 2010 at 03:24:09PM +0200, Hans Hagen wrote:
On 23-6-2010 1:39, Mojca Miklavec wrote:
when processing it with
texexec --xtx filename
so ... xetex ... you're sure xetex is run?
(/Users/mojca/soft/texlive/2010/texmf-dist/tex/context/base/spec-xet.mkii)
(/Users/mojca
from the
filename. This might mean being able to use fonts other than those from
Adobe, which would be nice.
You can also see
ttx: is written in python
http://sourceforge.net/projects/fonttools/
--
luigi
___
If your
it out from the
filename. This might mean being able to use fonts other than those from
Adobe, which would be nice.
Although a Perl user, I like your Python script, Michael !
Thanks
___
If your question is of interest
On 27-5-2010 1:00, luigi scarso wrote:
Hm again ttf vs TTF ?
There has been some changes in the filename checking (was needed for
usage in latex) and something might have got lost there. In retrospect i
should never have changed anything in our code for that reason and
definitely
+0200
@@ -576,7 +576,7 @@
otf.enhancers[merge cid fonts] = function(data,filename)
-- we can also move the names to data.luatex.names which might
-- save us some more memory (at the cost of harder tracing)
-if data.subfonts and data.glyphs and next(data.glyphs
end
function scripts.interface.context()
local filename = resolvers.find_file(environment.files[1] or mult-def.lua) or
if filename ~= then
local interface = dofile(filename)
if interface and next(interface) then
local variables, constants, commands, elements
= pdfdictionary {
@@ -423,12 +425,35 @@
local ref = stored_pr[tag]
if not ref then
-- weird, has to be a /Form and not an /Image so we need a wrap =
true key
--- local figure = img.immediatewrite { filename = preview, width =
width, height = height }
-local
901 - 1000 of 1623 matches
Mail list logo
