- ntg-context - Mailing Lists

Intermediate format
by Jan Tosovsky 24 Nov '13

24 Nov '13

Dear All, is it possible to get the complete representation of the layout that is processed in the luatex PDF generator? I mean coordinations of individual text boxes, their dimensions etc. In e.g. XSL-FO processors it is provided in the XML based formats: http://www.renderx.com/reference.html#IntermediateFormatSpecification http://xmlgraphics.apache.org/fop/1.1/intermediate.html Actually, I'd like to retrieve the page number and vertical position of my object with a specific id (reference) to be able to perform PDF post-processing. Is DVI way to go? How can I get it in MkIV? Thanks, Jan

1 0

[***SPAM***] Re: No full Unicode-Support in ConTeXt?
by "H. Özoguz" 24 Nov '13

24 Nov '13

> not at all, as you show way more input here as in the jpeg ... so first > make a minimal example I did gave a min-example, didn't I? The JPG was only to make clear, what I mean with "little signs". Is that clear now? Dont know how to say it better way (sorry my english) :), > also "another font" is not revealing either Of course it is not, yes, sorry. But sometimes I have problems with different fonts (e.g. the letters are not connected), and these problems do not occur in CorelDraw or some other programs. That is, what I meant. (Besides from that, it should be clear that I am a very big fan of ConTeXt and all the way I am talking about it to friends and collegues, so: no attacks at all :)). > the only issue i see is that this otf font has 2048 units and gets > scaled wrong (in luatex's backend probably) The problem is not the scaling (may be too, but not my problem here). Don't you get the following problem in this (your) code? \definefont[arabica][file:uthmantn1ver10.ttf*arabic at 45pt] \definefont[arabicb][file:arabtype.ttf*arabic at 45pt] \starttext \setupalign[r2l] \arabica شَدِيدٌۗ\blank\blank \arabicb شَدِيدٌۗ\par \stoptext Maybe its an issue of my context-version, so see the attachment. With the font "arabtype" everything is fine, with the font "uthmantnver10" the sign is missing. Huseyin

1 0

No full Unicode-Support in ConTeXt?
by "H. Özoguz" 24 Nov '13

24 Nov '13

Hello there, I wonder why working with fonts is soo hard in ConText (much easier in Word or CorelDraw). See this following font (free, opensource): http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10… And try now this Context-Code: \definefont[arabic][file:UthmanTN1Ver10.ttf*arabic at 15pt] \starttext \arabic\setupalign[r2l] مِن قَبْلُ هُدًى لِّلنَّاسِ وَأَنزَلَ ٱلْفُرْقَانَۗ إِنَّ ٱلَّذِينَ كَفَرُوا بِـَٔايَـٰتِ ٱللَّهِ لَهُمْ عَذَابٌ شَدِيدٌۗ وَٱللَّهُ عَزِيزٌ ذُو ٱنتِقَامٍ \stoptext You see, this little signs above the letters are vanished in the PDF. But they are set in CoreDraw (for example). Why, what is the problem? Similar problems you can see with another font, no problem in CorelDraw, but problems in ConText. Hope for help. Thank you very much. Huseyin

3 6

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

24 Nov '13

> The extend feature stretches the glyphs to get narrow or wide font but it doesn’t embolden it. > > The best solution is to get a font with a real bold style, money shouldn’t be a problem because fonts are cheap nowadays. > > Wolfgang Thanks, I hoped the it could really embold ist (like I did it in CorelDraw). Of course, money is not the problem at all - I am using it commercially, so the company should by any arabic font I would suggest. But it is very hard to find an modern font, which is capable of typsetting Quran, with full supprt and all special symbols (wich are not a part of standard modern arabic) - and more hard to find such a find in this style (Uthmanic). Huseyin

2 1

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] > > \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. ++++++++++++++++ \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

[***SPAM***] Re: No full Unicode-Support in ConTeXt?
by "H. Özoguz" 24 Nov '13

24 Nov '13

To be more concrete, I added an jpeg from CorelDraw, which shows, what I mean with these "little signs" above the letters. They are vanished in ConText, but are correctly set in CorelDraw with the very same font. Huseyin

1 0

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

Eliminating orphans/widows when grid is on
by Jan Tosovsky 23 Nov '13

23 Nov '13

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? Thanks, Jan

1 0

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 23 Nov '13

23 Nov '13

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' normally linespacing in the toc is the same as in the rest of the document unless one has assigned to before/after -- ----------------------------------------------------------------- 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 Jan Tosovsky 23 Nov '13

23 Nov '13

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. Regards, Jan

1 0

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 23 Nov '13

23 Nov '13

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... >>> >>> I've 'invented' this: >>> >>> \setupcombinedlist[content][list=chapter, alternative=c] >>> >>> \starttext >>> >>> \title{Table of Contents} >>> \setupinterlinespace[line=0.8ex] % too small, just for testing >>> \placecontent >>> \setupinterlinespace[line=2.75ex] >>> %\setupinterlinespace[reset] >>> >>> \startfrontmatter >>> \chapter{Intro}text >>> >>> text >>> >>> text >>> \startfrontmatter >>> \startbodymatter >>> \chapter{Chapter}text >>> \stopbodymatter >>> \startbackmatter >>> \chapter{Appendix}text >>> \stopbackmatter >>> \stoptext >>> >>> I cannot use simply the \completecontent command as the linespacing >>> is effective already between the title and the first entry line... >>> so I am splitting the title and the rest and set the linespacing >>> just before list rendering. Finally I am resetting the value manually. >>> >>> Are there better ways to tweak linespacing in TOC ? >> >> \title{Table of Contents} >> >> \start >> \setupinterlinespace[line=0.8ex] % too small, just for testing >> \placecontent >> \stop > > Thanks for the hint. > > 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 precedes a line without > ascenders > \chapter{pppppppp}. % line with descenders is followed with a line with > ascenders > \chapter{ŠŠŠŠŠŠŠŠ}. % the result is an inconsistent baseline distance > \stoptext > > Is there any remedy for this? Can I fix the baseline distance somehow? > > I have such cases in my TOC :-( > (but not so extreme as here) \definegridsnapping[crap] [fit,0.2] \setuplayout[grid=crap] but if you really need that kind of tweaks you might consider using a better font: if interlinespace is too small you will never get nice results you can try to play with the h/d ratio: \setupinterlinespace[line=2.8ex,height=0.8,depth=0.2] \showstruts \strut x \setupinterlinespace[line=2.8ex,height=0.7,depth=0.3] \showstruts \strut x or you can plug in a command (in the toc handler) that puts each line in a box with manipulated dimensions 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

Paragraph - the last line handling
by Jan Tosovsky 22 Nov '13

22 Nov '13

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? Thanks, Jan

1 0

Re: [NTG-context] Linespacing in TOC
by Hans Hagen 22 Nov '13

22 Nov '13

On 11/19/2013 11:48 PM, Jan Tosovsky wrote: > Dear All, > > I'd like to tweak a default TOC linespacing... > > I've 'invented' this: > > \setupcombinedlist[content][list=chapter, alternative=c] > > \starttext > > \title{Table of Contents} > \setupinterlinespace[line=0.8ex] % too small, just for testing > \placecontent > \setupinterlinespace[line=2.75ex] > %\setupinterlinespace[reset] > > \startfrontmatter > \chapter{Intro}text > > text > > text > \startfrontmatter > \startbodymatter > \chapter{Chapter}text > \stopbodymatter > \startbackmatter > \chapter{Appendix}text > \stopbackmatter > \stoptext > > I cannot use simply the \completecontent command as the linespacing is > effective already between the title and the first entry line... so I am > splitting the title and the rest and set the linespacing just before list > rendering. Finally I am resetting the value manually. The 'reset' keyword > seems to be somehow ignored... > > Are there better ways to tweak linespacing in TOC ? \title{Table of Contents} \start \setupinterlinespace[line=0.8ex] % too small, just for testing \placecontent \stop ----------------------------------------------------------------- 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

Footnote line position
by Jan Tosovsky 22 Nov '13

22 Nov '13

Dear All, when a single line footnote is used, the footnote divider is rendered in larger distance than for footnotes with two or more lines (I mean a gap between the line and the footnote text). Initially I though there must be an 'empty' paragraph in my footnote but looking into the source it turned out to be a false alarm as it seems to be consistent. It can be tested easily: \chapter{Chapter}Foo\footnote{Bar}. \chapter{Chapter}Foo\footnote{Bar Bar}. Is this behaviour deliberate? Thanks, Jan ConTeXt 2013.11.14 & Win 7

1 0

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

22 Nov '13

Thank you Wolfgang, it does what I want. However, I realised after trying the following code inside environments (frontmatter, bodymatter, backmatter and appendices) that the default behaviour is WRONG because the conversions of prefixes are not always automatic. For instance, in the appendix environment, by default chapter numbers are Characters and every prefix representing a chapter number is also a Character (section prefixes, caption prefixes and so on). Now if you decide to switch chapter numbers to Romannumerals, you will get something totally inconsistent if you don’t do many conversions manually: *\startsectionblockenvironment[appendix]* * \defineconversionset[romannumeralsconversionset][][R]* * \setuphead[chapter][sectionconversionset=romannumeralsconversionset]* *\stopsectionblockenvironment* *\starttext* *\startappendices* *\chapter{Cool}* *\placefigure{A cow}{\externalfigure[cow]}* *\chapter{Cat}* *\section{Mouse}* *\section{Dog}* *\placefigure{A cow}{\externalfigure[cow]}* *\stopappendices* *\stoptext* which gives: *I Cool* *[figure] Figure I.I Cow % <-- Here the prefix conversion from 'A' to 'I' works.* *II Cat* *B.1 Mouse % <-- Here the prefix conversion from 'B' to 'II' does NOT work.* *B.2 Dog % <-- Here the prefix conversion from 'B' to 'II' does NOT work.* *[figure] Figure B.II Cow % <-- Here the prefix conversion from 'B' to 'II' does NOT work (because of the presence of the 2 sections B.1 and B.2 where the prefix conversion already did not work I think, so here is the BUG).* Extra: is it normal that caption NUMBERS (not prefixes) are converted to Romannumerals by default INSIDE the appendix environment (outside they are usual numbers)? ('Figure I.I Cow' and 'Figure B.II Cow' instead of 'Figure A.1 Cow' and 'Figure B.2 Cow'.)

2 1

Re: [NTG-context] Problem with urls.
by Robert Blackstone 22 Nov '13

22 Nov '13

On 21 Nov 2013, at 19:53 , Wolfgang Schuster <schuster.wolfgang(a)gmail.com> wrotr >> > > I can process your example without problems. > > ConTeXt ver: 2013.11.16 12:43 MKIV beta fmt: 2013.11.21 int: english/english > > Wolfgang Thank you for your reaction. This is odd. Here this EM does not work with CONTEXT version 2013.11.14 23:22, (which uses LuaTeX version 0.76.0 as engine.) (to get this information I had of course to outcomment the "\from[apurl]") Still stranger: when I plugged the url into some other TeX-file it did work with the same ConTeXt version. So it seems that there is some essential difference between these files (apart from their content) Do you have any idea what that could be? Could it be a matter of text encoding? (I use TeXShop as the front end.) Best regards, Robert Blackstone

2 1