[NTG-context] unable to define 'texgyrepagella-regula' error etc.
Dear all,Yesterday, I asked about a font problem without a mwe.Here is a MWE.%\setuplanguage[kr][patterns=us]\mainlanguage[kr]\setscript[hangul]\usetypescriptfile[type-hcrlvt]\usetypescript[HcrFont] \definefontfeature[kr][script=hang,language=kor,mode=node,analyze=yes]\setupbodyfont[Myface, rm, 11pt]\starttextThis is a test file. %이것은 시험 파일입니다.{\bf This is a test file for font.}%{\bf 이것은 시험 파일입니다.}{\sl This is a test file for font.}%{\sl 이것은 시험 파일입니다.}\stoptextHere is a part of log file of the first run.mtx-context | run 1: luatex --fmt="/Users/graph/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en" --jobname="test" --lua="/Users/graph/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui" --no-parse-first-line --c:currentrun=1 --c:fulljobname="./test.tex" --c:input="./test.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:purgeall "cont-yes.mkiv"This is LuaTeX, Version 1.08.0 (TeX Live 2018) system commands enabled.open source > level 1, order 1, name '/Users/graph/ConTeXt/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'system > system > ConTeXt ver: 2018.07.20 21:20 MKIV beta fmt: 2018.7.24 int: english/englishsystem > system > 'cont-new.mkiv' loadedopen source > level 2, order 2, name '/Users/graph/ConTeXt/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'system > beware: some patches loaded from cont-new.mkivclose source > level 2, order 2, name '/Users/graph/ConTeXt/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'system > files > jobname 'test', input './test', result 'test'fonts > latin modern fonts are not preloadedlanguages > language 'en' is activeopen source > level 2, order 3, name '/Users/graph/Documents/TeXfiles/test.tex'open source > level 3, order 4, name '/Users/graph/ConTeXt/tex/texmf-local/context/type-hcrlvt.mkiv'open source > level 4, order 5, name '/Users/graph/ConTeXt/tex/texmf-context/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'close source > level 4, order 5, name '/Users/graph/ConTeXt/tex/texmf-context/tex/context/fonts/mkiv/type-imp-texgyre.mkiv'close source > level 3, order 5, name '/Users/graph/ConTeXt/tex/texmf-local/context/type-hcrlvt.mkiv'fonts > defining > font with asked name 'texgyrepagella-regular' is not found using lookup 'file'fonts > defining > unknown font 'texgyrepagella-regular', loading abortedfonts > defining > unable to define 'texgyrepagella-regular' as 'dummy--0'fonts > defining > font with asked name 'texgyrepagella-bold' is not found using lookup 'file'fonts > defining > unknown font 'texgyrepagella-bold', loading abortedfonts > 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 abortedfonts > defining > unable to define 'texgyrepagella-regular' as 'dummy--0'backend > xmp > using file '/Users/graph/ConTeXt/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'pages > flushing realpage 1, userpage 1, subpage 1close source > level 2, order 5, name '/Users/graph/Documents/TeXfiles/test.tex'close source > level 1, order 5, name '/Users/graph/ConTeXt/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.luamkiv lua stats > used cache path: /Users/graph/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32emkiv lua stats > resource resolver: loadtime 0.006 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 14 found files, scanned paths: mkiv lua stats > stored bytecode data: 428 modules (0.208 sec), 93 tables (0.013 sec), 521 chunks (0.220 sec)mkiv lua stats > traced context: maxstack: 1309, freed: 0, unreachable: 1309mkiv lua stats > cleaned up reserved nodes: 58 nodes, 9 lists of 455mkiv lua stats > node memory usage: 2 glue, 2 kern, 2 penalty, 13 attribute, 50 glue_spec, 4 attribute_list, 2 temp, 2 user_definedmkiv lua stats > node list callback tasks: 8 unique task lists, 6 instances (re)created, 43 callsmkiv lua stats > used backend: pdf (backend for directly generating pdf output)mkiv lua stats > jobdata time: 0.001 seconds saving, 0.000 seconds loadingmkiv lua stats > callbacks: internal: 146, file: 617, direct: 2, late: 0, function 868, total: 1633mkiv lua stats > loaded patterns: en::2 kr::51, load time: 0.000mkiv lua stats > result saved in file: test.pdf, compresslevel 3, objectcompresslevel 3mkiv lua stats > loaded fonts: 3 files: latinmodern-math.otf, hanbatang-lvt.ttf, hanbatangb-lvt.ttfmkiv lua stats > font engine: otf 3.103, afm 1.513, tfm 1.000, 9 instances, 4 shared in backend, 4 common vectors, 0 common hashes,
Re: [NTG-context] Numbering properties in a chapter
The correct key to set the period after the number is "numberstopper" which is inherited from \setupcounter. Wolfgang Pablo Rodriguez schrieb am 24.07.18 um 17:09: 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 ___ 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
Am 2018-07-25 um 19:50 schrieb Hans Hagen : >> In any case, I would very much appreciate another “frozen” release like MK >> II that one can use for documents that need to be retypeset over years >> (like my lecture notes that need an update every few years). > > When we have luatex 1.10 that will be easier because older code can run on a > newer engine then. > > But even then, if we make snapshots that can be downloaded for a long time, > we need some way to recognize them (by year?). LilyPond (as a somewhat similar program) requires a version statement in every source file; and then there’s a converter script that understands and updates all constructs that are part of the official syntax - of course, if you use custom scripting (Scheme in this case), you are on your own again. Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD ___ 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 7/25/2018 3:12 PM, Weber, Matthias wrote: I have an entirely different suggestion, possibly fitting the description of a possible “lean” version. One important feature of TeX has been the longevity of the documents. This is of course of little interest to those of us who typeset a book/journal for publishing and care little about it when it’s done. But there is an interest in keeping the documents available in the long term, meaning decades and possibly centuries (making assumptions about the human race here). TeX has survived the transition from dvi/ps to pdf, and it is probably fair to assume that pdf won’t be around forever. But it is probably also fair to assume that there will be straightforward ways to generate from TeX sources documents in a future PDF replacement. so far no replacemtn showed up (ok, html is an alternatiev but that's a different thing) .. even pdf 2.0 (which we support) isn't revolutionary different from 1.7 This is in particular of concern in the scientific community where mathematical/physical/chemical formulas and diagrams are very hard to parse semantically (which, admittedly, might change in the future, too). For instance, the preprint server at arXiv.org has been storing scientific preprints since 1991, preferably in TeX or LaTeX. It would be an enormous benefit if the arXiv would accept a ConTeXt version. Scientific journals might then follow suit. At the moment I believe they use LaTeX from TeXLive 2016. It is of course a question whether a potentially much larger user base is desirable, because it likely means more requests for support/documentation etc. I don't think that a larger user base is a problem. It might actually trigger users into writing more manuals, wiki entries, tutorials. But 'marketing' in a world where tex is equivalent to latex is not trivial. In any case, I would very much appreciate another “frozen” release like MK II that one can use for documents that need to be retypeset over years (like my lecture notes that need an update every few years). When we have luatex 1.10 that will be easier because older code can run on a newer engine then. But even then, if we make snapshots that can be downloaded for a long time, we need some way to recognize them (by year?). Using snapshots in parallel is no big deal. One problem is that one also needs to save the fonts (it will probably take a few years before the lm/gyre collection is long term stable). Matthias On Jul 25, 2018, at 8:50 AM, Hans Hagen wrote: On 7/25/2018 12:03 PM, Richard Mahoney | Indica et Buddhica wrote: Agree wholeheartedly, and possibly also support for Tibetan. define support ... what is needed - 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 ___ -- - 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
On 7/25/2018 6:18 PM, Alan Braslau wrote:
On Wed, 25 Jul 2018 09:50:58 -0400
Rik Kabel wrote:
On 7/25/2018 04:19, Henning Hraban Ramm wrote:
Am 2018-07-25 um 03:29 schrieb Rik Kabel
:
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.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects.
Didn’t try real bibliographies or xml input yet, but I guess you
can change the setup to use those.
\definehighlight does not (by default) nest. You can handle this to
some degree in css or xslt for XML exports, but it is not an
acceptable replacement for font switches with pdf output. And since
the syntax for highlights ( \highlight{text} ) differs from that for
font switches ( {\highlight text} ), it is not simply a matter of
different environments for each output format, although perhaps
\groupedcommand might help (I have not tried this).
But that is in some ways beside the point. A user should not have to
find and modify every instance in the source where such setups occur.
When exports or tagging are enabled, it would be good if this were
automatically done.
Do you know about
\savebtxdataset
[default]
[bibliography.xml]
[alternative=xml,
criterium=all]
You can thus save your bibliography data for use, rather than or in
addition to the rendered list.
I'll upload a beta with
- tagged publications
- embedded bib data in xml format and bibtex format
that should be enough for postprocessing magic. Of course we cannot
catch cases where users mess around with specific setups which is no big
deal as fo rexporting purposes one can use a simple standard style.
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
On Wed, 25 Jul 2018 09:50:58 -0400
Rik Kabel wrote:
> On 7/25/2018 04:19, Henning Hraban Ramm wrote:
> > Am 2018-07-25 um 03:29 schrieb Rik Kabel
> > :
> >> 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.
> > Generally, you get stylistic tagging by using \definehighlight.
> > I replaced \em and \bf by \emph{} and \strong{} in my projects.
> >
> > Didn’t try real bibliographies or xml input yet, but I guess you
> > can change the setup to use those.
>
> \definehighlight does not (by default) nest. You can handle this to
> some degree in css or xslt for XML exports, but it is not an
> acceptable replacement for font switches with pdf output. And since
> the syntax for highlights ( \highlight{text} ) differs from that for
> font switches ( {\highlight text} ), it is not simply a matter of
> different environments for each output format, although perhaps
> \groupedcommand might help (I have not tried this).
>
> But that is in some ways beside the point. A user should not have to
> find and modify every instance in the source where such setups occur.
> When exports or tagging are enabled, it would be good if this were
> automatically done.
>
Do you know about
\savebtxdataset
[default]
[bibliography.xml]
[alternative=xml,
criterium=all]
You can thus save your bibliography data for use, rather than or in
addition to the rendered list.
Alan
___
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 7/25/2018 3:50 PM, Rik Kabel wrote:
On 7/25/2018 04:19, Henning Hraban Ramm wrote:
Am 2018-07-25 um 03:29 schrieb Rik Kabel :
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.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects.
Didn’t try real bibliographies or xml input yet, but I guess you can
change the setup to use those.
\definehighlight does not (by default) nest. You can handle this to some
degree in css or xslt for XML exports, but it is not an acceptable
replacement for font switches with pdf output. And since the syntax for
highlights ( \highlight{text} ) differs from that for font switches (
{\highlight text} ), it is not simply a matter of different environments
for each output format, although perhaps \groupedcommand might help (I
have not tried this).
font switches using 'style' are bound to a structural element
But that is in some ways beside the point. A user should not have to
find and modify every instance in the source where such setups occur.
When exports or tagging are enabled, it would be good if this were
automatically done.
you can't expect reliable structure from non-structured input so if you
want an export that is ok, the penalty is proper structuring
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
On 7/25/2018 04:19, Henning Hraban Ramm wrote:
Am 2018-07-25 um 03:29 schrieb Rik Kabel :
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.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects.
Didn’t try real bibliographies or xml input yet, but I guess you can change the
setup to use those.
\definehighlight does not (by default) nest. You can handle this to some
degree in css or xslt for XML exports, but it is not an acceptable
replacement for font switches with pdf output. And since the syntax for
highlights ( \highlight{text} ) differs from that for font switches (
{\highlight text} ), it is not simply a matter of different environments
for each output format, although perhaps \groupedcommand might help (I
have not tried this).
But that is in some ways beside the point. A user should not have to
find and modify every instance in the source where such setups occur.
When exports or tagging are enabled, it would be good if this were
automatically done.
--
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
___
Re: [NTG-context] future versions
I have an entirely different suggestion, possibly fitting the description of a possible “lean” version. One important feature of TeX has been the longevity of the documents. This is of course of little interest to those of us who typeset a book/journal for publishing and care little about it when it’s done. But there is an interest in keeping the documents available in the long term, meaning decades and possibly centuries (making assumptions about the human race here). TeX has survived the transition from dvi/ps to pdf, and it is probably fair to assume that pdf won’t be around forever. But it is probably also fair to assume that there will be straightforward ways to generate from TeX sources documents in a future PDF replacement. This is in particular of concern in the scientific community where mathematical/physical/chemical formulas and diagrams are very hard to parse semantically (which, admittedly, might change in the future, too). For instance, the preprint server at arXiv.org has been storing scientific preprints since 1991, preferably in TeX or LaTeX. It would be an enormous benefit if the arXiv would accept a ConTeXt version. Scientific journals might then follow suit. At the moment I believe they use LaTeX from TeXLive 2016. It is of course a question whether a potentially much larger user base is desirable, because it likely means more requests for support/documentation etc. In any case, I would very much appreciate another “frozen” release like MK II that one can use for documents that need to be retypeset over years (like my lecture notes that need an update every few years). Matthias > On Jul 25, 2018, at 8:50 AM, Hans Hagen wrote: > > On 7/25/2018 12:03 PM, Richard Mahoney | Indica et Buddhica wrote: >> Agree wholeheartedly, and possibly also support for Tibetan. > define support ... what is needed > > - > 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 ___
Re: [NTG-context] future versions
On 7/25/2018 12:03 PM, Richard Mahoney | Indica et Buddhica wrote: Agree wholeheartedly, and possibly also support for Tibetan. define support ... what is needed - 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
On 7/25/2018 9:45 AM, Robert Zydenbos wrote: On 24. Jul 2018, at 20:43, Hans Hagen wrote: Hi, […] That said, a logical question is how about next versions of context. Are there fundamental features missing? Is more needed? […] At the risk of sounding like a scratched, repeating gramophone record -- support for Indic scripts would be wonderful. I know. There's only a small piece of definitions missing. So that will happen eventually. (Kai is looking into that as he also has sample texts.) 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
On 7/25/2018 3:29 AM, Rik Kabel wrote: On 7/24/2018 14:43, Hans Hagen wrote: 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'll add some structure to publications but styling is upto a css and will never be part of the export (so on ehas to use 'detail' etc then). 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. Indeed. So basic subtags is one thing. The other is including the whole blob for whatever usage. 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. This needs more thinking. 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] Set up a theorem style
On Wed, 25 Jul 2018, Fabrice Couvreur wrote:
Hello,
I used LaTeX for a long time before converting (with difficulty !) to
ConteXt. For example, to define my new theorems, I used the amsthm package
and I did this :
\newtheoremstyle{theoremdd}% name of the style to be used
{\topsep}% measure of space to leave above the theorem. E.g.: 3pt
{\topsep}% measure of space to leave below the theorem. E.g.: 3pt
{\itshape}% name of font to use in the body of the theorem
{0pt}% measure of space to indent
{\bfseries}% name of head font
* {. ---}% punctuation between head and body*
{ }% space after theorem head; " " = normal interword space
{\thmname{#1}\thmnumber{ #2}\thmnote{ (#3)}}
\theoremstyle{theoremdd}
\newtheorem{thmd}{Theorem}[section]
I'm trying to do the same thing with ConTeXt but I can not do it completely
:
What are you missing?
Aditya
\setupenumerations[
before={\blank},
after={\blank},
text=Théorème,
alternative=serried,
title=no,
prefix=yes,
prefixsegments=chapter,
way=bysection,
right=.,
titlestyle=bold,
style=italic,
width=broad,
]
\defineenumeration[theorem]
\starttext
\startchapter[title={First Chapter}]
\startsection[title={First Section}]
\dorecurse{2}{
\starttheorem
\input ward
\stoptheorem}
\stopsection
\stopchapter
\startchapter[title={Second Chapter}]
\startsection[title={Second Section}]
\dorecurse{2}{
\starttheorem
\input ward
\stoptheorem}
\stopsection
\stopchapter
\stoptext
Thanks
Fabrice
___
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] Set up a theorem style
Hello,
I used LaTeX for a long time before converting (with difficulty !) to
ConteXt. For example, to define my new theorems, I used the amsthm package
and I did this :
\newtheoremstyle{theoremdd}% name of the style to be used
{\topsep}% measure of space to leave above the theorem. E.g.: 3pt
{\topsep}% measure of space to leave below the theorem. E.g.: 3pt
{\itshape}% name of font to use in the body of the theorem
{0pt}% measure of space to indent
{\bfseries}% name of head font
* {. ---}% punctuation between head and body*
{ }% space after theorem head; " " = normal interword space
{\thmname{#1}\thmnumber{ #2}\thmnote{ (#3)}}
\theoremstyle{theoremdd}
\newtheorem{thmd}{Theorem}[section]
I'm trying to do the same thing with ConTeXt but I can not do it completely
:
\setupenumerations[
before={\blank},
after={\blank},
text=Théorème,
alternative=serried,
title=no,
prefix=yes,
prefixsegments=chapter,
way=bysection,
right=.,
titlestyle=bold,
style=italic,
width=broad,
]
\defineenumeration[theorem]
\starttext
\startchapter[title={First Chapter}]
\startsection[title={First Section}]
\dorecurse{2}{
\starttheorem
\input ward
\stoptheorem}
\stopsection
\stopchapter
\startchapter[title={Second Chapter}]
\startsection[title={Second Section}]
\dorecurse{2}{
\starttheorem
\input ward
\stoptheorem}
\stopsection
\stopchapter
\stoptext
Thanks
Fabrice
___
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
Agree wholeheartedly, and possibly also support for Tibetan. Best, Richard -- Richard Mahoney - Indica et Buddhica Littledene Bay Road Oxford New Zealand T: +64 3 312 1699 M: +64 210 640 216 r.maho...@indica-et-buddhica.org http://indica-et-buddhica.org/ -Original Message- From: Robert Zydenbos Reply-to: mailing list for ConTeXt users To: mailing list for ConTeXt users Subject: Re: [NTG-context] future versions Date: Wed, 25 Jul 2018 09:45:47 +0200 Mailer: Apple Mail (2.3445.8.2) On 24. Jul 2018, at 20:43, Hans Hagen wrote: > Hi, > > […] > That said, a logical question is how about next versions of context. > Are there fundamental features missing? Is more needed? […] At the risk of sounding like a scratched, repeating gramophone record -- support for Indic scripts would be wonderful. RZ ___ 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 ___
Re: [NTG-context] Numbering properties in a chapter
Hi Pablo, Thank you for the link, it is true that I have to read this manual more often. Fabrice 2018-07-24 17:09 GMT+02:00 Pablo Rodriguez : > 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 > > ___ > ___ 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] unable to define 'texgyrepagella-regula' error etc.
Hi Dalyoung, The question of TXGyre fonts has been mentioned on this list recently, and the following answer from Wolfgang Schuster seems to solve the problem (until the original problem is fixed). This answer was on the thread « Problem with pagella font (beta) »: > On 23 Jul 2018, at 12:39, Wolfgang Schuster > wrote: > > Hi Fabrice, > > you can download the fonts from the GUST [1] website (the flat package is > enough because you need only the opentype files) and put them in your local > tex directory in your home folder, e.g. > > ~/texmf/fonts/data/texgyre/ > > or you put them in your tex installation, e.g. > > texmf-fonts/fonts/data/texgyre/ > > [1] http://www.gust.org.pl/projects/e-foundry/tex-gyre/whole > > Wolfgang Best regards: OK > On 25 Jul 2018, at 01:40, Jeong Dal wrote: > > 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]
Re: [NTG-context] future versions
Am 2018-07-25 um 03:29 schrieb Rik Kabel :
> 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.
Generally, you get stylistic tagging by using \definehighlight.
I replaced \em and \bf by \emph{} and \strong{} in my projects.
Didn’t try real bibliographies or xml input yet, but I guess you can change the
setup to use those.
> 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.
Seconded. Same with other references like footnotes. (I need to try the current
state, my last ePub was somewhen last year, and there the locations of
footnotes were messed up.)
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___
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 24. Jul 2018, at 20:43, Hans Hagen wrote: > Hi, > > […] > That said, a logical question is how about next versions of context. Are > there fundamental features missing? Is more needed? […] At the risk of sounding like a scratched, repeating gramophone record -- support for Indic scripts would be wonderful. RZ ___ 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 ___
