- dev-context - NTG Mailing Lists

Re: [dev-context] setup-en.pdf and mkiv command list
by Wolfgang Schuster 16 May '17

16 May '17

> Idris Samawi Hamid ادريس سماوي حامد <mailto:Idris.Hamid@colostate.edu> > 16. Mai 2017 um 15:17 > On Sun, 14 May 2017 14:04:41 -0600, Wolfgang Schuster > <schuster.wolfgang(a)gmail.com> wrote: > >>> Idris Samawi Hamid ادريس سماوي حامد <mailto:Idris.Hamid@colostate.edu> >>> 14. Mai 2017 um 20:55 >>> On Sun, 14 May 2017 12:20:43 -0600, Wolfgang Schuster >>> <schuster.wolfgang(a)gmail.com> wrote: >>> >>>>> OTOH user-defined commands can be added to the ConTeXt lexer via the >>>>> Style Configurator (Notepad++) and get their own highlight color. I >>>>> have found this very useful in writing long documents. See attached >>>>> (User-defined Keywords dialog). >>>> >>>> You can limit the number of custom commands when you use >>>> >>>> \startnamedsection[topic][title=...] >>>> >>>> instead of >>>> >>>> \starttopic[title=...] >>> >>> First time encountering these two commands; they're not on the wiki, >>> need to learn more about them.. >>> >>> Can you explain or give a complete sample test file illustrating how >>> they apply in the matter under discussion? Thanks. >> This is only a example to demonstrate that you can create new commands >> without using new command names (and the need to add them to your lexer) >> in your document. >> >> In the example below I create a new section but I don’t have to use >> a new user generated command in the document itself. >> >> \definehead[topic][subject] >> >> \starttext >> >> \startnamedsection[topic][title=This is a topic] >> ... >> \stopnamedsection >> >> \stoptext > > I see your point. Will make a note of it for the lexer documentation. > >>>> Adding tags to the commands is planned but the question is how to >>>> categorize them (internal, api, user level, low level, primitives, >>>> defininitions (\define...), setups etc.). >>> >>> This is good to know. At the moment we're working on a full-featured >>> ConTeXt lexer and are experimenting with different ideas of organizing >>> commands for user-friendly syntax highlighting. Currently considering >>> something like the following: >>> >>> TeX primitives - Knuth >>> luaTeX primitives - excluding Knuth >> The syntax files contain at the moment only ConTeXt specific command, >> primitives aren’t included. > > Sure, we get the TeX and luaTeX commands from the scite*.lua files > >>> macro structure - e.g., sectioning etc. >>> micro structure - e.g., itemizations, tables etc. >>> mode structure - e.g., metapost, xml, markdown >> The XML source has a category attribute for this information. > > Could you give a couple of examples? Below is a example for \m{…}. <cd:command name="m" category="mathematics" file="math-ini.mkiv"> <cd:arguments> <cd:resolve name="keyword-name-optional"/> <cd:content/> </cd:arguments> </cd:command> Wolfgang

1 0

Re: [dev-context] setup-en.pdf and mkiv command list
by Wolfgang Schuster 16 May '17

16 May '17

> Idris Samawi Hamid ادريس سماوي حامد <mailto:Idris.Hamid@colostate.edu> > 16. Mai 2017 um 14:27 > Hi Wolfgang, > > On Mon, 15 May 2017 13:00:37 -0600, Wolfgang Schuster > <schuster.wolfgang(a)gmail.com> wrote: > >> >>> Hans Hagen <mailto:pragma@wxs.nl> > >>> low level is fuzzy anyway: \xmlfirst (more low level?) vs \xmlfilter >>> (more generic) >> I can add class="system|primitive" (or level="...") to the XML files, >> commands without attribute are user-level. > > It would be great to include this system-primitive class in the lexer, > but if that's too much of a burden short-term then perhaps we should > not wait... Do you have an approximate time-frame for when this can be > done? I presume it will take a long time to put that class together... Marking internal/system command is simple but it will take a few days (boring stuff you won’t do for a few hours). Wolfgang

1 0

Re: [dev-context] setup-en.pdf and mkiv command list
by Hans Hagen 16 May '17

16 May '17

On 5/13/2017 9:41 PM, Idris Samawi Hamid ادريس سماوي حامد wrote: > Dear gang, > > We need to generate a complete list of mkiv commands. setup-en.pdf has > everything but some clarification and modification is needed: > > 1. Clarification: Does setup-en.pdf includes both mkii and mkiv > commands? If so, then can a version of the auto-generation script be > made that will generate a version setup-mkiv-en.pdf that is complete but > restricted to mkiv commands? this is mkiv (there is an cont-en.xml file describing mkii mostly) ... remmeber: mkii is frozen and phased out > [Is the auto-generation script publicly available?] all scripts are in the distribution > 2. Modification: It appears that all command names that appear in > slanted text are used to mention user-defined commands of a particular > class, e.g., > > /\BACKGROUND/ - slanted text > > which obviously names each of a class of commands defined by > > \definebackground - regular text > > Can a version of the auto-generation script be made that will generate a > version setup-mkiv-strict-en.pdf that is restricted to mkiv commands > explicitly defined in mkiv, excluding class commands or anything else > represented in slanted text? it's xml so one can benerate anything from the file (i was in the process of generating instances in the lua files for scintilla but (1) had to prepare for bachotex, (2) got back and ill, (3) need some motivation to pick up that thread) > 3. Although it is intuitive, a legend precisely explaining the semantics > of the command list in setup.pdf would be useful. If there is already > one available, could you point it out to me? dunno, maybe somewhere on the wiki > 4. Would it be possible for the auto-generation to export the command > list to a semi-formatted text file? Copying the text of setup-en.pdf to > a text file gives usable results but a text file with some regular > structure might be better. one can (1) use some xml transformation or (2) use the lua tables to get strings > In sum: we need - urgently - a comprehensive ConTeXt command list > restricted to mkiv that excludes class names for user definitions and > the like. Any help is greatly appreciated, and thanks in advance! > > Best wishes > Idris > -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

3 19

Re: [dev-context] setup-en.pdf and mkiv command list
by Hans Hagen 16 May '17

16 May '17

On 5/16/2017 2:35 PM, Idris Samawi Hamid ادريس سماوي حامد wrote: > On Tue, 16 May 2017 06:27:49 -0600, Idris Samawi Hamid ادريس سماوي حامد > <Idris.Hamid(a)colostate.edu> wrote: > >> Hi Wolfgang, >> >> On Mon, 15 May 2017 13:00:37 -0600, Wolfgang Schuster >> <schuster.wolfgang(a)gmail.com> wrote: >> >>> >>>> Hans Hagen <mailto:pragma@wxs.nl> >> >>>> low level is fuzzy anyway: \xmlfirst (more low level?) vs \xmlfilter >>>> (more generic) >>> I can add class="system|primitive" (or level="...") to the XML files, >>> commands without attribute are user-level. >> >> It would be great to include this system-primitive class in the lexer, >> but if that's too much of a burden short-term then perhaps we should >> not wait... Do you have an approximate time-frame for when this can be >> done? I presume it will take a long time to put that class together... > > Apologies, got confused, assumed we were talking about low-level context > commands, not TeX/luaTeX primitives. sure, but a categorization has to cover all aspects of tex 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

Re: [dev-context] setup-en.pdf and mkiv command list
by Hans Hagen 16 May '17

16 May '17

On 5/16/2017 2:27 PM, Idris Samawi Hamid ادريس سماوي حامد wrote: > Hi Wolfgang, > > On Mon, 15 May 2017 13:00:37 -0600, Wolfgang Schuster > <schuster.wolfgang(a)gmail.com> wrote: > >> >>> Hans Hagen <mailto:pragma@wxs.nl> > >>> low level is fuzzy anyway: \xmlfirst (more low level?) vs \xmlfilter >>> (more generic) >> I can add class="system|primitive" (or level="...") to the XML files, >> commands without attribute are user-level. > > It would be great to include this system-primitive class in the lexer, > but if that's too much of a burden short-term then perhaps we should not > wait... Do you have an approximate time-frame for when this can be done? > I presume it will take a long time to put that class together... everything setups is long term and normally ctx group meetings are moments when something is/gets done (if you'd seen Wolfgangs awesome ledgers at the last meeting you'd probably understand better what i mean) 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

Re: [dev-context] setup-en.pdf and mkiv command list
by Idris Samawi Hamid ادريس سماوي ح امد 13 May '17

13 May '17

On Sat, 13 May 2017 13:41:04 -0600, Idris Samawi Hamid ادريس سماوي حامد <Idris.Hamid(a)colostate.edu> wrote: CHANGE > Copying the text of setup-en.pdf to a text file gives usable results but > a text file with some regular structure might be better. TO Copying the text of setup-en.pdf to a text file gives usable results but a text file with some regular structure, auto-generated via the script, might be better. -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80512

1 0

setup-en.pdf and mkiv command list
by Idris Samawi Hamid ادريس سماوي ح امد 13 May '17

13 May '17

Dear gang, We need to generate a complete list of mkiv commands. setup-en.pdf has everything but some clarification and modification is needed: 1. Clarification: Does setup-en.pdf includes both mkii and mkiv commands? If so, then can a version of the auto-generation script be made that will generate a version setup-mkiv-en.pdf that is complete but restricted to mkiv commands? [Is the auto-generation script publicly available?] 2. Modification: It appears that all command names that appear in slanted text are used to mention user-defined commands of a particular class, e.g., /\BACKGROUND/ - slanted text which obviously names each of a class of commands defined by \definebackground - regular text Can a version of the auto-generation script be made that will generate a version setup-mkiv-strict-en.pdf that is restricted to mkiv commands explicitly defined in mkiv, excluding class commands or anything else represented in slanted text? 3. Although it is intuitive, a legend precisely explaining the semantics of the command list in setup.pdf would be useful. If there is already one available, could you point it out to me? 4. Would it be possible for the auto-generation to export the command list to a semi-formatted text file? Copying the text of setup-en.pdf to a text file gives usable results but a text file with some regular structure might be better. In sum: we need - urgently - a comprehensive ConTeXt command list restricted to mkiv that excludes class names for user definitions and the like. Any help is greatly appreciated, and thanks in advance! Best wishes Idris -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80512

1 0

Re: [dev-context] [MacTeX] Context Problem?
by Norbert Preining 04 May '17

04 May '17

Hi ConteXt people, here a problem report from Herbert on MacOS, but it is the same on Linux in tlpretest. Thanks Norbert On Wed, 03 May 2017, Herbert Schulz wrote: > Howdy, > > I know virtually nothing about ConTeXt but have a few very simple test files that I picked up from who knows where. In the process of testing TeX Live 2017 pretest I happened to try out the latest ConTeXt on the enclosed file (all updates, including context, this morning). I also enclose the pdf output. > > I checked with the final TeX Live 2016 and the problem doesn't exist in that distribution. > > > > I'm sure there are some folks on this list that understand what is happening here and can pass on worthwhile information to the ConTeXt folks. > > Good Luck, > > Herb Schulz > (herbs at wideopenwest dot com) > -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

2 2

LuaTeX 1.0.3 announcement
by luigi scarso 17 Feb '17

17 Feb '17

============================================================== LuaTeX Release 1.0.3 was released 2017021514 ============================================================== This is a minor upgrade and probably this version will go on texlive. There are a couple of fixes and additions. - We added a few a few more helpers in the pdf namespace (like set|get]gentounicode, [set|get]omitcidset and set|get]decimaldigits. Some helpers were moved from the tex to the pdf namespace. - We added a build_page_insert callback for inserts so that one can for instance adapt spacing on demand. - On the agenda has been some more control over word start and end in hyphenation and this is now possible via hyphenationbounds. We also updated the manual with some more details. - An old tracker item with respect to control over spacing around math was revived and has resulted in mathsurroundmode (one can wonder how useful this is). - We improved the resolution detection in included jpeg images. - An ffi library has been added to luatex so that it is more in sync with luajittex. This permits easy and flexible loading of libraries. Our policy is to make luatex as lean as possible with no dependencies and this is a step towards that. Eventually we hope to support all relevant platforms. - The glue and skip register accessors have been improved as a step in freeing the user from glue spec management. - We added a few more getters and setters for nodes in order to get a more consistent set. - Irrelevant fields have been removed from the status table and an engine identifier has been added. - Of course there are numerous fixes and improvements but none of these have consequences for the interfaces. - The manual has been updated but will be improved over time. Have fun, Hans, Luigi, Taco

1 0

\pdfannot
by Taco Hoekwater 14 Feb '17

14 Feb '17

Hi Hans, I just tried this with a fairly new ConTeXt: \starttext \message{pdfannot: [\meaning \pdfannot] pdflastannot: [\meaning \pdflastannot] \stoptext reports pdfannot: [\relax] pdflastannot: [\count1160] which is not really useful. It actually hit me inside a file that was actually using \pdfannot to do some fancy stuff, which was working fine a few years back. (I know it is now called "\pdfextension annot", that is not actually the problem) If you do no longer want to support the primitives in ConTeXt, sure. But could you at least produce a message and/or error ? In particular, the \let \pdfannot \relax creates mayhem inside the produced PDF, because of all the associated keywords in the primitive \pdfannot implementation that are now suddenly being typeset as-is, which is rather messy. Best wishes, Taco

1 0