On 10-9-2012 04:45, Andre Caldas wrote:
Hello, list!
I am really new to ConTeXt. I am writing a book
http://topologia-geral.ourproject.org/
It is written in LaTeX and I intend to migrate it to ConTeXt.
I want to migrate and I want to be as far from HACKS as I can. So I
want to know the
On 10-9-2012 03:26, Bill Meahan wrote:
Trying to define some spot colors using the wiki examples. I get the
following error message every time I run MKIV:
colors cmyk color space is not supported
harmless
Here's the relevant section of my environment file:
% Turn on colors.
dear all,
I’m trying to build a stepwise presentation, but the following minimal
example (got it from the ML[1]) produces an error:
ConTeXt ver: 2012.09.06 23:03 MKIV fmt: 2012.9.9
…
!LuaTeX error: There should have been a lua node here, not an object
with type string!
The example
I am making my first steps in ConTeXt. I am only interested in Mk-iv and
am using version 2012.09.06 23:03. I tried to explore the possibilities of
the
additional module *lettrine* following its documentation
(*lettrine-doc.pdf*)
and prepared the following example, which reproduces almost
On 2012-09-10 Ian Lawrence physics.roo...@gmail.com wrote:
Hi Ian,
I'd like to pass variables into context on invocation, just as you can do
with setting modes
So
context --arguments=number=8, time=full-time --mode=trial test.tex
context --number=8 --time=full-time test.tex
On Mon, Sep 10 2012, Marco Patzer wrote:
context --number=8 --time=full-time test.tex
Then you have to be sure, that --number and --time will never be special
parameters for context.
Alternatives:
--MarcoPatzerNumber=8 --MarcoPatzerTime=full-time
Or:
% context
Hello Francisco,
Welcome to ConTeXt! You are sure to enjoy it here.
My conclusion is that *lettrine* does not work correctly with Mark-iv and
there is somewhere a bug that has to be corrected. But I could be
mistaken. Am I doing something wrongly?
No, you are correct, there is a bug. It
2012-09-10: Peter Münster pmli...@free.fr
Then you have to be sure, that --number and --time will never be special
parameters for context.
Indeed.
Alternatives:
--MarcoPatzerNumber=8 --MarcoPatzerTime=full-time
Or:
% context --arguments=number=8,time=full-time test.tex
This seems
When I write a project, product, component or environment file, why
would I want the references I made to be dependent on the directory
where the script was called? Shouldn't things be like the
#include relative_path.h
used in the C language, for example? That is, shouldn't those paths be
Documented at http://wiki.contextgarden.net/Command/getdocumentargument,
in the category Command/Internals.
--Sietse
On Mon, Sep 10, 2012 at 2:00 PM, Marco Patzer home...@lavabit.com wrote:
2012-09-10: Peter Münster pmli...@free.fr
Then you have to be sure, that --number and --time will never
On Mon 10 Sep 2012, Andre Caldas wrote:
Do you really need to use context mkii? As it's a new project,
using context mkiv might be a better idea.
No, I don't. I want to use always the preferred solution. I want to
follow your guidelines and be enlightened... :-)
How did you know I was
I had to switch to \placeinitial, e.g.
Instead of:
% \usemodule[lettrine]
% \setuplettrine[Raise=0.1,FontHook=\darkgrey,TextFont=\tf]
I used:
\setupinitial[color=darkgrey,n=2,voffset=-1.5ex]
and then:
\placeinitial My text …
See also
On 09/10/2012 03:13 AM, Hans Hagen wrote:
harmless
\definecolor
[PantoneTwoNineFour]
[c=1,m=.68,y=7,k=.28]
Thanks as always. Spotted the 7 not .7 typo two minutes after I hit
the send key. Sigh.
Everything is working fine now and even the error message has disappeared.
Hi, I am running the latest minimals on a 64bit Linux system and ran
into a luatex crash with a specific file. I reduced the file down to a
simpler version that still triggers the crash, and thought it would be
of some interest to post (the resulting pdf, if generated, will be ugly
since I
On 2012-09-10, at 10:42 AM, Bill Meahan subscribed_li...@meahan.net wrote:
On 09/10/2012 03:13 AM, Hans Hagen wrote:
harmless
\definecolor
[PantoneTwoNineFour]
[c=1,m=.68,y=7,k=.28]
Thanks as always. Spotted the 7 not .7 typo two minutes after I hit the
send key. Sigh.
On 09/10/2012 10:59 AM, Aditya Mahajan wrote:
Just curious. Why don't you enable hanging punctuation?
Aditya
I thought I did! From my environment file:
\definefontfeature
[default]
[default]
[protrusion=quality,expansion=quality]
\setupalign[hz,hanging]
--
Bill Meahan
Westland,
Thanks to all. After about 30 mins exploring, it all came together.
I'll try to add something to the wikithe link below is fine if you know
it's there, and that this is what you want. But the search function
(arguments and variants thereof did not find it for me).
The best match for what
I have a macro to typeset function definitions:
\define[5]\functionarray
{
\startalign[n=4, align={left,right,center,left}]
\NC #1: \NC #2 \NC \to \NC #3 \NR
\NC \NC #4 \NC \mapsto \NC #5
\stopalign
}
I use it like this: (notice the period at the end)
On Mon, 10 Sep 2012, Andre Caldas wrote:
I have a macro to typeset function definitions:
\define[5]\functionarray
{
\startalign[n=4, align={left,right,center,left}]
\NC #1: \NC #2 \NC \to \NC #3 \NR
\NC \NC #4 \NC \mapsto \NC #5
\stopalign
}
I use it like this:
On Mon, 10 Sep 2012, Bill Meahan wrote:
On 09/10/2012 10:59 AM, Aditya Mahajan wrote:
Just curious. Why don't you enable hanging punctuation?
I thought I did! From my environment file:
\definefontfeature
[default]
[default]
[protrusion=quality,expansion=quality]
On 09/10/2012 08:06 PM, Aditya Mahajan wrote:
It did not look enabled at first glance. All the end quotes on 69 [1]
look a bit short of the line length (but I don't recall whether
hanging punctuation hangs the quotes or not).
However, now that I looked carefully, I see that hanging
21 matches
Mail list logo
