font[name:allerlight*default at 36pt]
>
> instead of:
> \definedfont[file:allerlt*default at 36pt]
>
> then it works.
> Changed:
> file: -> name:
> allerlt -> allerlight
When “file:allerlt” doesn’t work your fonts have a different filename than mine.
W
PS. By composing this example I noticed that \savebuffer do nothing.
Unless something has changed recently, \savebuffer[buffer-list][filename]
concatenates all the buffers in `buffer-list` and saves them to the file
`\jobname-filename.tmp`.
In the filter module, I work around this
y
for user interaction. To use the script, simply run
update [modulename]
The script will prompt you for username and password, then display a list
of all the modules that you own, and you can select a module to update.
Then, the script asks for a new version number and filename for the zip
>
>
> Thanks for any help
>
> Lutz
hm, strange, it seems that
externalfigure is redefined
This is ok
\starttext
\startMPcode
def externalfigure primary filename =
if false :
rawtextext("\externalfigure[" & filename & "]")
else :
image
1.ttf
telegrotesknornormal telegrotesknorm c:/windows/fonts/t036013t_v21.ttf
The --info output for normal ...
mtx-fonts | mapping : telegrotesknornormal
mtx-fonts | fontname: telegrotesknorm
mtx-fonts | fullname: telegrotesknor
mtx-fonts | filename: c:/windows/fonts/t036013t_v21.ttf
mtx-
n TLT
..\hbox(306.75749+0.0)x245.15184, glue set 245.15184fil, direction TLT
...\hbox(306.75749+0.0)x0.0, direction TLT []
...\hbox(306.75749+0.0)x0.0, direction TLT []
...\glue 0.0 plus 1.0fil minus 1.0fil
.\penalty 1
.\glue(\parfillskip) 0.0
.etc.
pages > flushing realpage 10,
> modules > checking file: 't-vim.mkvi'
resolvers > modules > checking file: 't-vim.mkiv'
resolvers > modules > checking file: 't-vim.tex'
resolvers > modules > loading: '/ifs2/S2PH/qiuhw/opt/context-1008/tex/texmf-m
x: Undefined control sequence ...
1 \usemodule[vim]
2
3 >> \definevimtyping[RUBY][syntax=ruby]
4
5 \starttext
6
7 \startRUBY
8 puts "Hello"
9 \stopRUBY
10
11 \stoptext
12
l.3 \definevimtyping
[RUBY][sy
The 'converter' program can filter the pages ... so we need to pass the page
number.
Page number is already passed. The filename conversion should make
use of it.
I think that the best solution is to allow the user to configure (using a
directive) the function that sets the new name
Am 26.08.2011 15:43, schrieb Hans van der Meer:
>
> On 26 aug. 2011, at 15:14, Taco Hoekwater wrote:
>
>>
>> On Aug 26, 2011, at 2:55 PM, Hans van der Meer wrote:
>>
>>> Still a mystery to me. In your logfile I see the line
>>> used files >
On 26 aug. 2011, at 15:14, Taco Hoekwater wrote:
>
> On Aug 26, 2011, at 2:55 PM, Hans van der Meer wrote:
>
>> Still a mystery to me. In your logfile I see the line
>> used files > 16: filename=AntykwaTorunska-Regular | filetype=otf |
>> format=otf |
&
On Aug 26, 2011, at 2:55 PM, Hans van der Meer wrote:
> Still a mystery to me. In your logfile I see the line
> used files > 16: filename=AntykwaTorunska-Regular | filetype=otf |
> format=otf |
> foundname=R:/tex/texmf/fonts/opentype/public/antt/AntykwaTorun
Still a mystery to me. In your logfile I see the line
used files > 16: filename=AntykwaTorunska-Regular | filetype=otf |
format=otf |
foundname=R:/tex/texmf/fonts/opentype/public/antt/AntykwaTorunska-Regular.otf |
usedmethod=database
I therefore concluse in your system ConTeXt has fo
tion or something like this. Does it work in an easier
> > way with MkIV? (I mean, I just do context filename and don't care
> > about multiple runs etc.)
>
> In MkIV you don't need to pass --arrange. In one of my projects, I
> have
>
>\setuppapersize[h
On Fri, 26 Aug 2011, Marcin Borkowski wrote:
Hi,
imposition in ConTeXt is great, but...
1. When I last used it (MkII), I had to invoke texexec with the
--arrange option or something like this. Does it work in an easier way
with MkIV? (I mean, I just do context filename and don't care
Hi,
imposition in ConTeXt is great, but...
1. When I last used it (MkII), I had to invoke texexec with the
--arrange option or something like this. Does it work in an easier way
with MkIV? (I mean, I just do context filename and don't care about
multiple runs etc.)
2. I'd like to
ined
control sequence ...
\doassigncheckedframeoffset ...checkedframeoffset
{#2}#1\ifx \checkedframeof...
... [\doassigncheckedframeoffset ]\tex
\scratchcounter =\NOfMargi...
\doifelsenothing #1->
On Mon, 22 Aug 2011, Hans Hagen wrote:
On 22-8-2011 00:14, Aditya Mahajan wrote:
On Sun, 21 Aug 2011, Henning Hraban Ramm wrote:
Current version doesn’t work at all:
- it writes the buffer with doubled filename and extension parts, i.e.
from foo.tex "foo-foo-temp-lilypond.tmp.tmp",
On 22-8-2011 00:14, Aditya Mahajan wrote:
On Sun, 21 Aug 2011, Henning Hraban Ramm wrote:
Current version doesn’t work at all:
- it writes the buffer with doubled filename and extension parts, i.e.
from foo.tex "foo-foo-temp-lilypond.tmp.tmp", but looks for
"foo-temp-lilyp
On Sun, 21 Aug 2011, Henning Hraban Ramm wrote:
Current version doesn’t work at all:
- it writes the buffer with doubled filename and extension parts, i.e. from
foo.tex "foo-foo-temp-lilypond.tmp.tmp", but looks for
"foo-temp-lilypond.tmp".
The \savebuffer command has ch
filename-1.pdf sometimes not. Can I force it to always give
filename-1.pdf or always give filename.pdf
IME there’s always a filename.pdf; you get filename-1.pdf for your
first page; if you use the preamble quoted above, you’ll get
filename-1.pdf etc. for every system.
Greetlings from
h work, IMO.
Probably.
Do you know how lilypond numbers its output files. In some cases I
get filename-1.pdf sometimes not. Can I force it to always give
filename-1.pdf or always give filename.pdf
LilyPond adds a number to EPS, if there’s more that one page.
But in my songbook setup, I al
ng. I’ll look into that.
>
> OK.
>
>> But I don’t know how we can make it "right" WRT LilyPond snippets - I’d want
>> to align a note systems’s base line with ConTeXt’s text baseline, but the
>> height and clipping of a snippet depends on the visible element
x
\scratchcounter
=\NOfMargi... \doifelsenothing #1->\edef \!!stringa {#1
}\ifx \!!stringa \empty
\expandafte... \domargindata ...ta ][#1]\fi \doifelsenothing {#3}
\donefalse \
anually.
Does lilypond-book handle this at all? It does not appear to. Manually
adjusting each inline snippet will be too much work, IMO.
Do you know how lilypond numbers its output files. In some cases I get
filename-1.pdf sometimes not. Can I force it to always give filename-1.pdf
pets
manually.
Do you know how lilypond numbers its output files. In some cases I
get filename-1.pdf sometimes not. Can I force it to always give
filename-1.pdf or always give filename.pdf
LilyPond adds a number to EPS, if there’s more that one page.
But in my songbook setup, I alway
g for LilyPond.
Do you know how lilypond numbers its output files. In some cases I get
filename-1.pdf sometimes not. Can I force it to always give filename-1.pdf
or always give filename.pdf
Which OSes do you have access
effect of some cleaning up of filename code deep down.
Normally in mkiv buffers are not saved on disk (as with mkii).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061
dows or even MS Office
> File wingdings.ttf I do not see there …
I have two versions of the font on my system, one came with Mac OS and the
other with MS Office and each has “Wingdings.ttf” as filename.
I have also the other two fonts you mentioned but their filenames on my system
are “Wi
cter#1{\char#1{}}
\let\dochar\numcharacter
\definefont[wingding][wingding.ttf at 12pt]
\starttext
{\wingding \dochar{74}\dochar{75}\dochar{76}}
\stoptext
That just gives JKL.
The filename of the font is “windings.ttf”.
Wo
Am 18.08.2011 um 09:40 schrieb Cecil Westerhof:
> 2011/8/17 Wolfgang Schuster
> The filename of the font is “windings.ttf”.
>
> I now have:
> […]
>
> But it just gives:
> windings: JKL
It’s “wingdings” with a “g” in the name!
\definefontsynonym[Wingding
2011/8/17 Wolfgang Schuster
> The filename of the font is “windings.ttf”.
>
I now have:
\def\numcharacter#1{\char#1{}}
\let\dochar\numcharacter
\definefont[wingding][windings.ttf at 12pt]
\starttext
windings: {\wingding \dochar{74}\dochar{75}\dochar{76}}
\stoptext
But it just
wingding][wingding.ttf at 12pt]
>
> \starttext
>
> {\wingding \dochar{74}\dochar{75}\dochar{76}}
>
> \stoptext
>
> That just gives JKL.
The filename of the font is “windings.ttf”.
Wolfgang___
1{\indent \hbox {\ifx #2\re...
...gen [linewidth, setuplinewidth]\tex
\scratchcounter =\NOfMargi...
\doifelsenothing #1->\edef \!!stringa {#1
}\ifx \!!strin
could say
context --usemodule=markdown --mode=process file.markdown
and get a pdf output.
It’s already there:
context --extra=markdown file.markdown
Does not work. `context --extra=markdown filename` just gives a list of
available extras (including markdown), but the file is not processed.
Is
--mode=process file.markdown
and get a pdf output.
It’s already there:
context --extra=markdown file.markdown
Does not work. `context --extra=markdown filename` just gives a list of
available extras (including markdown), but the file is not processed.
Is there a mtx-context-markdown.tex file on
output.
It’s already there:
context --extra=markdown file.markdown
Does not work. `context --extra=markdown filename` just gives a list of
available extras (including markdown), but the file is not processed.
There are limitations in Hans method because you can’t define completely
10:21, Peter Münster napsal(a):
On Tue, Jul 26 2011, Jaroslav Hajtmar wrote:
Conversely, if "+" is part of the filename, while images are found, the
compilation will collapse and prints a message that I mention below.
Short answer: don't use "+"
On Tue, Jul 26 2011, Jaroslav Hajtmar wrote:
> Conversely, if "+" is part of the filename, while images are found, the
> compilation will collapse and prints a message that I mention below.
Short answer: don't use "+" in filenames.
See also:
http://ar
Hello ConTeXist
I met with great strangeness. When I was looking for a mistake in my
source text, so I experimented and at one point I renamed myfile so that
there are "+" in its name. At that moment compilation ran flawlessly. I
know that the use of + in the filename is rela
onts > otf loading > file size: 95160
fonts > otf loading > saving in cache:
/home/marcin/context/tex/texmf/fonts/opentype/public/lm/lmsans12-regular.otf
system > logs > lua: compiling
/home/marcin/context/tex/texmf-cache/luatex-cache/context/2448223e6
installation (well, I
knew the filename already, but `mtxrun --script fonts` should help for
locating fonts in more general way though I never had success with it).
You have to copy the whole family (i.e. italic, bold and bolditalic too)
to the Windows machine, and it should make the Adobe th
xrun.
> They are independent and separated from the system.
> The same for texlive.
>
I just ran:
mtxrun --script fonts --list --info --pattern="*"
but only get:
mtx-fonts |
mtx-fonts | mapping : texmfhome
mtx-fonts | fontname: texmfhome
mtx-fonts | full
alone up and running has taken weeks.
>
> If you have it up and running, you can use it now also for XeTeX.
>
> The only difference is that you have to run "texexec --xtx filename"
> as opposed to "context filename".
>
> > You'd think it w
it now also for XeTeX.
The only difference is that you have to run "texexec --xtx filename"
as opposed to "context filename".
> You'd think it would just be something really simple like
> \switchfont[devangari]
> तरीकिन
> \unswitchfont
With ConTeXt+XeTeX it bo
as predefined typescripts for Times New Roman,
Arial and Courier but they don’t work on each system
(e.g. the fonts use different filenames on the Mac).
The simplefonts module makes things a little bit easier
because it tries a few combinations to find the files
but it still depends on the filename.
Am 23.05.2011 um 12:54 schrieb Andreas Schneider:
> On Monday, May 23, 2011 12:11 Wolfgang Schuster wrote:
>
>> \filename{cp \$SOMEVAR/some/very/very/very/long/directory/WITHFILE
>> \$SOMEVAR/other/long/directory}
>
>> Wolfgang
>
> It's kinda depressing
On Monday, May 23, 2011 12:11 Wolfgang Schuster wrote:
> \filename{cp \$SOMEVAR/some/very/very/very/long/directory/WITHFILE
> \$SOMEVAR/other/long/directory}
> Wolfgang
It's kinda depressing how easy some solutions are, that one could have
found themselves if one just looked
is particular case for example)
> break a word even in the middle if necessary, and without hyphenation
> mark. Especially in similar cases where I have a very very long
> directory name, I wouldn't care if it gets broken "the hard way&q
ither "stylesheet" for css or the xhtml filename without
the suffix
* opf: itemref needs to be the name of the xhtml without the suffix
Here's a very dirty quick fix I did to get a working epub:
add after line 112 or so:
+ local id = file.removesuffix(filename)
line 116:
-
regenerating the filename database:
mtxrun --generate
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
/contextgarden.net/contextwiki/images/4/46/P1030314.jpg': No such file
or directory.
convert: missing an image filename
`/var/www/contextgarden.net/contextwiki/images/thumb/4/46/P1030314.jpg/300px-P1030314.jpg'.
Is there something amiss here?
Yes, the images appear
/images/4/46/P1030314.jpg': No such file
or directory.
convert: missing an image filename
`/var/www/contextgarden.net/contextwiki/images/thumb/4/46/P1030314.jpg/300px-P1030314.jpg'.
Is there something amiss here?
Hans va
and
http://wiki.contextgarden.net/Reference/en/clip
I guess, that "\" in a filename is not allowed.
Perhaps it's better to use "c:/test/test.pdf".
--
Peter
___
If your question is of interes
On 16-4-2011 8:24, Aditya Mahajan wrote:
On Sat, 16 Apr 2011, Aditya Mahajan wrote:
Hi Hans,
In buff-ini.lua, line 73 should be
return concat(t,separator or "\n") -- AM: was \r
Actually, I am not sure if this is a bug or not. I was testing by "cat
filename" and was
On Sat, 16 Apr 2011, Aditya Mahajan wrote:
Hi Hans,
In buff-ini.lua, line 73 should be
return concat(t,separator or "\n") -- AM: was \r
Actually, I am not sure if this is a bug or not. I was testing by "cat
filename" and was only seeing the last line. Opening the f
x.lua
None of which is younger than last October.
No trace of “x-ldx.mkiv” in the commitdiffs from the gitorious
repo either.
Did something go wrong?
Regards, Philipp
PS: “$ mtxrun --find-file filename” results in a Lua error.
Commenting out line 1
stay
Still, one can access context’s language substitution tables to
achieve a quasilocale effect (concerning the month, that is).
(-> attachments.)
Good night all, Philipp
>
> > function modification_date(file, format)
> > local f= file
> > local attr = lfs.attribu
s(f)
why the f?
function modification_date(filename,format)
local attr = lfs.attributes(filename)
if type(attr) == "table" and attr.mode ~= "directory" then
if format == "nice" then
return os.date("%Y-%m-%dT%X",attr.modifica
>> Thanks, nice! I suppose the filename is also directly reachable from inside
>> \startluacode ... \stopluacode. How?
>
> \start-stop luacode expands its contents. So, the following should work
> (untested)
>
> \startluacode
> thisfilename = "\thisfilena
On Thu, 24 Mar 2011, Florian Wobbe wrote:
How would you automatically find out the filename which the macro is called
from? For instance if the file with the macro is included in a master document.
\inputfilename
So, if you want the name of the file in which this macro is defined in, then
>> How would you automatically find out the filename which the macro is called
>> from? For instance if the file with the macro is included in a master
>> document.
>
> \inputfilename
>
> So, if you want the name of the file in which this macro is defined in, then
On Thu, 24 Mar 2011, Florian Wobbe wrote:
\def\getdate
{\dosingleempty\dogetdate}
\def\dogetdate[#1]%
{\ctalua{context(modification_date("\jobname.tex", "#1"))}}
How would you automatically find out the filename which the macro is called
from? For instance if the fi
> \def\getdate
> {\dosingleempty\dogetdate}
>
> \def\dogetdate[#1]%
> {\ctalua{context(modification_date("\jobname.tex", "#1"))}}
How would you automatically find out the filename which the macro is called
from? For instance if the file with the mac
> > anymore.)
>
>
> There is a bug in lxml-dir.lua. Open lxml-dir.lua and change
>
> local collection = xml.applylpath({ getid(xml.load(filename)) },"directive")
> -- is { } needed ?
>
> to
>
> local collection = xml.applylpath(getid(xml.l
-dir.lua and change
local collection = xml.applylpath({ getid(xml.load(filename)) },"directive") --
is { } needed ?
to
local collection = xml.applylpath(getid(xml.load(filename)),"directive")
-- AM: removed { }
[@Hans: I do not checked if this affects other uses
All,
I could have phrased my question better ... here is another attempt:
I use ConTeXt to generate a PDF for upload using the command "context filename"
on either Mac OS X or Ubuntu. I have installed ConTeXt by installing a TeX Live
distribution on each platform. The command complet
> I was quite surprised that I can't run "context.lua" (eg. for making formats)
> anymore, after I cleaned the cache.
> When I did it ("mtxrun --script cache --erase"), Is there something I can do
> to get my context install running again?
mtxrun --gene
Hi,
I have an image file with two dots: file.xy.pdf
I can embed this file with
\externalfigure[file.xy.pdf][][width=\textwidth]
When leaving out the extension, the image is not found, e.g.:
\externalfigure[file.xy][][width=\textwidth]
For the time being, I renamed the files but it would b
On 6-3-2011 9:36, Vnpenguin wrote:
"/dev/null" as folder name ? Wow, what a crazy idea !
well, \input /dev/null/thesis-chapter-1.tex
does miracles (in germany)
Hans
-
Hans Hagen | PRAGM
On Sat, Mar 5, 2011 at 21:26, Thomas Schmitz wrote:
> On Sat, 5 Mar 2011 20:09:12 +
> "Reviczky, Adam" wrote:
>
>>
>> It works with the "+" character though.
>> The same problem goes for the directory names; directories with "~" in
"Reviczky, Adam" writes:
>>> only Hans can decide if this can/should be changed
> I won't argue for any changes, just thought to ask about it.
> A simple "yes, can be done" or "no, its a really bad idea" is perfectly enough
> for me.
See also section 1.7 on page 11 of the ConTeXt manual¹.
Feel
On Sat, 5 Mar 2011, Reviczky, Adam wrote:
only Hans can decide if this can/should be changed
I won't argue for any changes, just thought to ask about it.
I'll think about a workaround outside context.
The "error" is with the backend.
luatex (and pdftex and even tex) do not like filenames wi
>> only Hans can decide if this can/should be changed
I won't argue for any changes, just thought to ask about it.
A simple "yes, can be done" or "no, its a really bad idea" is perfectly enough
for me.
I'll think about a workaround outside context.
Cheers,
Adam
__
On Sat, 5 Mar 2011 20:38:13 +
"Reviczky, Adam" wrote:
Dear Thomas
I understand, that it's not a good idea, and I've seen
similar issues on the list
(http://www.ntg.nl/pipermail/ntg-context/2010/052339.html).
I ran into this by making a deb package of a software
(that includes context f
>> Yeah, please fix this ASAP. I keep all my context files in
>> a directory which I call /dev/null, and for some reason,
>> this doesn't really work. But I am not going to change the
>> name of my directory, no, you have to rewrite your
>> software!
>>
>> Thomas
Dear Thomas
I understand, that it
On Sat, 5 Mar 2011 20:09:12 +
"Reviczky, Adam" wrote:
It works with the "+" character though.
The same problem goes for the directory names;
directories with "~" in the name drops and error, even if
the filename has no special characters in it.
Can th
Hi
Context fails to run with an input (filename or directoryname) that includes
special characters.
example files:
%%%
reviczky@arlequin ~/minimal % la
total 0
drwxrwxr-x 1 reviczky reviczky 60 2011-03-05 19:58 ./
drwxr-xr-x 1 reviczky reviczky 2148 2011-03-05 20:00 ../
drwxrwxr-x 1 reviczky
On 2011-02-26 Aditya Mahajan wrote:
> > So after the project is done one can run context --purgeall filename to
> > get a clean directory structure without having to archive 30 temporary
> > files.
>
> I don't know how to implement this functionality and still
On Wed, 23 Feb 2011, Marco wrote:
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-externalfilter-CON-0.vimout % not removed
So after
vips/lm/lm-math.map}{C:/contextminimal/texmf/fonts/map/dvips/lm/lm-rm.map}
fonts > fallback modern rm 12pt is loaded
system > begin file lily.tex at line 3
structure > sectioning > subject @ level 3 : 0.0.0 -> Telemann, TWV 40:11
!
ontext --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 is of in
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
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-ex
would 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 remo
On 2011-02-23 Andreas Harder 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: 2
ad 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]
>
> Then you can use
>
> \noffigurepages
> \figurenaturalwidth \figurenaturalheigh
wondering if Aditya's filter module could be used 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 th
hould 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]
Then you can use
\noffigurepages
\figurenaturalwidth
\figurenaturalheight
to place each page of the figure. Something like:
\getfiguredimensions[fil
Dear Hans,
On Mon, 21 Feb 2011, Hans Hagen wrote:
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 ma
uot; as in the
examples 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
rd)
wreak havoc for Windows and some Windows applications, 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 comp
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
trouble 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
ection == "" then
context("no selection given")
else
if document.arguments.sort then
table.sort(document.files)
end
for _, filename in ipairs(document.files) do
if not string.find(filename,"^mtx%-context%-") the
I can't do that directly 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 wit
ame/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 wi
+ 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 following the dot is the
extension, while
o http://www.ntg.nl/pipermail/ntg-context/2010/052339.html ;)
>
>well, having a * in a filename is a bad idea anyway
>
>Hans
>
>-
> Hans Hagen | PRAGMA ADE
> R
On 18-1-2011 10:04, Peter Münster wrote:
Renaud AUBIN 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
801 - 900 of 1663 matches
Mail list logo
