November 2013 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Palatino patch for the current ConTeXt version
by Hans Hagen 27 Nov '13

27 Nov '13

On 11/17/2013 12:23 PM, honyk wrote: > Hello Everyone, > > I am trying to fix a Palatino small caps issue using the procedure explained > here: > http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV > > That fix seems to be obsolete nowadays and returning errors. > > I've changed > fonts.otf.enhancers.patches["^pala"] > to > fonts.handlers.otf.enhancers.patches["^pala"] > which compiles, but it does nothing. > > I've also tried this variant, but that 'patch' function is never called even > though I clear my font cache every run: > > \startluacode > local fonts = fonts > local otf = fonts.handlers.otf > local patches = otf.enhancers.patches > local register = patches.register > local report = patches.report > > function patch (data,filename) > report("I am here") > report("processing data %s", table.serialize(data)) > end > > register("after","prepare glyphs","^pala", patch) > \stopluacode > > > Any idea? patches are applied when a font is cached so you need to wipe the cache after defining such a patch there are several ways to apply patches runtime, see *.lfg files (and also fonts-mkiv.pdf) Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Re: [NTG-context] PDF bookmarks - incorrect titles for registers
by Hans Hagen 26 Nov '13

26 Nov '13

On 11/26/2013 8:03 PM, Jan Tosovsky wrote: > On 2013-11-18 Jan Tosovsky wrote: >> >> when I specify custom titles for my registers, they are ignored in >> bookmarks: >> >> \setupinteraction[state=start] >> \placebookmarks[chapter] >> \setupinteractionscreen[option=bookmark] >> >> \defineregister[indexname][indexnames] >> \defineregister[indexsubject][indexsubjects] >> \setupheadtext[indexname=Name Index] >> \setupheadtext[indexsubject=Subject Index] >> >> \starttext >> \completecontent >> \chapter{Chapter}text\indexname{primary}\indexsubject{primary} >> \startbackmatter >> \completeindexname >> \completeindexsubject >> \stopbackmatter >> \stoptext >> >> Is it necessary to switch something else on? > > According to the proposed solution at > http://tracker.luatex.org/view.php?id=865 > > it can be switched on using this magic formula > \enabledirectives[references.bookmarks.preroll] > > What is the correct usage of this? And are there any details why it is > required and what exactly it does? by default the title is set to a label which is not expandable the directive will convert the typeset title into a bookmark > When it is added to the beginning of my example, it returns an error: > attempt to call field 'boxtostring' (a nil value) ah, only in my experimental tree, i'll add it to the beta > But to be honest, I'd expect setting this flag internally by default as I > cannot imagine any use case where the index ID should be preferred in favor > of the title... as titles can be anything and bookmarks are limited, we need to have some protection in place ... unexpandable macros are simply dropped so \labeltext{index} becomes index Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 2

Re: [NTG-context] PDF bookmarks - incorrect titles for registers
by Hans Hagen 26 Nov '13

26 Nov '13

On 11/26/2013 8:30 PM, Jan Tosovsky wrote: > Thanks for this detailed explanation. If I understand correctly, this switch > is intentional and won't be applied automatically even for registers or > other peculiar cases where title is specified differently/unexpectedly. the bookmark setting defaults to the title itself but you can always set a bookmark title explicitly with bookmark= >>> When it is added to the beginning of my example, it returns an error: >>> attempt to call field 'boxtostring' (a nil value) >> >> ah, only in my experimental tree, i'll add it to the beta > > Thanks, but this one is not so urgent. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Re: [NTG-context] Eliminating orpans in the Index
by Jan Tosovsky 26 Nov '13

26 Nov '13

On 2013-11-23 Jan Tosovsky wrote: > > in my two-column index there are several cases when the last > entry in the given letter group overflows to the next column/page. > In the extreme case it is just the last page reference. > ... > Additionaly, columns are not balanced properly in all cases. When the > first is longer, it is not a big problem. But the opposite case > looks weird. As the registers are rendered programatically, I cannot intervene into this process. But can I influence it e.g. using 'processors' applied to problematic index entries? Processors can be used for setting the font-weight or color of particular entry. Can the same method used for manual setting of 'keep-with-previous/next' ? Thanks, Jan

1 0

Re: [NTG-context] PDF bookmarks - incorrect titles for registers
by Jan Tosovsky 26 Nov '13

26 Nov '13

On 2013-11-18 Jan Tosovsky wrote: > > when I specify custom titles for my registers, they are ignored in > bookmarks: > > \setupinteraction[state=start] > \placebookmarks[chapter] > \setupinteractionscreen[option=bookmark] > > \defineregister[indexname][indexnames] > \defineregister[indexsubject][indexsubjects] > \setupheadtext[indexname=Name Index] > \setupheadtext[indexsubject=Subject Index] > > \starttext > \completecontent > \chapter{Chapter}text\indexname{primary}\indexsubject{primary} > \startbackmatter > \completeindexname > \completeindexsubject > \stopbackmatter > \stoptext > > Is it necessary to switch something else on? According to the proposed solution at http://tracker.luatex.org/view.php?id=865 it can be switched on using this magic formula \enabledirectives[references.bookmarks.preroll] What is the correct usage of this? And are there any details why it is required and what exactly it does? When it is added to the beginning of my example, it returns an error: attempt to call field 'boxtostring' (a nil value) But to be honest, I'd expect setting this flag internally by default as I cannot imagine any use case where the index ID should be preferred in favor of the title... Jan

1 0

Automatic adjusting the font size to fill the text-area
by "H. Özoguz" 26 Nov '13

26 Nov '13

Hello there, in my actual book there is one special condition: It is already clear which paragraphs of the text have to be set on page 1, which on page 2 etc.pp. (a nearly 700 pages-project). So there are no page-breaks within a paragraph, no overruns are allowed. But now the question: The text for each page has not always the same length. So on some pages there might be many empty space at the buttom, while on others the textarea is completely filled. At the beginning I have to set an font-size - so I have to set it, such that the longest text fits into the text area on its page. But of course, many other pages maye filled only 60%. (That is the spectrum of the text-lengths in this project). So one direct solution is clear (if one wants to have filled or nearly-filled pages, and I want this): I can change the font-size for every single page. But which size? It is a experiment, so I have to try 10pt, then compile, then 10.8pt .... ok, was too much, got an page-overrun .... lets try 10.4pt ..... and this for every single of the 700 pages. That is possible of course, and if there is no other way, this will be my approach. So: Is there some trick or way for automatically find the best (biggest) font-size (up to some precision, maybe one digit after decimal point in pt), s.t. the text produces no overrun (no page-brake)? I guess no, because ConTeXt had to run the compiling several times or so ... but better to ask and then to begin with the exhausting work. Thanks. Huseyin

1 0

Re: [NTG-context] Calculating with variables
by "H. Özoguz" 26 Nov '13

26 Nov '13

> which is why the next is better: > > \definemeasure[fontsize:big] [17pt] > \definemeasure[fontsize:small][0.7\measured{fontsize:big}] > > \definefont[big] [name:arial at \measure{fontsize:big}] > \definefont[small][name:arial at \measure{fontsize:small}] > > \starttext > \big Dies ist ein großer Text. \blank > \small Dies ist ein kleiner Text. > \stoptext > > Best wikify this! > > Alternatively you can set up symbolic sizes (like we already have a b c > d), so that > > \definefont[big] [name:arial sa a] > > etc can be used > > Hans Thank you! I will wikify it, hopefully in the next days. Huseyin

1 0

Calculating with variables
by "H. Özoguz" 26 Nov '13

26 Nov '13

Hello there, I am new in variables in ConTeXt, so I tried the the following example of two font-sizes wich should have a ratio of 0.7: \setvariables[fontsize][bigsize=17pt] \setvariables[fontsize][smallsize=0.7\getvariable{fontsize}{size}] \definefont[big][name:arial at \getvariable{fontsize}{bigsize}] \definefont[small][name:arial at \getvariable{fontsize}{smallsize}] \starttext \big Dies ist ein großer Text.\blank \small Dies ist ein kleiner Text. \stoptext That does not work, what is the correct syntax? [Second question about this will be much more involving I think ... :), but I will give it his own thread]. Thanks. Huseyin

2 1

Re: [NTG-context] Converting normal font into bold
by "H. Özoguz" 26 Nov '13

26 Nov '13

> > >>/ May be ConTeXt experts would have better suggestions, till then you > />>/ may want to look at the fake bold option in simplefonts - > />>/ http://wiki.contextgarden.net/Simplefonts#Faking_italics_and_bold_fonts > />/ > />/ Thanks for your advice. > />/ Unfortunately I did not manish to work with this font by simplefonts. I use the following simple setup: > />/ > />/ > />/ \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] > / > \definefontfeature[fakebold][extend=1.1] > > \definefont[arabic][file:<fontname>*arabic,fakebold at 15pt] > > >/ \starttext > />/ \arabic\setupalign[r2l] ??????? ??? ???????? ?????? ???? ???????? ??????????? > />/ \stoptext > />/ > />/ How can I get these "fake bolds" with this setup? Or is it absolutely necessary to use Simplefont for these fake-bolds? > / > The feature is unrelated to simplefonts. > > Wolfgang Thanks Wolfgang, but that does not seem to work with this font. See attachment, the font is wider, but not bold. See the difference to the intended result, achieved with Corel Draw (with the same font), see attachment. In ConTeXt I had the following code (see attachment for the compiled pdf): ++++++++++++++++ \definefont[arabic][file:bliblablup_0.ttf*arabic at 15pt] \definefont[arabics][file:bliblablup_0.ttf*arabic at 15pt] \definefontfeature[fakebold][extend=1.2] \definefont[arabic][file:bliblablup_0.ttf*arabic,fakebold at 15pt] \starttext \arabic\setupalign[r2l] ??????? ??? ???????? ?????? ???? ???????? ??????????? \blank\arabics\setupalign[r2l] ??????? ??? ???????? ?????? ???? ???????? ??????????? \stoptext ++++++++++++++++ Huseyin

2 1

pstrics module again
by DesdeChaves 26 Nov '13

26 Nov '13

Dear sirs The pstrics module don't work anymore. I tried to run this simple code but I found a lot of errors. \usemodule[pstric] \starttext \startPSTRICKS \pspicture(0,0)(20,20) \psline(0,0)(20,20) \psline(1,1)(10,10) \endpspicture \stopPSTRICKS \stoptext This module is no longer supported? There is still any hope of being able to use pstric and some of its extensions (pst-spectra, for example)? Thanks a lot Sorry for my persistence about pstrics module. Thanks a lot Jorge

3 9