June 2020 - dev-context - NTG Mailing Lists

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

29 Jun '20

Aditya Mahajan submitted an update to the vim syntax highlighting package. Version number: 2020.06.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: ---------------------------------------------------------------------- This is a major release that adds support for XML export. Many thanks to Christoph HintermÃÂ¼ller for the initial implementation and extensive brainstorming and testing. When export is enabled, e.g., using \setupbackend[export=yes] then \definevimtyping[CODE][syntax=..., alternative=colorscheme] \startCODE ... \stopextCODE is exported as <vimtyping detail="colorscheme"> ... </vimtyping> And, \inlineCODE{...} is exported as <inlinevimtyping detail="colorscheme">...</inlinevimtyping> Each line is wrapped inside a `<verbatimline>...</verbatimline>` and each syntax group is wrapped inside `<syntaxgroup detail="vim....">...</syntaxgroup>`. See the updated documentation for details. The module ships with a default CSS file which can be included as \setupexport[cssfile=\vimtypingcssfile] This CSS file tries to mimic the default PDF output. If you want to tweak the output then it is recommended that you copy the default CSS file and modify it as appropriate. ----------------------------------------------------------------------

1 0

CGModules update: Filter version 2020.06.29 published.
by modules＠contextgarden.net 29 Jun '20

29 Jun '20

Aditya Mahajan submitted an update to the Filter package. Version number: 2020.06.29 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: ---------------------------------------------------------------------- This release adds support for XML export. When export is enabled, e.g., using \setupbackend[export=yes] then \defineexternalfilter[whatever][....] \startwhatever ... \stopextwhatever is exported as <externalfilter detail="whatever"> ... </externalfilter> And, \inlinewhatever{...} is exported as <inlineexternalfilter detail="whatever">...</inlineexternalfilter> This is mainly a feature enhancement to support the XML export for the vim module, but might be useful in its own right. ----------------------------------------------------------------------

1 0

CGModules update: vim syntax highlighting version 2020.06.25 published.
by modules＠contextgarden.net 25 Jun '20

25 Jun '20

Aditya Mahajan submitted an update to the vim syntax highlighting package. Version number: 2020.06.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: ---------------------------------------------------------------------- This is a bug-fix of the previous bug-fix The previous fix vim-2020.06.23 inadventently introduced a bug. The name of the color gets stored as a macro rather than the expanded value. Added an explicit `\expand` fixed this. ----------------------------------------------------------------------

1 0

CGModules update: vim syntax highlighting version 2020.06.23 published.
by modules＠contextgarden.net 23 Jun '20

23 Jun '20

Aditya Mahajan submitted an update to the vim syntax highlighting package. Version number: 2020.06.23 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: ---------------------------------------------------------------------- This is a bug-fix release with mutliple minor bugfixes: * Improvement in how catcodes are set internally. This ensures that space gets exported correctly in XML. Partially resolves #34. * Bugfix so that names of colors don't leak across different colorschemes. Closes #37. * Improved documentation. Added documentation of colorscheme and added a TOC to READMEs. ----------------------------------------------------------------------

1 0

strc-itm.mklx: \startspecialitemgroupitem
by Wolfgang Schuster 23 Jun '20

23 Jun '20

Hi, the \startspecialitemgroupitem command lacks a entry for \txt. A new entry on line 1324 is needed: \letvalue{\??itemgroupstart\v!item}\strc_itemgroups_start_do_item \letvalue{\??itemgroupstart\v!sub }\strc_itemgroups_start_subitem \letvalue{\??itemgroupstart\v!sym }\strc_itemgroups_start_symbol \letvalue{\??itemgroupstart\v!ran }\strc_itemgroups_start_edge \letvalue{\??itemgroupstart\v!its }\strc_itemgroups_start_items \letvalue{\??itemgroupstart\v!mar }\strc_itemgroups_start_margin +\letvalue{\??itemgroupstart\v!txt }\strc_itemgroups_start_text Wolfgang

2 1

strc-itm.mklx: Interface check
by Wolfgang Schuster 22 Jun '20

22 Jun '20

Hi, the check for the current interface on line 1596 doesn't work because it uses the undefined \v!english variable which should be \s!english. To ensure commands like \sym work after the fix a few synonyms have to be added to \itemgroupcommands. Line 1579 ff: \appendtoks \let\item \strc_itemgroups_start_do_item + \let\sub \strc_itemgroups_start_subitem + \let\sym \strc_itemgroups_start_symbol + \let\ran \strc_itemgroups_start_edge + \let\its \strc_itemgroups_start_items + \let\mar \strc_itemgroups_start_margin \let\noitem \strc_itemgroups_start_no_item \let\itm \strc_itemgroups_start_do_item \let\but \strc_itemgroups_start_button \let\nop \strc_itemgroups_start_dummy \let\txt \strc_itemgroups_start_text \let\head \strc_itemgroups_head \let\headsym \strc_itemgroups_start_head_sym \let\startitem \startitemgroupitem \let\stopitem \stopitemgroupitem \let\starthead \startitemgrouphead \let\stophead \stopitemgroupitemhead \let\startspecialitem\startspecialitemgroupitem \let\stopspecialitem \stopspecialitemgroupitem \to \itemgroupcommands -\ifx\currentinterface \v!english \else +\ifx\currentinterface\s!english \else Wolfgang

1 0

Line endings with \starttypescript
by Aditya Mahajan 17 Jun '20

17 Jun '20

Hi, This question is motivated by a question of TeX.SE (https://tex.stackexchange.com/questions/549725/context-strange-issue-with-t…) Basically, the OP defined \starttypescriptcollection[fira] ... \stoptypescriptcollection \setuphead[section][style={\switchtobodyfont[fira,sans]}] \starttext \section{section 1} \section{section 2} \section{section 3} \stoptext and found that the first section was indented. As Wolfgang explained in a comment, this happens because of the newlines at the end of each \definesynonym in \starttypescriptcollection. Wolfgang also explained how to avoid this error. I am wondering if it makes sense to change the definition of \starttypescriptcollection or \starttypescript so that newlines are automatically ignored (similar to \startsetups). Aditya

2 1

Need a bit of help for source.contextgarden.net
by Taco Hoekwater 16 Jun '20

16 Jun '20

Hi, About source.cg.net: Right now, I am starting texlua twice. Once for mtxrun doing the actual work (that is fine) but also once for the dispatch to that script. I wonder if someone with a bit of knowledge of php can help me replace that dispatcher by php? It seems wasteful to start an external program for what is essentially just a setenv() and an execute(). My index.lua currently looks likes this #!/opt/texweb/opt/context/tex/texmf-linux-64/bin/texlua -f os.setenv('PATH', os.env['CONTEXT_PATH'] .. '/texmf-linux-64/bin:' .. os.env['PATH']) print ("Content-type: text/html; charset=utf-8\n\n") os.execute('mtxrun --script /var/…etc…’) I assume it would be simple to replace this with a few php lines, but I do not know enough about php to do it myself. Help appreciated! Best wishes, Taco

1 0

Light colors in colo-imp-rgb.mkiv
by Aditya Mahajan 08 Jun '20

08 Jun '20

Hi, The 'light' colors defined in colo-imp-rgb.mkiv are not light! \definecolor [lightred] [r=1, g=0, b=0] \definecolor [lightgreen] [r=0, g=1, b=0] \definecolor [lightblue] [r=0, g=0, b=1] \definecolor [lightcyan] [r=0, g=1, b=1] \definecolor [lightmagenta] [r=1, g=0, b=1] \definecolor [lightyellow] [r=1, g=1, b=0] Is this intentional? How about replacing them with somewhat reasonable defaults? \definecolor [lightred] [r=1, g=0.5, b=0.5] \definecolor [lightgreen] [r=0.5, g=1, b=0.5] \definecolor [lightblue] [r=0.75, g=1, b=1] \definecolor [lightcyan] [r=0.5, g=1, b=1] \definecolor [lightmagenta] [r=1, g=0.5, b=1] \definecolor [lightyellow] [r=1, g=1, b=0.5] See attached output. These are not the ideal choices in terms of shades, but I have chosen values which are least subjective and still give reasonable shades. Aditya

3 3