Am 20.03.2012 um 06:49 schrieb Kip Warner:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take down the entire
Hello,
I have solved my old question connected with preflight and overprinting of
pure text. Now I am able to have clean output, the last warning (just info)
is about the fact context files have fonts embedded like CID Type 1 fonts.
I am using this colors setup:
Am 20.03.2012 um 06:17 schrieb Wolfgang Schuster:
Am 19.03.2012 um 22:27 schrieb Steffen Wolfrum:
Hi,
are subfootnotes not yet rewritten, or did the syntax change?
The following example expects 2.a but gives 2.1:
\definestructureseparatorset [footnote][][]
On 20-3-2012 01:43, Kip Warner wrote:
On Mon, 2012-03-19 at 22:49 +0100, Hans Hagen wrote:
On 19-3-2012 00:29, Kip Warner wrote:
I've cc'd the luatex user mailing list since this is probably, I
suppose, a luatex issue more than a ConTeXt one.
not that probable
Actually highly probably,
... and what is the new syntax for \setnumber[footnote]?
(the old notation \setnumber[footnote]{123} now results in printing the figures
123)
Steffen
___
If your question is of interest to others as well, please
On 20-3-2012 06:49, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take down the entire
operating
Hi,
how can I define the length of footnote's rule and the distance below it?
rulecommand doesn't seem to take these values (see below).
Steffen
---
\setupnote[footnote]
[rulecolor=orange,% OK
rulecommand={\vrule width10mm\vskip10mm},% ???
rulethickness=5pt]% OK
\starttext
Hello,
I have found that placing figures in grid mode does problems with
[left,right...] parameters. The figure brokes the text flow. (It suffice to
turn grid=yes.)
Any solution, please?
Thanks, Honza
\enableregime[utf]
\mainlanguage[cz]
\setuppapersize[A5][A5]
\setuplayout[
*grid=yes*
]
On Tue, Mar 20, 2012 at 9:17 AM, Hans Hagen pra...@wxs.nl wrote:
On 20-3-2012 06:49, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went
Hi,
this is continuing of my last question.
Please, what is wrong with this?
\enableregime[utf]
\mainlanguage[en]
\setuppapersize[A5][A5]
\definefloat[figure][figures]
\setupcaption[figure][align=left]
\starttext
\input tufte
\placefigure[left]{sdf}{\externalfigure[none][width=5cm]}
\input
Am 20.03.2012 um 10:10 schrieb Steffen Wolfrum:
Hi,
how can I define the length of footnote's rule and the distance below it?
rulecommand doesn't seem to take these values (see below).
You have to enable you own command with “rule=command” but then you have to set
rulecolor and rule
On Mon, Mar 19, 2012 at 10:49:48PM -0700, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take
On Tue, Mar 20, 2012 at 08:21:35AM +0100, Patrick Gundlach wrote:
Am 20.03.2012 um 06:49 schrieb Kip Warner:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was
Am 20.03.2012 um 09:16 schrieb Steffen Wolfrum:
... and what is the new syntax for \setnumber[footnote]?
(the old notation \setnumber[footnote]{123} now results in printing the
figures 123)
You need brackets for both arguments (i.e. \setnumber[footnote][123]), this was
changed because
Am 20.03.2012 um 14:42 schrieb Wolfgang Schuster:
You have to enable you own command with “rule=command” but then you have to
set rulecolor and rule thickness in your own definition (best us \blackrule
for this).
rule=command,rulecommand=\MyRule
instead of
rulecommand=\MyRule
hm ...
Am 20.03.2012 um 17:01 schrieb Wolfgang Schuster:
Am 20.03.2012 um 09:16 schrieb Steffen Wolfrum:
... and what is the new syntax for \setnumber[footnote]?
(the old notation \setnumber[footnote]{123} now results in printing the
figures 123)
You need brackets for both arguments
Am 20.03.2012 um 17:35 schrieb Steffen Wolfrum:
Am 20.03.2012 um 14:42 schrieb Wolfgang Schuster:
You have to enable you own command with “rule=command” but then you have to
set rulecolor and rule thickness in your own definition (best us \blackrule
for this).
Hello,
WinEDT finally has Unicode support and the screenshot shows ConTeXt in
typesetting menu as well (no idea if that runs texexec or context).
http://winedt.com
It has been my first TeX editor and I liked it a lot because of
newbie-friendliness (lots of tex characters in menu, so no need
On Tue, Mar 20, 2012 at 6:16 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
Hello,
WinEDT finally has Unicode support and the screenshot shows ConTeXt in
typesetting menu as well (no idea if that runs texexec or context).
Maybe T means pdftex engine, L luatex.
--
luigi
Am 20.03.2012 um 17:45 schrieb Wolfgang Schuster:
Am 20.03.2012 um 17:35 schrieb Steffen Wolfrum:
Am 20.03.2012 um 14:42 schrieb Wolfgang Schuster:
You have to enable you own command with “rule=command” but then you have to
set rulecolor and rule thickness in your own definition
On 20-3-2012 18:59, Steffen Wolfrum wrote:
But nevertheless, isn't that already implied if I use rulecommand=\MyRule?
To me this already means exactly this: tell context it should use my rule.
Then we need double checking and I'm pretty sure that you would run into
expansion mess again and
On Tue, 2012-03-20 at 09:17 +0100, Hans Hagen wrote:
which is not really a crash of my operating system; there is not much
I
can do about this issue I fear.
Totally up to you. I just wanted to bring it to your attention.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail
On Tue, 2012-03-20 at 16:57 +0200, Khaled Hosny wrote:
Older TeX engines had hard memory limit, so in case of such
syntactical errors the engine would consume all its allocated memory
and die (with a misleading error message), LuaTeX dynamically allocates
memory (for good reasons) so it won't
Can someone tell me what \xmlinclude is supposed to do? I have experimented a
lot but didn't come further to an understanding.
I have called it through:
\startxmlsetups xam:include
\xmlinclude{#1}{include}{file}
\stopxmlsetups
from a node include in:
probleminclude
On Mon, Mar 19, 2012 at 23:12, Hans Hagen wrote:
On 19-3-2012 22:08, Mojca Miklavec wrote:
Out of curiosity: is inability to create password-protected PDF files
with pdfTeX/LuaTeX due to legal issues or due to nobody caring enough
to implement it?
it's not worth the trouble. Afaik it's a
On 20-3-2012 19:59, Kip Warner wrote:
On Tue, 2012-03-20 at 16:57 +0200, Khaled Hosny wrote:
Older TeX engines had hard memory limit, so in case of such
syntactical errors the engine would consume all its allocated memory
and die (with a misleading error message), LuaTeX dynamically allocates
On 20-3-2012 20:23, Mojca Miklavec wrote:
On Mon, Mar 19, 2012 at 23:12, Hans Hagen wrote:
On 19-3-2012 22:08, Mojca Miklavec wrote:
Out of curiosity: is inability to create password-protected PDF files
with pdfTeX/LuaTeX due to legal issues or due to nobody caring enough
to implement it?
Am 20.03.2012 um 19:49 schrieb Hans Hagen:
On 20-3-2012 18:59, Steffen Wolfrum wrote:
But nevertheless, isn't that already implied if I use rulecommand=\MyRule?
To me this already means exactly this: tell context it should use my rule.
Then we need double checking and I'm pretty sure
On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { }
while true do
t[#t+1] = just a bogus string: .. (#t+1)
end
at some point your system will run out of (virtual) memory or lua will
run out of whatever its limits
On Tue, Mar 20, 2012 at 8:59 PM, Kip Warner k...@thevertigo.com wrote:
On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { }
while true do
t[#t+1] = just a bogus string: .. (#t+1)
end
at some point your system will run
On 20-3-2012 20:59, Kip Warner wrote:
On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { }
while true do
t[#t+1] = just a bogus string: .. (#t+1)
end
at some point your system will run out of (virtual) memory or lua will
On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
When TeX says
! TeX capacity exceeded, sorry [token memory size=...]
it is its graceful way to exit from an irreversible situation.
It can be caused by luatex or ConTeXt mkiv
but it's *not* a segmentation fault, as you said early:
Le mardi 20 mars 2012 à 20:23 +0100, Mojca Miklavec a écrit :
On Mon, Mar 19, 2012 at 23:12, Hans Hagen wrote:
On 19-3-2012 22:08, Mojca Miklavec wrote:
Out of curiosity: is inability to create password-protected PDF files
with pdfTeX/LuaTeX due to legal issues or due to nobody caring
On Tue, 2012-03-20 at 21:44 +0100, Hans Hagen wrote:
sure, but mu experience is that browsers of email clients are way more
demanding than tex when it comes to memory usage
I've never had either take down the entire operating system. There is a
different from intended memory usage and
In the processing of incoming xml-data this is typeset as is, not as processed
text.
Thus for example: with \xmlflush{#1} the incoming data:
textits_content/text is not typeset as: its_content, but as:
textits_content/text.
Substitution of \xmlcontext{#1}{.} for \xmlflush{#1} makes everything
On Tue, Mar 20, 2012 at 10:24 PM, Kip Warner k...@thevertigo.com wrote:
On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
When TeX says
! TeX capacity exceeded, sorry [token memory size=...]
it is its graceful way to exit from an irreversible situation.
It can be caused by luatex or
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
You can’t have a assignment in both parameters because this would lead
to the same problem as before,
combine both settings in one argument and it works.
I must not be doing it right because the item numbers are gone now and
replaced
On Tue, 20 Mar 2012, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
You can’t have a assignment in both parameters because this would lead
to the same problem as before,
combine both settings in one argument and it works.
I must not be doing it right because
2012/3/20 Mojca Miklavec mojca.miklavec.li...@gmail.com:
If qpdf exists it is probably not a legal issue to do password protection
then.
Of course.
But from the same perspective ... one first needs PDF to be (almost)
finished before being able to sign it. One needs to read as-good-as
the
Hi all,
I am designing a document suite consisting of two dozen or so documents that
are all interrelated. I was wondering whether there is a way that I can define
a reference point for an entire document within a project and then refer to
that from another document, like
40 matches
Mail list logo
