[NTG-context] Strange behavior concerning pdf-output of .png-externalfigures

2019-05-21 Thread Rudolf Bahr
On Thu, May 16, 2019 at 02:40:07PM +0200, Hans Hagen wrote: > On 5/16/2019 12:21 PM, Rudolf Bahr wrote: > > The problem with artefacts in .png images is still unsolved for me. > > I can circumvent it by using .jpg or .tiff images instead of .png images > > as long as no transparent areas in the

Re: [NTG-context] (forw) Re: Strange behavior concerning pdf-output of externalfigures

2019-05-21 Thread Taco Hoekwater
Hi, Just for fun, I ran the test myself. I do not have gm installed, so the inclusion of the tiff failed, and (perhaps not coincidentally) I have no artifacts in the png image in my output either. Best wishes, Taco > On 21 May 2019, at 09:52, Hans Hagen wrote: > > On 5/17/2019 9:43 AM,

Re: [NTG-context] (forw) Re: Strange behavior concerning pdf-output of externalfigures

2019-05-21 Thread Hans Hagen
On 5/17/2019 9:43 AM, Rudolf Bahr wrote: On Thu, May 16, 2019 at 02:40:07PM +0200, Hans Hagen wrote: On 5/16/2019 12:21 PM, Rudolf Bahr wrote: The problem with artefacts in .png images is still unsolved for me. I can circumvent it by using .jpg or .tiff images instead of .png images as long

Re: [NTG-context] Strange behavior concerning pdf-output of .png-externalfigures

2019-05-21 Thread Hans Hagen
On 5/17/2019 10:23 AM, Rudolf Bahr wrote: On Thu, May 16, 2019 at 02:40:07PM +0200, Hans Hagen wrote: On 5/16/2019 12:21 PM, Rudolf Bahr wrote: The problem with artefacts in .png images is still unsolved for me. I can circumvent it by using .jpg or .tiff images instead of .png images as long

Re: [NTG-context] UTF8 chars in attribute values (XML)

2019-05-21 Thread Hans Hagen
On 5/19/2019 7:38 PM, Pablo Rodriguez wrote: Hi Hans, I’m afraid I found another issue with UTF8 chars in attribute values when printing them. \starttext \startTEXpage[offset=1em] \startXML \stopXML \stopTEXpage \stoptext Inspecting buff-imp-xml.lua, I

Re: [NTG-context] UTF8 chars in attribute values (XML)

2019-05-21 Thread Pablo Rodriguez
On 5/21/19 10:19 AM, Hans Hagen wrote: > On 5/19/2019 7:38 PM, Pablo Rodriguez wrote: >> [...] >> Inspecting buff-imp-xml.lua, I understand that "alsoname" should be >> added to "key". But I don’t know where or how this could be achieved. >> >> Sorry for not providing a patch, > fixed in next beta

Re: [NTG-context] section to have different conversion in body part and appendices

2019-05-21 Thread Pablo Rodriguez
On 5/21/19 3:10 PM, Procházka Lukáš Ing. wrote: > Hello, > > is there a way to tell \section (or other heads) to be "number-converted" > differently in bodypart and appendices? Hi Lukáš, I think this is what you want to achieve: \definestructureconversionset [sectionnumbers]

Re: [NTG-context] (forw) Re: Strange behavior concerning pdf-output of externalfigures

2019-05-21 Thread Alan Braslau
On Fri, 17 May 2019 09:43:29 +0200 Rudolf Bahr wrote: > And then the same .png-image > to which I added a red frame by GIMP2.10. This one shows artefacts in > ConTeXt! I *always* use MetaPost to add features (and to clip) images. These features (arrows, labels, etc.) are then vectorial and

[NTG-context] section to have different conversion in body part and appendices

2019-05-21 Thread Procházka Lukáš Ing .
Hello, is there a way to tell \section (or other heads) to be "number-converted" differently in bodypart and appendices? Something like: \setuphead[section][] % e.g. "appendices:numberconversion=A"? \starttext \starbodyamtter \section{In body} % To produce "1. In body"