I figured it out. I was wrongly calculating the page size argument for gs.
Thank you very, very much again Max!
On Thu, Jun 2, 2022 at 4:41 AM Stefan Nedeljkovic
wrote:
> There is one more problem: the pdf generated has incorrect margins. I
> tried to manually calculate the size in ps points
There is one more problem: the pdf generated has incorrect margins. I tried
to manually calculate the size in ps points and run gs directly, but the
results are the same. How can I get an accurate rendering of the page?
On Thu, Jun 2, 2022 at 4:22 AM Max Chernoff wrote:
> On 2022-06-01 8:00
On 2022-06-01 8:00 p.m., Stefan Nedeljkovic wrote:
Thank you very much Max! It works indeed! One more question. How would I
import the eps file back into MPpage, so I could do trickery with text.
Convert the PostScript file into PDF with either "ps2pdf" or
GhostScript, then you can import the
Thank you very much Max! It works indeed! One more question. How would I
import the eps file back into MPpage, so I could do trickery with text.
)
On Thu, Jun 2, 2022 at 1:46 AM Max Chernoff wrote:
> > I have a large .tex file with metapost embedded in it and want to compile
> > it, but it
I have a large .tex file with metapost embedded in it and want to compile
it, but it fails. Do you know of a way to compile it?
Just use plain MetaPost:
diff --git a/belgrade_gm.tex b/belgrade_gm.mp
index 3281754..d536b64 100644
--- a/belgrade_gm.tex
+++ b/belgrade_gm.mp
@@
> On 1 Jun 2022, at 22:30, Stefan Nedeljkovic via ntg-context
> wrote:
>
> Dear Thomas,
>
> I'm sorry for all the shortcomings of my question. I'll try to be more
> concrete. If you won't download my file, could you at least give me a hint on
> how to configure LMTX?
>
> I Tried editing
Now, I still don’t understand LPEG and don’t know if there’s a general
“character” class that doesn’t need a list...
Well looking through the XML spec
https://www.w3.org/TR/REC-xml/#NT-NameChar
you'd think that we'd want a pattern like this:
local name = (R("az","AZ","09",
Dear Thomas,
I'm sorry for all the shortcomings of my question. I'll try to be more
concrete. If you won't download my file, could you at least give me a hint
on how to configure LMTX?
I Tried editing the file context/tex/texmf/web2c/texmfcnf.lua, and running
context --generate, context --make,
On 6/1/22 22:15, Stefan Nedeljkovic via ntg-context wrote:
The problem *is* the file size. There is not a minimal example,
because everything works when there is less drawdot commands. There is
125000+ drawdot commands in the file.
The run ends with the message:
If you really absolutely need
P.S. Use the last link I posted, the updated file is there.
On Wed, Jun 1, 2022 at 10:15 PM Stefan Nedeljkovic
wrote:
> The problem *is* the file size. There is not a minimal example,
> because everything works when there is less drawdot commands. There is
> 125000+ drawdot commands in the
The problem *is* the file size. There is not a minimal example,
because everything works when there is less drawdot commands. There is
125000+ drawdot commands in the file.
The run ends with the message:
If you really absolutely need more capacity, you can ask a wizard to
enlarge me.
mtx-context
On 6/1/22 19:35, Stefan Nedeljkovic via ntg-context wrote:
Sorry, i just updated the file, should now compile, but fail due to
resources. Are the configuration options to context that would enable
this file to be compiled?
The question still stands: what do you expect us to do? Hunt for a
Am 01.06.22 um 19:45 schrieb Pablo Rodriguez via ntg-context:
But I don’t know which file deals with it (so I could try to submit a
patch).
That would be texmf-context/tex/context/modules/mkiv/m-scite.mkiv
and
texmf-context/context/data/scite/context/lexers/scite-context-lexer-xml.lua
and
On 6/1/22 18:58, Henning Hraban Ramm via ntg-context wrote:
> Am 01.06.22 um 18:47 schrieb Pablo Rodriguez via ntg-context:
>> [...]
>> Could anyone confirm the issue?
>
> Hi Pablo,
>
> with LMTX version 2022.05.11, both elements are displayed, but the first
> in blue, the second in red.
Sorry, i just updated the file, should now compile, but fail due to
resources. Are the configuration options to context that would enable this
file to be compiled?
On Wed, Jun 1, 2022 at 7:24 PM Bruce Horrocks wrote:
> Hi Stefan,
>
> What exactly are you asking for help with?
>
> The previous
Hi Stefan,
What exactly are you asking for help with?
The previous file was 12MB and simply ran out of resource when compiled. The
new file is 812KB and compiles provided you remove the references to
\setxheight[...] because \setxheight generates an error.
> On 1 Jun 2022, at 17:43, Stefan
Am 01.06.22 um 18:47 schrieb Pablo Rodriguez via ntg-context:
Dear list,
I have the following sample:
\usemodule[scite]
\starttext
\startTEXpage[offset=1ex]
\type[option=xml]{}
\type[option=xml]{<áñß/>}
\stopTEXpage
\stoptext
Using scite, I don’t get the second element
Dear list,
I have the following sample:
\usemodule[scite]
\starttext
\startTEXpage[offset=1ex]
\type[option=xml]{}
\type[option=xml]{<áñß/>}
\stopTEXpage
\stoptext
Using scite, I don’t get the second element right.
Without scite, both elements are displayed right.
In both Geany
Just fixed the file, here is the new link:
https://drive.google.com/file/d/16jTzHbaqxPmhgmNaDOBRijlhlmUCnH4j/view?usp=sharing
On Wed, Jun 1, 2022 at 4:48 PM Stefan Nedeljkovic
wrote:
> Dear list,
>
> I have a large .tex file with metapost embedded in it and want to compile
> it, but it fails.
Dear list,
I have a large .tex file with metapost embedded in it and want to compile
it, but it fails. Here is a link to the file (~12MB):
https://drive.google.com/file/d/1t-6mxFmGp-nzpl0RrPgNFq8KRvpplgDv/view?usp=sharing
Do you know of a way to compile it?
BTW, the file is automatically
Hi,
several times I got problems with my publishing house when they noticed that
the headerlines jump up and down on pages that end/begin with qoutes (i.e.
smaller interlineskip), see example below: on page 1 the blackrule is about 1mm
higher than on page 2.
In the past I then used really
Am 01.06.22 um 02:39 schrieb Max Chernoff:
the formatting of Lua multi-line strings messes up the source
structure, in the following MWE, the "one" is displayed after "[[":
I can reproduce this. As a workaround, you can insert a non-breaking
space (U+00A0) immediately after the "[[":
Good
22 matches
Mail list logo
