- dev-context - NTG Mailing Lists

Re: [dev-context] Libertinus Mono (type-imp) -- improvement
by Hans Hagen 25 May '20

25 May '20

On 5/25/2020 3:56 PM, Tomas Hala wrote: > Hi, > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%% > \setupbodyfont[libertinus] > \starttext > a--b > \startMP > a--b > \stopMP > \stoptext > %%%%%%%%%%%%%%%%%%%%%%%%%%%%% > > I found out that this code produces dash instead of double hyphen > also when typing the code which seems not to be correct. > > Solution: (type-imp-libertinus.mkiv from TL2020, line 71) > OLD: \definefontsynonym [\s!Mono] [LibertinusMono-Regular][\s!features=\s!default] > NEW: \definefontsynonym [\s!Mono] [LibertinusMono-Regular][\s!features=\s!none] > > If there is no other reason to keep the default features here, I would like > to propose the change above. sure, mono is always 'none' so it's a bug that we will fix 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 -----------------------------------------------------------------

1 0

CGModules update: vim syntax highlighting version 2020.05.17 published.
by modules＠contextgarden.net 17 May '20

17 May '20

Aditya Mahajan submitted an update to the vim syntax highlighting package. Version number: 2020.05.17 License type: BSD License (simplified) Wants to be in ConTeXt distribution: yes Wants to be synced with CTAN: yes Summary description: This module uses Vim editor's syntax files to syntax highlight verbatim code in ConTeXt Announcement text: ---------------------------------------------------------------------- Minor feature enhancement: export minor groups The default vim syntax highlighting has two typees of syntax highlighting groups: preffered groups and minor groups. By default, in `syncolors.vim`, the minor groups are mapped to preffered groups. This is overridden by most colorschemes, but since `2context.vim` does not load a colorscheme, we got the default mapping. As a result, the generated `*.vimout` file only contained the preffered group. In this release, default mappings for all minor groups are added to `2context.vim`, so the generated `*.vimout` file now contains all the default group names (both preffered and minor). The minor groups are already mapped to the appropriate preffered groups in `t-vim`, so this has no visible impact on any existing code, but it does allow the user to change the mappings of the minor groups. Based on a bug report by Nicola on the context mailing list. ----------------------------------------------------------------------

1 0

Minor Problems with ma-cb-en.pdf
by Sebastian Miele 12 May '20

12 May '20

On page 117 in appendix A (Command definitions) the "OPT" repeatedly protrudes into the following lines of text. On page 11 in chapter 6 (Heads), the following probably signifies some sort of error: "missing: stp:x:chapter missing: stp:x:section [..]". There are many more such places ("missing: stp:x:..."). "In addition we could also use the command \displaystyle. If we would type": After that, the result of some ConTeXt input follows twice. But it should be the verbatim ConTeXt input followed by the result. There is a single \phantom example in the PDF. It probably is meant to align the two plus signs. But the lower plus sign is more to the left. "lable" instead of "label". "furtilizer". "CONTEXT support the BIBTEX way": "support" instead of "supports". "As you have seen you": Superfluous "you". "If you want to have backgrounds in the gray areas of the page layout of figure 36.1 you type": There are no gray areas in figure 36.1. Apart from that there is a slight performance issue with the document: I use a computer with quite low power consumption. It has significantly less peak performance than 'usual' computers. But, usually, it more than suffices for all that I do. I use Arch Linux and Evince on x86_64. In many places, the rendering of ma-cb-en.pdf is quite slow, especially on the first and last page of the PDF. Apart from that, using Evince to search, e.g. for 'bla', through the whole ma-cb-en.pdf is very slow. (And when I search for '\phantom' then it finds matches in the background graphic of the first and last page of the PDF.) Other documents, even much longer ones like the ConTeXt reference manual, usually pose no such problems at all on my computer. I suspect that the manual uses fancy graphical stuff (in a way) that takes lots of time to render and somehow also makes it more complicated to search through it. The computing power of my computer may be comparable to a recent Raspberry PI. The slowness with ma-cb-en.pdf is no real problem for me, because I most probably will not peruse this specific document in a way that makes the problems really bad. In particular, I will not search a lot through the document, as I often do in refence manuals. But I wanted to have noted that the problem or such problems do exist.

1 0

typo-del.mkiv
by Wolfgang Schuster 30 Apr '20

30 Apr '20

Hi, the patch below makes it possible to change the interlinespace for blockquote etc. with the style key, e.g. \setupblockquote[style={\setupinterlinespace[...]}. The extra group is needed for the nextleft and nextright keys. \def\typo_delimited_start_par_indeed[#1]% {\let\typo_delimited_stop\typo_delimited_stop_par \edef\p_delimited_spacebefore{\delimitedtextparameter\c!spacebefore}% \ifx\p_delimited_spacebefore\empty \else \blank[\p_delimited_spacebefore]% \fi \delimitedtextparameter\c!before \iffirstargument \edef\m_delimited_argument{#1}% \fi \ifx\m_delimited_argument\empty \let\m_delimited_argument\m_delimited_argument \fi \ifx\m_delimited_argument\empty \endgraf \doadaptleftskip {\delimitedtextparameter\c!leftmargin}% \doadaptrightskip{\delimitedtextparameter\c!rightmargin}% \let\typo_delimited_stop_par_indeed\endgraf \else % backward compatible direct directive \startnarrower[\m_delimited_argument]% \let\typo_delimited_stop_par_indeed\stopnarrower \fi % so far \push_macro_checkindentation \useindentingparameter\delimitedtextparameter % \begingroup \usedelimitedtextstyleandcolor\c!style\c!color % + \begingroup \edef\p_delimited_left {\delimitedtextparameter{\c!left}}% \edef\p_delimited_right {\delimitedtextparameter{\c!right}}% \edef\p_delimited_nextleft {\delimitedtextparameter{\c!nextleft}}% \edef\p_delimited_nextright{\delimitedtextparameter{\c!nextright}}% % \leftdelimitedtextmark % \setnextleftdelimitedtextmark \setnextrightdelimitedtextmark % \typo_delimited_start_content} \def\typo_delimited_stop_par {\typo_delimited_stop_content \rightdelimitedtextmark + \carryoverpar\endgroup + \endgraf + \endgroup % new per 2013-01-21 ... please left floats - \carryoverpar\endgroup % new per 2013-01-21 ... please left floats \pop_macro_checkindentation \typo_delimited_stop_par_indeed \delimitedtextparameter\c!after \edef\p_delimited_spaceafter{\delimitedtextparameter\c!spaceafter}% \ifx\p_delimited_spaceafter\empty \else \blank[\p_delimited_spaceafter]% \fi \useindentnextparameter\delimitedtextparameter \aftergroup\dorechecknextindentation}% AM: This was missing! Wolfgang

1 0

CGModules update: vim syntax highlighting version 2020.04.29 published.
by modules＠contextgarden.net 29 Apr '20

29 Apr '20

Aditya Mahajan submitted an update to the vim syntax highlighting package. Version number: 2020.04.29 License type: BSD License (simplified) Wants to be in ConTeXt distribution: yes Wants to be synced with CTAN: yes Summary description: This module uses Vim editor's syntax files to syntax highlight verbatim code in ConTeXt Announcement text: ---------------------------------------------------------------------- Added `vimcommand` option to specify the location of vim program: \setupvimtyping[vimcommand=/path/to/vim] Can also use used to call neovim instead of vim: \setupvimtyping[vimcommand=nvim] On my laptop, nvim is amout 10% faster than vim for parsing medium sized (approx 500 lines) files. ----------------------------------------------------------------------

1 0

CGModules update: vim syntax highlighting version 2020.04.25 published.
by modules＠contextgarden.net 26 Apr '20

26 Apr '20

Aditya Mahajan submitted an update to the vim syntax highlighting package. Version number: 2020.04.25 License type: BSD License (simplified) Wants to be in ConTeXt distribution: yes Wants to be synced with CTAN: yes Summary description: This module uses Vim editor's syntax files to syntax highlight verbatim code in ConTeXt Announcement text: ---------------------------------------------------------------------- Added a new feature to escape in TeX mode using /BTEX .. /ETEX. This feature is enabled using `escape=command`. See the documentation for detailed iusage instructions. Thanks to Christoph HintermÃÂ¼ller for the implementation. ----------------------------------------------------------------------

1 0

CGModules update: Filter version 2020.04.25 published.
by modules＠contextgarden.net 26 Apr '20

26 Apr '20

Aditya Mahajan submitted an update to the Filter package. Version number: 2020.04.25 License type: BSD License (simplified) Wants to be in ConTeXt distribution: yes Wants to be synced with CTAN: yes Summary description: A module to run external programs on the contents of start-stop evironment Announcement text: ---------------------------------------------------------------------- Minor bugfix ----------------------------------------------------------------------

1 0

Some hint on how linenumbering works in context
by Christoph Hintermüller 14 Apr '20

14 Apr '20

Hi After some struggling with xml exporter i have managed to get the output quit nicely including css and others. The only thing which still worries me a bit is the line numbering. While location set to left and not placing the content inside float environment, everything seems to be fine. So my question is. Is there besides codes any documentation how linenumber placement works inside context and how far the backend exporter hooks into this process at all? If codes only which source files should i read to understand how things work. And how things change between pdf and xml/xhtml export? Would help in deciding whether and how to place some hints inside the document to facilitate line numberplacing in export mode. Also let me know if this question is better placed on the ntg-context mailing list instead of the development mailing list Best Xristoph

1 0

data-vir.lua: Extra tracker
by Wolfgang Schuster 05 Apr '20

05 Apr '20

Hi, the following tracker has to be removed because a) there is a tracker with the same name in data-zip.lua and b) the file contains another tracker for trace_virtual. data-vir.lua (line 15): trackers.register("resolvers.locating", function(v) trace_virtual = v end) Wolfgang

1 1

Keep extreme tables on the same page as previous content
by Wolfgang Schuster 04 Apr '20

04 Apr '20

Hi, when you use extreme tables without a float environment but repeat the header the table always starts on a new page. %%%% begin example \starttext \samplefile{weisman} \blank \startxtable[header=repeat,split=repeat] \startxtablehead \startxrow \startxcell Table head \stopxcell \stopxrow \stopxtablehead \startxtablebody \dorecurse{100}{\startxrow \startxcell Table body \stopxcell \stopxrow} \stopxtablebody \stopxtable \stoptext %%%% end example The reason for this is the height set for the part of each page, on the first page ConTeXt uses a box with the height of \pagegoal forces a page break because the content doesn't fit. \setvalue{\??xtableflushsplit\v!repeat}% {\doloop {\clf_x_table_flush method {\v!split}% height \ifdim\pagegoal=\maxdimen\textheight\else\pagegoal\fi \relax \ifcase\c_tabl_x_state \exitloop \else \page \fi}} While determining the available space is easy we need a method to ensure the table stays on the page when the user adds a vertical skip (e.g. \blank[...]) before the table because this can lead to another page break. Wolfgang

3 4