- ntg-context - Mailing Lists

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

24 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] \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? Thanks. Huseyin

2 1

[OT] − RobotoSlab Italics… or not
by Renaud Aubin 24 Nov '13

24 Nov '13

Hi folks, I'm working on a Roboto typescript and starting from the work done by Zen Lima back in last July, I would like to push things further. Since I work on some Android projects and use Google Keep mostly on a daily basis, I was surprised to not find italics for the RobotoSlab (either on the web or by extracting the assets of the Keep package). Why am I surprised: Keep do have serif title placeholders for the new note EditText and I see it everyday! $ mtxrun --script font --list --all --pattern=robotoslab robotoslab robotoslabbold RobotoSlab-Bold.ttf robotoslabbold robotoslabbold RobotoSlab-Bold.ttf robotoslablight robotoslablight RobotoSlab-Light.ttf robotoslabregular robotoslabregular RobotoSlab-Regular.ttf robotoslabthin robotoslabthin RobotoSlab-Thin.ttf OK, RobotoSlab fonts are accessible and I have a working typescript to use RobotoSlab with ConTeXt MkIV (I'll made the git repo public soon). At first, my thoughts are: nevermind the Slab italics but now, I'm curious since Inkscape, LibreOffice, … propose the italic and bolditalic features of the RobotoSlab (check out the attached font-manager screenshot). I've worked with different kind of fonts'family (more or less complete) and used and modified many typescripts in my ConTeXter's life but there I should be missing something obvious. Where are the RobotoSlab Italics??? My experience is that italic and bolditalic should correspond to files… First guess: no files so the RobotoSlab Italic and BoldItalic features are just faked ones composed by my GNU/Linux Debian system. No, I must be wrong here too… Any thoughts on "The Quest of the Hidden Italics of the RobotoSlab fonts!"? Best Regards, Renaud

3 5

Converting normal font into bold
by "H. Özoguz" 24 Nov '13

24 Nov '13

Hello together, I have an arabic font, which is quite perfect, but only a little bit too thin, so that it seems to "vanish" into the white of the paper. Unfortunately this font does not come with an bold-variant. Now I tried to manipulate it with CorelDraw, just converted into curves and added an contour (verys small 0.13pt, while font was 11pt) - and it worked! This "aritificial bold-font" works very well, better then I hoped, no problems - although it is no hand-tundes bold, but only countour-adding. Now the question: I obviously cant set the entire book (more than 600 pages) with Corel-Draw, and want too use ConText, of course. So is there a way to produce this boldness out of this too thin font within ConText, too? Thank your very much. Best regards, Huseyin

2 1

Simplefonts (new) fallback issue with Linux Libertine O
by Rik 24 Nov '13

24 Nov '13

Fallbacks (at least the range I tested) do not work with the roman face of Linux Libertine O in the new (core) simplefonts implementation. I first thought that this might be a Libertine issue, but further testing makes me suspect it may be a simplefonts issue. Or perhaps I have used the wrong syntax with the new implementation. Below are two MWEs, one based on the current standalone (current version: 2013.11.16 12:43), running on Windows 8.1 with the win64 bins, and the second based on an up-to-date TL13 (ConTeXt ver: 2013.05.28 00:36 MKIV) on the same system. Linux Libertine O is version When I run the standalone version, the fallback characters do not appear between the first angles, but do appear between the bf and it angles. They appear between angles in all cases with the TL13 MWE. I do not see the problem with my home-grown typescript for Libertine under either TL13 or the current standalone. I do not see the problem with Junicode, Gentium Book Basic, or Gentium Basic. I have not yet tried other fonts. Standalone MWE: \definefallbackfamily [libertine] [serif] [Gentium Plus] [range={0x02052-0x02058},force=yes] \definefontfamily [libertine] [serif] [Linux Libertine O] \setupbodyfont [libertine] \def\SDQP{⁓⁗}% Swung Dash Quad Prime U02053U02057 \starttext >\SDQP< >{\bf \SDQP}< >{\it \SDQP}< >{\bf{\it \SDQP}}< \stoptext TL13 MWE: \setupbodyfontenvironment [default][em=italic] \usemodule [simplefonts] \setmainfontfallback [Gentium Plus] [range={0x02052-0x02058},force=yes] \setmainfont [Linux Libertine O] \def\SDQP{⁓⁗}% Swung Dash Quad Prime U02053U02057 \starttext >\SDQP< >{\bf \SDQP}< >{\it \SDQP}< >{\bf{\it \SDQP}}< \stoptext -- Rik Kabel

2 2

Re: [NTG-context] Numberconversion problem in caption prefixes
by Géry Ogam 23 Nov '13

23 Nov '13

Thanks again Wolfgang, with this setup everything is fine. But I wanted to bring to the attention of Hans the inconsistency of the prefix conversions by defaut, so that he can correct them: I A chapter [a figure] Figure I.1 % <-- Here the conversion of the prefix to Romannumerals is done AUTOMATICALLY. 1.1 A section [a figure] Figure 1.2 % <-- Here the conversion of the prefix to Romannumerals is NOT done AUTOMATICALLY (the presence of a section before seems to DISCARD THE AUTOMATIC CONVERSION). Nor in the prefix of the section. Code: \setuphead[chapter][conversion=Romannumerals] \starttext \chapter{A chapter} \placefigure{}{\externalfigure} \section{A section} \placefigure{}{\externalfigure} \stoptext Every prefix should be AUTOMATICALLY converted, not half of them. Hans, could you please correct that in the next betas? Best regards.

1 0

[***SPAM***] Eliminating orpans in the Index
by Jan Tosovsky 23 Nov '13

23 Nov '13

Hello Everyone, 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. Can I somehow prevent this? E.g. keep at least two/three index entries together when the overflowing is triggered? And always keep all the page references together? 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. Can I influence this behaviour? Thanks, Jan PS: Grid is not activated.

1 0

Re: [NTG-context] Index entries - custom font size
by Jan Tosovsky 23 Nov '13

23 Nov '13

On 2013-11-16 Jan Tosovsky wrote: > there are lot of index entries in my document and with the standard > body font size they occupy too much space. I've tried to decrease > the size by the textstyle parameter. It works, but it is applied > recursively to every nested level: secondary items are smaller twice > and tertiary items three times... > > \setupregister[index][command=\Word, textstyle=small] > \starttext > \index{primary}\index{primary+secondary}\index{primary+secondary+tertia > ry}Text > \completeindex > \stoptext > The following code switches the font size for all the index content. Even for group titles (letters), but it is beneficial here. The index title is split to keep the original size. \startbackmatter \chapter{Index} \start \switchtobodyfont[8pt] \placeindex \stop \stopbackmatter Jan

1 0

Re: [NTG-context] Paragraph - the last line handling
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/22/2013 11:07 PM, Jan Tosovsky wrote: > Hello Everyone, > > in my document there are lot of cases when the last line in the paragraph > has a very narrow gap on the right (case 1 below). I understand it is > sometimes difficult to squeeze characters to the desired lenght (case 2) > without any impact to the final quality, but this looks very unnatural now > (besides all other lines, which are nicely typeset keeping the optical edge > on the right). > > Is it possible to somehow define that under a certain limit the line will be > expanded to the end (case 3)? > > xxxxxxxxxxxx (1) > xxxxxxxxxxxxxx > xxxxxxxxxxxxx > xxxxxxxxxxxx (2) > xxxxxxxxxxxxxx > xxxxxxxxxxxx > xxxxxxxxxxxx (3) > xxxxxxxxxxxxxx > xxxxxxxxxxxxxx > > I use the following setup now: > > \setupalign[hz, hanging] > \setuptolerance[verystrict] % even 'strict' doesn't help here > \setupindenting[medium, yes] > > Any idea? \hsize 15.4cm \input tufte \parfillskip30pt plus 1 fill \input tufte ----------------------------------------------------------------- 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] Linespacing in TOC
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/23/2013 1:44 PM, Jan Tosovsky wrote: > On 2013-11-23 Hans Hagen wrote: >> On 11/23/2013 12:16 PM, Jan Tosovsky wrote: >>> On 2013-11-23 Jan Tosovsky wrote: >>>> On 2013-11-22 Hans Hagen wrote: >>>>> On 11/22/2013 9:44 PM, Jan Tosovsky wrote: >>>>>> On 2013-11-20 Hans Hagen wrote: >>>>>>> On 11/19/2013 11:48 PM, Jan Tosovsky wrote: >>>>>>>> >>>>>>>> I'd like to tweak a default TOC linespacing... >>>>>>>> >>>>>>> \title{Table of Contents} >>>>>>> >>>>>>> \start >>>>>>> \setupinterlinespace[line=0.8ex] >>>>>>> \placecontent >>>>>>> \stop >>>>>> >>>>>> But as I found, any value below 2.8ex causes interline >>>>>> inconsistencies when >>>>>> special cases appears, see the extreme below: >>>>>> >>>>>> \starttext >>>>>> \start >>>>>> \setupinterlinespace[line=1.0ex] >>>>>> \placecontent >>>>>> \stop >>>>>> \chapter{aaaaaaaa}. % line without descenders >>>>>> \chapter{pppppppp}. % line with descenders >>>>>> \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline >>>>>> \stoptext >>>>>> >>>>>> Is there any remedy for this? Can I fix the baseline distance >>>>>> somehow? >>>>>> >>>>> >>>>> \definegridsnapping[crap] [fit,0.2] >>>>> \setuplayout[grid=crap] >>>> >>>> This helps! But... it breaks something else :-( >>> >>> I've finally found an acceptable solution. >>> >>> During my tests I found a crucial difference between: >>> >>> \setupinterlinespace[line=2.0ex] >>> >>> and >>> >>> \setupinterlinespace[0.25] >>> >>> The latter sets the baseline distance correctly even without that >>> problematic snapping to the grid! >>> >>>> All lines in my book have a certain (default) linespacing. >>>> TOC entries are rendered (by default) using bigger linespacing. >>> >>> Btw, is there any option to override a default (huge) TOC >> linespacing? I >>> still consider my solution rather a hack. >> >> just set 'before' and 'after' > > Ok. I haven't realize that. > >> normally linespacing in the toc is the same as in the rest of the >> document unless one has assigned to before/after > > This example shows different behaviour: > > \showgrid > \starttext > \start > \placecontent > \stop > \chapter{aaaaaaaa}Foo > > Bar > \chapter{pppppppp}. > \chapter{ŠŠŠŠŠŠŠŠ}. > \stoptext > > On my computer the TOC linespacing is almost twice as big as that in the > paragraph. if the grid is on that can indeed be the case but only if there are lines with > lineheight so that's why you can use less strict options (older mails) 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] Eliminating orphans/widows when grid is on
by Hans Hagen 23 Nov '13

23 Nov '13

On 11/23/2013 1:49 PM, Jan Tosovsky wrote: > Dear All, > > when the grid is switched on in my document, there are lots of orphan and > widows in the output. > > \setuplayout[grid=yes] % grid=tolerant doesn't help > > According to the manual the grid typesetting is a solely ConTeXt feature not > available in the core TEX. Is it production ready? Are there any options to > handle o/w correctly? indeed no core tex but context specific ... and work in progress but the fundamentals will not change, only more options / control / better heuristics might show up (also as side effect of opening up tex more) (usually i spend time on such things when i need it myself or in projects) 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