- ntg-context - Mailing Lists

Tagging and startitemize[columns]
by Christoph Reller 22 Mar '16

22 Mar '16

Hi, Stil ConTeXt is the only TeX-based typesetting system that can produce tagged PDF - this is a unique feature, thank you Hans! I have, however, found that the following MWE produces wrongly nested tagging information. Specifically: - The itemization with columns (\startitemize[columns]) is not contained in an "itemgroup" - The second itemization (without columns) is tagged outside of the "sectioncontent" (Maybe the second issue is a consequence of the first.) I am afraid but this might be a bug. Thank you for any feedback. Cheers, Christoph MWE: \setuptagging[state=start] \starttext \startsectionlevel[title=Chapter] Text. \startitemize[columns] \item A \item B \stopitemize \startitemize \item A \item B \stopitemize More Text. \stopsectionlevel \stoptext

2 1

Re: [NTG-context] Protrusion cancellation by index term
by Hans Hagen 21 Mar '16

21 Mar '16

On 2/22/2014 2:38 PM, Jan Tosovsky wrote: > On 2014-02-22 Jan Tosovsky wrote: >> >> when a punctuated phrase appears at the beginning of the line, it is >> not protruded correctly when preceded by an index term. >> >> ... \index{foo}>Bar< ... >> >> A minimal example is available at >> http://drifted.in/other/sample.tex >> >> I cannot place the space character between these two parts (which >> helps) as I sometimes need to join this and the previous phrase with >> the non-breaking space. >> > > It is more serious issue than expected. Consider next two variants: > > (1) sentence, \index{primary}>Primary< > (2) sentence,\index{primary} >Primary< > > When the line is broken after a comma: > ad 1) starting guillemet is not protruded > ad 2) ending comma is not protruded > > When \index is surrounded by spaces from both sides, the space is rendered > at the beginning of the next line (resulting in 'indenting'). > > :-S > > I'd be grateful for ignoring any non document content preceding punctuation > to avoid its influence on protrusion. well, think of it like this: [something]<text>[something else] with [something] being bound to < ... so that is then the boundary of the word, not < ... i might know a solution (but such -major- changes have to fit into my schedule) 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

Length range control of the last line of paragraph
by Jan Tosovsky 21 Mar '16

21 Mar '16

Dear All, when paragraphs are separated by indenting the first line (instead of an empty line), these rules should be followed: (1) the last line lenght is greater than the left indent xxxxxxxxxxxxxxxx xxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxxx (2) the last line is shorter than block width xxxxxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxxx (ad 1) Some suggestions can be found in http://tex.stackexchange.com/questions/28357/ensure-minimal-length-of-last-l ine - but to be honest, it is not very clear to me how to apply it and even combine with (2) (ad 2) This can be done using \parfillskip XXpt plus 1fil (where XX is required gap) I'd be grateful for any command which would set this globally for all paragraphs. Partly requested here http://tracker.luatex.org/view.php?id=885 One could set (a) minimum length - default=2*indent (b) minimum gap - default=indent (c) minimum block width where (a) and (b) are still to be applied - default=2*a+b (ad c) if there are narrower blocks within the document (e.g. blockquotes), we should still have some room for typesetting the last line content. If the area width is insufficient, the last line would be typeset without these (a+b) restrictions. In meantime, any suggestion how to combine a+b manually are welcome. Thanks, Jan

1 0

placelist not working in latest beta
by Schmitz Thomas A. 21 Mar '16

21 Mar '16

Hi all, example attached with output from latest beta and an older one. The \placelist command appears to have changed recently; the older beta I tested is from November, but this used to work in February as well, the change must be recent. Thanks a lot Thomas \definelist[MyTopics][criterium=all] \def\MyMark{} \def\Topic% {\dosingleargument\doTopic} \def\doTopic[#1]{% \gdef\MyMark{#1}% \writetolist[MyTopics][location=none]{#1}{}} \define[3]\FancyEntry{% \doifelse{\rawstructurelistfirst}{\MyMark}% {\quad\color[red]{#1}\quad} {\quad #1\quad}} \setuplist[MyTopics] [pagenumber=no, alternative=command, command=\FancyEntry] \setupfootertexts [{\switchtobodyfont[8pt]\quad{\placelist[MyTopics]}}] \starttext \Topic[First] \contextversion First Topic \page \Topic[Second] Second Topic \page \Topic[Third] Third Topic \stoptext

2 2

Controlling table split in natural tables
by Mari Voipio 21 Mar '16

21 Mar '16

Hello all! I have a natural table that is too large to fit into one page, so it is split. Unfortunately it now splits between rows 28 and 29 that I'd like to keep together. I want the table to split between rows 27 and 28. Is this possible? I couldn't find anything on the wiki nor the mailing list archives... Thanks, Mari

2 2

Sebastian Rathz
by luigi scarso 18 Mar '16

18 Mar '16

http://www.gust.org.pl/r.i.p.-sebastian-rathz-en -- luigi

2 1

What is wrong with PocketDiary module?
by DesdeChaves 18 Mar '16

18 Mar '16

PocketDiary module don't works anymore with the actual Context version. What is wrong? Why this module isn't more supported? Thanks Jorge context PocketDiary.tex mtx-context | run 1: luatex --fmt="/Applications/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en" --jobname="PocketDiary" --lua="/Applications/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui" --no-parse-first-line --c:currentrun=1 --c:fulljobname="./PocketDiary.tex" --c:input="./PocketDiary.tex" --c:kindofrun=1 --c:maxnofruns=9 "cont-yes.mkiv" This is LuaTeX, Version beta-0.89.4 (TeX Live 2016/dev) system commands enabled. open source > 1 > 1 > /Applications/context/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv ConTeXt ver: 2016.03.13 23:40 MKIV beta fmt: 2016.3.14 int: english/english system > 'cont-new.mkiv' loaded open source > 2 > 2 > /Applications/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv close source > 2 > 2 > /Applications/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv system > files > jobname 'PocketDiary', input './PocketDiary', result 'PocketDiary' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > 2 > 3 > /Users/jorgem/Desktop/t-scancsv_ConTeXt_module/PocketDiary.tex resolvers > modules > 'pocketdiary' is loaded open source > 3 > 4 > t-pocketdiary.tex resolvers > lua > loading file 't-calendar.lua' succeeded loading > ConTeXt User Module / PocketDiary open source > 4 > 5 > /Applications/context/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv close source > 4 > 5 > /Applications/context/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv fonts > symbols > library 'mvs' loaded colors > 'rgb' color space is supported colors > 'cmyk' color space is supported close source > 3 > 5 > t-pocketdiary.tex fonts > typescripts > unknown library 'seravek' fonts > typescripts > unknown library 'Seravek' fonts > preloading latin modern fonts (third stage) fonts > 'fallback modern-designsize ss 9pt' is loaded system > '1.1' arranged at '1' tex error > tex error on line 147 in file virtual://buffer.Week.2: ! You can't use `\prevdepth' in restricted horizontal mode \nointerlineskip ->\prevdepth -\thousandpoint \tabl_ntb_row_align_stop_inject ...ointerlineskip \ifenableTBLbreak \tabl_nt... \tabl_ntb_flush_content ...table \the \t_tabl_ntb \dostoptagged \tabl_ntb_table_stop ...g \tabl_ntb_flush_content }\ifcase \tabl_ntb_get_gal... \eTABLE ...oveunwantedspaces \tabl_ntb_table_stop \stopTBLprocessing \fi \po... l.147 \eTABLE ... l.12 ...ary}{Week}}{\getvariable{PocketDiary}{Year}} <empty file>

2 1

subsentences
by Alan BRASLAU 17 Mar '16

17 Mar '16

One can obtain language-dependent marking for sub-sentences through the use of |<| this is an aside |>| or through the command \startsubsentence ... \stopsubsentence or the (depreciated?) \subsentence{...}. I have several questions, and the source code appears to hold traces of previous long discussions on this topic. 1. \stopsubsentence at the end of a sentence is rather funny. I suppose in this case one can use an unbalanced |<| (but it would be ideally better if \stopsubsentence could detect the end of the sentence, generally: . ! ?). 2. I have been told that some editors want the emdash surrounded by spaces and others insist that it appear without spaces. So, for English at least, there are several schools, and they can be quite insistent. Can this be setup though a parameter or do we believe that the rules only depend on language? Furthermore, do the commands add or gobble-up extra spaces in the text source? Alan

1 0

Howto use the lua io.read() function only in the first context run?
by Romain Diss 17 Mar '16

17 Mar '16

Hi all, I want to write a cld document with some data read on the standard input. I'm using the lua io.read() function but it's launched at every context passes (depending on the case, it is launched 2 to 3 times). -- Minimum not working example local name = io.read() context.startdocument() context("Hello " .. name) context.stopdocument() Thanks in advance. -- Romain Diss

3 4

Possible typo in source file type-imp-lato.mkiv
by Tom Harrop 16 Mar '16

16 Mar '16

Hi, I was having trouble getting italics to work for a PDF that uses the Lato font. Bold and 'normal' were rendering just fine. In the log I saw some lines like: > fonts > defining > font with asked name 'lato-reglta' is not > found using lookup 'file' > fonts > defining > unknown font 'lato-reglta', loading aborted I noticed Context was searching for *reglta (with a lower case "L") rather than regita (with an "i"). Looking at the file http://source.contextgarden.net/tex/context/base/type-imp-lato.mkiv I can see that all the synonyms point to *lta rather than *lta inside the \definefontsynonym commands. I tried changing all the instances of *lta to *ita in type-imp-lato.mkiv on two different systems (Ubuntu and MacOS) and in both cases I subsequently got italics in my PDF. I suppose this could be a bug. Is this list the right place to report it? My apologies if it is in fact something I was doing wrong! Thanks, Tom

2 1