Re: [NTG-context] future versions
On 7/24/2018 14:43, Hans Hagen wrote: Hi, Around the upcoming context meeting we expect to release luatex 1.09 (or 1.10 ... yet undecided) which is the prelude to the next year tex live version. It's another step towards a stable version in terms of functionality as we don't expect much more to be added (in fact, I'm wondering if it makes sense to come up with a leaner and meaner version at some point because context can probably benefit from that). Of course under the hood there are improvements possible and we have some ideas (that might materialize at some point) but generally spoken, this is what one gets. That said, a logical question is how about next versions of context. Are there fundamental features missing? Is more needed? Keep in mind that we're not talking of desk top publishing (click and point and place stuff) and also not of word processing (office like stuff) but of mostly automated structured document rendering. Also, keep in mind the landscape that we operate in (context development is mostly user driven as publishers imo long ago lost interest in any research and development and the potential of tex and friends is largely unknown elsewhere). It's not my intention to implement each possible feature as core feature (no one would document it anyway). Also, as development is basically a spare time effort, don't expect complex commercially interesting niches to come for free either as in that case one can wait till I a find a reason for implementing it for fun or development is driven by a project. When thinking of future additions, tex, lua, metapost of a mix is possible. They should be of interest for more than one user. Of course it can also be that everything needed is there. Maybe existing mechanisms can be improved in terms of functionality or performance (although i think that performance wise we're ok). But again keep in mind that the boundary conditions (all these interacting sub mechanisms) also prohibit some functionality. Hans I would ask for more stylistic or semantic tagging to be added to the XML export. A good example is that of bibliographies, where font styles carry significant semantic meaning (depending on the standard used: italic for book titles, ibold or talic for volume and issue numbers, and so on.) The xml output reflects none of this. I do not know whether one would want stylistic tagging (italic, bold, ...) or semantic (booktitle, issue number). In either case, they could be implemented as highlights or tagged elements, both of which are currently carried through, and the user could then apply the appropriate styling with css or other transformation mechanisms. The ability to point register entries to something other than page numbers would also be useful. For export formats (XML) this requires that label references be part of the export. -- Rik ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] unable to define 'texgyrepagella-regula' error etc.
Dear all, I found some warning message in the log file which concerns about the font. I didn’t see this kind of error before. (I might missed this error.) However, it produced an output. fonts > defining > font with asked name 'texgyreheros-regular' is not found using lookup 'file' fonts > defining > unknown font 'texgyreheros-regular', loading aborted fonts > defining > unable to define 'texgyreheros-regular' as 'dummy--0' floatblocks > '1' placed (here) fonts > defining > font with asked name 'texgyrepagella-regular' is not found using lookup 'file' fonts > defining > unknown font 'texgyrepagella-regular', loading aborted fonts > defining > unable to define 'texgyrepagella-regular' as 'dummy--4' fonts > defining > font with asked name 'texgyrepagella-regular' is not found using lookup 'file' fonts > defining > unknown font 'texgyrepagella-regular', loading aborted fonts > defining > unable to define 'texgyrepagella-regular' as 'dummy--5' fonts > defining > font with asked name 'texgyrepagella-bold' is not found using lookup 'file' fonts > defining > unknown font 'texgyrepagella-bold', loading aborted fonts > defining > unable to define 'texgyrepagella-bold' as 'dummy--0' fonts > defining > font with asked name 'texgyrepagella-regular' is not found using lookup 'file' fonts > defining > unknown font 'texgyrepagella-regular', loading aborted fonts > defining > unable to define 'texgyrepagella-regular' as 'dummy--0' How to remove this kind of error? The main file is too big to list here. Here is a part of typescript file which was made by the help of Hans. \loadtypescriptfile[texgyre] %\loadtypescriptfile[euler] %\loadtypescriptfile[xits] \definefontfeature [kr-default] [mode=node,script=hang,lang=kor] \definefontfeature [kr-slanted] [mode=node,script=hang,lang=kor,slant=.2] \definefontfeature [kr-latin-default] [default] \definefontfeature [kr-latin-slanted] [krlatindefault] [slant=.2] \definefontfeature [kr-latin-slanted-mono] [slant=.2] \definefontfeature [kr-latin-smallcaps] [krlatindefault] [smcp=yes] \definefontfeature [kr-latin-smallcaps-mono] [cmcp=yes] \definefontfallback[kr-serif] [texgyrepagella-regular*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-serifbold] [texgyrepagella-bold*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-serifitalic] [texgyrepagella-italic*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-serifbolditalic] [texgyrepagella-bolditalic*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-serifslanted] [texgyrepagella-regular*kr-latin-slanted] [0x-0x0400][force=yes] \definefontfallback[kr-serifboldslanted][texgyrepagella-bold*kr-latin-slanted] [0x-0x0400][force=yes] \definefontfallback[kr-serifcaps] [texgyrepagella-regular*kr-latin-smallcaps][0x-0x0400][force=yes] \definefontfallback[kr-sans][texgyreheros-regular*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-sansbold][texgyreheros-bold*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-sansitalic] [texgyreheros-italic*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-sansbolditalic] [texgyreheros-bolditalic*kr-latin-default] [0x-0x0400][force=yes] \definefontfallback[kr-sansslanted] [texgyreheros-regular*kr-latin-slanted] [0x-0x0400][force=yes] \definefontfallback[kr-sansboldslanted] [texgyreheros-bold*kr-latin-slanted] [0x-0x0400][force=yes] \definefontfallback[kr-sanscaps] [texgyreheros-regular*kr-latin-smallcaps] [0x-0x0400][force=yes] \definefontfallback[kr-mono][texgyrecursor-regular] [0x-0x0400][force=yes] \definefontfallback[kr-monobold][texgyrecursor-bold] [0x-0x0400][force=yes] \definefontfallback[kr-monoitalic] [texgyrecursor-italic] [0x-0x0400][force=yes] \definefontfallback[kr-monobolditalic] [texgyrecursor-bolditalic] [0x-0x0400][force=yes] \definefontfallback[kr-monoslanted] [texgyrecursor-regular*kr-latin-slanted-mono] [0x-0x0400][force=yes] \definefontfallback[kr-monoboldslanted] [texgyrecursor-bold*kr-latin-slanted-mono] [0x-0x0400][force=yes] \definefontfallback[kr-monocaps] [texgyrecursor-regular*kr-latin-smallcaps-mono][0x-0x0400][force=yes] %\starttypescriptcollection[hcrfonts] \starttypescript [serif] [HCRMJ] \definefontsynonym [HanBatang] [file:HANBatang-LVT.ttf] [features=kr-default,fallbacks=kr-serif] \definefontsynonym [HanBatangbold] [file:HANBatangB-LVT.ttf][featur
Re: [NTG-context] future versions
On 7/24/2018 11:02 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Hi Hans, all,
One needed feature that would be of general use is better support for
synctex. Thinking especially of structural elements such as headings,
footnotes, etc. which mostly do not work with synctex - i.e., clicking
on these elements in the pdf do not take one back to the correct
location in the relevant TEX file.
Synctex is a beast. Basically it is not that useable for context which
is why we have a different implementation with a rather clean, minimal,
and predictable output. Unfortunately the usual approahc is to use a
library for interoreting the synctex files which has too much heuristics
built in. More flexible would be to let the viewer cann an external
program which then can interpret the synctex file based on a page and
position. This also would make it possible to have more clever
synchronization and/or adapt to a macro package. Anyway, were sort of
stuck and can only try to make the best of it.
That said, the context generated synctex file is nornally okay unless we
render from lua, which happens for instance with titles. Just try
\ctxlua{context("foo bar")}
and you will also see that there is no line related positioning.
Tweaking luatex for this is not really an options because whatever
decision we make here will backfire at some point. (I can look into some
option later but it needs bit of thinking)
Anyway, i can cheat at the tex/lua end if needed and support e.g. titles
but i'm not going to pollute the code with every place where we come
from lua (also because in most cases there is no relation with the
source anyway then). Also, I will not add code that can have an impact
on performance when synctex is turned off. But for a subset of
constructs that are relatively short in usage it is doable (but doesn't
really qualify as fun -- also, i don't use it myself).
(One complication is that for instance fixing it for some constructs
will break it for xml input which also supports synctex.)
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] future versions
Hi Hans, all, On Tue, 24 Jul 2018 12:43:51 -0600, Hans Hagen wrote: Hi, Around the upcoming context meeting we expect to release luatex 1.09 (or 1.10 ... yet undecided) which is the prelude to the next year tex live version. It's another step towards a stable version in terms of functionality as we don't expect much more to be added (in fact, I'm wondering if it makes sense to come up with a leaner and meaner version at some point because context can probably benefit from that). Of course under the hood there are improvements possible and we have some ideas (that might materialize at some point) but generally spoken, this is what one gets. That said, a logical question is how about next versions of context. Are there fundamental features missing? Is more needed? Keep in mind that we're not talking of desk top publishing (click and point and place stuff) and also not of word processing (office like stuff) but of mostly automated structured document rendering. Also, keep in mind the landscape that we operate in (context development is mostly user driven as publishers imo long ago lost interest in any research and development and the potential of tex and friends is largely unknown elsewhere). It's not my intention to implement each possible feature as core feature (no one would document it anyway). Also, as development is basically a spare time effort, don't expect complex commercially interesting niches to come for free either as in that case one can wait till I a find a reason for implementing it for fun or development is driven by a project. When thinking of future additions, tex, lua, metapost of a mix is possible. They should be of interest for more than one user. Of course it can also be that everything needed is there. Maybe existing mechanisms can be improved in terms of functionality or performance (although i think that performance wise we're ok). But again keep in mind that the boundary conditions (all these interacting sub mechanisms) also prohibit some functionality. One needed feature that would be of general use is better support for synctex. Thinking especially of structural elements such as headings, footnotes, etc. which mostly do not work with synctex - i.e., clicking on these elements in the pdf do not take one back to the correct location in the relevant TEX file. Best wishes Idris -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80512 ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] issue with font features
On 07/24/2018 09:52 PM, Hans Hagen wrote: > On 7/24/2018 9:24 PM, Pablo Rodriguez wrote: >> [...] >> The new font instance is what I was missing in many of the issues I had >> with features. > > hm, only with those that affect the glyph shapes in some way, not with > normal otf kind of features i assume Sorry, Hans, but I don’t remember. These two months are being demanding and my memory is far from being perfect. I think my problems were related to glyph shapes. But in any case, if I detect what I think it might be a bug, rest assured I’ll report it. Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] future versions
On 07/24/2018 09:07 PM, Hans van der Meer wrote: > I am using XML a lot for structured data and typesetting them with > hopefully not too much attention to detail — although I must confess > often being a hopeless perfectionist. But is it possible to use ConTeXt without paying attention to the details? 🙂 I mean, aren’t we using ConTeXt to attain perfection (or at least, to evince it)? Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] future versions
On 07/24/2018 08:43 PM, Hans Hagen wrote: > [...] > It's not my intention to implement each possible feature as core feature > (no one would document it anyway). Also, as development is basically a > spare time effort, don't expect complex commercially interesting niches > to come for free either as in that case one can wait till I a find a > reason for implementing it for fun or development is driven by a project. Hans, if that were possible, I would like to make two proposals (that come from the roadmap thread [https://mailman.ntg.nl/pipermail/ntg-context/2018/091512.html]). It took me two months to catch up. I think it could be interesting to have the implementation of vertical scaling (as Hermann Zapf suggested to you) to avoid orphan an widows in MkIV (https://mailman.ntg.nl/pipermail/ntg-context/2018/091541.html). As mentioned in the past (https://mailman.ntg.nl/pipermail/ntg-context/2018/091525.html), I would like to have notes that handle automatically page registers. Unfortunately, I cannot attend the ConTeXt Meeting. But the notes with automatic page registers may qualify as unusual usage of ConTeXt. These are relevant for language-learning texts (such as https://geoffreysteadman.com/platos-crito/). Many thanks for your excellent work with ConTeXt, LuaTeX and MetaPost, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] issue with font features
On 7/24/2018 9:24 PM, Pablo Rodriguez wrote:
On 07/24/2018 07:02 PM, Hans Hagen wrote:
On 7/24/2018 6:20 PM, Pablo Rodriguez wrote:
[...]
\starttext
{\feature[+][effect]1234567890}
1234567890 {\feature[+][oldle]1234567890}
\stoptext
I wonder why the first font feature ("effect") doesn’t work. What am I
missing?
because effects are not regular features so you need to create a new
instance (which makes sense as you cannot turn a regular font into an
italic or bold one either this way)
Many thanks for your explanation, Hans.
The new font instance is what I was missing in many of the issues I had
with features.
hm, only with those that affect the glyph shapes in some way, not with
normal otf kind of features i assume
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] issue with font features
On 07/24/2018 07:02 PM, Hans Hagen wrote:
> On 7/24/2018 6:20 PM, Pablo Rodriguez wrote:
>> [...]
>> \starttext
>> {\feature[+][effect]1234567890}
>> 1234567890 {\feature[+][oldle]1234567890}
>> \stoptext
>>
>> I wonder why the first font feature ("effect") doesn’t work. What am I
>> missing?
> > because effects are not regular features so you need to create a new
> instance (which makes sense as you cannot turn a regular font into an
> italic or bold one either this way)
Many thanks for your explanation, Hans.
The new font instance is what I was missing in many of the issues I had
with features.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] future versions
I am using XML a lot for structured data and typesetting them with hopefully not too much attention to detail — although I must confess often being a hopeless perfectionist. If there are general improvements that can be made in that direction, I would welcome them. Although I apologise not being able to propose concrete suggestions at the moment, I hope this post will incite those more knowledgeable than me, to do so. They are thanked beforehand. Hans van der Meer > On 24 Jul 2018, at 20:43, Hans Hagen wrote: > > Hi, > > Around the upcoming context meeting we expect to release luatex 1.09 (or 1.10 > ... yet undecided) which is the prelude to the next year tex live version. > It's another step towards a stable version in terms of functionality as we > don't expect much more to be added (in fact, I'm wondering if it makes sense > to come up with a leaner and meaner version at some point because context can > probably benefit from that). Of course under the hood there are improvements > possible and we have some ideas (that might materialize at some point) but > generally spoken, this is what one gets. > > That said, a logical question is how about next versions of context. Are > there fundamental features missing? Is more needed? Keep in mind that we're > not talking of desk top publishing (click and point and place stuff) and also > not of word processing (office like stuff) but of mostly automated structured > document rendering. Also, keep in mind the landscape that we operate in > (context development is mostly user driven as publishers imo long ago lost > interest in any research and development and the potential of tex and friends > is largely unknown elsewhere). > > It's not my intention to implement each possible feature as core feature (no > one would document it anyway). Also, as development is basically a spare time > effort, don't expect complex commercially interesting niches to come for free > either as in that case one can wait till I a find a reason for implementing > it for fun or development is driven by a project. > > When thinking of future additions, tex, lua, metapost of a mix is possible. > They should be of interest for more than one user. Of course it can also be > that everything needed is there. Maybe existing mechanisms can be improved in > terms of functionality or performance (although i think that performance wise > we're ok). But again keep in mind that the boundary conditions (all these > interacting sub mechanisms) also prohibit some functionality. > > 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 > - > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] future versions
Hi, Around the upcoming context meeting we expect to release luatex 1.09 (or 1.10 ... yet undecided) which is the prelude to the next year tex live version. It's another step towards a stable version in terms of functionality as we don't expect much more to be added (in fact, I'm wondering if it makes sense to come up with a leaner and meaner version at some point because context can probably benefit from that). Of course under the hood there are improvements possible and we have some ideas (that might materialize at some point) but generally spoken, this is what one gets. That said, a logical question is how about next versions of context. Are there fundamental features missing? Is more needed? Keep in mind that we're not talking of desk top publishing (click and point and place stuff) and also not of word processing (office like stuff) but of mostly automated structured document rendering. Also, keep in mind the landscape that we operate in (context development is mostly user driven as publishers imo long ago lost interest in any research and development and the potential of tex and friends is largely unknown elsewhere). It's not my intention to implement each possible feature as core feature (no one would document it anyway). Also, as development is basically a spare time effort, don't expect complex commercially interesting niches to come for free either as in that case one can wait till I a find a reason for implementing it for fun or development is driven by a project. When thinking of future additions, tex, lua, metapost of a mix is possible. They should be of interest for more than one user. Of course it can also be that everything needed is there. Maybe existing mechanisms can be improved in terms of functionality or performance (although i think that performance wise we're ok). But again keep in mind that the boundary conditions (all these interacting sub mechanisms) also prohibit some functionality. 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] issue with font features
On 7/24/2018 6:20 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\definefontfeature[effect]%[effect=.2]
[effect={width=.3,delta=0.4,factor=0.3}]
\definefontfeature[oldle][onum=yes]
\setupbodyfont[palatino]
\starttext
{\feature[+][effect]1234567890}
1234567890 {\feature[+][oldle]1234567890}
\stoptext
I wonder why the first font feature ("effect") doesn’t work. What am I
missing?
because effects are not regular features so you need to create a new
instance (which makes sense as you cannot turn a regular font into an
italic or bold one either this way)
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Modifying bibliography entries using lua
On 7/24/2018 4:41 PM, Stanislav Sokolenko wrote:
I went with the following little extension to match and make bold
multiple names:
ok.
(this document.CompareNames makes a good candidate for a 'how to improve
your lua code' tutorial ... maybe something for the ctx meeting)
I didn't check what it does but ... for instance
> BoldNames = {
> full_entry = ''
use locals!
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] issue with font features
Dear list,
I have the following sample:
\definefontfeature[effect]%[effect=.2]
[effect={width=.3,delta=0.4,factor=0.3}]
\definefontfeature[oldle][onum=yes]
\setupbodyfont[palatino]
\starttext
{\feature[+][effect]1234567890}
1234567890 {\feature[+][oldle]1234567890}
\stoptext
I wonder why the first font feature ("effect") doesn’t work. What am I
missing?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Numbering properties in a chapter
On 07/24/2018 11:04 AM, Fabrice Couvreur wrote: > Hi Pablo, > Thank you Pablo for your answer that corresponds to what I seek to do. > Small question: how to have a point at the end of the numbering that is > to say : > > Property 1.1. > Property 1.2. Hi Fabrice, the option seems to be: right=., according to http://www.pragma-ade.com/general/qrcs/setup-en.pdf#page=203 (aka i-context.pdf in the distribution). tex/texmf-context/tex/context/interface/mkiv/i-context.pdf is one of your best friends here. I hope it helps, Pablo -- http://www.ousia.tk ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Modifying bibliography entries using lua
That's perfect, thank you!
On 2018-07-23 06:32 PM, Hans Hagen wrote:
\startsetups btx:list:author:normalshort
\fastsetup{btx:list:author:concat}
\begingroup
\ctxluacode{document.CheckMeB("\currentbtxdataset","\currentbtxtag",\number\currentbtxauthorindex)}
\ifx\currentbtxinitials\empty \else
\currentbtxinitials
\btxparameter{separator:initials}
\fi
\ifx\currentbtxvons\empty \else
\currentbtxvons
\ifx\currentbtxsurnames\empty \else
\btxparameter{separator:vons}
\fi
\fi
\ifx\currentbtxsurnames\empty \else
\currentbtxsurnames
\ifx\currentbtxjuniors\empty \else
\btxparameter{separator:juniors}
\currentbtxjuniors
\fi
\fi
\endgroup
\fastsetup{btx:list:author:others}
\stopsetups
I went with the following little extension to match and make bold
multiple names:
|\startbuffer[ref]@article{solo, author ={MyLast, MyFirst}, title ={Solo
work}, journal ={Journal}, year ={2000}, month ={1}, volume
={1}}@article{co, author ={OtherLast, OtherFirst and MyLast, MyFirst and
CoLast, CoFirst}, title ={Joint work}, journal ={Journal}, month ={1},
year ={2000}, volume
={1}}\stopbuffer\usebtxdataset[ref][ref.buffer]\setupbtx[dataset=ref]\definebtxrendering[ref][dataset=ref]\setupbtx[default:cite][alternative=authoryear,
etallimit=1, authorconversion=normalshort]\startluacodeBoldNames
={{firstnames ="MyFirst", surnames ="MyLast"}, {initials ="C", surnames
="CoLast"}, }function document.CompareNames(reference, targets)-- Loop
over targets for _, target in pairs(targets)do -- Loop over fields for
key, value in pairs(target)do if reference[key]==nil then break end
full_entry ='' for _, part in ipairs(reference[key])do full_entry
=full_entry .. ' ' .. part end full_entry =string.sub(full_entry, 2)if
full_entry ==value then return(true)end end end return(false)end
function document.BoldNames(set, tag, aut)local c
=publications.getcasted(set, tag, "author")if
document.CompareNames(c[aut], BoldNames)then context("\\bf")end end
\stopluacode\startsetupsbtx:list:author:normalshort
\fastsetup{btx:list:author:concat}\begingroup\ctxluacode{document.BoldNames("\currentbtxdataset","\currentbtxtag",\number\currentbtxauthorindex)}\ifx\currentbtxinitials\empty\else\currentbtxinitials\btxparameter{separator:initials}\fi\ifx\currentbtxvons\empty\else\currentbtxvons\ifx\currentbtxsurnames\empty\else\btxparameter{separator:vons}\fi\fi\ifx\currentbtxsurnames\empty\else\currentbtxsurnames\ifx\currentbtxjuniors\empty\else\btxparameter{separator:juniors}\currentbtxjuniors\fi\fi\endgroup\fastsetup{btx:list:author:others}\stopsetups\starttextCitations:
\cite[solo]\cite[co]\startsubject[title=Bibliography]\placelistofpublications[ref][method=dataset]\stopsection\stoptext|
Cheers,
Stan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] Numbering properties in a chapter
Hi Pablo, Thank you Pablo for your answer that corresponds to what I seek to do. Small question: how to have a point at the end of the numbering that is to say : Property 1.1. Property 1.2. . Thanks Fabrice 2018-07-23 17:39 GMT+02:00 Pablo Rodriguez : > On 07/23/2018 05:11 PM, Fabrice Couvreur wrote: > > Hello, > > I would like the numbering of the properties to be like this : > > [...] > > I thought it was enough to use the key way = bychapter > > Hi Fabrice, > > "way=bychapter" resets numbering in each chapter. > > You need this: > > \setupenumerations[ >prefix=yes, >prefixsegments=chapter, > ] > > You need to enable the prefix and say what you want as prefix. > > I hope it helps, > > Pablo > -- > http://www.ousia.tk > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/ > listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
