On 4/28/2019 8:10 PM, Rudolf Bahr wrote:
Dear list,
I'm getting unexplainable artefacts in the pdf-output.
My MWE is:
--
\starttext
\externalfigure
[input.png]
[width=100mm]
\stoptext
--
I append the output "MWE.pdf" and the input-figure "input.png
@luigi: Version 11. I know, it isn't supported anymore since October 2017.
___
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/mail
On Sun, Apr 28, 2019 at 9:42 PM Paul Schalck wrote:
>
> I use Acrord because I'm used to it and because I think it still has the
> best subpixel rendering, at least in the Linux world (with Wine). Mozilla's
> PDF.js comes close though.
>
which version of adobe reader are you using?
--
luigi
@Hans: Thanks a lot, I'm looking forward to testing it.
@Alan: Like Hans said. It's a new option, and I have it activated in my local
environment file. It's the only and clumsy way to control the interface setting
since Adobe Reader cannot save the state of the menu bar permanently (which is
co
Hans Hagen schrieb am 28.04.2019 um 18:42:
On 4/28/2019 5:56 PM, Aditya Mahajan wrote:
On Sun, 28 Apr 2019, Wolfgang Schuster wrote:
The problem are these settings in buff-imp-default.mkiv:
\setupstartstop
[DefaultSnippet]
[\c!before={\typingparameter\c!before},
\c!after={\typingparamet
Dear list,
I'm getting unexplainable artefacts in the pdf-output.
My MWE is:
--
\starttext
\externalfigure
[input.png]
[width=100mm]
\stoptext
--
I append the output "MWE.pdf" and the input-figure "input.png" for comparison.
I'm experiencing the artef
On 4/28/2019 5:56 PM, Aditya Mahajan wrote:
On Sun, 28 Apr 2019, Wolfgang Schuster wrote:
The problem are these settings in buff-imp-default.mkiv:
\setupstartstop
[DefaultSnippet]
[\c!before={\typingparameter\c!before},
\c!after={\typingparameter\c!after},
\c!style={\typingparameter\
Sun, Apr 28, 2019 ve 01:01:12PM +0200 Hans Hagen napsal(a):
# On 4/27/2019 10:55 PM, Tomas Hala wrote:
# >Hi all,
# >
# >I tried linetable tables (mkiv, TL2017) because I need even
# >horizontal splitting. It works fine but I do not know how to make
# >either horizontal or vertical lines.
# >
# >H
On Sun, 28 Apr 2019, Wolfgang Schuster wrote:
The problem are these settings in buff-imp-default.mkiv:
\setupstartstop
[DefaultSnippet]
[\c!before={\typingparameter\c!before},
\c!after={\typingparameter\c!after},
\c!style={\typingparameter\c!style}]
In buff-imp-tex.mkiv these values
On 4/28/2019 5:25 PM, Alan Braslau wrote:
On 28Apr19, at 04:27, Hans Hagen wrote:
\setupinteractionscreen[option=nomenubar] switch.
I wonder if it would be possible to add this little feature to the source code.
Why don’t you simply put this setup in your local environment (texmf-local) as
> On 28Apr19, at 04:27, Hans Hagen wrote:
>
>> \setupinteractionscreen[option=nomenubar] switch.
>> I wonder if it would be possible to add this little feature to the source
>> code.
Why don’t you simply put this setup in your local environment (texmf-local) as
I do not believe that it shoul
> On 28Apr19, at 02:55, Pablo Rodriguez wrote:
>
> I add the path, otherwise no mtxrun would be found.
Of course, Otared is saying:
$CONTEXTHOME/tex/texmf-osx-64/bin/mtxrun -generate
where osx-64 is the platform.
--
Alan Braslau
__
The problem are these settings in buff-imp-default.mkiv:
\setupstartstop
[DefaultSnippet]
[\c!before={\typingparameter\c!before},
\c!after={\typingparameter\c!after},
\c!style={\typingparameter\c!style}]
In buff-imp-tex.mkiv these values are inherited:
\definestartstop
[TexSnippet
Hi,
The following minimal example:
\definetextbackground
[EXAMPLE]
[
location=paragraph,
rulethickness=1pt,
leftoffset=5em,
rightoffset=0mm,
]
\setuptyping[option=tex, before=\startEXAMPLE, after=\stopEXAMPLE]
\starttext
\starttyping
A = B + C
\stopt
On 4/27/2019 10:55 PM, Tomas Hala wrote:
Hi all,
I tried linetable tables (mkiv, TL2017) because I need even
horizontal splitting. It works fine but I do not know how to make
either horizontal or vertical lines.
Have somebody got some experience with this?
There are no options (yet) for that b
On 4/27/2019 6:07 PM, Paul Schalck wrote:
Hi,
I use the "Hide menu bar" option extensively in Adobe Acrobat Reader to get a
cleaner interface. To this end, I usually hack lpdf-mis.lua after a ConTeXt upgrade to
create a \setupinteractionscreen[option=nomenubar] switch.
I wonder if it would be
On 4/27/19 11:06 PM, Aditya Mahajan wrote:
> On Sat, 27 Apr 2019, Pablo Rodriguez wrote:
>> [...]
>> If the soft symlink for the fonts directory is itself tex/texmf-fonts/,
>> ConTeXt LMTX handles the fonts right.
>
> The texmf-fonts directory must follow TDS (tex document structure).
> Assuming th
On 4/27/19 9:50 PM, Otared Kavian wrote:
> Hi Pablo,
>
> I don't know if this may help, but in principle in order to use
> system fonts in LMTX you should invoke the mtxrun in the bin
> directory of your installation of LMTX. For me, working on MacOS, the
> following worked fine:
>
> /context
18 matches
Mail list logo