Re: [NTG-context] option for printing range
On Tue, Feb 27, 2018 at 10:05 PM, Hans Hagen wrote: > On 2/27/2018 7:47 PM, Christoph Reller wrote: > > anyway, i normally test pdf with an old acrobat X pro (i don't want to lock > into some subscription and i don't really need a more modern version) and i > preview / print pdf using sumatra pdf > > (printing houses often use pretty old versions anyway) > You may actually be better off with Acrobat X then with Acrobat DC when it comes to testing, because Acrobat DC has an even stronger tendency to ignore errors silently. :-) Cheers, Christoph ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Question about text offset
Dear list,
I was wondering, why is the text in the main text block offset by .25\exheight
from above (and below)? Also, can you point me to the source line where this
offset is added in shipout because it is not there in \setuplayout. If you
don't know what I mean, see MWE below.
Cheers, Henri
---
\definelayer
[pagebg]
[width=\textwidth,
height=\textheight]
\setupbackgrounds
[text][background=pagebg]
\showframe
\starttext
\setlayer
[pagebg]
[voffset=.25\exheight] % why?
{\vbox{\strut\input lorem\par}}
\input lorem\par
\stoptext
___
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/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] option for printing range
On 2/27/2018 7:47 PM, Christoph Reller wrote: On Tue, 27 Feb 2018 09:15:37 +0100 Hans Hagen wrote: On 2/26/2018 8:02 PM, Pablo Rodriguez wrote: On 02/25/2018 10:51 PM, Hans Hagen wrote: On 2/25/2018 9:12 PM, Pablo Rodriguez wrote: [...] The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10" (the document only contains 10 pages). is ok here (looking in the pdf file) I have tested the file in Acrobat XI and since I got the same wrong page ranges, I asked to an Adobe engineer. He confirmed that the spec is wrong. Page counting for /PrintPageRange should be zero-based and it shouldn’t start from one. This is only one of many cases for which ISO-32000 is the spec and the Adobe Reader is the de-facto spec. Others affect annotations and rendering. the pdf spec sometimes looks like a mixture between wishful thinking and reverese engineered spec (as there are some real weird constructs in there) anyway, i normally test pdf with an old acrobat X pro (i don't want to lock into some subscription and i don't really need a more modern version) and i preview / print pdf using sumatra pdf (printing houses often use pretty old versions anyway) Sorry for this. Could you correct the implementation? the usual pdf spec rubish ... no one uses it (although tex is often first), they it gets a bugged implementation and then the specs change ... one of the reasons why i don't bother too much in implementing the latest pdf gadgets ... i wasted too much time adapting to changed (interpretation of the) specs Hans (I don't officially have the latest spec as i refuse to pay for a pdf specification that could be distributed in pdf format.) A small detail: The ISO specification for PDF 2.0 also defines the first page in /PrintPageRange to be page number 1 (not 0). :( makes me wonder if there was a 0/1 bug in some adobe pdf generator that then defined the standard to have a bug instead -) Hans -- - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] option for printing range
Am 2018-02-27 um 09:15 schrieb Hans Hagen : > (I don't officially have the latest spec as i refuse to pay for a pdf > specification that could be distributed in pdf format.) Since DANTE is now a member of the PDF Association, don’t "we" get it for free? Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] option for printing range
On Tue, 27 Feb 2018 09:15:37 +0100 Hans Hagen wrote: > On 2/26/2018 8:02 PM, Pablo Rodriguez wrote: >> On 02/25/2018 10:51 PM, Hans Hagen wrote: >>> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote: [...] The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10" (the document only contains 10 pages). >>> >>> is ok here (looking in the pdf file) >> >> I have tested the file in Acrobat XI and since I got the same wrong page >> ranges, I asked to an Adobe engineer. >> >> He confirmed that the spec is wrong. Page counting for /PrintPageRange >> should be zero-based and it shouldn’t start from one. This is only one of many cases for which ISO-32000 is the spec and the Adobe Reader is the de-facto spec. Others affect annotations and rendering. >> Sorry for this. Could you correct the implementation? > the usual pdf spec rubish ... no one uses it (although tex is often > first), they it gets a bugged implementation and then the specs change > ... one of the reasons why i don't bother too much in implementing the > latest pdf gadgets ... i wasted too much time adapting to changed > (interpretation of the) specs > > Hans > > (I don't officially have the latest spec as i refuse to pay for a pdf > specification that could be distributed in pdf format.) A small detail: The ISO specification for PDF 2.0 also defines the first page in /PrintPageRange to be page number 1 (not 0). :( Cheers, Christoph ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] export breaks float p
On Tue, 27 Feb 2018 15:41:41 +0100
Henning Hraban Ramm wrote:
> Try to compile this with and without the first line:
>
>
> \setupbackend[export=yes]
>
> \starttext
>
> \input tufte
> \placefigure[right]{}{%
> \externalfigure[hacker][width=.33\textwidth]%
> }%
> \input tufte
> \input tufte
>
> \stoptext
>
>
> With \setupbackend[export=yes] the image is placed "here" and never
> "right" or "left".
I "reported" this a while ago. The answer is that right or left are
meaningless for the export and that the export is built somehow using
the generated PDF.
I requested that this PDF be placed in the export (sub)directory so as
not to "break" the PDF produced on a previous run without export. I can
deal with multiple runs when exporting, although ideally one could
decide to export systematically and the process would produce two PDFs
including the one used in creating the export. If this seems awkward or
clumsy then at least preserving the "production" PDF would be desirable.
I believe that Hans' workflow includes controlling the export run by
viewing the export PDF (in sumatra), so he has been reluctant to change
the behavior.
Alan
___
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/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] export breaks float p
Try to compile this with and without the first line:
\setupbackend[export=yes]
\starttext
\input tufte
\placefigure[right]{}{%
\externalfigure[hacker][width=.33\textwidth]%
}%
\input tufte
\input tufte
\stoptext
With \setupbackend[export=yes] the image is placed "here" and never "right" or
"left".
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___
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/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] option for printing range
Am 2018-02-27 um 14:43 schrieb Floris van Manen : >> On 27 Feb 2018, at 13:50, Henning Hraban Ramm wrote: >> Too bad I can’t live (make a living) without Photoshop, InDesign etc... > > well, that depends as how you organise the workflow… > i switched away from adobe using context instead. I’m using ConTeXt for most of my serious products (books, magazines) nowadays, but it’s only efficient if you need TeX’s strengths (and can avoid its weaknesses) and make several issues with the same layout. I’m struggling a lot with ConTeXt’s quirks (e.g. the recently fixed spacing bug, but also just the lack of documentation on all the commands and their options) and too often I get no answers to my questions on this list or I can’t even ask something because I can’t come up with a minimal example, e.g. I recognized just today, float placement "right" or "left" failed to work because I compiled with --mode=something ... For one-off products (flyers, advertising etc.) ConTeXt is just not an option. And while I’m very fast in image processing with Photoshop I probably didn’t try enough achieving the same results with Gimp... Oh, and Scribus doesn’t help either - the GUI feels clumsy (like the old versions of Corel Draw I tried), and it’s still not possible to properly use layers in templates. At the moment I’m trying to typeset a book with a lot of poems and similar artsy stuff where every second needs a different formatting - not really a suitable ConTeXt project, but it also has a lot of footnotes that I wouldn’t like to typeset in InDesign.. Sorry, that went OT... Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] How to use fonts.handlers.otf.enhancers.patches?
On 2/27/2018 11:10 AM, Henri Menke wrote:
Thank you for the prompt solution!
The enhancers.patches solution does not work with ConTeXt from TeXlive
2017. I suspect that the font name matching on "^ebgaramond.*" is
incorrect, because the patch function is never called (MWE and log
attached).
you could print the filename and see what gets by (maybe the ^ is not
needed)
If I wanted to do this in ConTeXt I'd use the feature approach but
unfortunately the unicode-math package for LaTeX gives no option to set
mode=base to have features applied in math mode :/
i have no clue what happens there so ...
Cheers, Henri
On 02/27/2018 09:34 PM, Hans Hagen wrote:
On 2/26/2018 11:54 PM, Henri Menke wrote:
Dear list,
The EB Garamond font is lacking the ϵ glyph but it contains ε. So
naturally you
want to remap ϵ to ε. It cannot be done using font features because
the the
slot 0x03B5 (ϵ) is just missing, so substitution will not kick in. I
tried
adapting the mechanism to add uppercase greek to Latin Modern Math
from lm-
math.lfg. Unfortunately, my code is not working. What am I doing wrong?
Cheers, Henri
---
\startluacode
local patches = fonts.handlers.otf.enhancers.patches
local function patch(data,filename)
local uni_to_ind = data.map.map
if not uni_to_ind[0x3F5] then
patches.report("add ε for ϵ")
uni_to_ind[0x3F5] = uni_to_ind[0x3B5]
end
end
patches.register("after","missing glyphs","^ebgaramond*", patch)
\stopluacode
\setupbodyfont[ebgaramond]
\starttext
ε % = 03B5
ϵ % = 03F5
\stoptext
if you want to use the patch mechanism:
\startluacode
local function patch(data,filename)
data.descriptions[utf.byte("ϵ")] = data.descriptions[utf.byte("ε")]
end
fonts.handlers.otf.enhancers.patches.register("after","missing
glyphs","^ebgaramond*", patch)
\stopluacode
\setupbodyfont[ebgaramond]
\starttext
ϵ ε
\stoptext
or when you want to buse features:
\startluacode
fonts.handlers.otf.addfeature {
name = "ccmp", -- or "ebhack"
type = "substitution",
nocheck = true,
data = {
["ϵ"] = "ε",
}
}
\stopluacode
% \definefontfeature[default][default][ebhack=yes]
\setupbodyfont[ebgaramond]
\starttext
ϵ ε
\stoptext
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] option for printing range
> On 27 Feb 2018, at 13:50, Henning Hraban Ramm wrote: > > Too bad I can’t live (make a living) without Photoshop, InDesign etc... well, that depends as how you organise the workflow… i switched away from adobe using context instead. .F signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] option for printing range
Am 2018-02-26 um 20:02 schrieb Pablo Rodriguez : > On 02/25/2018 10:51 PM, Hans Hagen wrote: >> On 2/25/2018 9:12 PM, Pablo Rodriguez wrote: >>> [...] >>> The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10" >>> (the document only contains 10 pages). >> >> is ok here (looking in the pdf file) > > I have tested the file in Acrobat XI and since I got the same wrong page > ranges, I asked to an Adobe engineer. > > He confirmed that the spec is wrong. Page counting for /PrintPageRange > should be zero-based and it shouldn’t start from one. That’s so typical Adobe! Write faulty/unusable specs, let everyone in the dark and declare their implementation right. :( Too bad I can’t live (make a living) without Photoshop, InDesign etc... Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] How to use fonts.handlers.otf.enhancers.patches?
Thank you for the prompt solution!
The enhancers.patches solution does not work with ConTeXt from TeXlive
2017. I suspect that the font name matching on "^ebgaramond.*" is
incorrect, because the patch function is never called (MWE and log
attached).
If I wanted to do this in ConTeXt I'd use the feature approach but
unfortunately the unicode-math package for LaTeX gives no option to set
mode=base to have features applied in math mode :/
Cheers, Henri
On 02/27/2018 09:34 PM, Hans Hagen wrote:
> On 2/26/2018 11:54 PM, Henri Menke wrote:
>> Dear list,
>>
>> The EB Garamond font is lacking the ϵ glyph but it contains ε. So
>> naturally you
>> want to remap ϵ to ε. It cannot be done using font features because
>> the the
>> slot 0x03B5 (ϵ) is just missing, so substitution will not kick in. I
>> tried
>> adapting the mechanism to add uppercase greek to Latin Modern Math
>> from lm-
>> math.lfg. Unfortunately, my code is not working. What am I doing wrong?
>>
>> Cheers, Henri
>>
>> ---
>>
>> \startluacode
>> local patches = fonts.handlers.otf.enhancers.patches
>>
>> local function patch(data,filename)
>> local uni_to_ind = data.map.map
>> if not uni_to_ind[0x3F5] then
>> patches.report("add ε for ϵ")
>> uni_to_ind[0x3F5] = uni_to_ind[0x3B5]
>> end
>> end
>>
>> patches.register("after","missing glyphs","^ebgaramond*", patch)
>> \stopluacode
>>
>> \setupbodyfont[ebgaramond]
>>
>> \starttext
>>
>> ε % = 03B5
>> ϵ % = 03F5
>>
>> \stoptext
> if you want to use the patch mechanism:
>
> \startluacode
> local function patch(data,filename)
> data.descriptions[utf.byte("ϵ")] = data.descriptions[utf.byte("ε")]
> end
>
> fonts.handlers.otf.enhancers.patches.register("after","missing
> glyphs","^ebgaramond*", patch)
> \stopluacode
>
> \setupbodyfont[ebgaramond]
>
> \starttext
>
> ϵ ε
>
> \stoptext
>
> or when you want to buse features:
>
> \startluacode
> fonts.handlers.otf.addfeature {
> name = "ccmp", -- or "ebhack"
> type = "substitution",
> nocheck = true,
> data = {
> ["ϵ"] = "ε",
> }
> }
> \stopluacode
>
> % \definefontfeature[default][default][ebhack=yes]
>
> \setupbodyfont[ebgaramond]
>
> \starttext
>
> ϵ ε
>
> \stoptext
>
>
>
>
> -
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
open source > level 1, order 1, name '/usr/local/texlive/2017/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
system >
system > ConTeXt ver: 2017.05.15 21:48 MKIV beta fmt: 2017.12.29 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name '/usr/local/texlive/2017/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
close source> level 2, order 2, name '/usr/local/texlive/2017/texmf-dist/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'test', input './test.mkvi', result 'test'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
interface > macros > processed mkvi file '/home/user/TeX/test.mkvi', delta 0
interface > macros > processed mkvi file '/home/user/TeX/test.mkvi', delta 0
open source > level 2, order 3, name '/home/user/TeX/test.mkvi'
open source > level 3, order 4, name '/usr/local/texlive/2017/texmf-dist/tex/context/fonts/mkiv/type-imp-ebgaramond.mkiv'
close source> level 3, order 4, name '/usr/local/texlive/2017/texmf-dist/tex/context/fonts/mkiv/type-imp-ebgaramond.mkiv'
open source > level 3, order 5, name '/usr/local/texlive/2017/texmf-dist/tex/context/fonts/mkiv/type-imp-dejavu.mkiv'
close source> level 3, order 5, name '/usr/local/texlive/2017/texmf-dist/tex/context/fonts/mkiv/type-imp-dejavu.mkiv'
open source > level 3, order 6, name '/usr/local/texlive/2017/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
close source> level 3, order 6, name '/usr/local/texlive/2017/texmf-dist/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'
backend > xmp > using file '/usr/local/texlive/2017/texmf-dist/tex/context/base/mkiv/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1, subpage 1
close source> level 2, order 6, name '/home/user/TeX/test.mkvi'
close source> level 1, order 6, name '/usr/local/texlive/2017/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
system > structure > start used structure
used structure > text: test
system > structure > stop used structure
system > files > start used files
used file >1: filename=cont-yes.mkiv filetype=tex foundname=/usr/local/texlive/2017/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv usedmethod=database
used file
Re: [NTG-context] How to use fonts.handlers.otf.enhancers.patches?
On 2/26/2018 11:54 PM, Henri Menke wrote:
Dear list,
The EB Garamond font is lacking the ϵ glyph but it contains ε. So naturally you
want to remap ϵ to ε. It cannot be done using font features because the the
slot 0x03B5 (ϵ) is just missing, so substitution will not kick in. I tried
adapting the mechanism to add uppercase greek to Latin Modern Math from lm-
math.lfg. Unfortunately, my code is not working. What am I doing wrong?
Cheers, Henri
---
\startluacode
local patches = fonts.handlers.otf.enhancers.patches
local function patch(data,filename)
local uni_to_ind = data.map.map
if not uni_to_ind[0x3F5] then
patches.report("add ε for ϵ")
uni_to_ind[0x3F5] = uni_to_ind[0x3B5]
end
end
patches.register("after","missing glyphs","^ebgaramond*", patch)
\stopluacode
\setupbodyfont[ebgaramond]
\starttext
ε % = 03B5
ϵ % = 03F5
\stoptext
if you want to use the patch mechanism:
\startluacode
local function patch(data,filename)
data.descriptions[utf.byte("ϵ")] = data.descriptions[utf.byte("ε")]
end
fonts.handlers.otf.enhancers.patches.register("after","missing
glyphs","^ebgaramond*", patch)
\stopluacode
\setupbodyfont[ebgaramond]
\starttext
ϵ ε
\stoptext
or when you want to buse features:
\startluacode
fonts.handlers.otf.addfeature {
name= "ccmp", -- or "ebhack"
type= "substitution",
nocheck = true,
data= {
["ϵ"] = "ε",
}
}
\stopluacode
% \definefontfeature[default][default][ebhack=yes]
\setupbodyfont[ebgaramond]
\starttext
ϵ ε
\stoptext
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] option for printing range
On 2/26/2018 8:02 PM, Pablo Rodriguez wrote: On 02/25/2018 10:51 PM, Hans Hagen wrote: On 2/25/2018 9:12 PM, Pablo Rodriguez wrote: [...] The print range for Acrobat is "3,6,9-11" when it should be "2,5,8-10" (the document only contains 10 pages). is ok here (looking in the pdf file) I have tested the file in Acrobat XI and since I got the same wrong page ranges, I asked to an Adobe engineer. He confirmed that the spec is wrong. Page counting for /PrintPageRange should be zero-based and it shouldn’t start from one. Sorry for this. Could you correct the implementation? the usual pdf spec rubish ... no one uses it (although tex is often first), they it gets a bugged implementation and then the specs change ... one of the reasons why i don't bother too much in implementing the latest pdf gadgets ... i wasted too much time adapting to changed (interpretation of the) specs Hans (I don't officially have the latest spec as i refuse to pay for a pdf specification that could be distributed in pdf format.) - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] synctex file is not compressed
On 2/26/2018 4:53 PM, Ulrike Fischer wrote: I seem to be not able to get a synctex.gz instead of a synctex file. I tried context --synctex=1 file and context --synctex=-1 file but in both cases a simple synctex-file is created. Is this normal? Sure, because - context doesn't use syntex's internal code but uses its own logic - there is no gain in zipping - we have relative small synctex files because we use a different logic the way to enable synctex is in the document (see workflows.pdf): \setupsynctex[state=start] it's a bit pitty that pdf viewers have hard coded syntex file parsing instead of calling a program with coordinates as arguments that starts the editor because that would make a more powerful combo and give room for additional functionality: > mtxrun --script synctex but anyway, i can only test with summatra pdf and it works ok here (last time i checked) a collegue uses synctex with documents that are constructed runtime of thousands of small xml files deeply nested and filesize of the synctex file is neglectable by the size fo the pdf Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
