\type

Re: [NTG-context] Bibliography in MKIV, custom rendering

2017-08-12 Thread Rik Kabel


On 2017-08-12 22:38, Alan Braslau wrote:

On Fri, 11 Aug 2017 14:58:53 -0400
Rik Kabel <cont...@rik.users.panix.com> wrote:


The lack of either an author or an editor is currently flagged in
ConTeXt as an error for books and perhaps other bibtex entry types as
well. Or do you mean to apply this recommendation to only the
electronic type or some other limited subset of types?

This will be corrected for types other than electronic when I look into
a consistent set.


Perhaps it is better to use the association name as an author and
protect it with a layer of curlies or quotation marks, as {{Apple,
Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do
the job and also serve to prevent what would surely be unwanted
abbreviation for styles that abbreviate what are parsed as given
names.

This won't happen. We made a design choice not to follow such sloppy
bibtex/LaTeX use and to require clean datasets. Apple Inc. is NOT a
named author, it is an organization, and the APA specification is clear
about this (it even has screwy rules about the first citation and then
the following when one should abbreviate names [such as APA]). Of
course, the specifications have to be fixed to handle this correctly
and consistently, also trying to be consistent with the fields that are
defined by the original bibtex documentation and followed by many
bibtex manipulating tools (such as jabref). The problem is that the use
of bibtex in the real world is a big mess!

ALan


So organization will simply become a stand-in for author but with 
different parsing rules. A book will require an author or editor or 
organization. The first two will be parsed for surname, given name, and 
so on, while the last will not, and precedence rules will apply when 
more than one is present, as they do already.


But until that point, as Hans said, using the author field and 
protecting it with curlies will work.


How will other screwy rules be handled? Will there be an override 
mechanism, or is it your belief that a compliant subsystem can be 
developed? (Yes, I know that is a false dichotomy.)


--
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] Bibliography in MKIV, custom rendering

2017-08-12 Thread Alan Braslau

On Fri, 11 Aug 2017 14:58:53 -0400
Rik Kabel <cont...@rik.users.panix.com> wrote:

> The lack of either an author or an editor is currently flagged in 
> ConTeXt as an error for books and perhaps other bibtex entry types as 
> well. Or do you mean to apply this recommendation to only the
> electronic type or some other limited subset of types?

This will be corrected for types other than electronic when I look into
a consistent set.

> Perhaps it is better to use the association name as an author and 
> protect it with a layer of curlies or quotation marks, as {{Apple, 
> Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do 
> the job and also serve to prevent what would surely be unwanted 
> abbreviation for styles that abbreviate what are parsed as given
> names.

This won't happen. We made a design choice not to follow such sloppy
bibtex/LaTeX use and to require clean datasets. Apple Inc. is NOT a
named author, it is an organization, and the APA specification is clear
about this (it even has screwy rules about the first citation and then
the following when one should abbreviate names [such as APA]). Of
course, the specifications have to be fixed to handle this correctly
and consistently, also trying to be consistent with the fields that are
defined by the original bibtex documentation and followed by many
bibtex manipulating tools (such as jabref). The problem is that the use
of bibtex in the real world is a big mess!

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] Bibliography in MKIV, custom rendering

2017-08-12 Thread Rik Kabel


On 2017-08-12 11:28, Rik Kabel wrote:

On 2017-08-12 04:54, Hans Hagen wrote:

On 8/11/2017 8:58 PM, Rik Kabel wrote:

On 2017-08-11 10:01, Alan Braslau wrote:

...


2) Apple Inc. is not a name so you should not be using author:
organization is more appropriate.


I do not think that this should be the case.

APA and Chicago/Turbanian (and doubtless others) accept association 
names as author names, and provide rules for handling them.


and as a consequence i bet this is why journals get typeset partly by 
hand (tweak and cheat on these things) ... and why each publisher 
then has its own style (with cheats and tricks)


The lack of either an author or an editor is currently flagged in 
ConTeXt as an error for books and perhaps other bibtex entry types 
as well. Or do you mean to apply this recommendation to only the 
electronic type or some other limited subset of types?


Perhaps it is better to use the association name as an author and 
protect it with a layer of curlies or quotation marks, as {{Apple, 
Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do 


one can do that of course (an dit will work) but then someone will 
come along and say that ...


our recomendation is that one spends some time on a proper database 
as it pays off


the job and also serve to prevent what would surely be unwanted 
abbreviation for styles that abbreviate what are parsed as given names.
we really try to get away from fuzzyness ... in fact, the bib format 
or at least the way it's often used is a structural coding nightmare 
(and often tex commands are then used to bypass things) .. i think 
that it never went through a proper 'design, test, review, revise' cycle


reverse engineering what is there + side effects took us quite a 
while and esp the author bit is a pain (this parsing) ... there have 
been proposals for alternatives in the past decades (take mlbibtex) 
but so far we're stuck with historic stuff: making a database in a 
format that is not that suitable (no nesting) using practices that 
are counter intuitive and demand lots of obscure magic


(one day Alan will wrap this up in an article)

Hans


Alan has stated elsewhere that his intent is to provide first an 
APA-compliant subsystem, and to add after that support for other 
regimes. He has also expressed an understandable reluctance to add 
non-standard fields to bibtex. But it is clearly impossible to provide 
an APA-compliant system under such a constraint—for example, for some 
works APA requires an original publication date and bibtex does not 
support that. It is similarly difficult to see how one can comply with 
other requirements of APA, such as square brackets around estimated 
dates for archival sources (how do you identify an estimated date?), 
constructing shortened titles that are then alphabetized by the first 
non-significant word, spelling out author names where two or more 
authors share the same abbreviated names, and so on. Biblatex attempts 
to address some of these issues with an explosion of new fields, and 
still, I think, does not succeed. CSL may do a better job on some of 
these, but again, I do not think that the type of organic standards 
set forth by APA and others are fully amenable to any automated 
parsing. This is why I suggested to Alan (off-line) that we need a 
mechanism to override the generated citation and 
bibliography/reference list entries with customized versions (\citeas, 
or additional fields for \cite).


Clearly bibtex is not compatible with the requirements of current 
documentation standards. Those who require compliant citation to 
whatever standard with which they are burdened need a better database, 
support for conversion from bibtex, and a mechanism to override 
whatever automated result is produced. Of these, the last is most 
crucial.


As to the specific issue of association names as author names: Why is 
widening the definition of the author name field using an 
already-supported protection mechanism worse than overloading the use 
of the organization field, which is intended denote an affiliation and 
is not currently supported in the major entry categories?


Sorry, rereading what I wrote, I see that I mistakenly suggested that 
the btx subsystem does not support origdate. It does, but it is a 
non-standard extension of bibtex, which was my point.


--
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] Bibliography in MKIV, custom rendering

2017-08-12 Thread Rik Kabel


On 2017-08-12 04:54, Hans Hagen wrote:

On 8/11/2017 8:58 PM, Rik Kabel wrote:

On 2017-08-11 10:01, Alan Braslau wrote:

...


2) Apple Inc. is not a name so you should not be using author:
organization is more appropriate.


I do not think that this should be the case.

APA and Chicago/Turbanian (and doubtless others) accept association 
names as author names, and provide rules for handling them.


and as a consequence i bet this is why journals get typeset partly by 
hand (tweak and cheat on these things) ... and why each publisher then 
has its own style (with cheats and tricks)


The lack of either an author or an editor is currently flagged in 
ConTeXt as an error for books and perhaps other bibtex entry types as 
well. Or do you mean to apply this recommendation to only the 
electronic type or some other limited subset of types?


Perhaps it is better to use the association name as an author and 
protect it with a layer of curlies or quotation marks, as {{Apple, 
Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do 


one can do that of course (an dit will work) but then someone will 
come along and say that ...


our recomendation is that one spends some time on a proper database as 
it pays off


the job and also serve to prevent what would surely be unwanted 
abbreviation for styles that abbreviate what are parsed as given names.
we really try to get away from fuzzyness ... in fact, the bib format 
or at least the way it's often used is a structural coding nightmare 
(and often tex commands are then used to bypass things) .. i think 
that it never went through a proper 'design, test, review, revise' cycle


reverse engineering what is there + side effects took us quite a while 
and esp the author bit is a pain (this parsing) ... there have been 
proposals for alternatives in the past decades (take mlbibtex) but so 
far we're stuck with historic stuff: making a database in a format 
that is not that suitable (no nesting) using practices that are 
counter intuitive and demand lots of obscure magic


(one day Alan will wrap this up in an article)

Hans


Alan has stated elsewhere that his intent is to provide first an 
APA-compliant subsystem, and to add after that support for other 
regimes. He has also expressed an understandable reluctance to add 
non-standard fields to bibtex. But it is clearly impossible to provide 
an APA-compliant system under such a constraint—for example, for some 
works APA requires an original publication date and bibtex does not 
support that. It is similarly difficult to see how one can comply with 
other requirements of APA, such as square brackets around estimated 
dates for archival sources (how do you identify an estimated date?), 
constructing shortened titles that are then alphabetized by the first 
non-significant word, spelling out author names where two or more 
authors share the same abbreviated names, and so on. Biblatex attempts 
to address some of these issues with an explosion of new fields, and 
still, I think, does not succeed. CSL may do a better job on some of 
these, but again, I do not think that the type of organic standards set 
forth by APA and others are fully amenable to any automated parsing. 
This is why I suggested to Alan (off-line) that we need a mechanism to 
override the generated citation and bibliography/reference list entries 
with customized versions (\citeas, or additional fields for \cite).


Clearly bibtex is not compatible with the requirements of current 
documentation standards. Those who require compliant citation to 
whatever standard with which they are burdened need a better database, 
support for conversion from bibtex, and a mechanism to override whatever 
automated result is produced. Of these, the last is most crucial.


As to the specific issue of association names as author names: Why is 
widening the definition of the author name field using an 
already-supported protection mechanism worse than overloading the use of 
the organization field, which is intended denote an affiliation and is 
not currently supported in the major entry categories?


--
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] Bibliography in MKIV, custom rendering

2017-08-12 Thread Hans Hagen


On 8/11/2017 8:58 PM, Rik Kabel wrote:

On 2017-08-11 10:01, Alan Braslau wrote:

...


2) Apple Inc. is not a name so you should not be using author:
organization is more appropriate.


I do not think that this should be the case.

APA and Chicago/Turbanian (and doubtless others) accept association 
names as author names, and provide rules for handling them.


and as a consequence i bet this is why journals get typeset partly by 
hand (tweak and cheat on these things) ... and why each publisher then 
has its own style (with cheats and tricks)


The lack of either an author or an editor is currently flagged in 
ConTeXt as an error for books and perhaps other bibtex entry types as 
well. Or do you mean to apply this recommendation to only the electronic 
type or some other limited subset of types?


Perhaps it is better to use the association name as an author and 
protect it with a layer of curlies or quotation marks, as {{Apple, 
Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do 


one can do that of course (an dit will work) but then someone will come 
along and say that ...


our recomendation is that one spends some time on a proper database as 
it pays off


the job and also serve to prevent what would surely be unwanted 
abbreviation for styles that abbreviate what are parsed as given names.
we really try to get away from fuzzyness ... in fact, the bib format or 
at least the way it's often used is a structural coding nightmare (and 
often tex commands are then used to bypass things) .. i think that it 
never went through a proper 'design, test, review, revise' cycle


reverse engineering what is there + side effects took us quite a while 
and esp the author bit is a pain (this parsing) ... there have been 
proposals for alternatives in the past decades (take mlbibtex) but so 
far we're stuck with historic stuff: making a database in a format that 
is not that suitable (no nesting) using practices that are counter 
intuitive and demand lots of obscure magic


(one day Alan will wrap this up in an article)

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] Bibliography in MKIV, custom rendering

2017-08-11 Thread Rik Kabel


On 2017-08-11 10:01, Alan Braslau wrote:

...


2) Apple Inc. is not a name so you should not be using author:
organization is more appropriate.


I do not think that this should be the case.

APA and Chicago/Turbanian (and doubtless others) accept association 
names as author names, and provide rules for handling them.


The lack of either an author or an editor is currently flagged in 
ConTeXt as an error for books and perhaps other bibtex entry types as 
well. Or do you mean to apply this recommendation to only the electronic 
type or some other limited subset of types?


Perhaps it is better to use the association name as an author and 
protect it with a layer of curlies or quotation marks, as {{Apple, 
Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do 
the job and also serve to prevent what would surely be unwanted 
abbreviation for styles that abbreviate what are parsed as given names.


--
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] changing pdf type

2017-08-06 Thread Mikael P. Sundqvist

On Sun, Aug 6, 2017 at 7:27 PM, John Culleton  wrote:
> I need to have pdf files for U.S. printers in " PDF/X-1a2001" format. Hans
> gave me the magic formula a few years back but I lost that reply.
> Can someone help me out?
>
> John Culleton
>
>
>
> ___
> 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
> ___

This link?

http://wiki.contextgarden.net/PDFX

/Mikael
___
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] changing pdf type

2017-08-06 Thread John Culleton

I need to have pdf files for U.S. printers in " PDF/X-1a2001" format. Hans 
gave me the magic formula a few years back but I lost that reply.
 Can someone help me out?
  
 John Culleton
  
  

___
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] TwoColumns in two different languages, with alternate text on even and odd page.

2017-08-03 Thread Jean-Pierre Delange

Hi again Marcello,

I was somehow busy and forgot that I made a promise to give you a better answer
than I did about bilingual texts on two columns. If you need only to print some
simple texts on two columns, there is no major issues. Problems occur when you
want to print two texts in different languages, with a complex criticus
apparatus.

But I've forgotten that (when I first began to work with ConTeXt, under the
Pablo Rodriguez's eye), I was looking for a mechanism which allow to print
greek/latin original text on the left column with a translation within the
right column and a few series of footnotes in the footer. Notes dealing with
the original text and different notes for the translation, given that if the
original text was on the even page (left), a commentary might be print on the
right page. The situation is clear : an even page with original language and
translation (on two separate columns), and criticus apparatus in the footer;
an odd page which contains some material like a commentary. It is without
saying that the translation has to follow the original text line by line, not
in a strictly way, but almost, when the odd page may be much more flexible. I
know there are some technical ways under LaTeX (Maieul Rouquette made some work
on that), and with non-free software but I had forgotten that Wolfgang made a
simple proposal with the Stream mechanism. I have to work on that, but I am
currently working on other jobs.

See what Wolfgang wrote in the end of 2016 here on the wiki :
http://wiki.contextgarden.net/Columns#Streams

There are two non-free softwares, just as CET (Critical Edition Typesetter) :
http://karas.ch/cet/cetinfo.htm

or Classical Text Editor :
http://cte.oeaw.ac.at/

- Mail original -
De: "Jean-Pierre Delange" <adeiman...@free.fr>
À: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Envoyé: Jeudi 27 Juillet 2017 12:11:05
Objet: Re: [NTG-context] TwoColumns in two different languages, with alternate
text on even and odd page.

Hi Marcello,

As you say "this feature could be really interesting", but as far as I know,
there are many issues to deal with, in order to print 2 columns on the same
page with different languages (say : greek and latin). This is not only because
of two languages (say : english and russian, or greek and german), but because
such work needs some editing datas, like footnotes, or more complex type of
single line footnotes. I'll give some samples in a few hours. I've written once
to Maieul Rouquette (author of (xe)LaTeX and in charge or reledpar
(http://distrib-coffee.ipsl.jussieu.fr/pub/mirrors/ctan/macros/latex/contrib/reledmac/reledpar.pdf)
and reledmac
(ftp://ftp.dante.de/tex-archive/macros/latex/contrib/reledmac/reledmac.pdf)
LaTeX packages for asking him about complex "criticus apparatus" in edition
issues for Classics. Pablo Rodriguez has a better knowledfge as me on these
topics.
In fact, there is currently no strictly satisfying way to deal with different
texts with ConTeXt on even and odd page (or on the same page with two columns),
except if there is no need of footnotes (or criticus apparatus), because some
mismatches between texts with the second page. But, there is possibly some
solutions with XML and CTX (which I didn't try) ?

- Mail original -
De: "Marcello Urgo" <marcello.u...@polimi.it>
À: ntg-context@ntg.nl
Envoyé: Samedi 22 Juillet 2017 19:14:03
Objet: Re: [NTG-context] TwoColumns in two different languages, with alternate
text on even and odd page.

Dear Hans,
I am also intersted in this issue.
In the last years I am dealing with a multi-language technical lexicon.
Hence, different languages refer to different columns, and if the languages are
three or four, then it is better to go with two pages side-by-side.
Nevertheless this seems a problem also in LaTeX redelpar (multiple columns are
not supported).
I tried to manage it with \linetable but without success (
https://tex.stackexchange.com/questions/380923/synchronise-data-spanning-over-two-side-by-side-pages-in-context
)
I think this feature could be really interesting because, according to my
knowledge, ConTeXt is at present the best way to manage the publishing of XML
data.
Hence, this could be a useful tool to publish large sets of data.
Thank you in advance

Marcello Urgo, Ph.D.
Assistant Professor
Manufacturing and Production Systems Lab.
Mechanical Engineering Department
POLITECNICO DI MILANO
Via La Masa, 1 - 20156 Milano

Phone +39 02 2399 8521
Fax +39 02 2399 8585
tecnologie.mecc.polimi.it
www.polimi.it

Re: [NTG-context] bug in latest beta (2017.08.02 18:59)

2017-08-03 Thread Hans Hagen


On 8/3/2017 7:49 AM, Pablo Rodriguez wrote:

On 08/03/2017 07:13 AM, Pablo Rodriguez wrote:

On 08/02/2017 11:08 PM, Hans Hagen wrote:

ok i uploaded a new beta (but with some experimental font stuff so who
knows what happens now)


I’m afraid I get a new crash with the same source (the log contains it):
[...]
lua error   > lua error on line 1 in file tex-bug.tex:

...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: You
cannot set field glue_sign in a node of type glue_spec
stack traceback:
[C]: in function 'setfield'
...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: in
function 'setboxglue'
...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:131: in
function <...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:64>

1 >>  \setupnote[footnote]
2 [align={hanging}]


Hans,

since it seems you don’t reproduce the bug, I wonder whether this might
be caused by Linux 32bit luatex binaries being version 1.0.5 and Windows
64bt has version 1.0.6.x.
no, it's more that i always have a newer luatex so older stuff has to be 
simulated


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] bug in latest beta (2017.08.02 18:59)

2017-08-02 Thread Pablo Rodriguez

On 08/03/2017 07:13 AM, Pablo Rodriguez wrote:
> On 08/02/2017 11:08 PM, Hans Hagen wrote:
>> ok i uploaded a new beta (but with some experimental font stuff so who 
>> knows what happens now)
> 
> I’m afraid I get a new crash with the same source (the log contains it):
> [...]
> lua error   > lua error on line 1 in file tex-bug.tex:
> 
> ...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: You
> cannot set field glue_sign in a node of type glue_spec
> stack traceback:
>   [C]: in function 'setfield'
>   ...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: in
> function 'setboxglue'
>   ...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:131: in
> function <...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:64>
> 
> 1 >>  \setupnote[footnote]
> 2 [align={hanging}]

Hans,

since it seems you don’t reproduce the bug, I wonder whether this might
be caused by Linux 32bit luatex binaries being version 1.0.5 and Windows
64bt has version 1.0.6.x.

Just in case 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] bug in latest beta (2017.08.02 18:59)

2017-08-02 Thread Pablo Rodriguez

On 08/02/2017 11:08 PM, Hans Hagen wrote:
> ok i uploaded a new beta (but with some experimental font stuff so who 
> knows what happens now)

Hans,

I’m afraid I get a new crash with the same source (the log contains it):

open source > level 1, order 1, name
'/home/ousia/ctxbeta/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'
system  >
system  > ConTeXt  ver: 2017.08.02 23:00 MKIV beta  fmt:
2017.8.3  int: english/english
system  >
system  > 'cont-new.mkiv' loaded
open source > level 2, order 2, name
'/home/ousia/ctxbeta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
close source> level 2, order 2, name
'/home/ousia/ctxbeta/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system  > files > jobname 'tex-bug', input './tex-bug.xml',
result 'tex-bug'
fonts   > latin modern fonts are not preloaded
languages   > language 'en' is active
open source > level 2, order 3, name 'tex-bug.tex'
fonts   > beware: no fonts are loaded yet, using 'lm mono' in box
fonts   > preloading latin modern fonts (second stage)
fonts   > 'fallback modern-designsize rm 12pt' is loaded
open source > level 3, order 4, name
'/home/ousia/ctxbeta/tex/texmf-context/tex/context/sample/common/knuth.tex'
close source> level 3, order 4, name
'/home/ousia/ctxbeta/tex/texmf-context/tex/context/sample/common/knuth.tex'

lua error   > lua error on line 1 in file tex-bug.tex:

...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: You
cannot set field glue_sign in a node of type glue_spec
stack traceback:
[C]: in function 'setfield'
...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: in
function 'setboxglue'
...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:131: in
function <...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:64>

1 >>  \setupnote[footnote]
2 [align={hanging}]
3
4 \starttext
5 a\footnote{\input knuth}
6 \stoptext
7


?

lua error   > lua error on line 1 in file tex-bug.tex:

...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: You
cannot set field glue_sign in a node of type glue_spec
stack traceback:
[C]: in function 'setfield'
...eta/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:965: in
function 'setboxglue'
...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:131: in
function <...eta/tex/texmf-context/tex/context/base/mkiv/pack-rul.lua:64>

1 >>  \setupnote[footnote]
2 [align={hanging}]
3
4 \starttext
5 a\footnote{\input knuth}
6 \stoptext
7

End of file on the terminal!

Many thanks for your help
-- 
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] Cambria official typescript (mis)behavior

2017-08-02 Thread Idris Samawi Hamid ادريس سماوي حامد


On Wed, 02 Aug 2017 15:17:07 -0600, Hans Hagen <pra...@wxs.nl> wrote:


On 8/2/2017 11:05 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

On Wed, 02 Aug 2017 14:34:25 -0600, Hans Hagen <pra...@wxs.nl> wrote:


On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

Dear gang,
 There appears to be something awry with type-imp-cambria.mkiv or  
type-imp-dejavu.mkiv. Consider the following:

 ===
\setupbodyfont
   [cambria,12pt]
 \starttext
Test % {\it Test} {\bf Test} {\bi Test}
\stoptext
===
 This produces a pdf with Cambria Italic instead of Cambria Regular.  
Uncommenting the other three options produces the expected results.

 Is this a bug or am I missing something? Awaiting your advice!

it's ok here; it could depend on the cambria on your machine

 Cambria Regular : cambria.ttc
Cambria Italic  : cambriai.ttf
 Inspection shows cambria.ttc is indeed regular.
 The log file says
:
mkiv lua stats  > loaded fonts: 2 files: cambria.ttc, cambriai.ttf
 Updating to "current version: 2017.08.02 18:59" and purging the cache  
doesn't help
 Why is cambriai.ttf being loaded at all? Fresh log (today's beta)  
attached


probably because it's the first 'name' that matches

you can try

cambria-x


=> LM


cambria-y


=> LM


cambria-a


=> LM


as variants ; here i have an official cambria


I only have the one that comes with the latest update to Windows 10

(Never tested Cambria with ConTeXt till a few days ago (\definefont  
worked), and never tested the typescript till last night.)


Aditya's suggestion did something that seems to have fixed it, not sure  
what..


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] Cambria official typescript (mis)behavior

2017-08-02 Thread Idris Samawi Hamid ادريس سماوي حامد

On Wed, 02 Aug 2017 15:15:59 -0600, Aditya Mahajan <adit...@umich.edu>  
wrote:



On Wed, 2 Aug 2017, Idris Samawi Hamid ادريس سماوي حامد wrote:


On Wed, 02 Aug 2017 14:34:25 -0600, Hans Hagen <pra...@wxs.nl> wrote:


On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
> Dear gang,
>  There appears to be something awry with type-imp-cambria.mkiv or
>  type-imp-dejavu.mkiv. Consider the following:
>  ===
> \setupbodyfont
>[cambria,12pt]
> \starttext
> Test % {\it Test} {\bf Test} {\bi Test}
> \stoptext
> ===
>  This produces a pdf with Cambria Italic instead of Cambria Regular.
>  Uncommenting the other three options produces the expected results.
>  Is this a bug or am I missing something? Awaiting your advice!
it's ok here; it could depend on the cambria on your machine


Cambria Regular : cambria.ttc
Cambria Italic  : cambriai.ttf

Inspection shows cambria.ttc is indeed regular.

The log file says
:
mkiv lua stats  > loaded fonts: 2 files: cambria.ttc, cambriai.ttf

Updating to "current version: 2017.08.02 18:59" and purging the cache  
doesn't

help


Not sure if it helps, but this is worth a try (note the force key):

mtxrun --script fonts --reload --force


Hmm, now I get

mkiv lua stats  > loaded fonts: 1 files: cambria.ttc

and the pdf file is correct. Thanks, Aditya! (Although I still don't  
understand why there was a problem to begin with!)


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] Cambria official typescript (mis)behavior

2017-08-02 Thread Hans Hagen


On 8/2/2017 11:05 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

On Wed, 02 Aug 2017 14:34:25 -0600, Hans Hagen <pra...@wxs.nl> wrote:


On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

Dear gang,
 There appears to be something awry with type-imp-cambria.mkiv or 
type-imp-dejavu.mkiv. Consider the following:

 ===
\setupbodyfont
   [cambria,12pt]
 \starttext
Test % {\it Test} {\bf Test} {\bi Test}
\stoptext
===
 This produces a pdf with Cambria Italic instead of Cambria Regular. 
Uncommenting the other three options produces the expected results.

 Is this a bug or am I missing something? Awaiting your advice!

it's ok here; it could depend on the cambria on your machine


Cambria Regular : cambria.ttc
Cambria Italic  : cambriai.ttf

Inspection shows cambria.ttc is indeed regular.

The log file says
:
mkiv lua stats  > loaded fonts: 2 files: cambria.ttc, cambriai.ttf

Updating to "current version: 2017.08.02 18:59" and purging the cache 
doesn't help


Why is cambriai.ttf being loaded at all? Fresh log (today's beta) attached


probably because it's the first 'name' that matches

you can try

cambria-x
cambria-y
cambria-a

as variants ; here i have an official cambria

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] Cambria official typescript (mis)behavior

2017-08-02 Thread Aditya Mahajan


On Wed, 2 Aug 2017, Idris Samawi Hamid ادريس سماوي حامد wrote:


On Wed, 02 Aug 2017 14:34:25 -0600, Hans Hagen <pra...@wxs.nl> wrote:


On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
> Dear gang,
>  There appears to be something awry with type-imp-cambria.mkiv or 
>  type-imp-dejavu.mkiv. Consider the following:

>  ===
> \setupbodyfont
>[cambria,12pt]
> \starttext
> Test % {\it Test} {\bf Test} {\bi Test}
> \stoptext
> ===
>  This produces a pdf with Cambria Italic instead of Cambria Regular. 
>  Uncommenting the other three options produces the expected results.

>  Is this a bug or am I missing something? Awaiting your advice!
it's ok here; it could depend on the cambria on your machine


Cambria Regular : cambria.ttc
Cambria Italic  : cambriai.ttf

Inspection shows cambria.ttc is indeed regular.

The log file says
:
mkiv lua stats  > loaded fonts: 2 files: cambria.ttc, cambriai.ttf

Updating to "current version: 2017.08.02 18:59" and purging the cache doesn't 
help


Not sure if it helps, but this is worth a try (note the force key):

mtxrun --script fonts --reload --force

Aditya___
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] Cambria official typescript (mis)behavior

2017-08-02 Thread Idris Samawi Hamid ادريس سماوي حامد


On Wed, 02 Aug 2017 14:34:25 -0600, Hans Hagen <pra...@wxs.nl> wrote:


On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

Dear gang,
 There appears to be something awry with type-imp-cambria.mkiv or  
type-imp-dejavu.mkiv. Consider the following:

 ===
\setupbodyfont
   [cambria,12pt]
 \starttext
Test % {\it Test} {\bf Test} {\bi Test}
\stoptext
===
 This produces a pdf with Cambria Italic instead of Cambria Regular.  
Uncommenting the other three options produces the expected results.

 Is this a bug or am I missing something? Awaiting your advice!

it's ok here; it could depend on the cambria on your machine


Cambria Regular : cambria.ttc
Cambria Italic  : cambriai.ttf

Inspection shows cambria.ttc is indeed regular.

The log file says
:
mkiv lua stats  > loaded fonts: 2 files: cambria.ttc, cambriai.ttf

Updating to "current version: 2017.08.02 18:59" and purging the cache  
doesn't help


Why is cambriai.ttf being loaded at all? Fresh log (today's beta) attached

Idris
--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512

test-cambria.log
Description: Binary data
___
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] Cambria official typescript (mis)behavior

2017-08-02 Thread Hans Hagen


On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

Dear gang,

There appears to be something awry with type-imp-cambria.mkiv or 
type-imp-dejavu.mkiv. Consider the following:


===
\setupbodyfont
   [cambria,12pt]

\starttext
Test % {\it Test} {\bf Test} {\bi Test}
\stoptext
===

This produces a pdf with Cambria Italic instead of Cambria Regular. 
Uncommenting the other three options produces the expected results.


Is this a bug or am I missing something? Awaiting your advice!

it's ok here; it could depend on the cambria on your machine



-
  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] Cambria official typescript (mis)behavior

2017-08-02 Thread Idris Samawi Hamid ادريس سماوي حامد


Dear gang,

There appears to be something awry with type-imp-cambria.mkiv or  
type-imp-dejavu.mkiv. Consider the following:


===
\setupbodyfont
  [cambria,12pt]

\starttext
Test % {\it Test} {\bf Test} {\bi Test}
\stoptext
===

This produces a pdf with Cambria Italic instead of Cambria Regular.  
Uncommenting the other three options produces the expected results.


Is this a bug or am I missing something? Awaiting your advice!

Best wishes
Idris
--
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512

test-cambria.log
Description: Binary data


test-cambria.pdf
Description: Adobe PDF document
___
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] (again) \typebufferinline for XML inline code

2017-08-02 Thread Hans Hagen


On 8/1/2017 9:12 PM, Pablo Rodriguez wrote:

On 08/01/2017 04:27 PM, Hans Hagen wrote:

On 7/31/2017 7:16 PM, Pablo Rodriguez wrote:

[...]
Would it be possible to have a new \typebufferinline that behaves such
as \type above (and has the same options in \setuptype)?

The most important part isn’t the suppression of line breaks inside, but
avoiding the addition of line breaks after and before the typed buffer.

I have been reading buff-ver.mkiv, but I’m afraid I cannot contribute
such a patch.

This is essential to have \xmlprettyprintinline and
\xmlprettyprintinlinetext in order to handle inline code in XML.


\startbuffer[foo]
foo \bar{crap}
\stopbuffer

\starttext
  \typebuffer[foo]
\stoptext


Many thanks for your reply, Hans.

I’m afraid this isn’t what I was looking for.


i'll make \xmlinlineprettyprinttext but there is where this madness stops


As shown in the following sample, I need \xmlprettyprinttext for code
inside a paragraph, not building its own paragraph.

 \startbuffer[demo]
 
 I can use colored code blocks:
 \starttext
 \ConTeXt\ is awesome!
 \stoptext
 But I’m afraid I cannot use \xmlprettyprinttext inline.
 
 \stopbuffer

 \startxmlsetups xml:initialize
  \xmlsetsetup{#1}{doc|p|code}{xml:*}
  \xmlsetsetup{#1}{pre/code}{xml:pre:code}
 \stopxmlsetups

 \xmlregistersetup{xml:initialize}

 \startxmlsetups xml:doc
  \xmlflush{#1}
 \stopxmlsetups

 \startxmlsetups xml:p
  \startpar\xmlflush{#1}\stoppar
 \stopxmlsetups

 \startxmlsetups xml:pre:code
  \xmlprettyprinttext{#1}{tex}
 \stopxmlsetups

 \startxmlsetups xml:code
 \begingroup\xmlprettyprinttext{#1}{tex}\endgroup
 \stopxmlsetups

 \starttext

 \subject{Dealing with XML}

  \xmlprocessbuffer{main}{demo}{}

 \subject{In standard \ConTeXt}

 \setuptyping[option=TEX]
 \setuptype[option=TEX]

 I can use colored code blocks:

 \starttyping
 \starttext
 \ConTeXt\ is awesome!
 \stoptext
 \stoptyping

 But I'm afraid I cannot use \type{\xmlprettyprinttext} inline.
 \stoptext

Many thanks for your help,

Pablo




--

-
  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] (again) \typebufferinline for XML inline code

2017-08-01 Thread Pablo Rodriguez

On 08/01/2017 04:27 PM, Hans Hagen wrote:
> On 7/31/2017 7:16 PM, Pablo Rodriguez wrote:
>> [...]
>> Would it be possible to have a new \typebufferinline that behaves such
>> as \type above (and has the same options in \setuptype)?
>>
>> The most important part isn’t the suppression of line breaks inside, but
>> avoiding the addition of line breaks after and before the typed buffer.
>>
>> I have been reading buff-ver.mkiv, but I’m afraid I cannot contribute
>> such a patch.
>>
>> This is essential to have \xmlprettyprintinline and
>> \xmlprettyprintinlinetext in order to handle inline code in XML.
> 
> \startbuffer[foo]
> foo \bar{crap}
> \stopbuffer
> 
> \starttext
>  \typebuffer[foo]
> \stoptext

Many thanks for your reply, Hans.

I’m afraid this isn’t what I was looking for.

As shown in the following sample, I need \xmlprettyprinttext for code
inside a paragraph, not building its own paragraph.

\startbuffer[demo]

I can use colored code blocks:
\starttext
\ConTeXt\ is awesome!
\stoptext
But I’m afraid I cannot use \xmlprettyprinttext inline.

\stopbuffer

\startxmlsetups xml:initialize
 \xmlsetsetup{#1}{doc|p|code}{xml:*}
 \xmlsetsetup{#1}{pre/code}{xml:pre:code}
\stopxmlsetups

\xmlregistersetup{xml:initialize}

\startxmlsetups xml:doc
 \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:p
 \startpar\xmlflush{#1}\stoppar
\stopxmlsetups

\startxmlsetups xml:pre:code
 \xmlprettyprinttext{#1}{tex}
\stopxmlsetups

\startxmlsetups xml:code
\begingroup\xmlprettyprinttext{#1}{tex}\endgroup
\stopxmlsetups

\starttext

\subject{Dealing with XML}

 \xmlprocessbuffer{main}{demo}{}

\subject{In standard \ConTeXt}

\setuptyping[option=TEX]
\setuptype[option=TEX]

I can use colored code blocks:

\starttyping
\starttext
\ConTeXt\ is awesome!
\stoptext
\stoptyping

But I'm afraid I cannot use \type{\xmlprettyprinttext} inline.
\stoptext

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] (again) \typebufferinline for XML inline code

2017-08-01 Thread Hans Hagen


On 7/31/2017 7:16 PM, Pablo Rodriguez wrote:

Hans,

sorry for asking for this again, but I really need it to write some
documents about ConTeXt.

I have the following sample:

 \startTEXpage[offset=1em]
 only \type{a

 b

 c} one line
 \stopTEXpage
 \stoptext

\type

Would it be possible to have a new \typebufferinline that behaves such
as \type above (and has the same options in \setuptype)?

The most important part isn’t the suppression of line breaks inside, but
avoiding the addition of line breaks after and before the typed buffer.

I have been reading buff-ver.mkiv, but I’m afraid I cannot contribute
such a patch.

This is essential to have \xmlprettyprintinline and
\xmlprettyprintinlinetext in order to handle inline code in XML.


\startbuffer[foo]
foo \bar{crap}
\stopbuffer

\starttext
\typebuffer[foo]
\stoptext


--

-
  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] (again) \typebufferinline for XML inline code

2017-07-31 Thread Pablo Rodriguez

Hans,

sorry for asking for this again, but I really need it to write some
documents about ConTeXt.

I have the following sample:

\startTEXpage[offset=1em]
only \type{a

b

c} one line
\stopTEXpage
\stoptext

\type

Would it be possible to have a new \typebufferinline that behaves such
as \type above (and has the same options in \setuptype)?

The most important part isn’t the suppression of line breaks inside, but
avoiding the addition of line breaks after and before the typed buffer.

I have been reading buff-ver.mkiv, but I’m afraid I cannot contribute
such a patch.

This is essential to have \xmlprettyprintinline and
\xmlprettyprintinlinetext in order to handle inline code in XML.

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] ligatures/substituation at word boundaries

2017-07-30 Thread Hans Hagen


On 7/30/2017 11:39 AM, Ulrike Fischer wrote:

Am Fri, 28 Jul 2017 23:21:18 +0200 schrieb Hans Hagen:


Is it possible to refer in fonts.handlers.otf.addfeature to the word
boundary? The luatex manual speaks of a virtual "left_boundary"
char, but I couldn't find a way to use it.



It is possible to check against spaces in contextual lookups. There
isn't something like left boundary. I added some test code to the beta
but keep in mind that this will only work with self-made features.


Thanks. It seems to work quite good and after some playing around I
also got the knack of the syntax.

A few questions:

1. "lookups = { 1 }," refers to the first lookup. Is it possible to
name the lookups and to refer to this name?.


no, because order matters


2. 0xFFFC refers more or less to the begin and end of line, right?
Why doesn't it interfere with hyphenations? I tried to get
   ab-
ab

and the second wasn't replaced (as wanted) and I wondered how it
worked.


0xFFFC is just the same as "anything other than glyph or discretionary"


3. Why is in the following example "abcd" not replaced by "12"?


i'll have a look at this (advancing in somewhat messy defined)


\startluacode
  fonts.handlers.otf.addfeature {
  name= "test-a",
  type= "chainsubstitution",
  lookups = {
  {
  type = "ligature",
  data = {
  ['1'] = { "a", "b" },
  ['2'] = { "c", "d" },
  },
  },
  },
  data = {
  rules = {
  {
  before  = { { " ", 0xFFFC } },
  current = { { "a" }, { "b" } },
  lookups = { 1 },
  },
  {
  current = { { "c" }, { "d" } },
  after   = { { 0xFFFC, " " } },
  lookups = { 1 },
  },
  },
  },
  }


\stopluacode

\definefontfeature[test-a][test-a=yes]

\startbuffer
xxx abcd abxcd xxx
\stopbuffer

\starttext

\typebuffer

\definedfont[file:dejavu-serif.ttf*default] \getbuffer \blank
\definedfont[file:dejavu-serif.ttf*default,test-a] \getbuffer \blank

\stoptext



--

-
  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] ligatures/substituation at word boundaries

2017-07-30 Thread Ulrike Fischer

Am Fri, 28 Jul 2017 23:21:18 +0200 schrieb Hans Hagen:

>> Is it possible to refer in fonts.handlers.otf.addfeature to the word
>> boundary? The luatex manual speaks of a virtual "left_boundary"
>> char, but I couldn't find a way to use it.

> It is possible to check against spaces in contextual lookups. There 
> isn't something like left boundary. I added some test code to the beta 
> but keep in mind that this will only work with self-made features. 

Thanks. It seems to work quite good and after some playing around I
also got the knack of the syntax.

A few questions: 

1. "lookups = { 1 }," refers to the first lookup. Is it possible to
name the lookups and to refer to this name?.

2. 0xFFFC refers more or less to the begin and end of line, right?
Why doesn't it interfere with hyphenations? I tried to get 
  ab-
ab 

and the second wasn't replaced (as wanted) and I wondered how it
worked. 

3. Why is in the following example "abcd" not replaced by "12"? 


\startluacode
 fonts.handlers.otf.addfeature {
 name= "test-a",
 type    = "chainsubstitution",
 lookups = {
 {
 type = "ligature",
 data = {
 ['1'] = { "a", "b" },
 ['2'] = { "c", "d" },
 },
 },
 },
 data = {
 rules = {
 {
 before  = { { " ", 0xFFFC } },
 current = { { "a" }, { "b" } },
 lookups = { 1 },
 },
 {
 current = { { "c" }, { "d" } },
 after   = { { 0xFFFC, " " } },
 lookups = { 1 },
 },
 },
 },
 }


\stopluacode

\definefontfeature[test-a][test-a=yes]

\startbuffer
xxx abcd abxcd xxx
\stopbuffer

\starttext

\typebuffer

\definedfont[file:dejavu-serif.ttf*default] \getbuffer \blank
\definedfont[file:dejavu-serif.ttf*default,test-a] \getbuffer \blank

\stoptext





-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] Problems with heads using margintext alternative

2017-07-29 Thread Rik


Willi, Pablo, and list,

Willi,

I understand that the overprint of the margin can be managed by changing 
the default layout. The left margin box displayed by \showframe using 
the default layout clearly shows the margin extending past the edge of 
the page.


I would think that the default layout should be usable as is, which for 
this purpose means that the defined text areas are contained within the 
page boundary. If the default layout is not intended to be usable, it 
should be so documented. I will gladly update the wiki if this is the 
case, but first I would like authoritative confirmation that this is the 
case.


Indeed, the extra line before the text occurs only when inter-paragraph 
whitespace is set and start/stop is used. This does indeed appear to be 
something that can be repaired.


Pablo,

The \inmargin commands do suffer from the same problem; you need simply 
change marg  to marg marg marg to see it. The problem is not that text 
is set outside the margin. It is all set in the margin. The problem is 
that the left margin is laid out over the page edge, and text set in the 
part of the margin that is off the page is lost.


--
Rik

On 2017-07-29 13:10, Pablo Rodriguez wrote:

On 07/23/2017 09:48 PM, Rik Kabel wrote:

The following example demonstrates two problems with
alternative=margintext in \setuphead:

  1. When used with start/stop sectioning, text following the title may
 be set on the wrong line.

Hi Rik,

the issue comes with \startparagraph and sectioning commands (other
margindata are fine):

 \setuphead
 [chapter]
 [alternative=margintext]
 \starttext
 \chapter{Chapter}
 \startparagraph\input jojomayer\stopparagraph
 \blank
 \inleft{marg}\startparagraph\input jojomayer\stopparagraph
 \blank
 \inright{marg}\startparagraph\input jojomayer\stopparagraph
 \blank
 \inouter{marg}\startparagraph\input jojomayer\stopparagraph
 \ininner{marg}\startparagraph\input jojomayer\stopparagraph
 \blank
 \inmargin{marg}\startparagraph\input jojomayer\stopparagraph
 \blank
 \inother{marg}\startparagraph\input jojomayer\stopparagraph
 \stoptext

But \inmargin has no problem with margin

  2. Without regard to the type of sectioning, margintext titles may
 spill over the left edge of the margin and beyond the page frame.

I cannot align them either. I don’t know what we may be missing here.

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] Problems with heads using margintext alternative

2017-07-29 Thread Pablo Rodriguez

On 07/23/2017 09:48 PM, Rik Kabel wrote:
> The following example demonstrates two problems with
> alternative=margintext in \setuphead:
> 
>  1. When used with start/stop sectioning, text following the title may
> be set on the wrong line.

Hi Rik,

the issue comes with \startparagraph and sectioning commands (other
margindata are fine):

\setuphead
[chapter]
[alternative=margintext]
\starttext
\chapter{Chapter}
\startparagraph\input jojomayer\stopparagraph
\blank
\inleft{marg}\startparagraph\input jojomayer\stopparagraph
\blank
\inright{marg}\startparagraph\input jojomayer\stopparagraph
\blank
\inouter{marg}\startparagraph\input jojomayer\stopparagraph
\ininner{marg}\startparagraph\input jojomayer\stopparagraph
\blank
\inmargin{marg}\startparagraph\input jojomayer\stopparagraph
\blank
\inother{marg}\startparagraph\input jojomayer\stopparagraph
\stoptext

But \inmargin has no problem with margin
>  2. Without regard to the type of sectioning, margintext titles may
> spill over the left edge of the margin and beyond the page frame.

I cannot align them either. I don’t know what we may be missing here.

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] Problems with headers using margintext alternative

2017-07-29 Thread Willi Egger

Hi,

I am not a guru, but I think that you should setup your pagesize properly. For 
the calculation of the paper-width margin widths are not used. The elements for 
calculations are the backspace and makeupwidth and the rest to sum up to the 
paperwidth as given in the definition of the papersize. Margins are kind of 
virtual. If text spills out of the margin then the backspace and the margin 
have to be adjusted.

e.g. 
\setuplayout
[location=middle,
 topspace=1.5cm,
 backspace=2cm,
 margin=18mm,
 width=middle]

Location=middle tells only, that the lettersized paper should placed centered 
onto the lettersized paper, oversized.

When I comment the line with insidesection= I get a consistent result i.e. that 
the text of the sections with start\stop in the text body starts one line to 
low compared to the traditional way of coding. 
Otherwise with this insidesection={\blank[-line]}  it appears, that the text 
next uneven section numbers is typeset at the expected place, where text next 
to even section numbers is not. — This might indeed be something which Hans 
should look at.


Best

Will
> On 29 Jul 2017, at 16:52, Rik <r...@panix.com> wrote:
> 
> Bump.
> 
> The problem persists two updates later.
> 
> In the picture below, the green line represents the edge of the page.
> 
> 
> 
> Does anyone else get the same result? 
> -- 
> Rik
> 
> On 2017-07-23 15:48, Rik Kabel wrote:
>> The following example demonstrates two problems with alternative=margintext 
>> in \setuphead:
>>  • When used with start/stop sectioning, text following the title may be 
>> set on the wrong line.
>>  • Without regard to the type of sectioning, margintext titles may spill 
>> over the left edge of the margin and beyond the page frame.
>> \setuppapersize
>> [letter]
>> [letter,oversized]
>> \setuplayout
>> [location={middle,middle}]
>> \showframe
>> \setuphead
>> [chapter]
>> [number=no,
>>  alternative=inmargin]
>> \setuphead
>> [section]
>> [
>>  alternative=margintext,
>>  insidesection={\blank[-line]},
>> ]
>> \starttext
>>   \starttitle
>>   [title={Problem description}]
>>   \bgroup
>>   \setupwhitespace[medium]
>>   \startparagraph
>>   This demonstrates two problems with
>>   \type{alternative=margintext} in \tex{setuphead}:
>>   \startitemize[packed,n]
>>   \startitem
>> When used with start/stop sectioning, text following the
>> title may be set on the wrong line.
>>   \stopitem
>>   \startitem
>> Without regard to the type of sectioning, \type{margintext}
>> titles may spill over the left edge of the margin and beyond
>> the page frame. (Oddly, \tex{paperwidth} is less than the
>> sum of \tex{makeupwidth} and the margin widths and
>> distances for both letter and A4 paper.)
>>   \stopitem
>>   \stopitemize
>>   \stopparagraph
>>   \startparagraph
>>   With start/stop sectioning, the text following the section
>>   title may begin one line below the start of the title. That
>>   can be remedied if there is no whitespace between paragraphs
>>   with \type{insidesection={\blank[-line]}}, but the remedy
>>   fails when there is whitespace, and increasing the correction
>>   has no effect. With traditional sectioning, the text appears
>>   baseline|-|aligned with the heading, as expected. The
>>   the correction has no effect in any case with traditional
>>   sectioning.
>>   \stopparagraph
>>   \startparagraph
>>   It makes no difference in any test how the paragraphs are
>>   delimited—blank lines, \tex{bpar}/\tex{epar},
>>   \tex{startparagraph}/\tex{stopparagraph}, or \tex{par}.
>>   \stopparagraph
>>   \startparagraph
>>   Tested with standalone beta 2017.07.17 00:20.
>>   \stopparagraph
>>   \egroup
>>   \page
>>   \startchapter
>>   [title={Start/stop sectioning}]
>>   \startsection[title={Mis\-cel\-la\-neous quo\-ta\-tions}]
>>   \startparagraph
>>   \input jojomayer
>>   \stopparagraph
>>   \startparagraph
>>   \input carrol \wordright{No indent no whitespace.}
>>   \stopparagraph
>>   \stopsection
>>   \bgroup
>>   \setupwhitespace[medium]
>>   \startsection[title={Miscellaneous quotations}]
>>   \startparagraph
>>   \input jojomayer
>>   \stopparagraph
>>   \startparagraph
>>   \input carrol \wordright{No indent medium whitespac

Re: [NTG-context] Problems with headers using margintext alternative

2017-07-29 Thread Rik


Bump.

The problem persists two updates later.

In the picture below, the green line represents the edge of the page.



Does anyone else get the same result?
--
Rik

On 2017-07-23 15:48, Rik Kabel wrote:


The following example demonstrates two problems with 
alternative=margintext in \setuphead:


 1. When used with start/stop sectioning, text following the title may
be set on the wrong line.
 2. Without regard to the type of sectioning, margintext titles may
spill over the left edge of the margin and beyond the page frame.

\setuppapersize
[letter]
[letter,oversized]
\setuplayout
[location={middle,middle}]
\showframe
\setuphead
[chapter]
[number=no,
 alternative=inmargin]
\setuphead
[section]
[
 alternative=margintext,
 insidesection={\blank[-line]},
]
\starttext
  \starttitle
  [title={Problem description}]
  \bgroup
  \setupwhitespace[medium]
  \startparagraph
  This demonstrates two problems with
  \type{alternative=margintext} in \tex{setuphead}:
  \startitemize[packed,n]
  \startitem
When used with start/stop sectioning, text following the
title may be set on the wrong line.
  \stopitem
  \startitem
Without regard to the type of sectioning, \type{margintext}
titles may spill over the left edge of the margin and beyond
the page frame. (Oddly, \tex{paperwidth} is less than the
sum of \tex{makeupwidth} and the margin widths and
distances for both letter and A4 paper.)
  \stopitem
  \stopitemize
  \stopparagraph
  \startparagraph
  With start/stop sectioning, the text following the section
  title may begin one line below the start of the title. That
  can be remedied if there is no whitespace between paragraphs
  with \type{insidesection={\blank[-line]}}, but the remedy
  fails when there is whitespace, and increasing the correction
  has no effect. With traditional sectioning, the text appears
  baseline|-|aligned with the heading, as expected. The
  the correction has no effect in any case with traditional
  sectioning.
  \stopparagraph
  \startparagraph
  It makes no difference in any test how the paragraphs are
  delimited—blank lines, \tex{bpar}/\tex{epar},
  \tex{startparagraph}/\tex{stopparagraph}, or \tex{par}.
  \stopparagraph
  \startparagraph
  Tested with standalone beta 2017.07.17 00:20.
  \stopparagraph
  \egroup
  \page
  \startchapter
  [title={Start/stop sectioning}]
  \startsection[title={Mis\-cel\-la\-neous quo\-ta\-tions}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{No indent no whitespace.}
  \stopparagraph
  \stopsection
  \bgroup
  \setupwhitespace[medium]
  \startsection[title={Miscellaneous quotations}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{No indent medium whitespace.}
  \stopparagraph
  \stopsection
  \egroup
  \bgroup
  \setupindenting[yes,small]
  \startsection[title={Miscellaneous quotations}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{Small indent no whitespace.}
  \stopparagraph
  \stopsection
  \egroup
  \bgroup
  \setupwhitespace[medium]
  \setupindenting[yes,small]
  \startsection[title={Miscellaneous quotations}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{Small indent medium whitespace.}
  \stopparagraph
  \stopsection
  \egroup
  \stopchapter
  \chapter{Traditional sectioning}
  \section{Mis\-cel\-la\-neous quo\-ta\-tions}
  \input jojomayer \par
  \input carrol  \wordright{No indent no whitespace.} \par
  No indent no whitespace. \par
  \bgroup
  \setupwhitespace[medium]
  \section{Miscellaneous quotations}
  \input jojomayer \par
  \input carrol \wordright{No indent medium whitespace.} \par
  \egroup
  \bgroup
  \setupindenting[yes,small]
  \section{Miscellaneous quotations}
  \input jojomayer \par
  \input carrol \wordright{Small indent no whitespace.} \par
  \egroup
  \bgroup
  \setupwhitespace[medium]
  \setupindenting[yes,small]
  \section{Miscellaneous quotations}
  \input jojomayer \par
  \input carrol \wordright{Small indent medium whitespace.} \par
  \egroup
\showlayout
\stoptext


--
Rik

Re: [NTG-context] ligatures/substituation at word boundaries

2017-07-28 Thread Hans Hagen


On 7/27/2017 8:09 PM, Ulrike Fischer wrote:

Is it possible to refer in fonts.handlers.otf.addfeature to the word
boundary? The luatex manual speaks of a virtual "left_boundary"
char, but I couldn't find a way to use it.

\startluacode
 fonts.handlers.otf.addfeature {
 name = "ltest",
 type = "ligature",
 data = {
 ['1'] = { "a", "b" },
 ['2'] = { "d", "a" },
 }
 }
\stopluacode

%how to replace only the start a

\startluacode
 fonts.handlers.otf.addfeature {
 name = "wtest",
 type = "ligature",
 data = {
 ['1'] = { "left_boundary", "a" },
 }
 }
\stopluacode

\definefontfeature[wtest][wtest=yes]
\definefontfeature[ltest][ltest=yes]
\starttext

 \definedfont[file:dejavu-serif.ttf*default]%


 {\addff{ltest} ababa\par}

 {\addff{wtest} ababa\par}


\stoptext
It is possible to check against spaces in contextual lookups. There 
isn't something like left boundary. I added some test code to the beta 
but keep in mind that this will only work with self-made features. (I 
have to check performance impact because I don't like making contextual 
lookups measurable slower due to some hardly used feature. First test 
show that it behaves ok.) In the test code below 0xFFFC is the boundary 
(this 0xFFFC check is the new thing). I adapted a few more things in the 
loader so best check that out too.


I'll upload a beta.

Hans

\starttext

\startluacode
fonts.handlers.otf.addfeature {
    name= "test-a",
type= "chainsubstitution",
lookups = {
{
type = "substitution",
data = {
["a"] = "A",
    ["b"] = "B",
["c"] = "C",
["d"] = "D",
},
},
{
type = "ligature",
data = {
['1'] = { "a", "b" },
['2'] = { "c", "d" },
},
},
},
data = {
rules = {
{
before  = { { " ", 0xFFFC } },
current = { { "a" }, { "b" } },
lookups = { 2 },
},
{
current = { { "c" }, { "d" } },
after   = { { 0xFFFC, " " } },
lookups = { 2 },
},
{
current = { { "a" } },
after   = { { "b" } },
lookups = { 1 },
    },
{
current = { { "c" } },
after   = { { "d" } },
lookups = { 1 },
},
},
},
}

fonts.handlers.otf.addfeature {
name= "test-b",
type= "chainsubstitution",
lookups = {
{
type = "ligature",
data = {
['1'] = { "a", "b" },
['2'] = { "c", "d" },
},
},
},
data = {
rules = {
{
-- the space is redundant as 0xFFFC contains it
before  = { { " ", 0xFFFC } },
current = { { "a" }, { "b" } },
    lookups = { 1 },
},
{
current = { { "c" }, { "d" } },
-- the space is redundant as 0xFFFC contains it
after   = { { 0xFFFC, " " } },
lookups = { 1 },
},
},
},
}

fonts.handlers.otf.addfeature {
name= "test-c",
type= "chainsubstitution",
lookups = {
{
type = "ligature",
data = {
['1'] = { "a", "b" },
['2'] = { "c", "d" },
},
},
},
data = {
rules = {
{
before  = { { " " } },
current = { { "a" }, { "b" } },
lookups = { 1 },
},
{
current = { { "c" }, { "d" } },
after   = { { " " } },

[NTG-context] ligatures/substituation at word boundaries

2017-07-27 Thread Ulrike Fischer

Is it possible to refer in fonts.handlers.otf.addfeature to the word
boundary? The luatex manual speaks of a virtual "left_boundary"
char, but I couldn't find a way to use it. 

\startluacode
fonts.handlers.otf.addfeature {
name = "ltest",
type = "ligature",
data = {
['1'] = { "a", "b" },
['2'] = { "d", "a" },
}
}
\stopluacode

%how to replace only the start a

\startluacode
    fonts.handlers.otf.addfeature {
name = "wtest",
type = "ligature",
data = {
['1'] = { "left_boundary", "a" },
}
}
\stopluacode

\definefontfeature[wtest][wtest=yes]
\definefontfeature[ltest][ltest=yes]
\starttext

\definedfont[file:dejavu-serif.ttf*default]%


{\addff{ltest} ababa\par}

{\addff{wtest} ababa\par}


\stoptext





-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] TwoColumns in two different languages, with alternate text on even and odd page.

2017-07-27 Thread Jean-Pierre Delange

Hi Marcello,

Marcello Urgo, Ph.D.
Assistant Professor
Manufacturing and Production Systems Lab.
Mechanical Engineering Department
POLITECNICO DI MILANO
Via La Masa, 1 - 20156 Milano

Phone +39 02 2399 8521
Fax +39 02 2399 8585
tecnologie.mecc.polimi.it
www.polimi.it

This message may contain confidential and/or otherwise reserved information and
is thus for use only by the intended recipient. If you received this in error,
please contact the sender and delete the e-mail and its attachments from your
computer. Thank you.
Il presente messaggio può contenere informazioni di carattere confidenziale e/o
riservate ed è quindi ad uso esclusivo del destinatario. Nel caso aveste
ricevuto questa e-mail per errore siete pregati di contattare immediatamente il
mittente e di cancellare il messaggio ed i suoi allegati dal vostro computer .
Grazie.

___
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!

Re: [NTG-context] Unable to switch math fonts

2017-07-25 Thread Sebastian L.


Thanks for your response Hans.

On 25/07/2017 00:12, Hans Hagen wrote:

On 7/24/2017 11:41 PM, Sebastian L. wrote:
Yes it helps, thanks; it explains why there was so little response to 
this. ;)
After some search I found regular style pictures of it. I was sure, 
that it was italic as standard, because that's what "modern" 
suggests: compability for current regulations (i.e. regular 
constants, italic variables) as well as an attractive style overall. 
But since Neo Euler seems to have no italic style, it is of no use 
for academic purposes, like in my case.


originally "euler" is a math companion font to "concrete" and it's not 
trivial to make en euler with all text styles (maybe some day the tex 
gyre project will give it a try) .. btw, the same is true for sans 
fonts: at some point one runs out of distinctive features


btw, it also fits with pagella (see type-imp-euler)


I don't want to argue with you Hans, as I know that you have better 
things to do. But for clarification: for a non-power TeX / CTX user this 
is information, that one usually doesn't get, as it makes deep interest 
in fonts creation necessary. On the other hand I don't expect you to be 
the one who teaches users about fonts, relationships or even the motives 
behind their creation. Thanks for your explanation though.


The story, to add to the subject of the mail, in case somebody 
searches the archive for this, is that I wasn't able to find out is 
how to change the math font only, as i like the standard font with 
\setupbodyfont[sans] as global setup but not the style of 
(non-modern) Euler.

I tried

\definefontfamily [mainface] [mm] [Xits Math]


most users who mess with fonts either use the selectfont mechanism or 
peek into the type-imp files to see how to set up a combination


I see. Well I just used search on the CTX wiki to find information about 
selectfont, but neither selectfont nor \selectfont gives me any result. 
If it's something TeX related, then I have to say that I didn't start to 
use CTX to get into TeX before. Anyways this is where it starts. This 
time it's type-imp, other topics will make it necessary to search other 
source files and then it starts over... This is something for you, the 
other coders or users who want to tweak CTX or its components, but a 
standard user will never do this, as he usually doesn't know where to 
look for info.



but this changes the whole typeface; not what I want.
So the trick is to define the standard font for the rest of the font 
variations. The standard font can be found out with \showbodyfont. At 
least that's what it suggests. But it gives you "modern-design" as 
font. When you use this within \definefontfamily then it gives you 
nothing, because the real id of the standard font is "modern". So to 
change the math font only and keep the main font standard, you have 
to use this command group (just in case somebody looks for it):


\definefontfamily [mainface] [rm] [Modern] % = serif
\definefontfamily [mainface] [ss] [Modern] % = sans
\definefontfamily [mainface] [tt] [Modern] % = mono (teletype)
\definefontfamily [mainface] [mm] [Xits Math] [rscale=1.03] % = math

But as this seems to be so trivial, that few people care, I really 
have to wonder why people who test CTX criticise the lack of 
documentation. We (especially who haven't been through LaTeX or even 
TeX) seem to be a minority.


In what sense?


In the sense that we (or let's even say just me) don't know where to 
look for information. I mean how many software do you have, where you go 
through its source files to understand how it does basic tasks? For me 
it's only CTX and as a consequence thereof Textadept, but for me that's 
already /too much/. So IMHO this must not be the future... Except for 
those who can't stop loving open source software that is usually made 
for a specific topic in the first place.




Anyway, there is quite some documentation (also about fonts) available 
(and the context distribution documentation section has examples).


There you are right. There is so much documentation that it's 
overwhelming. For instance documentation on fonts goes over several wiki 
pages. Suffice it to say you have to know what you are looking for, and 
not where. And the more you start searching, the more wiki pages you 
have to go through. A better approach might be to merge several pages 
that belong to a single chapter to one single wiki page. But that's just 
my opinion. Another example: I have found different links to manuals 
like Hoekwater's or Hagen's (on the wiki). But on several pages you get 
links to several versions of the manual, for instance I found one link 
to Hoekwater's 2003 version and to 2011 or 2013 version (I don't 
remember the exact dates as I deleted them both). Some time later I read 
that there is an online manual somewhere in the download area, that has 
to be built first. But there seems to be no manual for Windows use

Re: [NTG-context] Unable to switch math fonts

2017-07-24 Thread Hans Hagen


On 7/24/2017 11:41 PM, Sebastian L. wrote:
Yes it helps, thanks; it explains why there was so little response to 
this. ;)
After some search I found regular style pictures of it. I was sure, that 
it was italic as standard, because that's what "modern" suggests: 
compability for current regulations (i.e. regular constants, italic 
variables) as well as an attractive style overall. But since Neo Euler 
seems to have no italic style, it is of no use for academic purposes, 
like in my case.


originally "euler" is a math companion font to "concrete" and it's not 
trivial to make en euler with all text styles (maybe some day the tex 
gyre project will give it a try) .. btw, the same is true for sans 
fonts: at some point one runs out of distinctive features


btw, it also fits with pagella (see type-imp-euler)

The story, to add to the subject of the mail, in case somebody searches 
the archive for this, is that I wasn't able to find out is how to change 
the math font only, as i like the standard font with 
\setupbodyfont[sans] as global setup but not the style of (non-modern) 
Euler.

I tried

\definefontfamily [mainface] [mm] [Xits Math]


most users who mess with fonts either use the selectfont mechanism or 
peek into the type-imp files to see how to set up a combination



but this changes the whole typeface; not what I want.
So the trick is to define the standard font for the rest of the font 
variations. The standard font can be found out with \showbodyfont. At 
least that's what it suggests. But it gives you "modern-design" as font. 
When you use this within \definefontfamily then it gives you nothing, 
because the real id of the standard font is "modern". So to change the 
math font only and keep the main font standard, you have to use this 
command group (just in case somebody looks for it):


\definefontfamily [mainface] [rm] [Modern] % = serif
\definefontfamily [mainface] [ss] [Modern] % = sans
\definefontfamily [mainface] [tt] [Modern] % = mono (teletype)
\definefontfamily [mainface] [mm] [Xits Math] [rscale=1.03] % = math

But as this seems to be so trivial, that few people care, I really have 
to wonder why people who test CTX criticise the lack of documentation. 
We (especially who haven't been through LaTeX or even TeX) seem to be a 
minority.


In what sense?

Anyway, there is quite some documentation (also about fonts) available 
(and the context distribution documentation section has examples).



Cheers and thanks, S.
On 23/07/2017 21:22, Pablo Rodriguez wrote:

On 07/22/2017 03:16 AM, Sebastian L. wrote:

Hi, I have trouble with Neo Euler font after playing around with those
options.
[...]
I am pretty sure that before I started mixing the fonts in one single
document, Neo Euler was italic.

Does anybody have a clue what might have went wrong?

Hi Sebastian,

as far as I remember, Neo Euler is a regular font only
(https://github.com/khaledhosny/euler-otf).

Euler is an italic font and it might have the other regular, bold, bold
italic typefaces (I don’t know).

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
___




--

-
  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] Problems with headers using margintext alternative

2017-07-23 Thread Rik Kabel

The following example demonstrates two problems with 
alternative=margintext in \setuphead:


1. When used with start/stop sectioning, text following the title may
   be set on the wrong line.
2. Without regard to the type of sectioning, margintext titles may
   spill over the left edge of the margin and beyond the page frame.

   \setuppapersize
[letter]
[letter,oversized]
   \setuplayout
[location={middle,middle}]
   \showframe
   \setuphead
[chapter]
[number=no,
 alternative=inmargin]
   \setuphead
[section]
[
 alternative=margintext,
 insidesection={\blank[-line]},
]
   \starttext
  \starttitle
  [title={Problem description}]
  \bgroup
  \setupwhitespace[medium]
  \startparagraph
  This demonstrates two problems with
  \type{alternative=margintext} in \tex{setuphead}:
  \startitemize[packed,n]
  \startitem
When used with start/stop sectioning, text following the
title may be set on the wrong line.
  \stopitem
  \startitem
Without regard to the type of sectioning, \type{margintext}
titles may spill over the left edge of the margin and beyond
the page frame. (Oddly, \tex{paperwidth} is less than the
sum of \tex{makeupwidth} and the margin widths and
distances for both letter and A4 paper.)
  \stopitem
  \stopitemize
  \stopparagraph
  \startparagraph
  With start/stop sectioning, the text following the section
  title may begin one line below the start of the title. That
  can be remedied if there is no whitespace between paragraphs
  with \type{insidesection={\blank[-line]}}, but the remedy
  fails when there is whitespace, and increasing the correction
  has no effect. With traditional sectioning, the text appears
  baseline|-|aligned with the heading, as expected. The
  the correction has no effect in any case with traditional
  sectioning.
  \stopparagraph
  \startparagraph
  It makes no difference in any test how the paragraphs are
  delimited—blank lines, \tex{bpar}/\tex{epar},
  \tex{startparagraph}/\tex{stopparagraph}, or \tex{par}.
  \stopparagraph
  \startparagraph
  Tested with standalone beta 2017.07.17 00:20.
  \stopparagraph
  \egroup
  \page
  \startchapter
  [title={Start/stop sectioning}]
  \startsection[title={Mis\-cel\-la\-neous quo\-ta\-tions}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{No indent no whitespace.}
  \stopparagraph
  \stopsection
  \bgroup
  \setupwhitespace[medium]
  \startsection[title={Miscellaneous quotations}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{No indent medium whitespace.}
  \stopparagraph
  \stopsection
  \egroup
  \bgroup
  \setupindenting[yes,small]
  \startsection[title={Miscellaneous quotations}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{Small indent no whitespace.}
  \stopparagraph
  \stopsection
  \egroup
  \bgroup
  \setupwhitespace[medium]
  \setupindenting[yes,small]
  \startsection[title={Miscellaneous quotations}]
  \startparagraph
  \input jojomayer
  \stopparagraph
  \startparagraph
  \input carrol \wordright{Small indent medium whitespace.}
  \stopparagraph
  \stopsection
  \egroup
  \stopchapter
  \chapter{Traditional sectioning}
  \section{Mis\-cel\-la\-neous quo\-ta\-tions}
  \input jojomayer \par
  \input carrol  \wordright{No indent no whitespace.} \par
  No indent no whitespace. \par
  \bgroup
  \setupwhitespace[medium]
  \section{Miscellaneous quotations}
  \input jojomayer \par
  \input carrol \wordright{No indent medium whitespace.} \par
  \egroup
  \bgroup
  \setupindenting[yes,small]
  \section{Miscellaneous quotations}
  \input jojomayer \par
  \input carrol \wordright{Small indent no whitespace.} \par
  \egroup
  \bgroup
  \setupwhitespace[medium]
  \setupindenting[yes,small]
  \section{Miscellaneous quotations}
  \input jojomayer \par
  \input carrol \wordright{Small indent medium whitespace.} \par
  \egroup
   \showlayout
   \stoptext


--
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

Re: [NTG-context] generic font loader + luaotfload: 'nodepool' (a nil value)"

2017-07-14 Thread Hans Hagen


On 7/14/2017 8:26 PM, Ulrike Fischer wrote:

Am Fri, 14 Jul 2017 19:20:38 +0200 schrieb Hans Hagen:



local kern_injector = function (fillup, kern)
if fillup then
  local g = new_glue(kern)
  local s = getfield(g, "spec")
  setfield(s, "stretch", kern)
  setfield(s, "stretch_order", 1)
  return g
end
return new_kern(kern)
end


yes, i decided to limit the dependencies ... (also because the kern
allocator was a plug outside context)

you can use:

local new = node.direct.new

local g = new("glue")
setfield(g, "stretch", kern)
setfield(g, "stretch_order", 1)


And what I should do about the "return new_kern(kern)"?


local g = new("kern")
setfield(g,"kern",kern)


I tried various variants and got results from no letterspacing to
"invalid node type id" to " This can't happen (invalid node found in
discretionary)." to a luatex crash:


you can't put glue in discs so your letterspacing code should use kerns, 
not glue



-- UF changed 2017-07-14
local new = node.direct.new

local kern_injector = function (fillup, kern)
  if fillup then
local g = new("glue")
setfield(g, "stretch", kern)
setfield(g, "stretch_order", 1)
return g
  end
  --return new_kern(kern) --??
  --
end
--





--

-
  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] generic font loader + luaotfload: 'nodepool' (a nil value)"

2017-07-14 Thread Ulrike Fischer

Am Fri, 14 Jul 2017 19:20:38 +0200 schrieb Hans Hagen:

>> 
>> local kern_injector = function (fillup, kern)
>>if fillup then
>>  local g = new_glue(kern)
>>  local s = getfield(g, "spec")
>>  setfield(s, "stretch", kern)
>>  setfield(s, "stretch_order", 1)
>>  return g
>>end
>>return new_kern(kern)
>> end
> 
> yes, i decided to limit the dependencies ... (also because the kern 
> allocator was a plug outside context)
> 
> you can use:
> 
>local new = node.direct.new
> 
>local g = new("glue")
>setfield(g, "stretch", kern)
>setfield(g, "stretch_order", 1)

And what I should do about the "return new_kern(kern)"?

I tried various variants and got results from no letterspacing to
"invalid node type id" to " This can't happen (invalid node found in
discretionary)." to a luatex crash:

-- UF changed 2017-07-14
local new = node.direct.new

local kern_injector = function (fillup, kern)
 if fillup then
   local g = new("glue")
   setfield(g, "stretch", kern)
   setfield(g, "stretch_order", 1)
   return g
 end
 --return new_kern(kern) --??
 --
end
--


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] No cross-references in scrollmode

2017-07-13 Thread Andreas Becker

Hello,

when I pipe a file to context, it cannot resolve references, e. g. to figures or
chapters:

cat source.tex | context --pipe

Instead of the number, "??" is printed in the PDF document.

A minimal example is:
\ref[reference] \placefigure[][reference]{}{}

The command line output is like this:

[...]
mtx-context | entering scrollmode, end job with \endThis is LuaTeX, Version 
0.95.0 (TeX Live 2016/Arch Linux) 
 system commands enabled.
[...]
*
*
*(Please type a command or say `\end')
*structure   > sectioning > title @ level 2 : 0.0 -> Si(111) preparation

*(Please type a command or say `\end')
*
*
*
*
*
*
*
*
*
*references  > unknown reference '[][fig:si-oxide]'
[...]

Kind regards,
Andreas Becker
___
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] Problem with lucida fonts (again)

2017-06-29 Thread Eric Détrez


On 6/28/2017 9:21 AM, Eric Détrez wrote:


Here is an exemple, I show size 30 to see the differences but the size 
doesn't change the behaviour.


\starttext
\setupbodyfont[30pt]
texte $math$

\setupbodyfont[lucidaot,30pt]
texte $math$

\setupbodyfont[lucida,30pt]
texte $math$
\stoptext


I join 2 pdf with an "old" version of context (texlive 2016) and the 
last stable.

Le 29-06-2017 09:56, Hans Hagen a écrit :

i fixed something in the next beta for these type 1 fonts (with
slightly weird encodings)



I didn't have the open type lucidas, had to buy them.
They work fine

**
\starttext
\setupbodyfont[30pt]
texte $math'$

\setupbodyfont[lucidaot,30pt]
texte $math'$

\setupbodyfont[lucida,30pt]
texte $math'$

\stoptext
**

The ' was ugly in the "stable " version (too high) for lucidas, much 
better now.

But the Lucida's text is still crappy in type1 version.

So ...
I guess type1 fonts are messy (Lucida's or all of them ?)
--
Eric Détrez
Informatique
Lycée Faidherbe, Lille
http://eric-detrez.fr

sansnom-3.pdf
Description: Adobe PDF document
___
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] Problem with lucida fonts (again)

2017-06-29 Thread Hans Hagen


On 6/29/2017 2:11 PM, MF wrote:

i fixed something in the next beta for these type 1 fonts (with
slightly
weird encodings)



I'm getting some weird errors with the most recent versions of ConTeXt
too.

Currently I can't send you a sample to reproduce the problem but I can
only describe what happens with a big XML file of mine under these 3
conditions:

1 - latest beta (2017-06-29 9:32), with some OTF fonts (Garamond
Premier Pro, Myriad Pro, Quivira): the program ends with this error

luatex warning  > nodes: attempt to copy free glyph (f) node 67776,
ignored
! error:  (linebreak): invalid list tail, probably missing glue


2 - latest beta (2017-06-29 9:32), without OTF fonts: the program works


3 - ConTeXt 2016.05.17 from Debian repositories, with the fonts of case
1: the program works

i really need an example


-
  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] Problem with lucida fonts (again)

2017-06-29 Thread MF

> i fixed something in the next beta for these type 1 fonts (with
> slightly 
> weird encodings)
> 

I'm getting some weird errors with the most recent versions of ConTeXt
too.

Currently I can't send you a sample to reproduce the problem but I can
only describe what happens with a big XML file of mine under these 3
conditions:

1 - latest beta (2017-06-29 9:32), with some OTF fonts (Garamond
Premier Pro, Myriad Pro, Quivira): the program ends with this error

luatex warning  > nodes: attempt to copy free glyph (f) node 67776,
ignored
! error:  (linebreak): invalid list tail, probably missing glue


2 - latest beta (2017-06-29 9:32), without OTF fonts: the program works


3 - ConTeXt 2016.05.17 from Debian repositories, with the fonts of case
1: the program works

Sorry for such an imprecise feedback,
Best greetings,
Massi
___
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] Problem with lucida fonts (again)

2017-06-29 Thread Hans Hagen


On 6/28/2017 9:21 AM, Eric Détrez wrote:

Le 27-06-2017 23:00, Henri Menke a écrit :

You're this guy, right?

https://mailman.ntg.nl/pipermail/ntg-context/2016/087522.html
https://tex.stackexchange.com/questions/338849

Sorry, but as last time, we can't help you without you posting a
reproducible example.  The
following works fine for me on TL2016, TL2017, and latest beta.

\setupbodyfont[lucidaot]

\starttext

\input knuth

\stoptext


Here is an exemple, I show size 30 to see the differences but the size 
doesn't change the behaviour.


\starttext
\setupbodyfont[30pt]
texte $math$

\setupbodyfont[lucidaot,30pt]
texte $math$

\setupbodyfont[lucida,30pt]
texte $math$
\stoptext


I join 2 pdf with an "old" version of context (texlive 2016) and the 
last stable.


You'll see that lucidaot has an effect, it uses cm fonts but without 
italic in math

lucida shifts lhe letters in text, not in math.
i fixed something in the next beta for these type 1 fonts (with slightly 
weird encodings)


-
  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] Problem with lucida fonts (again)

2017-06-27 Thread Henri Menke

You're this guy, right?

https://mailman.ntg.nl/pipermail/ntg-context/2016/087522.html
https://tex.stackexchange.com/questions/338849

Sorry, but as last time, we can't help you without you posting a reproducible 
example.  The
following works fine for me on TL2016, TL2017, and latest beta.

\setupbodyfont[lucidaot]

\starttext

\input knuth

\stoptext

On Tue, 2017-06-27 at 21:45 +0200, Eric Détrez wrote:
> Hello
> 
> I already had this problem with lucida fonts.
> When I type text the letter are shifted : "b" becomes "a", "c" becomes 
> "b", ...
> I solved it with using the stable version.
> 
> I updated my system and I downloaded again context-minimal.
> The problem came back with both versions (last or stable).
> ConTeXt  ver: 2017.05.15 21:48 MKIV beta  fmt: 2017.6.27  int: 
> english/english
> ConTeXt  ver: 2017.06.27 18:05 MKIV beta  fmt: 2017.6.27  int: 
> english/english
> 
> If I use the tex-live version all is fine
> ConTeXt  ver: 2016.05.17 19:20 MKIV current  fmt: 2017.6.27  int: 
> english/english
> 
> It seems current version does provide a beta.
> 
> I'm afraid I'll can use Lucida soon
> 
___
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] Problem with lucida fonts (again)

2017-06-27 Thread Eric Détrez


Hello

I already had this problem with lucida fonts.
When I type text the letter are shifted : "b" becomes "a", "c" becomes 
"b", ...

I solved it with using the stable version.

I updated my system and I downloaded again context-minimal.
The problem came back with both versions (last or stable).
ConTeXt  ver: 2017.05.15 21:48 MKIV beta  fmt: 2017.6.27  int: 
english/english
ConTeXt  ver: 2017.06.27 18:05 MKIV beta  fmt: 2017.6.27  int: 
english/english


If I use the tex-live version all is fine
ConTeXt  ver: 2016.05.17 19:20 MKIV current  fmt: 2017.6.27  int: 
english/english


It seems current version does provide a beta.

I'm afraid I'll can use Lucida soon

--
Eric Détrez
Informatique
Lycée Faidherbe, Lille
http://eric-detrez.fr
___
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] Footnotes in paragraph form + annotating them in margin

2017-06-20 Thread Michelle Rodzis

Dear list,


in my document I have several kinds of footnotes including footnotes in
paragraph form. In some cases I need to annotate these. The annotation
should to appear in the outer margin of the page and in line with the
annotated footnote.

I tried a few different approaches, but none yields exactly the result I
want to obtain:


1. I defined a seperate footnote type for the annotations according to
the wiki, but the annotations are centered in the margin and not in line
with the footnote(s) they refer to.


2. As suggested on the mailinglist some time ago, I tested

\myCustomFootnote{Text.\margintext[scope=local]{Annotation.}}

but since I have \definenote[myCustomNote][paragraph=yes], no text in
the margin is displayed unless I delete this parameter (which
unfortunately is no option for my document layout).


Do you have any ideas how to solve this?


Thanks in advance and best regards,
Michelle


___
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] Bug regarding placement and size of primes

2017-06-15 Thread Hans Hagen

othing to do with special 
fonts of hybrid version or whatever. You get the problem using 
standard Latin Modern or any font else. Simply try
latin modern has all kind of issues ... and it's inconsistent with 
cambria, other gyre fonts etc ... in a decade of luatex and open type 
math fonts i captured a lot of font issues in runtiem fixes but that 
will always give side effects


so, i can fix somethign for you with lm and then someone else 
complains about lucida etc etc




I am not using Latin Modern. I only mentioned that because I wanted to 
stress that I am not referring to exotic fonts. (I totally agree on 
you regarding Latin Modern; I think Cambria should be the reference 
since this font is the font that established the opentype math standard.)
In fact I am using Minion Math (which is a really stunning font) or 
Stix 2. There had been no problems in those fonts with primes in the 
betas of the last weeks. And as Mikeal suggests the problems are 
resolved if I could use LuaTeX 1.05.


So in fact the only thing I am complaining about is that everything 
worked one or two betas ago until it is „broken“ in the newest beta 
since this one seems to be based on code that requires LuaTeX 1.05 
(which makes sense of course since this will be the upcoming release) 
that is not shipped alongside the beta. So I am not able to understand 
why code is provided in the beta that requires a LuaTeX version that 
is not shipped alongside (and especially in view of the fact that we 
had a perfectly working beta regarding primes last week; this means I 
think it would have been a great idea to wait including the newest 
code for primes that requires LuaTeX 1.05 until LuaTeX 1.05 is shipped 
with the beta too). :-)


as i explained before, primes are a mess conceptually .. not a real 
character and not a proper superscript candidate either so when one 
corrects for one aspect one has to fight the other


also, we have unicode and therefore multiple primes are one character

i simply have no time (nor motivation) to spend days on some 
temporary solution that will be complained about also and discarded a 
while later anyway


I perfectly understand that. And every work regarding primes is done, 
as I think. But one way to make us of it would be to use the beta of 
last week (or maybe the week before) or the most recent one together 
with LuaTeX 1.05. But I have no idea how to make use of that ways. :-)


So I am simply asking: How can I use older betas or how can I get the 
source of LuaTeX 1.05 on a Mac and compile it?
Mojca is setting up the build bots so one of these days there will be 
binaries.


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] Bug regarding placement and size of primes

2017-06-15 Thread Mathias Schickel

e provided to compile the 
>>> source of LuaTeX for every OS that can be used simply).
>> 
>> then just use old versions and then accept the bugs and limitations in those 
>> versions
> 
> How can I get the beta of last week or the week before? In those betas you 
> have not yet included the new code (for use with LuaTeX 1.05) and everything 
> worked really fine. The --context=current garden version has several bugs 
> regarding primes you have solved in the mentioned betas. So it would make no 
> sense at all to use this version. I would need one of the older betas or the 
> most recent one with LuaTeX 1.05.
> 
>> 
>>> And (to repeat myself) the problem has nothing to do with special fonts of 
>>> hybrid version or whatever. You get the problem using standard Latin Modern 
>>> or any font else. Simply try
>> latin modern has all kind of issues ... and it's inconsistent with cambria, 
>> other gyre fonts etc ... in a decade of luatex and open type math fonts i 
>> captured a lot of font issues in runtiem fixes but that will always give 
>> side effects
>> 
>> so, i can fix somethign for you with lm and then someone else complains 
>> about lucida etc etc
>> 
> 
> I am not using Latin Modern. I only mentioned that because I wanted to stress 
> that I am not referring to exotic fonts. (I totally agree on you regarding 
> Latin Modern; I think Cambria should be the reference since this font is the 
> font that established the opentype math standard.)
> In fact I am using Minion Math (which is a really stunning font) or Stix 2. 
> There had been no problems in those fonts with primes in the betas of the 
> last weeks. And as Mikeal suggests the problems are resolved if I could use 
> LuaTeX 1.05.
> 
> So in fact the only thing I am complaining about is that everything worked 
> one or two betas ago until it is „broken“ in the newest beta since this one 
> seems to be based on code that requires LuaTeX 1.05 (which makes sense of 
> course since this will be the upcoming release) that is not shipped alongside 
> the beta. So I am not able to understand why code is provided in the beta 
> that requires a LuaTeX version that is not shipped alongside (and especially 
> in view of the fact that we had a perfectly working beta regarding primes 
> last week; this means I think it would have been a great idea to wait 
> including the newest code for primes that requires LuaTeX 1.05 until LuaTeX 
> 1.05 is shipped with the beta too). :-)
> 
>> as i explained before, primes are a mess conceptually .. not a real 
>> character and not a proper superscript candidate either so when one corrects 
>> for one aspect one has to fight the other
>> 
>> also, we have unicode and therefore multiple primes are one character
>> 
>> i simply have no time (nor motivation) to spend days on some temporary 
>> solution that will be complained about also and discarded a while later 
>> anyway
> 
> I perfectly understand that. And every work regarding primes is done, as I 
> think. But one way to make us of it would be to use the beta of last week (or 
> maybe the week before) or the most recent one together with LuaTeX 1.05. But 
> I have no idea how to make use of that ways. :-)
> 
> So I am simply asking: How can I use older betas or how can I get the source 
> of LuaTeX 1.05 on a Mac and compile it?
> 
>> Hans
> 
> Mathias
> 
> 
>> 
>> -
>>  Hans Hagen | PRAGMA ADE
>>  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>>   tel: 038 477 53 69 | www.pragma-ade.nl <http://www.pragma-ade.nl/> | 
>> www.pragma-pod.nl <http://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 <mailto:ntg-context@ntg.nl> / 
> http://www.ntg.nl/mailman/listinfo/ntg-context 
> <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage  : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / 
> http://context.aanhet.net <http://context.aanhet.net/>
> archive  : https://bitbucket.org/phg/context-mirror/commits/ 
> <https://bitbucket.org/phg/context-mirror/commits/>
> wiki : http://contextgarden.net <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] typesetting serial letters in Context

2017-06-15 Thread r . ermers

I still cannot generate letters from my xml database, although there is 
apparently a solution to use csv files through lua code 
(https://tex.stackexchange.com/questions/72735/how-to-create-form-letters-from-spreadsheet-data-in-context
 
<https://tex.stackexchange.com/questions/72735/how-to-create-form-letters-from-spreadsheet-data-in-context>).

Your help is much appreciated!

Yet I found out how to generate certificates with backgrounds changing 
according to the candidate's course level, which I would like to share with you:

%

participants.xml



Janssen
Piet
P.
levelA
1 june 2017
Nijmegen





certificates.tex

\setuppapersize[A4,landscape][A4,landscape]
\setuplayout[width=170mm,topspace=60mm,rightmargindistance=2.5mm]
\definelayer[module][width=\paperwidth,height=\paperheight,preset=middle]
\useexternalfigure[levelA][sjablonen/CourseLevelA.pdf]
\resetlayer[level]{}

\setupbackgrounds[page][background={level}]

\startxmlsetups xml:setups
\xmlsetsetup{#1}{contacts}{xml:contacts}
\xmlsetsetup{#1}{contact}{xml:contacts:contact}
\stopxmlsetups

\xmlregistersetup{xml:setups}

\startxmlsetups xml:contacts
 \xmlflush{#1}
\stopxmlsetups

\startxmlsetups xml:contacts:contact

\setlayer[module][][]{\externalfigure[\xmltext{#1}{/courselevel}][factor=550]}

\startalignment [middle]
\color[red]{{\tfd \xmltext{#1}{/initials}} {\tfd 
\xmltext{#1}{/formalname}}\par

\blank[10mm]

{\ss \xmltext{#1}{/city}, \xmltext{#1}{/coursedate}}

\stopalignment
\page[yes]
\stopxmlsetups

\starttext
\xmlprocessfile{main}{./participants.xml}{}

\stoptext

Kind regards,

Robert


> Op 13 jun. 2017, om 15:59 heeft r.erm...@hccnet.nl het volgende geschreven:
> 
> I can take the information out of the nodes. The main problem is to use them 
> in a layout and in a sequences other the one they appear in the xml data file.
> 
> In the current (mkii) file I have something like this: 
> \midaligned{\XMLflush{formalname}, \XMLflush{informalname}}.
> 
> 
> Another point on my wishlist is to change the background of the certificate 
> depending on the type of certificate. In mkii I manage to do this as follows:
> 
> File: participants.xml
> 
> 
> Janssen
> Piet
> levelA
> 
> 
> 
> certificates.tex:
> \resetlayer[module]{}
> \setlayer[module][][]{\externalfigure[\XMLflush{courselevel}[width=\paperwidth,height=\paperheight]}
> 
> \useexternalfigure[levelA][sjablonen/backgroundlevelA.pdf]
> 
> Help is very much appreciated!
> 
> Robert
> 
> 
>> Op 13 jun. 2017, om 09:53 heeft luigi scarso <luigi.sca...@gmail.com> het 
>> volgende geschreven:
>> 
>> On Tue, Jun 13, 2017 at 9:40 AM,  <r.erm...@hccnet.nl> wrote:
>>> Hello all,
>>> 
>>> I have been using Context mkii with the x-corres.mkii module for a number 
>>> of years now, for many different purposes (mailings, certificates, etc). 
>>> The module works with an xml (actually rng) file with the following 
>>> structure:
>>> 
>>> 
>>>   
>>>   Janssen
>>>   Piet
>>>   
>>> 
>>> 
>>> The contents of each item is grabbed and put in the document by means of 
>>> the command \XMLflush{formalname}.
>>> 
>>> I would like to shift to mkiv now with all its possibilities.
>>> 
>>> Yet there is no x-corres.mkiv. Who can help me out?
>>> 
>> I don't remember x-corres.mkiv, but
>> mkiv has a guide
>> tex/texmf-context/doc/context/documents/general/manuals/xml-mkiv.pdf
>> 
>> -- 
>> luigi
>> ___
>> 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
> ___

___
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] typesetting serial letters in Context

2017-06-13 Thread r . ermers

I can take the information out of the nodes. The main problem is to use them in 
a layout and in a sequences other the one they appear in the xml data file.

In the current (mkii) file I have something like this: 
\midaligned{\XMLflush{formalname}, \XMLflush{informalname}}.


Another point on my wishlist is to change the background of the certificate 
depending on the type of certificate. In mkii I manage to do this as follows:

File: participants.xml


Janssen
Piet
levelA



certificates.tex:
\resetlayer[module]{}
\setlayer[module][][]{\externalfigure[\XMLflush{courselevel}[width=\paperwidth,height=\paperheight]}

\useexternalfigure[levelA][sjablonen/backgroundlevelA.pdf]

Help is very much appreciated!

Robert


> Op 13 jun. 2017, om 09:53 heeft luigi scarso <luigi.sca...@gmail.com> het 
> volgende geschreven:
> 
> On Tue, Jun 13, 2017 at 9:40 AM,  <r.erm...@hccnet.nl> wrote:
>> Hello all,
>> 
>> I have been using Context mkii with the x-corres.mkii module for a number of 
>> years now, for many different purposes (mailings, certificates, etc). The 
>> module works with an xml (actually rng) file with the following structure:
>> 
>> 
>>
>>Janssen
>>Piet
>>
>> 
>> 
>> The contents of each item is grabbed and put in the document by means of the 
>> command \XMLflush{formalname}.
>> 
>> I would like to shift to mkiv now with all its possibilities.
>> 
>> Yet there is no x-corres.mkiv. Who can help me out?
>> 
> I don't remember x-corres.mkiv, but
> mkiv has a guide
> tex/texmf-context/doc/context/documents/general/manuals/xml-mkiv.pdf
> 
> -- 
> luigi
> ___
> 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] Bug regarding placement and size of primes

2017-06-12 Thread Mathias Schickel

> Am 12.06.2017 um 17:10 schrieb Hans Hagen <pra...@wxs.nl>:
> 
> On 6/12/2017 4:54 PM, Mathias Schickel wrote:
>>> the alternative is that i waste time again and again on getting something 
>>> to work for all fonts and all combinations which leads to a mess that i 
>>> then need to maintain without any gain
>> At first: Thank you very much for your work!
>>> so, i decided to follow a route that works for most fonts / cases and not 
>>> some messy hybrid solution (and i don't want a different setup or bag of 
>>> tricks for each font that is out there as that is a long term no-go)
>> But I have to contradict you here: It has nothing to do with special or 
>> hybrid fonts. The problem persists at present (using the LuaTeX version that 
>> is shipped with the Garden version) in /all/ fonts. The primes are not 
>> rendered as they should in /any/ font I tried out.
>> As Mikael told me, you optimised the code for LuaTeX 1.05 which seems to be 
>> terminated September this year. But until then the output of primes will be 
>> not correct. I have no possibility to switch back to the current (non-beta) 
>> version of ConTeXt, because this version contains the bugs with primes you 
>> have already resolved.
> 
> there will probably be a 1.0.5 one of these days (also for other reasons) but 
> Mojca has to configure the garden compile farm
> 

Okay, that would be great. But could you tell me how I can get the files and 
compile them? Mikael did write me instructions that work for Linux, but I am on 
MacOS. My problem would be solved if I could get the source and compile LuaTeX 
1.05 on my own on MacOS. :-)

>> This means that ConTeXt is not usable for me until LuaTeX 1.05 will be 
>> released or until I am able to compile the source of LuaTeX 1.05 on my own. 
>> Some of the latest betas (the version one or two weeks ago) did solve all 
>> problems regarding primes. The problem I am referring to rose up in the most 
>> recent betas. As Mikael told me, this is because you introduced new code to 
>> work with LuaTeX 1.05. This is very nice, but because this version is not 
>> yet released, this decision is questionable, since this makes ConTeXt 
>> unusable until this release (if you need primes).
>> So I appreciate your hard work, but I would be nice to have a version that 
>> runs with the current LuaTeX version of the beta of ConTeXt (or 
>> alternatively it would be nice if instructions are provided to compile the 
>> source of LuaTeX for every OS that can be used simply).
> 
> then just use old versions and then accept the bugs and limitations in those 
> versions

How can I get the beta of last week or the week before? In those betas you have 
not yet included the new code (for use with LuaTeX 1.05) and everything worked 
really fine. The --context=current garden version has several bugs regarding 
primes you have solved in the mentioned betas. So it would make no sense at all 
to use this version. I would need one of the older betas or the most recent one 
with LuaTeX 1.05.

> 
>> And (to repeat myself) the problem has nothing to do with special fonts of 
>> hybrid version or whatever. You get the problem using standard Latin Modern 
>> or any font else. Simply try
> latin modern has all kind of issues ... and it's inconsistent with cambria, 
> other gyre fonts etc ... in a decade of luatex and open type math fonts i 
> captured a lot of font issues in runtiem fixes but that will always give side 
> effects
> 
> so, i can fix somethign for you with lm and then someone else complains about 
> lucida etc etc
> 

I am not using Latin Modern. I only mentioned that because I wanted to stress 
that I am not referring to exotic fonts. (I totally agree on you regarding 
Latin Modern; I think Cambria should be the reference since this font is the 
font that established the opentype math standard.)
In fact I am using Minion Math (which is a really stunning font) or Stix 2. 
There had been no problems in those fonts with primes in the betas of the last 
weeks. And as Mikeal suggests the problems are resolved if I could use LuaTeX 
1.05.

So in fact the only thing I am complaining about is that everything worked one 
or two betas ago until it is „broken“ in the newest beta since this one seems 
to be based on code that requires LuaTeX 1.05 (which makes sense of course 
since this will be the upcoming release) that is not shipped alongside the 
beta. So I am not able to understand why code is provided in the beta that 
requires a LuaTeX version that is not shipped alongside (and especially in view 
of the fact that we had a perfectly working beta regarding primes last week; 
this means I think it would have been a great idea to wait including the newest 
code

[NTG-context] Fwd: Re: Bug regarding placement and size of primes

2017-06-12 Thread Hans Hagen

 Forwarded Message 
Subject: Re: [NTG-context] Bug regarding placement and size of primes
Date: Mon, 12 Jun 2017 17:10:25 +0200
From: Hans Hagen <pra...@wxs.nl>
To: Mathias Schickel <m...@fa.uni-tuebingen.de>

On 6/12/2017 4:54 PM, Mathias Schickel wrote:
the alternative is that i waste time again and again on getting 
something to work for all fonts and all combinations which leads to a 
mess that i then need to maintain without any gain

At first: Thank you very much for your work!

so, i decided to follow a route that works for most fonts / cases and 
not some messy hybrid solution (and i don't want a different setup or 
bag of tricks for each font that is out there as that is a long term 
no-go)

But I have to contradict you here: It has nothing to do with special or 
hybrid fonts. The problem persists at present (using the LuaTeX version 
that is shipped with the Garden version) in /all/ fonts. The primes are 
not rendered as they should in /any/ font I tried out.
As Mikael told me, you optimised the code for LuaTeX 1.05 which seems to 
be terminated September this year. But until then the output of primes 
will be not correct. I have no possibility to switch back to the current 
(non-beta) version of ConTeXt, because this version contains the bugs 
with primes you have already resolved.

there will probably be a 1.0.5 one of these days (also for other 
reasons) but Mojca has to configure the garden compile farm

This means that ConTeXt is not usable for me until LuaTeX 1.05 will be 
released or until I am able to compile the source of LuaTeX 1.05 on my 
own. Some of the latest betas (the version one or two weeks ago) did 
solve all problems regarding primes. The problem I am referring to rose 
up in the most recent betas. As Mikael told me, this is because you 
introduced new code to work with LuaTeX 1.05. This is very nice, but 
because this version is not yet released, this decision is questionable, 
since this makes ConTeXt unusable until this release (if you need primes).

So I appreciate your hard work, but I would be nice to have a version 
that runs with the current LuaTeX version of the beta of ConTeXt (or 
alternatively it would be nice if instructions are provided to compile 
the source of LuaTeX for every OS that can be used simply).

then just use old versions and then accept the bugs and limitations in 
those versions

And (to repeat myself) the problem has nothing to do with special fonts 
of hybrid version or whatever. You get the problem using standard Latin 
Modern or any font else. Simply try
latin modern has all kind of issues ... and it's inconsistent with 
cambria, other gyre fonts etc ... in a decade of luatex and open type 
math fonts i captured a lot of font issues in runtiem fixes but that 
will always give side effects

so, i can fix somethign for you with lm and then someone else complains 
about lucida etc etc

as i explained before, primes are a mess conceptually .. not a real 
character and not a proper superscript candidate either so when one 
corrects for one aspect one has to fight the other

also, we have unicode and therefore multiple primes are one character

i simply have no time (nor motivation) to spend days on some temporary 
solution that will be complained about also and discarded a while later 
anyway

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] Position of prime for derivatives

2017-06-07 Thread Mikael P. Sundqvist

On Wed, Jun 7, 2017 at 9:57 PM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
> On Mon, Jun 5, 2017 at 11:00 PM, Hans Hagen <pra...@wxs.nl> wrote:
>> On 6/4/2017 11:06 PM, Otared Kavian wrote:
>>>
>>> Hi Mikael,
>>>
>>> Indeed your observation is correct, but using \over instead of \frac
>>> yields the correct behavior. Please try the following sample:
>>>
>>> %%% begin derivatives-prime-4.tex
>>> \setupbodyfont[lucidaot]
>>>
>>> \starttext
>>>
>>> Compare the position of the prime sign in $f'/g$ in these two expressions:
>>> the first one using \type{{... \over ...}}
>>> \startformula
>>> \left({f \over g}\right)' = {f' \over g} - {f \over g^2}g'
>>> \stopformula
>>> (which yields a correct position of the prime for $f'$ in $f'/g$), and the
>>> second using \type{\frac{...}{...}}
>>> \startformula
>>> \left(\frac{f}{g} \right)' = \frac{f'}{g} - \frac{f}{g^2} g'
>>> \stopformula
>>> which yields a prime sign for $f'$ a little bit lower.
>>>
>>> \stoptext
>>> %%% end derivatives-prime-4.tex
>>
>> The problem with primes is that it's a real mess, conceptually as well as in
>> fonts.
>>
>> - we need to deal with not only one prime but also with double, tripple and
>> quadruple ones and they need to become proper unicode symbols too
>>
>> - fonts have one, two or three sizes, often inconsistent and with funny
>> dimensions, onlyt the text size can be trusted
>>
>> - we cannot use prime as nuclues as it can be combined with a subscript
>>
>> - but it isn't designed as a script symbol and is already raised (somewhat)
>>
>> - so we have to deal with a good old tex / fonts / plain inheritance,
>> unicode but also want to avoid active character and parsing mess etc.
>>
>> I tried several approaches and it's hard to come up with a general solution
>> that suits all fonts.
>>
>> Now, the bad is that when we use a superscript with a smashed virtual
>> characters we end up in script choice mess with primes being one step too
>> small.
>>
>> So, I decided to follow a different route and extend luatex with a sizeless
>> super/subscript feature so that we can handle such weird cases (there might
>> be more).
>>
>> This also means that the primes get larger. I only use the text size prime
>> and scale that down for the other sizes i.e. no stty for primes as they are
>> such a mess) but we can live with that.
>>
>> The good news is that it gets better but the bad news is that you have to
>> wait till we release luatex 1.0.5 (planned for the ctx meeting but we might
>> do an intermediate garden release anyway).
>>
>> btw, with \frac you get cramped styles and these have different positioning.
>> Such is life.
>>
>> 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
>> ___
>
> Again, thanks.
>
> In 2017.06.06 13:22 something is still not correct.
>
> The input file
>
> \startTEXpage[offset=3pt]
> $f'(x)\hat{f}'(x)$
> \stopTEXpage
>
> gives the attached output. The prime of f'(x) looks wrong, the one of
> \hat{f}'(x) looks correct.
>
> /Mikael

I was too quick. The example

\setupbodyfont[lucidaot,10pt]
\setupmathematics[stylealternative={calligraphic}]% to get the normal
math lower case italic

\startTEXpage[offset=3pt]
$f'(x)\hat{f}'(x)$
\stopTEXpage

gives bad result in both cases. The first one with wrong size and
wrong vertical placement, the second one only with wrong vertical
placement (that was not obvious to me for latin modern).

/Mikael


ctx-listexample31.pdf
Description: Adobe PDF document
___
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] Position of prime for derivatives

2017-06-07 Thread Mikael P. Sundqvist

On Mon, Jun 5, 2017 at 11:00 PM, Hans Hagen <pra...@wxs.nl> wrote:
> On 6/4/2017 11:06 PM, Otared Kavian wrote:
>>
>> Hi Mikael,
>>
>> Indeed your observation is correct, but using \over instead of \frac
>> yields the correct behavior. Please try the following sample:
>>
>> %%% begin derivatives-prime-4.tex
>> \setupbodyfont[lucidaot]
>>
>> \starttext
>>
>> Compare the position of the prime sign in $f'/g$ in these two expressions:
>> the first one using \type{{... \over ...}}
>> \startformula
>> \left({f \over g}\right)' = {f' \over g} - {f \over g^2}g'
>> \stopformula
>> (which yields a correct position of the prime for $f'$ in $f'/g$), and the
>> second using \type{\frac{...}{...}}
>> \startformula
>> \left(\frac{f}{g} \right)' = \frac{f'}{g} - \frac{f}{g^2} g'
>> \stopformula
>> which yields a prime sign for $f'$ a little bit lower.
>>
>> \stoptext
>> %%% end derivatives-prime-4.tex
>
> The problem with primes is that it's a real mess, conceptually as well as in
> fonts.
>
> - we need to deal with not only one prime but also with double, tripple and
> quadruple ones and they need to become proper unicode symbols too
>
> - fonts have one, two or three sizes, often inconsistent and with funny
> dimensions, onlyt the text size can be trusted
>
> - we cannot use prime as nuclues as it can be combined with a subscript
>
> - but it isn't designed as a script symbol and is already raised (somewhat)
>
> - so we have to deal with a good old tex / fonts / plain inheritance,
> unicode but also want to avoid active character and parsing mess etc.
>
> I tried several approaches and it's hard to come up with a general solution
> that suits all fonts.
>
> Now, the bad is that when we use a superscript with a smashed virtual
> characters we end up in script choice mess with primes being one step too
> small.
>
> So, I decided to follow a different route and extend luatex with a sizeless
> super/subscript feature so that we can handle such weird cases (there might
> be more).
>
> This also means that the primes get larger. I only use the text size prime
> and scale that down for the other sizes i.e. no stty for primes as they are
> such a mess) but we can live with that.
>
> The good news is that it gets better but the bad news is that you have to
> wait till we release luatex 1.0.5 (planned for the ctx meeting but we might
> do an intermediate garden release anyway).
>
> btw, with \frac you get cramped styles and these have different positioning.
> Such is life.
>
> 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
> ___

Again, thanks.

In 2017.06.06 13:22 something is still not correct.

The input file

\startTEXpage[offset=3pt]
$f'(x)\hat{f}'(x)$
\stopTEXpage

gives the attached output. The prime of f'(x) looks wrong, the one of
\hat{f}'(x) looks correct.

/Mikael


ctx-listexample31.pdf
Description: Adobe PDF document
___
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] Position of prime for derivatives

2017-06-05 Thread Hans Hagen


On 6/4/2017 11:06 PM, Otared Kavian wrote:

Hi Mikael,

Indeed your observation is correct, but using \over instead of \frac yields the 
correct behavior. Please try the following sample:

%%% begin derivatives-prime-4.tex
\setupbodyfont[lucidaot]

\starttext

Compare the position of the prime sign in $f'/g$ in these two expressions: the 
first one using \type{{... \over ...}}
\startformula
\left({f \over g}\right)' = {f' \over g} - {f \over g^2}g'
\stopformula
(which yields a correct position of the prime for $f'$ in $f'/g$), and the 
second using \type{\frac{...}{...}}
\startformula
\left(\frac{f}{g} \right)' = \frac{f'}{g} - \frac{f}{g^2} g'
\stopformula
which yields a prime sign for $f'$ a little bit lower.

\stoptext
%%% end derivatives-prime-4.tex
The problem with primes is that it's a real mess, conceptually as well 
as in fonts.


- we need to deal with not only one prime but also with double, tripple 
and quadruple ones and they need to become proper unicode symbols too


- fonts have one, two or three sizes, often inconsistent and with funny 
dimensions, onlyt the text size can be trusted


- we cannot use prime as nuclues as it can be combined with a subscript

- but it isn't designed as a script symbol and is already raised (somewhat)

- so we have to deal with a good old tex / fonts / plain inheritance, 
unicode but also want to avoid active character and parsing mess etc.


I tried several approaches and it's hard to come up with a general 
solution that suits all fonts.


Now, the bad is that when we use a superscript with a smashed virtual 
characters we end up in script choice mess with primes being one step 
too small.


So, I decided to follow a different route and extend luatex with a 
sizeless super/subscript feature so that we can handle such weird cases 
(there might be more).


This also means that the primes get larger. I only use the text size 
prime and scale that down for the other sizes i.e. no stty for primes as 
they are such a mess) but we can live with that.


The good news is that it gets better but the bad news is that you have 
to wait till we release luatex 1.0.5 (planned for the ctx meeting but we 
might do an intermediate garden release anyway).


btw, with \frac you get cramped styles and these have different 
positioning. Such is life.


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] Position of prime for derivatives

2017-06-04 Thread Otared Kavian

Hi Mikael,

Indeed your observation is correct, but using \over instead of \frac yields the 
correct behavior. Please try the following sample:

%%% begin derivatives-prime-4.tex
\setupbodyfont[lucidaot]

\starttext

Compare the position of the prime sign in $f'/g$ in these two expressions: the 
first one using \type{{... \over ...}}
\startformula
\left({f \over g}\right)' = {f' \over g} - {f \over g^2}g'
\stopformula
(which yields a correct position of the prime for $f'$ in $f'/g$), and the 
second using \type{\frac{...}{...}}
\startformula
\left(\frac{f}{g} \right)' = \frac{f'}{g} - \frac{f}{g^2} g'
\stopformula
which yields a prime sign for $f'$ a little bit lower.

\stoptext
%%% end derivatives-prime-4.tex

derivatives-prime-4.pdf
Description: Adobe PDF document

> On 4 Jun 2017, at 19:42, Mikael P. Sundqvist <mic...@gmail.com> wrote:

> […]
> 
> I hate to bring this up again, but look at the attached output of
> 
> %%%
> %\setupbodyfont[lucidaot]
> 
> \starttext
> \startformula
> f'(0)=2\frac{f'(0)}{2}
> \stopformula
> \stoptext
> %%%
> 
> The prime in the fraction is in my opinion too low (it is more clear
> in the example with lucida).
> 
> /Mikael
> ___
> 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] Change kerning between math characters (prime and left parenthesis)

2017-06-02 Thread Mikael P. Sundqvist

On Fri, Jun 2, 2017 at 4:24 PM, Hans Hagen <pra...@wxs.nl> wrote:
> On 6/2/2017 10:59 AM, Mikael P. Sundqvist wrote:
>>
>> Hi!
>>
>> Now that the bug with primes is fixed in ConTeXt, I wonder if there is
>> a way to change the kerning between certain characters in mathematics
>> (in case one is not happy with the output from the font)? After
>> reading in fonts-mkiv.pdf this is what I came up with:
>
>
> you can also play withj:
>
> return {
> name = "cambria-math",
> mathematics = {
>kerns = {
>   [0x1D453] = {
>   force = true,
>   topright = {
>   {
>   kern = 1000,
>   },
>   },
>   bottomright = {
>   {
>   kern = 1000,
>   },
>   },
>   },
>   },
> },
> }
>
> currently you need to enable this:
>
> \enabledirectives[fontgoodies.mathkerning]
>
> keep in mind that some cambria (not all) have such staircase kerns which is
> why force is needed in order to overload
>
>> \startluacode
>> fonts.handlers.otf.addfeature {
>> name = "kerntest",
>> type = "kern",
>> data = {
>> [0x61] = { [0x62] = -150 }, -- a and b in text
>> [0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[kerntest][kerntest=yes]
>>
>> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
>> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
>>
>> \setupbodyfont[lucidaopentype,10pt]
>>
>>
>> \startTEXpage[offset=3pt]
>> abba $abba f'(x)$
>>
>> \addff{kerntest}
>>
>> abba $abba f'(x)$
>>
>> I prefer $f'\mkern-3mu(x)$
>> \stopTEXpage
>>
>> The output is attached as a png file. As you see the kerning works as
>> expected in text mode, but not at all in math mode, even not for the a
>> and b (which I hope I entered correctly).
>>
>> Something like the third line is what I'm after, but not having to use
>> \mkern in all places. Is it possible?
>>
>> /Mikael
>>
>> PS: This is a cross post of the question
>> https://tex.stackexchange.com/q/372857/52406, where I got the
>> suggestion to ask on the list.
>>
>>
>>
>>
>> ___
>> 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
> ___

Thank you Hans, that works.

Is there also a similar way to use the "kernpairs" instead of "kerns"?
I get no effect, even after adding force = true and
\enabledirectives[fontgoodies.mathkerning].

/Mikael
___
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] Change kerning between math characters (prime and left parenthesis)

2017-06-02 Thread Hans Hagen


On 6/2/2017 10:59 AM, Mikael P. Sundqvist wrote:

Hi!

Now that the bug with primes is fixed in ConTeXt, I wonder if there is
a way to change the kerning between certain characters in mathematics
(in case one is not happy with the output from the font)? After
reading in fonts-mkiv.pdf this is what I came up with:


you can also play withj:

return {
name = "cambria-math",
mathematics = {
   kerns = {
  [0x1D453] = {
  force = true,
  topright = {
  {
  kern = 1000,
  },
  },
  bottomright = {
  {
  kern = 1000,
  },
  },
  },
  },
},
}

currently you need to enable this:

\enabledirectives[fontgoodies.mathkerning]

keep in mind that some cambria (not all) have such staircase kerns which 
is why force is needed in order to overload



\startluacode
fonts.handlers.otf.addfeature {
name = "kerntest",
type = "kern",
data = {
[0x61] = { [0x62] = -150 }, -- a and b in text
[0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
[0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
}
}
\stopluacode

\definefontfeature[kerntest][kerntest=yes]

\definefontfamily[lucidaopentype][rm][Lucida Bright OT]
\definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]

\setupbodyfont[lucidaopentype,10pt]


\startTEXpage[offset=3pt]
abba $abba f'(x)$

\addff{kerntest}

abba $abba f'(x)$

I prefer $f'\mkern-3mu(x)$
\stopTEXpage

The output is attached as a png file. As you see the kerning works as
expected in text mode, but not at all in math mode, even not for the a
and b (which I hope I entered correctly).

Something like the third line is what I'm after, but not having to use
\mkern in all places. Is it possible?

/Mikael

PS: This is a cross post of the question
https://tex.stackexchange.com/q/372857/52406, where I got the
suggestion to ask on the list.



___
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] Change kerning between math characters (prime and left parenthesis)

2017-06-02 Thread Mikael P. Sundqvist

On Fri, Jun 2, 2017 at 1:39 PM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
> On Fri, Jun 2, 2017 at 11:39 AM, Mathias Schickel
> <m...@fa.uni-tuebingen.de> wrote:
>> Hi Mikael,
>>
>> math fonts are a bit different from text fonts. This means that you need 
>> special methods to influence them. Because I once had a similar concern like 
>> you I asked Hans to implement a way to influence kerning in math fonts 
>> between certain glyphs. I have attached an lfg-file that shows how to use it.
>>
>> To enable a goodie file like the one attached you have to define your 
>> typescript like
>>
>> \starttypescript [\s!math][cambriaown][\s!all]
>> \loadfontgoodies[cambriaown-math]
>> \definefontsynonym[\s!MathRoman][Cambria-Math]   
>>
>> [\s!features={\s!math\mathsizesuffix},\s!designsize=\s!auto,\s!goodies=cambriaown-math]
>> \stoptypescript
>>
>> I hope this helps!
>>
>> Best
>> Mathias
>>
>>
>>
>>
>>
>>> Am 02.06.2017 um 10:59 schrieb Mikael P. Sundqvist <mic...@gmail.com>:
>>>
>>> Hi!
>>>
>>> Now that the bug with primes is fixed in ConTeXt, I wonder if there is
>>> a way to change the kerning between certain characters in mathematics
>>> (in case one is not happy with the output from the font)? After
>>> reading in fonts-mkiv.pdf this is what I came up with:
>>>
>>> \startluacode
>>> fonts.handlers.otf.addfeature {
>>> name = "kerntest",
>>> type = "kern",
>>> data = {
>>> [0x61] = { [0x62] = -150 }, -- a and b in text
>>> [0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
>>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>>> }
>>> }
>>> \stopluacode
>>>
>>> \definefontfeature[kerntest][kerntest=yes]
>>>
>>> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
>>> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
>>>
>>> \setupbodyfont[lucidaopentype,10pt]
>>>
>>>
>>> \startTEXpage[offset=3pt]
>>> abba $abba f'(x)$
>>>
>>> \addff{kerntest}
>>>
>>> abba $abba f'(x)$
>>>
>>> I prefer $f'\mkern-3mu(x)$
>>> \stopTEXpage
>>>
>>> The output is attached as a png file. As you see the kerning works as
>>> expected in text mode, but not at all in math mode, even not for the a
>>> and b (which I hope I entered correctly).
>>>
>>> Something like the third line is what I'm after, but not having to use
>>> \mkern in all places. Is it possible?
>>>
>>> /Mikael
>>>
>>> PS: This is a cross post of the question
>>> https://tex.stackexchange.com/q/372857/52406, where I got the
>>> suggestion to ask on the list.
>>> ___
>>> 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
>> ___
>
> Thank you very much for your reply, Mathias!
>
> I'm not sure I get it, though. I find that there is already a file
> lucida-opentype-math.lfg in the distribution.
>
> Just experimenting, I added to this file an entry with kernpairs (see
> below), to see if I could make a change with a and b (if I cannot
> manage that, I don't see how I could get the prime and parenthesis
> case to work).
>
> %%% start of my new lucida-opentype-math.lfg
> - kern_250 = { bottomright = { { kern = -250 } }, force = true }
>
> return {
> nam

Re: [NTG-context] Change kerning between math characters (prime and left parenthesis)

2017-06-02 Thread Mikael P. Sundqvist

On Fri, Jun 2, 2017 at 11:39 AM, Mathias Schickel
<m...@fa.uni-tuebingen.de> wrote:
> Hi Mikael,
>
> math fonts are a bit different from text fonts. This means that you need 
> special methods to influence them. Because I once had a similar concern like 
> you I asked Hans to implement a way to influence kerning in math fonts 
> between certain glyphs. I have attached an lfg-file that shows how to use it.
>
> To enable a goodie file like the one attached you have to define your 
> typescript like
>
> \starttypescript [\s!math][cambriaown][\s!all]
> \loadfontgoodies[cambriaown-math]
> \definefontsynonym[\s!MathRoman][Cambria-Math]
>   
> [\s!features={\s!math\mathsizesuffix},\s!designsize=\s!auto,\s!goodies=cambriaown-math]
> \stoptypescript
>
> I hope this helps!
>
> Best
> Mathias
>
>
>
>
>
>> Am 02.06.2017 um 10:59 schrieb Mikael P. Sundqvist <mic...@gmail.com>:
>>
>> Hi!
>>
>> Now that the bug with primes is fixed in ConTeXt, I wonder if there is
>> a way to change the kerning between certain characters in mathematics
>> (in case one is not happy with the output from the font)? After
>> reading in fonts-mkiv.pdf this is what I came up with:
>>
>> \startluacode
>> fonts.handlers.otf.addfeature {
>> name = "kerntest",
>> type = "kern",
>> data = {
>> [0x61] = { [0x62] = -150 }, -- a and b in text
>> [0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
>> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
>> }
>> }
>> \stopluacode
>>
>> \definefontfeature[kerntest][kerntest=yes]
>>
>> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
>> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
>>
>> \setupbodyfont[lucidaopentype,10pt]
>>
>>
>> \startTEXpage[offset=3pt]
>> abba $abba f'(x)$
>>
>> \addff{kerntest}
>>
>> abba $abba f'(x)$
>>
>> I prefer $f'\mkern-3mu(x)$
>> \stopTEXpage
>>
>> The output is attached as a png file. As you see the kerning works as
>> expected in text mode, but not at all in math mode, even not for the a
>> and b (which I hope I entered correctly).
>>
>> Something like the third line is what I'm after, but not having to use
>> \mkern in all places. Is it possible?
>>
>> /Mikael
>>
>> PS: This is a cross post of the question
>> https://tex.stackexchange.com/q/372857/52406, where I got the
>> suggestion to ask on the list.
>> ___
>> 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
> ___

Thank you very much for your reply, Mathias!

I'm not sure I get it, though. I find that there is already a file
lucida-opentype-math.lfg in the distribution.

Just experimenting, I added to this file an entry with kernpairs (see
below), to see if I could make a change with a and b (if I cannot
manage that, I don't see how I could get the prime and parenthesis
case to work).

%%% start of my new lucida-opentype-math.lfg
- kern_250 = { bottomright = { { kern = -250 } }, force = true }

return {
name = "lucida-opentype-math",
version = "1.00",
comment = "Goodies that complement lucida opentype.",
author = "Hans Hagen",
copyright = "ConTeXt development team",
mathematics = {
alternates = {
italic   = { feature = 'ss01', value = 1, comment =
"Mathematical Alternative Lowercase Italic" },
arrow= { feature = 'ss02', value = 1, comment =
"Mathematical Alternative Smaller Arrows" },
operator = { feature = 'ss03',

Re: [NTG-context] Change kerning between math characters (prime and left parenthesis)

2017-06-02 Thread Mathias Schickel

Hi Mikael,

math fonts are a bit different from text fonts. This means that you need 
special methods to influence them. Because I once had a similar concern like 
you I asked Hans to implement a way to influence kerning in math fonts between 
certain glyphs. I have attached an lfg-file that shows how to use it.

To enable a goodie file like the one attached you have to define your 
typescript like

\starttypescript [\s!math][cambriaown][\s!all]
\loadfontgoodies[cambriaown-math]
\definefontsynonym[\s!MathRoman][Cambria-Math]  
[\s!features={\s!math\mathsizesuffix},\s!designsize=\s!auto,\s!goodies=cambriaown-math]
\stoptypescript

I hope this helps!

Best
Mathias



cambriaown-math.lfg
Description: Binary data



> Am 02.06.2017 um 10:59 schrieb Mikael P. Sundqvist <mic...@gmail.com>:
> 
> Hi!
> 
> Now that the bug with primes is fixed in ConTeXt, I wonder if there is
> a way to change the kerning between certain characters in mathematics
> (in case one is not happy with the output from the font)? After
> reading in fonts-mkiv.pdf this is what I came up with:
> 
> \startluacode
> fonts.handlers.otf.addfeature {
> name = "kerntest",
> type = "kern",
> data = {
> [0x61] = { [0x62] = -150 }, -- a and b in text
> [0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
> [0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
> }
> }
> \stopluacode
> 
> \definefontfeature[kerntest][kerntest=yes]
> 
> \definefontfamily[lucidaopentype][rm][Lucida Bright OT]
> \definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]
> 
> \setupbodyfont[lucidaopentype,10pt]
> 
> 
> \startTEXpage[offset=3pt]
> abba $abba f'(x)$
> 
> \addff{kerntest}
> 
> abba $abba f'(x)$
> 
> I prefer $f'\mkern-3mu(x)$
> \stopTEXpage
> 
> The output is attached as a png file. As you see the kerning works as
> expected in text mode, but not at all in math mode, even not for the a
> and b (which I hope I entered correctly).
> 
> Something like the third line is what I'm after, but not having to use
> \mkern in all places. Is it possible?
> 
> /Mikael
> 
> PS: This is a cross post of the question
> https://tex.stackexchange.com/q/372857/52406, where I got the
> suggestion to ask on the list.
> ___
> 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] Change kerning between math characters (prime and left parenthesis)

2017-06-02 Thread Mikael P. Sundqvist

Hi!

Now that the bug with primes is fixed in ConTeXt, I wonder if there is
a way to change the kerning between certain characters in mathematics
(in case one is not happy with the output from the font)? After
reading in fonts-mkiv.pdf this is what I came up with:

\startluacode
fonts.handlers.otf.addfeature {
name = "kerntest",
type = "kern",
data = {
[0x61] = { [0x62] = -150 }, -- a and b in text
[0x1d44e] = { [0x1d44f] = -150 }, -- mathematical italic small a and b
[0x02032] = { [0x00028] = -150 }, -- prime and left parenthesis
}
}
\stopluacode

\definefontfeature[kerntest][kerntest=yes]

\definefontfamily[lucidaopentype][rm][Lucida Bright OT]
\definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]

\setupbodyfont[lucidaopentype,10pt]


\startTEXpage[offset=3pt]
abba $abba f'(x)$

\addff{kerntest}

abba $abba f'(x)$

I prefer $f'\mkern-3mu(x)$
\stopTEXpage

The output is attached as a png file. As you see the kerning works as
expected in text mode, but not at all in math mode, even not for the a
and b (which I hope I entered correctly).

Something like the third line is what I'm after, but not having to use
\mkern in all places. Is it possible?

/Mikael

PS: This is a cross post of the question
https://tex.stackexchange.com/q/372857/52406, where I got the
suggestion to ask on the list.
___
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] setupitemgroup and 'command='

2017-05-24 Thread Thomas Floeren

Hans, thanks for your swift reply…



> On 24. May 2017, at 19:31, Hans Hagen <pra...@wxs.nl> wrote:
> 
> On 5/24/2017 6:28 PM, Thomas Floeren wrote:
>> Hi,
>> I used to use the “command=” parameter when setting up itemize. Now I 
>> noticed that it introduces a spurious horizontal whitespace after the item 
>> symbol when the item is of type “\sym{}”.
>> I also noticed that the problem goes away if I use “inner=” instead of 
>> “command=”.
> 
> command is applied to the text, try command=\WORD and after \sym is a space 
> so it depends on what command does with it


I see, \WORD does not introduce the whitespace. But I don’t understand why 
\setupwhitespace[none] should do anything with the space after \sym, what \WORD 
doesn’t do.


> 
>> Example:
>> \setuppapersize [A6]
>> \starttext
>> \start
>> \setupitemize [each][command={\setupwhitespace[none]}]
>> With \type{\command=}
>> \startitemize
>> \item \dorecurse{20}{bla }
>> \sym{Y} \dorecurse{20}{bla }
>> \stopitemize
>> \stop
>> \setupitemize [each][inner={\setupwhitespace[none]}]
>> With \type{\inner=}
>> \startitemize
>> \item \dorecurse{20}{bla }
>> \sym{Y} \dorecurse{20}{bla }
>> \stopitemize
>> \stoptext
>> This is with ConTeXt 2017.05.15 21:48. With an older ConTeXt, for example 
>> 2015.01.13 15:54, “inner=” and “command=” deliver identical, correct results.
>> So, I’m asking, has “command=” been deprecated or is it just a bug?
>> Or was I using it the wrong way, and “inner=” is the only correct parameter 
>> in the example above?
> \setupitemize [each][nowhite]


Tried that, but it does not the same as \setupwhitespace[none]. (It completely 
annihilates any whitespace.)

Compile this to see what I mean:



\definepapersize[Tmp][width=120mm,height=400mm]
\setuppapersize [Tmp]
\setupwhitespace[2\lineheight]

\startbuffer
bla, bla\crlf bla, bla 
\stopbuffer

\starttext

Normal text:

\getbuffer\par
\getbuffer

Itemize, unmodified:
\startitemize 
\item \getbuffer 
\sym{Y} \getbuffer 
\stopitemize

\start
\setupitemize [each][command={\setupwhitespace[none]}]
Itemize with \type{command={\setupwhitespace[none]}}:
\startitemize 
\item \getbuffer 
\sym{Y} \getbuffer 
\stopitemize
\stop

\start
\setupitemize [each][inner={\setupwhitespace[none]}]
Itemize with \type{inner={\setupwhitespace[none]}}:
\startitemize 
\item \getbuffer 
\sym{Y} \getbuffer 
\stopitemize
\stop

\start
\setupitemize [each][nowhite]
Itemize with \type{nowhite}:
\startitemize 
\item \getbuffer 
\sym{Y} \getbuffer 
\stopitemize
\stop

\stoptext


So it seems the only ways to get the desired result are either 
inner={\setupwhitespace[none]} or command={\setupwhitespace[none]}, where the 
first one seems to work correctly and the latter one introduces the whitespace 
with recent Betas. (well, recent = younger than 2 years or so)

Should I change all my existing documents to “inner”?


Thanks,
best,

– Tom

-- 
For macOS:  
http://dflect.net/context-typeset-tool/
___
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] setupitemgroup and 'command='

2017-05-24 Thread Hans Hagen


On 5/24/2017 6:28 PM, Thomas Floeren wrote:

Hi,


I used to use the “command=” parameter when setting up itemize. Now I noticed 
that it introduces a spurious horizontal whitespace after the item symbol when 
the item is of type “\sym{}”.

I also noticed that the problem goes away if I use “inner=” instead of 
“command=”.


command is applied to the text, try command=\WORD and after \sym is a 
space so it depends on what command does with it



Example:

\setuppapersize [A6]

\starttext
\start
\setupitemize [each][command={\setupwhitespace[none]}]
With \type{\command=}
\startitemize
\item \dorecurse{20}{bla }
\sym{Y} \dorecurse{20}{bla }
\stopitemize
\stop

\setupitemize [each][inner={\setupwhitespace[none]}]
With \type{\inner=}
\startitemize
\item \dorecurse{20}{bla }
\sym{Y} \dorecurse{20}{bla }
\stopitemize

\stoptext


This is with ConTeXt 2017.05.15 21:48. With an older ConTeXt, for example 
2015.01.13 15:54, “inner=” and “command=” deliver identical, correct results.

So, I’m asking, has “command=” been deprecated or is it just a bug?

Or was I using it the wrong way, and “inner=” is the only correct parameter in 
the example above?

\setupitemize [each][nowhite]


-
  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] setupitemgroup and 'command='

2017-05-24 Thread Thomas Floeren

Hi,


I used to use the “command=” parameter when setting up itemize. Now I noticed 
that it introduces a spurious horizontal whitespace after the item symbol when 
the item is of type “\sym{}”.

I also noticed that the problem goes away if I use “inner=” instead of 
“command=”.


Example:

\setuppapersize [A6] 

\starttext
\start
\setupitemize [each][command={\setupwhitespace[none]}]
With \type{\command=}
\startitemize 
\item \dorecurse{20}{bla } 
\sym{Y} \dorecurse{20}{bla } 
\stopitemize
\stop

\setupitemize [each][inner={\setupwhitespace[none]}]
With \type{\inner=}
\startitemize 
\item \dorecurse{20}{bla } 
\sym{Y} \dorecurse{20}{bla } 
\stopitemize

\stoptext


This is with ConTeXt 2017.05.15 21:48. With an older ConTeXt, for example 
2015.01.13 15:54, “inner=” and “command=” deliver identical, correct results.

So, I’m asking, has “command=” been deprecated or is it just a bug?

Or was I using it the wrong way, and “inner=” is the only correct parameter in 
the example above?

Thanks for any info,
Best wishes,

– Tom


-- 
For macOS:
http://dflect.net/context-typeset-tool/


___
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] Position of prime for derivatives

2017-05-21 Thread Mikael P. Sundqvist

On Sat, May 20, 2017 at 7:32 PM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
> On Sat, May 20, 2017 at 3:33 PM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
>> On Thu, May 18, 2017 at 9:50 AM, Mikael P. Sundqvist <mic...@gmail.com> 
>> wrote:
>>> Den 18 maj 2017 10:13 fm skrev "Otared Kavian" <ota...@gmail.com>:
>>>
>>> Hi Hans,
>>>
>>> Thanks for your explanations.
>>> When using constructions such as $f’’_2(x)$, I will adapt my input  in order
>>> to get what seems correct.
>>>
>>> Best regards: OK
>>>
>>>> On 17 May 2017, at 17:17, Hans Hagen <pra...@wxs.nl> wrote:
>>>>
>>>> On 5/17/2017 8:35 AM, Otared Kavian wrote:
>>>>> Hi Hans,
>>>>>
>>>>> Thanks for having fixed the behavior of the prime in the latest beta
>>>>> release (ConTeXt  version 2017.05.15 21:48).
>>>>> However, as you may see in the two attached PDF files, the result is
>>>>> still incorrect when one types for example $f_2’’(x)$, which should give 
>>>>> the
>>>>> same result as $f’’_2(x)$.
>>>>> The correct behaviour is that obtained with mkii. Indeed one can
>>>>> circumvent the behaviour of the latest beta release of mkiv by using 
>>>>> tricks
>>>>> such as the ones in the example code below, but this should be avoided in 
>>>>> my
>>>>> opinion.
>>>>
>>>> well, it depends on how one sees this '' mess
>>>>
>>>> the problem with primes is that in macro packages they are messy entities
>>>> that should collapse or not (active char mess) and the more clever a macro
>>>> packages becomes the harder it becomes to makes it robust and/or to fight
>>>> against such heuristics
>>>>
>>>> add to that the fact that the symbol itself is a funny positioned
>>>> something already raised in a font or not i.e. sometimes in need of
>>>> superscript and sometimes explicitly not
>>>>
>>>> for unicode we need to turn two '' into a double and ''' into a and triple
>>>> such
>>>>
>>>> that said, in context these thingies are at some point intercepted and
>>>> their current state is looked at: superscript? multipel in a row? one ebing
>>>> the nucleus of another ... etc .. the current (working again) behavior is
>>>> what we support and i don't look forward to more heuristics
>>>>
>>>>
>>>>> The following PDF have been obtained with mkii and mkiv with the
>>>>> following example code.
>>>>> Best regards: OK
>>>>>
>>>>> %%% begin derivatives-prime.tex
>>>>> \starttext
>>>>>
>>>>> \startformula
>>>>> f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % =
>>>>> f^{{}^{''}}_{2}(x)
>>>>> \stopformula
>>>>> As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not
>>>>> correct in \type{mkiv}.
>>>>>
>>>>> The following positions of the superscripts \type{(3)} are correct both
>>>>> in \type{mkii} and in \type{mkiv}.
>>>>> \startformula
>>>>> f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
>>>>> \stopformula
>>>>>
>>>>> \stoptext
>>>>> %%% end derivatives-prime.tex
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> 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
>>>>

Re: [NTG-context] Position of prime for derivatives

2017-05-20 Thread Mikael P. Sundqvist

On Sat, May 20, 2017 at 3:33 PM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
> On Thu, May 18, 2017 at 9:50 AM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
>> Den 18 maj 2017 10:13 fm skrev "Otared Kavian" <ota...@gmail.com>:
>>
>> Hi Hans,
>>
>> Thanks for your explanations.
>> When using constructions such as $f’’_2(x)$, I will adapt my input  in order
>> to get what seems correct.
>>
>> Best regards: OK
>>
>>> On 17 May 2017, at 17:17, Hans Hagen <pra...@wxs.nl> wrote:
>>>
>>> On 5/17/2017 8:35 AM, Otared Kavian wrote:
>>>> Hi Hans,
>>>>
>>>> Thanks for having fixed the behavior of the prime in the latest beta
>>>> release (ConTeXt  version 2017.05.15 21:48).
>>>> However, as you may see in the two attached PDF files, the result is
>>>> still incorrect when one types for example $f_2’’(x)$, which should give 
>>>> the
>>>> same result as $f’’_2(x)$.
>>>> The correct behaviour is that obtained with mkii. Indeed one can
>>>> circumvent the behaviour of the latest beta release of mkiv by using tricks
>>>> such as the ones in the example code below, but this should be avoided in 
>>>> my
>>>> opinion.
>>>
>>> well, it depends on how one sees this '' mess
>>>
>>> the problem with primes is that in macro packages they are messy entities
>>> that should collapse or not (active char mess) and the more clever a macro
>>> packages becomes the harder it becomes to makes it robust and/or to fight
>>> against such heuristics
>>>
>>> add to that the fact that the symbol itself is a funny positioned
>>> something already raised in a font or not i.e. sometimes in need of
>>> superscript and sometimes explicitly not
>>>
>>> for unicode we need to turn two '' into a double and ''' into a and triple
>>> such
>>>
>>> that said, in context these thingies are at some point intercepted and
>>> their current state is looked at: superscript? multipel in a row? one ebing
>>> the nucleus of another ... etc .. the current (working again) behavior is
>>> what we support and i don't look forward to more heuristics
>>>
>>>
>>>> The following PDF have been obtained with mkii and mkiv with the
>>>> following example code.
>>>> Best regards: OK
>>>>
>>>> %%% begin derivatives-prime.tex
>>>> \starttext
>>>>
>>>> \startformula
>>>> f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % =
>>>> f^{{}^{''}}_{2}(x)
>>>> \stopformula
>>>> As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not
>>>> correct in \type{mkiv}.
>>>>
>>>> The following positions of the superscripts \type{(3)} are correct both
>>>> in \type{mkii} and in \type{mkiv}.
>>>> \startformula
>>>> f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
>>>> \stopformula
>>>>
>>>> \stoptext
>>>> %%% end derivatives-prime.tex
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> 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
>

Re: [NTG-context] Position of prime for derivatives

2017-05-20 Thread Mikael P. Sundqvist

On Thu, May 18, 2017 at 9:50 AM, Mikael P. Sundqvist <mic...@gmail.com> wrote:
> Den 18 maj 2017 10:13 fm skrev "Otared Kavian" <ota...@gmail.com>:
>
> Hi Hans,
>
> Thanks for your explanations.
> When using constructions such as $f’’_2(x)$, I will adapt my input  in order
> to get what seems correct.
>
> Best regards: OK
>
>> On 17 May 2017, at 17:17, Hans Hagen <pra...@wxs.nl> wrote:
>>
>> On 5/17/2017 8:35 AM, Otared Kavian wrote:
>>> Hi Hans,
>>>
>>> Thanks for having fixed the behavior of the prime in the latest beta
>>> release (ConTeXt  version 2017.05.15 21:48).
>>> However, as you may see in the two attached PDF files, the result is
>>> still incorrect when one types for example $f_2’’(x)$, which should give the
>>> same result as $f’’_2(x)$.
>>> The correct behaviour is that obtained with mkii. Indeed one can
>>> circumvent the behaviour of the latest beta release of mkiv by using tricks
>>> such as the ones in the example code below, but this should be avoided in my
>>> opinion.
>>
>> well, it depends on how one sees this '' mess
>>
>> the problem with primes is that in macro packages they are messy entities
>> that should collapse or not (active char mess) and the more clever a macro
>> packages becomes the harder it becomes to makes it robust and/or to fight
>> against such heuristics
>>
>> add to that the fact that the symbol itself is a funny positioned
>> something already raised in a font or not i.e. sometimes in need of
>> superscript and sometimes explicitly not
>>
>> for unicode we need to turn two '' into a double and ''' into a and triple
>> such
>>
>> that said, in context these thingies are at some point intercepted and
>> their current state is looked at: superscript? multipel in a row? one ebing
>> the nucleus of another ... etc .. the current (working again) behavior is
>> what we support and i don't look forward to more heuristics
>>
>>
>>> The following PDF have been obtained with mkii and mkiv with the
>>> following example code.
>>> Best regards: OK
>>>
>>> %%% begin derivatives-prime.tex
>>> \starttext
>>>
>>> \startformula
>>> f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % =
>>> f^{{}^{''}}_{2}(x)
>>> \stopformula
>>> As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not
>>> correct in \type{mkiv}.
>>>
>>> The following positions of the superscripts \type{(3)} are correct both
>>> in \type{mkii} and in \type{mkiv}.
>>> \startformula
>>> f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
>>> \stopformula
>>>
>>> \stoptext
>>> %%% end derivatives-prime.tex
>>>
>>>
>>>
>>>
>>> ___
>>> 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
>>
>> ___
>
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http

Re: [NTG-context] change width of a character with fonts.handlers.otf.addfeature

2017-05-19 Thread Hans Hagen


On 5/19/2017 11:25 AM, Ulrike Fischer wrote:

Am Fri, 19 May 2017 11:05:58 +0200 schrieb Hans Hagen:




I'll add support for 'single' to user features:

\startluacode
 fonts.handlers.otf.addfeature {
 name = "stest",
     type = "single",
 data = {
 a = { -30, 0, -50, 0 },
 }
 }
\stopluacode


Thanks. Let's hope that luaotfload catch up and gets it too.


i suppose that it does catch up (not sure about the frequency, also 
because after the current we now enter beta again)



Did you saw the error message caused by the ccmp-feature
(https://github.com/lualatex/luaotfload/issues/412)? Does it affect


i don't follow all those lists


context too or has it been resolved in its fontloader?


i don't know ... i need a pure context example in order to check, maybe 
some discretionary thing


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] change width of a character with fonts.handlers.otf.addfeature

2017-05-19 Thread Ulrike Fischer

Am Fri, 19 May 2017 11:05:58 +0200 schrieb Hans Hagen:


 
> I'll add support for 'single' to user features:
> 
> \startluacode
>  fonts.handlers.otf.addfeature {
>  name = "stest",
>  type = "single",
>  data = {
>  a = { -30, 0, -50, 0 },
>  }
>  }
> \stopluacode

Thanks. Let's hope that luaotfload catch up and gets it too.


Did you saw the error message caused by the ccmp-feature
(https://github.com/lualatex/luaotfload/issues/412)? Does it affect
context too or has it been resolved in its fontloader?

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] change width of a character with fonts.handlers.otf.addfeature

2017-05-19 Thread Hans Hagen


On 5/19/2017 9:34 AM, Ulrike Fischer wrote:

In extensions-001.tex
(http://minimals.metatex.org/current/context/test/doc/context/tests/mkiv/fonts/extensions-001.tex)
there is an example how to add or change the kern between two chars:


fonts.handlers.otf.addfeature {
name = "ktest",
    type = "kern",
data = {
a = { b = -500 },
}
}


Can this be used to implement also a "Single adjustment positioning"
which would effectivly change the width of character?

(http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html#6.a)

(I tried a few probable variants but got either errors or no effect
at all).


I'll add support for 'single' to user features:

\startluacode
fonts.handlers.otf.addfeature {
    name = "stest",
type = "single",
data = {
a = { -30, 0, -50, 0 },
}
}
\stopluacode

\definefontfeature[whatever][default][stest=yes]

\starttext

\definedfont[Serif*whatever] \vl a\vl

\stoptext



-
  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] change width of a character with fonts.handlers.otf.addfeature

2017-05-19 Thread Ulrike Fischer

In extensions-001.tex
(http://minimals.metatex.org/current/context/test/doc/context/tests/mkiv/fonts/extensions-001.tex)
 
there is an example how to add or change the kern between two chars:


fonts.handlers.otf.addfeature {
name = "ktest",
    type = "kern",
data = {
a = { b = -500 },
}
}


Can this be used to implement also a "Single adjustment positioning" 
which would effectivly change the width of character? 

(http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html#6.a)

(I tried a few probable variants but got either errors or no effect
at all).



-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] Position of prime for derivatives

2017-05-18 Thread Mikael P. Sundqvist

Den 18 maj 2017 10:13 fm skrev "Otared Kavian" <ota...@gmail.com>:

Hi Hans,

Thanks for your explanations.
When using constructions such as $f’’_2(x)$, I will adapt my input  in
order to get what seems correct.

Best regards: OK

> On 17 May 2017, at 17:17, Hans Hagen <pra...@wxs.nl> wrote:
>
> On 5/17/2017 8:35 AM, Otared Kavian wrote:
>> Hi Hans,
>>
>> Thanks for having fixed the behavior of the prime in the latest beta
release (ConTeXt  version 2017.05.15 21:48).
>> However, as you may see in the two attached PDF files, the result is
still incorrect when one types for example $f_2’’(x)$, which should give
the same result as $f’’_2(x)$.
>> The correct behaviour is that obtained with mkii. Indeed one can
circumvent the behaviour of the latest beta release of mkiv by using tricks
such as the ones in the example code below, but this should be avoided in
my opinion.
>
> well, it depends on how one sees this '' mess
>
> the problem with primes is that in macro packages they are messy entities
that should collapse or not (active char mess) and the more clever a macro
packages becomes the harder it becomes to makes it robust and/or to fight
against such heuristics
>
> add to that the fact that the symbol itself is a funny positioned
something already raised in a font or not i.e. sometimes in need of
superscript and sometimes explicitly not
>
> for unicode we need to turn two '' into a double and ''' into a and
triple such
>
> that said, in context these thingies are at some point intercepted and
their current state is looked at: superscript? multipel in a row? one ebing
the nucleus of another ... etc .. the current (working again) behavior is
what we support and i don't look forward to more heuristics
>
>
>> The following PDF have been obtained with mkii and mkiv with the
following example code.
>> Best regards: OK
>>
>> %%% begin derivatives-prime.tex
>> \starttext
>>
>> \startformula
>> f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % =
f^{{}^{''}}_{2}(x)
>> \stopformula
>> As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not
correct in \type{mkiv}.
>>
>> The following positions of the superscripts \type{(3)} are correct both
in \type{mkii} and in \type{mkiv}.
>> \startformula
>> f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
>> \stopformula
>>
>> \stoptext
>> %%% end derivatives-prime.tex
>>
>>
>>
>> 
___
>> 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
> 
___


___
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

___


OK, very good, it seems that we have a working solution and one specific
way to write it. I have absolutely nothing against that, but I would like
us (me?) to document it, since I think future users might have use of it.
Is the math page in the wiki the right place?

(It will take some time before I will be able to act. I'm currently
travelling with close to no working connection.)

/Mikael

Re: [NTG-context] Position of prime for derivatives

2017-05-18 Thread Otared Kavian

Hi Hans,

Thanks for your explanations. 
When using constructions such as $f’’_2(x)$, I will adapt my input  in order to 
get what seems correct.

Best regards: OK

> On 17 May 2017, at 17:17, Hans Hagen <pra...@wxs.nl> wrote:
> 
> On 5/17/2017 8:35 AM, Otared Kavian wrote:
>> Hi Hans,
>> 
>> Thanks for having fixed the behavior of the prime in the latest beta release 
>> (ConTeXt  version 2017.05.15 21:48).
>> However, as you may see in the two attached PDF files, the result is still 
>> incorrect when one types for example $f_2’’(x)$, which should give the same 
>> result as $f’’_2(x)$.
>> The correct behaviour is that obtained with mkii. Indeed one can circumvent 
>> the behaviour of the latest beta release of mkiv by using tricks such as the 
>> ones in the example code below, but this should be avoided in my opinion.
> 
> well, it depends on how one sees this '' mess
> 
> the problem with primes is that in macro packages they are messy entities 
> that should collapse or not (active char mess) and the more clever a macro 
> packages becomes the harder it becomes to makes it robust and/or to fight 
> against such heuristics
> 
> add to that the fact that the symbol itself is a funny positioned something 
> already raised in a font or not i.e. sometimes in need of superscript and 
> sometimes explicitly not
> 
> for unicode we need to turn two '' into a double and ''' into a and triple 
> such
> 
> that said, in context these thingies are at some point intercepted and their 
> current state is looked at: superscript? multipel in a row? one ebing the 
> nucleus of another ... etc .. the current (working again) behavior is what we 
> support and i don't look forward to more heuristics
> 
> 
>> The following PDF have been obtained with mkii and mkiv with the following 
>> example code.
>> Best regards: OK
>> 
>> %%% begin derivatives-prime.tex
>> \starttext
>> 
>> \startformula
>> f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % = 
>> f^{{}^{''}}_{2}(x)
>> \stopformula
>> As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not 
>> correct in \type{mkiv}.
>> 
>> The following positions of the superscripts \type{(3)} are correct both in 
>> \type{mkii} and in \type{mkiv}.
>> \startformula
>> f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
>> \stopformula
>> 
>> \stoptext
>> %%% end derivatives-prime.tex
>> 
>> 
>> 
>> ___
>> 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
> ___

___
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] Position of prime for derivatives

2017-05-17 Thread Hans Hagen


On 5/17/2017 8:35 AM, Otared Kavian wrote:

Hi Hans,

Thanks for having fixed the behavior of the prime in the latest beta release 
(ConTeXt  version 2017.05.15 21:48).
However, as you may see in the two attached PDF files, the result is still 
incorrect when one types for example $f_2’’(x)$, which should give the same 
result as $f’’_2(x)$.
The correct behaviour is that obtained with mkii. Indeed one can circumvent the 
behaviour of the latest beta release of mkiv by using tricks such as the ones 
in the example code below, but this should be avoided in my opinion.


well, it depends on how one sees this '' mess

the problem with primes is that in macro packages they are messy 
entities that should collapse or not (active char mess) and the more 
clever a macro packages becomes the harder it becomes to makes it robust 
and/or to fight against such heuristics


add to that the fact that the symbol itself is a funny positioned 
something already raised in a font or not i.e. sometimes in need of 
superscript and sometimes explicitly not


for unicode we need to turn two '' into a double and ''' into a and 
triple such


that said, in context these thingies are at some point intercepted and 
their current state is looked at: superscript? multipel in a row? one 
ebing the nucleus of another ... etc .. the current (working again) 
behavior is what we support and i don't look forward to more heuristics




The following PDF have been obtained with mkii and mkiv with the following 
example code.
Best regards: OK

%%% begin derivatives-prime.tex
\starttext

\startformula
f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % = f^{{}^{''}}_{2}(x)
\stopformula
As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not correct 
in \type{mkiv}.

The following positions of the superscripts \type{(3)} are correct both in 
\type{mkii} and in \type{mkiv}.
\startformula
f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
\stopformula

\stoptext
%%% end derivatives-prime.tex



___
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
___

[NTG-context] Position of prime for derivatives

2017-05-17 Thread Otared Kavian

Hi Hans,

Thanks for having fixed the behavior of the prime in the latest beta release 
(ConTeXt  version 2017.05.15 21:48).
However, as you may see in the two attached PDF files, the result is still 
incorrect when one types for example $f_2’’(x)$, which should give the same 
result as $f’’_2(x)$.
The correct behaviour is that obtained with mkii. Indeed one can circumvent the 
behaviour of the latest beta release of mkiv by using tricks such as the ones 
in the example code below, but this should be avoided in my opinion.

The following PDF have been obtained with mkii and mkiv with the following 
example code.
Best regards: OK

%%% begin derivatives-prime.tex
\starttext

\startformula
f''_{2}(x) = f_{2}''(x) = f^{''}_{2}(x) = f_{2}^{''}(x) % = f^{{}^{''}}_{2}(x)
\stopformula
As one may see the result of \type{f_{2}''(x) = } $f_{2}''(x)$ is not correct 
in \type{mkiv}. 

The following positions of the superscripts \type{(3)} are correct both in 
\type{mkii} and in \type{mkiv}.
\startformula
f^{(3)}_{2}(x) = f_{2}^{(3)}(x)
\stopformula

\stoptext
%%% end derivatives-prime.tex



derivatives-prime-mkii.pdf
Description: Adobe PDF document


derivatives-prime-mkiv.pdf
Description: Adobe PDF document
___
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] mathdigits no longer works

2017-05-15 Thread Mohammad Hossein Bateni

Thanks, Hans!  It seems to work in the latest beta.

On Mon, May 15, 2017 at 5:36 AM, Hans Hagen <pra...@wxs.nl> wrote:

> On 5/15/2017 5:37 AM, Mohammad Hossein Bateni wrote:
>
>> The version
>> in tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv is
>> a typescript.  Here is a simpler version using defintfontfamily and
>> definefallbackfamily, which doesn't work in the recent beta (but worked
>> well back in January).
>>
>>
>> \definefontfamily [minionmath] [rm] [Minion Pro]
>> \definefallbackfamily [minionmath] [mm] [dejavusansmono]
>> [range=digitsextendedarabicindic,offset=digitsnormal]
>> \definefallbackfamily [minionmath] [mm] [dejavusansmono]
>> [range=digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
>> \definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]
>>
>> \startttext
>>
>> \switchtobodyfont[minionmath]
>>
>> \startformula
>> {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3}
>> \stopformula
>>
>> \stoptext
>>
>>
>> With beta version 2017.01.17 17:37 it used to work and change the digits
>> to Indic inside math.  With beta version 2017.04.27 01:00, the digits do
>> not change to Indic.  However, everything in math changes to
>> dejavusansmono (bold, because that was the last fallback definition?).
>>
>
> there has been some fixes in the math fallbacks recently so only report
> issues that fail in the *latest* garden version
>
> 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/list
> info/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] mathdigits no longer works

2017-05-15 Thread Otared Kavian

Dear Mohammad Hossein,

The small modification I was talking about has nothing to do with the 
definition of fonts. In any case here is the file I used to typeset your 
example (I think you had \startttext instead of \starttext, and also you used 
\switchtobodyfont instead of \setupbodyfont: however I am not sure whether this 
is important or not) :

 begin

\definefontfamily [minionmath] [rm] [Minion Pro]
\definefallbackfamily [minionmath] [mm] [dejavusansmono] 
[range=digitsextendedarabicindic,offset=digitsnormal]
\definefallbackfamily [minionmath] [mm] [dejavusansmono] 
[range=digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
\definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]

%\switchtobodyfont[minionmath]
\setupbodyfont[minionmath]
\starttext

\startformula
{\tf xyz} xyz {\bf xyz} {\bi xyz}, 
\stopformula

\startformula
2+3+4+5+6+7+8+9+10 = {\bf 2+3+4+5+6+7+8+9+10}
\stopformula

\stoptext

 end

Best regrads: Otared K.

> On 15 May 2017, at 11:00, Mohammad Hossein Bateni <bat...@gmail.com> wrote:
> 
> Dear Otared, what is the small modification you mentioned?  Could you share 
> the code you shared to get this output in the latest beta?
> 
> On Mon, May 15, 2017 at 3:27 AM, Otared Kavian <ota...@gmail.com 
> <mailto:ota...@gmail.com>> wrote:
> Hi Mohammad Hossein,
> 
> I don’t get what you expected to obtain in your message, but typesetting your 
> example code (with a small modification) I get the attached PDF file, which 
> seems correct to me.
> I am using ConTeXt  version 2017.05.12 22 <tel:2017.05.12%2022>:40 MKIV beta, 
> with LuaTeX version 1.0.4 on MacOS 10.12.5.
> 
> Best regards: Otared K.
> 
> 
> 
> 
> 
> 
> > On 15 May 2017, at 05:37, Mohammad Hossein Bateni <bat...@gmail.com 
> > <mailto:bat...@gmail.com>> wrote:
> >
> > The version in 
> > tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv is a 
> > typescript.  Here is a simpler version using defintfontfamily and 
> > definefallbackfamily, which doesn't work in the recent beta (but worked 
> > well back in January).
> >
> >
> > \definefontfamily [minionmath] [rm] [Minion Pro]
> > \definefallbackfamily [minionmath] [mm] [dejavusansmono] 
> > [range=digitsextendedarabicindic,offset=digitsnormal]
> > \definefallbackfamily [minionmath] [mm] [dejavusansmono] 
> > [range=digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
> > \definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]
> >
> > \startttext
> >
> > \switchtobodyfont[minionmath]
> >
> > \startformula
> > {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3}
> > \stopformula
> >
> > \stoptext
> >
> >
> > With beta version 2017.01.17 17 <tel:2017.01.17%2017>:37 it used to work 
> > and change the digits to Indic inside math.  With beta version 2017.04.27 
> > 01 <tel:2017.04.27%2001>:00, the digits do not change to Indic.  However, 
> > everything in math changes to dejavusansmono (bold, because that was the 
> > last fallback definition?).
> >
> > On Fri, May 12, 2017 at 7:34 PM, Mohammad Hossein Bateni <bat...@gmail.com 
> > <mailto:bat...@gmail.com>> wrote:
> > Hi,
> >
> > The example for replacing Arabic numerals by Indic digits inside math used 
> > to work (at least) until version 2017.01.17 17 <tel:2017.01.17%2017>:37.
> >
> > tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv
> >
> > Now in version 2017.04.27 01 <tel:2017.04.27%2001>:00, this does not 
> > produce the desired output: it's all "Latin" digits.
> >
> > Has something changed regarding fontfallback definitions?
> >
> > Thanks,
> > MHB
> >
> > ___
> > If your question is of interest to others as well, please add an entry to 
> > the Wiki!
> >
> > maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / 
> > http://www.ntg.nl/mailman/listinfo/ntg-context 
> > <http://www.ntg.nl/mailman/listinfo/ntg-context>
> > webpage  : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / 
> > http://context.aanhet.net <http://context.aanhet.net/>
> > archive  : https://bitbucket.org/phg/context-mirror/commits/ 
> > <https://bitbucket.org/phg/context-mirror/commits/>
> > wiki : http://contextgarden.net <http://contextgarden.net/>
> > ___
> 
> 
> __

Re: [NTG-context] mathdigits no longer works

2017-05-15 Thread Hans Hagen


On 5/15/2017 5:37 AM, Mohammad Hossein Bateni wrote:

The version
in tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv is
a typescript.  Here is a simpler version using defintfontfamily and
definefallbackfamily, which doesn't work in the recent beta (but worked
well back in January).


\definefontfamily [minionmath] [rm] [Minion Pro]
\definefallbackfamily [minionmath] [mm] [dejavusansmono]
[range=digitsextendedarabicindic,offset=digitsnormal]
\definefallbackfamily [minionmath] [mm] [dejavusansmono]
[range=digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
\definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]

\startttext

\switchtobodyfont[minionmath]

\startformula
{\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3}
\stopformula

\stoptext


With beta version 2017.01.17 17:37 it used to work and change the digits
to Indic inside math.  With beta version 2017.04.27 01:00, the digits do
not change to Indic.  However, everything in math changes to
dejavusansmono (bold, because that was the last fallback definition?).


there has been some fixes in the math fallbacks recently so only report 
issues that fail in the *latest* garden version


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] mathdigits no longer works

2017-05-15 Thread Mohammad Hossein Bateni

Dear Otared, what is the small modification you mentioned?  Could you share
the code you shared to get this output in the latest beta?

On Mon, May 15, 2017 at 3:27 AM, Otared Kavian <ota...@gmail.com> wrote:

> Hi Mohammad Hossein,
>
> I don’t get what you expected to obtain in your message, but typesetting
> your example code (with a small modification) I get the attached PDF file,
> which seems correct to me.
> I am using ConTeXt  version 2017.05.12 22:40 MKIV beta, with LuaTeX
> version 1.0.4 on MacOS 10.12.5.
>
> Best regards: Otared K.
>
>
>
>
>
>
> > On 15 May 2017, at 05:37, Mohammad Hossein Bateni <bat...@gmail.com>
> wrote:
> >
> > The version in 
> > tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv
> is a typescript.  Here is a simpler version using defintfontfamily and
> definefallbackfamily, which doesn't work in the recent beta (but worked
> well back in January).
> >
> >
> > \definefontfamily [minionmath] [rm] [Minion Pro]
> > \definefallbackfamily [minionmath] [mm] [dejavusansmono] [range=
> digitsextendedarabicindic,offset=digitsnormal]
> > \definefallbackfamily [minionmath] [mm] [dejavusansmono] [range=
> digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
> > \definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]
> >
> > \startttext
> >
> > \switchtobodyfont[minionmath]
> >
> > \startformula
> > {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3}
> > \stopformula
> >
> > \stoptext
> >
> >
> > With beta version 2017.01.17 17:37 it used to work and change the
> digits to Indic inside math.  With beta version 2017.04.27 01:00, the
> digits do not change to Indic.  However, everything in math changes to
> dejavusansmono (bold, because that was the last fallback definition?).
> >
> > On Fri, May 12, 2017 at 7:34 PM, Mohammad Hossein Bateni <
> bat...@gmail.com> wrote:
> > Hi,
> >
> > The example for replacing Arabic numerals by Indic digits inside math
> used to work (at least) until version 2017.01.17 17:37.
> >
> > tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv
> >
> > Now in version 2017.04.27 01:00, this does not produce the desired
> output: it's all "Latin" digits.
> >
> > Has something changed regarding fontfallback definitions?
> >
> > Thanks,
> > MHB
> >
> > 
> ___
> > 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
> 
> ___
>
___
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] mathdigits no longer works

2017-05-15 Thread Otared Kavian

Hi Mohammad Hossein,

I don’t get what you expected to obtain in your message, but typesetting your 
example code (with a small modification) I get the attached PDF file, which 
seems correct to me.
I am using ConTeXt  version 2017.05.12 22:40 MKIV beta, with LuaTeX version 
1.0.4 on MacOS 10.12.5.

Best regards: Otared K.






mathdigits.pdf
Description: Adobe PDF document

> On 15 May 2017, at 05:37, Mohammad Hossein Bateni <bat...@gmail.com> wrote:
> 
> The version in 
> tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv is a 
> typescript.  Here is a simpler version using defintfontfamily and 
> definefallbackfamily, which doesn't work in the recent beta (but worked well 
> back in January).
> 
> 
> \definefontfamily [minionmath] [rm] [Minion Pro]
> \definefallbackfamily [minionmath] [mm] [dejavusansmono] 
> [range=digitsextendedarabicindic,offset=digitsnormal]
> \definefallbackfamily [minionmath] [mm] [dejavusansmono] 
> [range=digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
> \definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]
> 
> \startttext
> 
> \switchtobodyfont[minionmath]
> 
> \startformula
> {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3}
> \stopformula
> 
> \stoptext
> 
> 
> With beta version 2017.01.17 17:37 it used to work and change the digits to 
> Indic inside math.  With beta version 2017.04.27 01:00, the digits do not 
> change to Indic.  However, everything in math changes to dejavusansmono 
> (bold, because that was the last fallback definition?).
> 
> On Fri, May 12, 2017 at 7:34 PM, Mohammad Hossein Bateni <bat...@gmail.com> 
> wrote:
> Hi,
> 
> The example for replacing Arabic numerals by Indic digits inside math used to 
> work (at least) until version 2017.01.17 17:37.
> 
> tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv
> 
> Now in version 2017.04.27 01:00, this does not produce the desired output: 
> it's all "Latin" digits.
> 
> Has something changed regarding fontfallback definitions?
> 
> Thanks,
> MHB
> 
> ___
> 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] mathdigits no longer works

2017-05-14 Thread Mohammad Hossein Bateni

The version in tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv
is a typescript.  Here is a simpler version using defintfontfamily and
definefallbackfamily, which doesn't work in the recent beta (but worked
well back in January).

\definefontfamily [minionmath] [rm] [Minion Pro]
\definefallbackfamily [minionmath] [mm] [dejavusansmono]
[range=digitsextendedarabicindic,offset=digitsnormal]
\definefallbackfamily [minionmath] [mm] [dejavusansmono]
[range=digitsextendedarabicindic,offset=digitsbold,tf=style:bold]
\definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math]

\startttext

\switchtobodyfont[minionmath]

\startformula
{\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3}
\stopformula

\stoptext

With beta version 2017.01.17 17:37 it used to work and change the digits to
Indic inside math.  With beta version 2017.04.27 01:00, the digits do not
change to Indic.  However, everything in math changes to dejavusansmono
(bold, because that was the last fallback definition?).

On Fri, May 12, 2017 at 7:34 PM, Mohammad Hossein Bateni <bat...@gmail.com>
wrote:

> Hi,
>
> The example for replacing Arabic numerals by Indic digits inside math used
> to work (at least) until version 2017.01.17 17:37.
>
> tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv
>
> Now in version 2017.04.27 01:00, this does not produce the desired output:
> it's all "Latin" digits.
>
> Has something changed regarding fontfallback definitions?
>
> Thanks,
> MHB
>
___
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] mathdigits no longer works

2017-05-12 Thread Mohammad Hossein Bateni

Hi,

The example for replacing Arabic numerals by Indic digits inside math used
to work (at least) until version 2017.01.17 17:37.

tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv

Now in version 2017.04.27 01:00, this does not produce the desired output:
it's all "Latin" digits.

Has something changed regarding fontfallback definitions?

Thanks,
MHB
___
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] \overline and \overbar

2017-05-10 Thread Henri Menke

Neither is correct in a mathematics context.  Use \bar.

On 05/10/2017 05:54 PM, Jeong Dal wrote:
> Dear all,
> 
> In the following sample, the outputs of \overline and of \overbar are 
> slightly different.
> I used \overline in LaTeX. 
> But  it takes more vertical space that cause the alignment trouble while 
> using \overbar has no problem at all.
> Is it normal behavior? 
> 
> Thank you.
> 
> Best regards,
> 
> Dalyoung
> 
> 
> \starttext
> \startitemize[n]
> \item Which is true?
> 
>   \startitemize[n, packed, columns, two][stopper=,left=(, right=)]
>   \item $\overline{A} = A \cup A^\circ$
>   \item $\overline{A\cup B} = \overline{A} \cup \overline{B}$
>   \item If $A \subset B$ then $\overline{B} \subset \overline{A}$
>   \item $A\cup A'$ is an open set.
>   \stopitemize
>   
> \item Which is true?
> 
>   \startitemize[n, packed, columns, two][stopper=,left=(, right=)]
>   \item $\overbar{A} = A \cup A^\circ$
>   \item If $A \subset B$ then $\overbar{B} \subset \overbar{A}$
>   \item $\overbar{A\cup B} = \overbar{A} \cup \overbar{B}$
>   \item $A\cup A'$ is an open set.
>   \stopitemize
> 
> \stopitemize
> 
> \stoptext
> 
> 
>> 2017. 5. 9. 오후 7:00, ntg-context-requ...@ntg.nl 작성:
>>
>> Send ntg-context mailing list submissions to
>>  ntg-context@ntg.nl
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>  https://mailman.ntg.nl/mailman/listinfo/ntg-context
>> or, via email, send a message with subject or body 'help' to
>>  ntg-context-requ...@ntg.nl
>>
>> You can reach the person managing the list at
>>  ntg-context-ow...@ntg.nl
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ntg-context digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Re: BUG: % is comment in btx fields (Henri Menke)
>>   2. Re: BUG: % is comment in btx fields (Rik Kabel)
>>   3. Re: BUG: % is comment in btx fields (Ulrike Fischer)
>>
>>
>> --
>>
>> Message: 1
>> Date: Tue, 09 May 2017 13:40:55 +1200
>> From: Henri Menke <henrime...@gmail.com>
>> To: ntg-context@ntg.nl
>> Subject: Re: [NTG-context] BUG: % is comment in btx fields
>> Message-ID: <1494294055.19890.36.ca...@gmail.com>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> On Mon, 2017-05-08 at 20:15 -0400, Rik Kabel wrote:
>>> On 2017-05-08 17:44, Henri Menke wrote:
>>>> Dear list,
>>>>
>>>> The percent character in btx field is taken as a comment characters
>>>> which leads to the rest of the field being discarded.  In the MWE
>>>> below, the URL is cut off at the % sign and everything after it is
>>>> lost.
>>>>
>>>> Cheers, Henri
>>>>
>>>>
>>>> ---
>>>>
>>>>
>>>> \startbuffer[references]
>>>> @misc{kraft,
>>>>   author = "Kraft, Nathan",
>>>>   title = "Mr Kraft's Virtual Filing Cabinet",
>>>>   year = "2015",
>>>>   url = "http://mrkraft.wikispaces.com/Mr+Kraft%27s+Virtual+Filing+
>>>> Cabi
>>>> net"
>>>> }
>>>> \stopbuffer
>>>>
>>>> \usebtxdataset[references.buffer]
>>>> \usebtxdefinitions[apa]
>>>>
>>>> \starttext
>>>>
>>>> \nocite[kraft]
>>>> \placelistofpublications
>>>>
>>>> \stoptext
>>>  The bibtex entry in this example is provided in a buffer. The buffer
>>> mechanism does not handle characters any differently than other text
>>> in the file, and % in a ConTeXt buffer has to be escaped if it does
>>> not signify a comment.
>>
>> That is simply not true!  Content inside ConTeXt buffers is as verbatim
>> as reading an external file.  Try \typebuffer instead of \getbuffer
>> your example below and observe that the comment sign is perfectly
>> preserved.
>>
>>> If you specify an external (.bib or .bibtex) file to supply the
>>> data,  % does not need to be escaped. So, this part is simple user
>>> error.
>>> (With
>>> \starttext
>>> \startbuffer
>>>   abc%def
>>>
>>>   ghi\%jkl
>>> \stopbuffer
>>> \getbuffer
>>> \stoptext
>>> you do not get %def in the output. Why do yo

[NTG-context] \overline and \overbar

2017-05-09 Thread Jeong Dal

Dear all,

In the following sample, the outputs of \overline and of \overbar are slightly 
different.
I used \overline in LaTeX. 
But  it takes more vertical space that cause the alignment trouble while using 
\overbar has no problem at all.
Is it normal behavior? 

Thank you.

Best regards,

Dalyoung


\starttext
\startitemize[n]
\item Which is true?

\startitemize[n, packed, columns, two][stopper=,left=(, right=)]
\item $\overline{A} = A \cup A^\circ$
\item $\overline{A\cup B} = \overline{A} \cup \overline{B}$
\item If $A \subset B$ then $\overline{B} \subset \overline{A}$
\item $A\cup A'$ is an open set.
\stopitemize

\item Which is true?

\startitemize[n, packed, columns, two][stopper=,left=(, right=)]
\item $\overbar{A} = A \cup A^\circ$
\item If $A \subset B$ then $\overbar{B} \subset \overbar{A}$
\item $\overbar{A\cup B} = \overbar{A} \cup \overbar{B}$
\item $A\cup A'$ is an open set.
\stopitemize

\stopitemize

\stoptext


> 2017. 5. 9. 오후 7:00, ntg-context-requ...@ntg.nl 작성:
> 
> Send ntg-context mailing list submissions to
>   ntg-context@ntg.nl
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://mailman.ntg.nl/mailman/listinfo/ntg-context
> or, via email, send a message with subject or body 'help' to
>   ntg-context-requ...@ntg.nl
> 
> You can reach the person managing the list at
>   ntg-context-ow...@ntg.nl
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ntg-context digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: BUG: % is comment in btx fields (Henri Menke)
>   2. Re: BUG: % is comment in btx fields (Rik Kabel)
>   3. Re: BUG: % is comment in btx fields (Ulrike Fischer)
> 
> 
> --
> 
> Message: 1
> Date: Tue, 09 May 2017 13:40:55 +1200
> From: Henri Menke <henrime...@gmail.com>
> To: ntg-context@ntg.nl
> Subject: Re: [NTG-context] BUG: % is comment in btx fields
> Message-ID: <1494294055.19890.36.ca...@gmail.com>
> Content-Type: text/plain; charset="UTF-8"
> 
> On Mon, 2017-05-08 at 20:15 -0400, Rik Kabel wrote:
>> On 2017-05-08 17:44, Henri Menke wrote:
>>> Dear list,
>>> 
>>> The percent character in btx field is taken as a comment characters
>>> which leads to the rest of the field being discarded.  In the MWE
>>> below, the URL is cut off at the % sign and everything after it is
>>> lost.
>>> 
>>> Cheers, Henri
>>> 
>>> 
>>> ---
>>> 
>>> 
>>> \startbuffer[references]
>>> @misc{kraft,
>>>   author = "Kraft, Nathan",
>>>   title = "Mr Kraft's Virtual Filing Cabinet",
>>>   year = "2015",
>>>   url = "http://mrkraft.wikispaces.com/Mr+Kraft%27s+Virtual+Filing+
>>> Cabi
>>> net"
>>> }
>>> \stopbuffer
>>> 
>>> \usebtxdataset[references.buffer]
>>> \usebtxdefinitions[apa]
>>> 
>>> \starttext
>>> 
>>> \nocite[kraft]
>>> \placelistofpublications
>>> 
>>> \stoptext
>>  The bibtex entry in this example is provided in a buffer. The buffer
>> mechanism does not handle characters any differently than other text
>> in the file, and % in a ConTeXt buffer has to be escaped if it does
>> not signify a comment.
> 
> That is simply not true!  Content inside ConTeXt buffers is as verbatim
> as reading an external file.  Try \typebuffer instead of \getbuffer
> your example below and observe that the comment sign is perfectly
> preserved.
> 
>> If you specify an external (.bib or .bibtex) file to supply the
>> data,  % does not need to be escaped. So, this part is simple user
>> error.
>> (With
>> \starttext
>> \startbuffer
>>   abc%def
>> 
>>   ghi\%jkl
>> \stopbuffer
>> \getbuffer
>> \stoptext
>> you do not get %def in the output. Why do you expect different
>> behavior if the buffer holds a bibtex entry?)
>> 
>> The way hyphenatedurl handles things may well be worthy of
>> improvement.
>> 
>> -- 
>> 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/nt
>> g-context
>> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
>> archive  : ht

Re: [NTG-context] BUG: % is comment in btx fields

2017-05-09 Thread Ulrike Fischer

Am Mon, 8 May 2017 17:56:08 -0600 schrieb Alan Braslau:

> So bibtex has a funny way of dealing with comments, and do we really
> care about Scribe?

biber handles comments differently than bibtex, see e.g.
https://tex.stackexchange.com/questions/261261/are-comments-discouraged-in-a-bibtex-file

As a thumbrule one can sum the rule up that *inside* field text
comment chars should be input according the tex rule for the field
*type*. That means that normal textfields should use \%, while url's
and other verbatim-like field can use %.



> We made the choice NOT to remain *strictly* bibtex
> compatible, after all bibtex is limited to ASCII 7-bit!

That's not true bibtex has no real problem with 8-bit-encodings, and
works even quite often quite good with utf8 (when you don't try to
use at places where it can be broken into parts.




-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] BUG: % is comment in btx fields

2017-05-08 Thread Alan Braslau

On Tue, 9 May 2017 11:27:51 +1200
Henri Menke <henrime...@gmail.com> wrote:

> However, I wonder whether the treatment of % in bib files is correct,
> as regular BibTeX does treat the % verbatim.  Because the following
> LaTeX example works just fine, with unescaped %.  In my opinion this
> behaviour should be adopted by ConTeXt.

From BibTeXing:

7. For Scribe compatibility, the database files allow an @COMMENT
command; it’s not really needed because BibTEX allows in the database
files any comment that’s not within an entry. If you want to comment
out an entry, simply remove the ‘@’ character preceding the entry type.

...

14. LATEX’s comment character ‘%’ is not a comment character in the
database files.

From Tame the BeaST:

New entries always start with @. Anything outside the “argument” of a
“command” starting with an @ is considered as a comment. This gives an
easy way to comment a given entry: just remove the initial @. As usual
when a language allows comments, don’t hesitate to use them so that you
have a clean, ordered, and easy-to-maintain database. Conversely,
anything starting with an @ is considered as being a new entry.

There is a special entry type named @comment. The main use of such an
entry type is to comment a large part of the bibliography easily, since
anything outside an entry is already a comment, and commenting out one
entry may be achieved by just removing its initial @.

So bibtex has a funny way of dealing with comments, and do we really
care about Scribe? We made the choice NOT to remain *strictly* bibtex
compatible, after all bibtex is limited to ASCII 7-bit!

The % comment is *universal* in TeX, Metapost, etc. so we chose to
respect this, much stronger in my opinion, convention.

Alan

-- 
Alan Braslau
CEA DSM-IRAMIS-SPEC
CNRS UMR 3680
Orme des Merisiers
91191 Gif-sur-Yvette cedex FRANCE
tel: +33 1 69 08 73 15
fax: +33 1 69 08 87 86
mailto:alan.bras...@cea.fr
___
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] (geen onderwerp)

2017-05-05 Thread r . ermers

Dear Contexters,

Since yesterday I have a font-problem. Until yesterday this would work 
perfectly:

\usemodule[simplefonts][size=10pt] %voor mkiv
\setmainfont[dejavuserif] %voor simplefonts

The system fonts worked too. Yesterday I wanted to make a presentation with 
simpleslides. The fonts did not work. Then I tried complexslides. The modules 
work fine, the fonts do not. I then updated to the latest bèta: luatools — 
generate, context —generate, etc. No improvement.

Through mtxrun —script fonts I can see which fonts are accessible to Context. 
There things are probably going wrong, yet I do not know what. It appears that 
Context does not find the local fonts, and the system fonts only partially.

I work on OS X, Context versie: 2017.04.27 01:00
/Applications/ContextStandalone/tex/texmf-context/tex/context/base/mkiv/context.mkiv

Adjustments of texmf.cnf:
/Applications/ContextStandalone/tex/texmf/web2c/texmf.cnf
OSFONTDIR =.;~/Library/Fonts//;/System/Library/Fonts

Thank you on beforehand for your help. It is much appreciated.

Robert




Snippets from the log file:

fonts   > latin modern fonts are not preloaded
languages   > language 'en' is active


fonts   > names > font database has mismatching configuration and file 
hashes
fonts   > names > unable to access database cache
simplefonts > font ''fontin'' not found
simplefonts > font ''fontin'' not found
[many identical lines]
fonts   > defining > font with asked name 'unknown' is not found using 
lookup 'file'
fonts   > defining > unknown font 'unknown', loading aborted
fonts   > defining > unable to define 'unknown' as 
'simplefonts:1-9pt-rm-tf-0--0'
fonts   > otf loading > loading 

—> some of the otf files are being found:

'/Applications/ContextStandalone/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf',
 hash 'latinmodern-math'
fonts   > otf loading > loading done
fonts   > otf loading > file size: 733500
fonts   > otf loading > missing specification
[many identical lines]
fonts   > otf loading > loading, optimizing, packing and caching time 
0.248, pack time 0.045
simplefonts > font ''delicious'' not found
simplefonts > font ''delicious'' not found
[many identical lines]
fonts   > defining > font with asked name 'unknown' is not found using 
lookup 'file'
fonts   > defining > unknown font 'unknown', loading aborted
fonts   > defining > unable to define 'unknown' as 
'simplefonts:2-9pt-rm-tf-0–0'

close source> level 5, order 10, name 
'/Applications/ContextStandalone/tex/texmf-context/tex/context/fonts/mkiv/type-imp-euler.mkiv'
fonts   > defining > font with asked name 'unknown' is not found using 
lookup 'file'
fonts   > defining > unknown font 'unknown', loading aborted
fonts   > defining > unable to define 'unknown' as 
'simplefonts:4-9pt-rm-tf-0--0'

close source> level 6, order 10, name 
'/Applications/ContextStandalone/tex/texmf-context/tex/context/fonts/mkiv/type-imp-dejavu.mkiv'
close source> level 5, order 10, name 
'/Applications/ContextStandalone/tex/texmf-context/tex/context/fonts/mkiv/type-imp-euler.mkiv'
fonts   > defining > font with asked name 'unknown' is not found using 
lookup 'file'
fonts   > defining > unknown font 'unknown', loading aborted

[snippet]

Overfull \hbox (23.24092pt too wide) in paragraph at lines 10--14

[This text is then printed in the pdf:]
[][Serif][DefaultFont][fallbacks=mainfontregularfallbacks,features=mainfontregularfeatures][SerifItalic][DefaultFont][fallbacks=mainfontitalicfallbacks,features=mainfontitalicfeatures][SerifSlanted][DefaultFont][fallbacks=mainfontslantedfallbacks,features=mainfontslantedfeatures][SerifBold][DefaultFont][fallbacks=mainfontboldfallbacks,features=mainfontboldfeatures][SerifBoldItalic][DefaultFont]

identifierfamilynamefontname  filename   
subfont   instances
fontinsmallcaps   fontinsmallcaps   fontinsmallcaps   Fontin-SmallCaps.otf

Yet other fonts from the Fontine are installed system-wide (found by fc-list):

/Users/mac/Library/Fonts/Fontin-Regular.ttf: Fontin:style=Regular
/Users/mac/Library/Fonts/Fontin-Bold.ttf: Fontin:style=Bold
/Users/mac/Library/Fonts/Fontin-SmallCaps.ttf: Fontin SmallCaps:style=SmallCaps
/Users/mac/Library/Fonts/Fontin-Italic.ttf: Fontin:style=Italic

The same fonts I placed in my local installation: 
Applications/ContextStandalone/tex/texmf-local/fonts/public/fontin/otf/Fontin-Bold.otf
Fontin-Italic.otf
Fontin-Regular.otf
Fontin-SmallCaps.otf


___
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/listin

Re: [NTG-context] getting the glyph of a character

2017-05-01 Thread Alan Braslau

On Mon, 1 May 2017 21:20:33 -0400
Mohammad Hossein Bateni <bat...@gmail.com> wrote:

> MetaPost's documentation mentions that glyph operator works on Adobe
> Type 1 fonts.  Does it also work with OpenType fonts when used from
> within LuaTeX and CONTEXT?

The metafun manual gives many ways of manipulating text.
(the metapost "glyph" operator is a bit archaic...)

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] getting the glyph of a character

2017-05-01 Thread Mohammad Hossein Bateni

MetaPost's documentation mentions that glyph operator works on Adobe Type 1
fonts.  Does it also work with OpenType fonts when used from within LuaTeX
and CONTEXT?

On Mon, May 1, 2017 at 7:36 PM, Jeong Dal <hak...@me.com> wrote:

> Dear all,
>
> First of all, the sample code is working under the ConTeXt
> beta(standalone) installed in my notebook.
> I am very sorry to send mails of false result.
>
> I found the file “lm-ec.map” installed in the ConTeXt beta(standalone),
> and I don’t know why it was not working in the iMac. I have to check the
> installation.
>
> However, I’d like to know how to make map files of the fonts in the system
> for which the map file is not provided?
>
> Thank you for reading.
>
> Best regards,
>
> Dalyoung
>
>
> \startbuffer[outline]
> fontmapfile "=lm-ec.map";
> %beginfig(56);
> picture q;
> path p;
> interim ahlength := 12bp;
> interim ahangle := 25;
> q := glyph “E" of "ec-lmr10" scaled .2;
> %draw q;
>  for item within q:
>   p := pathpart item;
>   draw p withcolor (.6,.9,.6)
>   withpen pencircle scaled 1.5;
> endfor
> \stopbuffer
>
> \starttext
> \processMPbuffer[outline]
> \stoptext
> 
> ___
> 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] getting the glyph of a character

2017-05-01 Thread Jeong Dal

Dear all.

At page 50-52 of  the manual of metapost, “Mpman”, it is explained to get a 
glyph of font using the command ‘glyph'.
glyph ⟨numeric expression⟩ of ⟨string expression⟩ 

glyph ⟨string expression⟩ of ⟨string expression⟩ . 

Is it possible to do the similar thing in metafun?

I couldn’t make it happen using the following code.

\startbuffer[outline]
%fontmapfile "=lm-ec.map";
  picture q;
  path p;
  interim ahlength := 12bp;
  interim ahangle := 25;
  q := glyph 100 of "ArialMT"; %nfont defaultfont  scaled defaultscale;
 draw q;
\stopbuffer

\starttext
\processMPbuffer[outline]
\stoptext

if the first line “fontmapfile …” is alive, then fatal error occurred.
Without it, it is running without error, but no output at all.

I copied the sample code in mpman below.

Thank you for reading.

Best regards,

Dalyoung



fontmapfile “=lm-ec.map”;
beginfig(56);
  picture q;
  path p;
  interim ahlength := 12bp;
  interim ahangle := 25;
  q := glyph "Dcaron" of "ec-lmr10" scaled .2;
  for item within q:
p := pathpart item;
drawarrow p withcolor (.6,.9,.6)
withpen pencircle scaled 1.5;
for j=0 upto length p:
  pickup pencircle scaled .7;
  draw (point j of p -- precontrol j of p)
  dashed evenly withcolor blue;
  draw (point j of p -- postcontrol j of p)
  dashed evenly withcolor blue;
  pickup pencircle scaled 3;
  draw precontrol j of p withcolor red;
  draw postcontrol j of p withcolor red;
  pickup pencircle scaled 2;
  draw point j of p withcolor black;
endfor
  endfor
endfig; 

 



> 2017. 4. 30. 오후 7:00, ntg-context-requ...@ntg.nl 작성:
> 
> Send ntg-context mailing list submissions to
>   ntg-context@ntg.nl
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://mailman.ntg.nl/mailman/listinfo/ntg-context
> or, via email, send a message with subject or body 'help' to
>   ntg-context-requ...@ntg.nl
> 
> You can reach the person managing the list at
>   ntg-context-ow...@ntg.nl
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ntg-context digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Wrong redirection in contextgarden.net (Mojca Miklavec)
>   2. Re: Wrong redirection in contextgarden.net (Nicola)
>   3. Re: Wrong redirection in contextgarden.net (Mojca Miklavec)
>   4. High-level command for translated names (Henri Menke)
>   5. Re: High-level command for translated names (Wolfgang Schuster)
> 
> 
> --
> 
> Message: 1
> Date: Sat, 29 Apr 2017 18:05:14 +0200
> From: Mojca Miklavec <mojca.miklavec.li...@gmail.com>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] Wrong redirection in contextgarden.net
> Message-ID:
>   <calbomsbtkzqwa9k7vfnjoyacumyc3xs8hu9gg-pyx-yxmbx...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> On 29 April 2017 at 09:47, Nicola wrote:
>> For a while now, when I connect to contextgarden.net, I get redirected
>> to wiki.contextgarden.net// (note the double slash). Is it just me, or
>> something to be fixed in the web site?
> 
> The server uses
>RedirectMatch permanent ^(.*)$ http://wiki.contextgarden.net/$1
> 
> I'm looking for a better suggestion.
> 
> Mojca
> 
> 
> --
> 
> Message: 2
> Date: Sat, 29 Apr 2017 20:25:20 +0200
> From: Nicola <nvitacolo...@gmail.com>
> To: ntg-context@ntg.nl
> Subject: Re: [NTG-context] Wrong redirection in contextgarden.net
> Message-ID: <oe2lqb$ehk$1...@blaine.gmane.org>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 29/04/2017 18:05, Mojca Miklavec wrote:
>> On 29 April 2017 at 09:47, Nicola wrote:
>>> For a while now, when I connect to contextgarden.net, I get redirected
>>> to wiki.contextgarden.net// (note the double slash). Is it just me, or
>>> something to be fixed in the web site?
>> 
>> The server uses
>>RedirectMatch permanent ^(.*)$ http://wiki.contextgarden.net/$1
>> 
>> I'm looking for a better suggestion.
> 
> Wouldn't just
> 
>   Redirect permanent / http://wiki.contextgarden.net/
> 
> do? (It may be recursive if the virtual host is the same.)
> 
> If not, how about:
> 
> RedirectMatch permanent ^/(.*)$ http://wiki.contextgarden.net/$1
> 
> As a last resource, mod_rewrite should work:
> 
> RewriteEngine on
> RewriteCond %{HTTP_HOST} ^contextgarden\.net$ [NC]
> RewriteRule ^(.*)$ http://wiki.contextgarden.net/$1 [R=301,L]
> 
> Nicola
> 
> 
> 
> 
> --
> 
> Message: 3
> Date: Sat, 29 Apr 2017 21:29:06 +0200
> From: Mojca Miklavec <mojca.miklavec.li...@gmail.com>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] Wrong redirection in contextgarden.net
> Message-ID:
>

Re: [NTG-context] Teletype in tabulate

2017-04-20 Thread Willi Egger

Ah, stupid me, should have known that. Thank you Hans!

Willi
> On 20 Apr 2017, at 17:17, Hans Hagen <pra...@wxs.nl> wrote:
> 
> On 4/20/2017 4:53 PM, Willi Egger wrote:
>> Hi all,
>> 
>> I have the context version 2017.04.16 12:32.
>> 
>> Now I detect that here the tabulate environment throws an error when using 
>> the T key for teletype in the preamble.
>> 
>> I am stuck…
>> 
>> /Users/willi/Documents/TEXdata/lezingenMAPSNTG/Bachotex2017/test.tex: ! 
>> Missing number, treated as zero
>> 
>> 
>> \unskip
>> \tabl_tabulate_column_normal #1->\unskip
>> \aligntab \ifconditional 
>> \c_tabl_ta...
>> \tabl_tabulate_insert_body ...NC \paperheight \NC
>>  29.000cm \NC \NR
>> \tabl_tabulate_insert_content ...late_insert_body
>>  
>> \tabl_tabulate_insert_foot...
>> \tabl_tabulate_process ...tabulate_insert_content
>>  \crcr 
>> }}\anch_backgrounds_...
>> l.14 \stoptabulate
>> 
>> 
>> \starttext
>> \starttabulate[|lT|r|]
>>  \NC \paperheight \NC 29.000cm \NC\NR
>> \stoptabulate
>> 
>> \stoptext
> 
> because T is not \type
> 
>   \NC \type{\paperheight} \NC 29.000cm \NC\NR
> 
> or
> 
>   \NC \string\paperheight \NC 29.000cm \NC\NR
> 
> -
>  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] Teletype in tabulate

2017-04-20 Thread Hans Hagen


On 4/20/2017 4:53 PM, Willi Egger wrote:

Hi all,

I have the context version 2017.04.16 12:32.

Now I detect that here the tabulate environment throws an error when using the 
T key for teletype in the preamble.

I am stuck…

/Users/willi/Documents/TEXdata/lezingenMAPSNTG/Bachotex2017/test.tex: ! Missing 
number, treated as zero


\unskip
\tabl_tabulate_column_normal #1->\unskip
 \aligntab \ifconditional \c_tabl_ta...
\tabl_tabulate_insert_body ...NC \paperheight \NC
  29.000cm \NC \NR
\tabl_tabulate_insert_content ...late_insert_body
  \tabl_tabulate_insert_foot...
\tabl_tabulate_process ...tabulate_insert_content
  \crcr }}\anch_backgrounds_...
l.14 \stoptabulate


\starttext
\starttabulate[|lT|r|]
\NC \paperheight \NC 29.000cm \NC\NR
\stoptabulate

\stoptext


because T is not \type

\NC \type{\paperheight} \NC 29.000cm \NC\NR

or

\NC \string\paperheight \NC 29.000cm \NC\NR

-
  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] Choosing STIX stylistic sets

2017-04-16 Thread Hans Hagen


On 4/16/2017 6:01 PM, Hans Åberg wrote:



On 16 Apr 2017, at 16:37, Hans Hagen <pra...@wxs.nl> wrote:

On 4/16/2017 3:56 PM, Hans Åberg wrote:



On 15 Apr 2017, at 00:22, Hans Hagen <pra...@wxs.nl> wrote:

On 4/14/2017 12:42 PM, Hans Åberg wrote:

With the STIX Two fonts [1-2], one can choose say Stylistic Set 8  for 
more upright integrals. How is that done in ConTeXt with XITS?

1. https://sourceforge.net/projects/stixfonts/
2. https://en.wikipedia.org/wiki/STIX_Fonts_project#STIX_2.0.0


see stix-two-math.lfg

\setmathfontalternate{whatever}


This is complicated, it seems: The STIX2Math font does not have the text 
support that STIX has, so one might want a virtual font, or set the math font 
independently (I could find any info about that on ConTeXtGarden).


there is no real text support in math fonts ... it's alphabets ... the fact 
that one shares e.g. a textfont in math mode with a regular text font outside 
math is something traditional tex (and more a font design and macro package 
issue that an engine thing)


So far I have only used \setupbodyfont[xits,10pt], but found no info about how 
to specifically selecting fonts for the different modes or ranges.


\setupbodyfont[termes]
\setupbodyfont[pagella]
\setupbodyfont[bonum]

on windows (cambria is the opentype reference fonmt for math):

\setupbodyfont[cambria]

or when you bought lucida ot:

\setupbodyfont[lucidaot]

all have math


just use a text font .. why does texinfo needs a math font? only for math i 
assume


Right, and writing the Unicode math characters in the UTF-8 source file, in 
part because they will be also used as such in the source code of a program. 
One can otherwise embed formulas using traditional TeX syntax.


it's a bit more complex in the tex world: users are accustomed to seeing 
the a in $a$ becoming a math italic a and $\bf a$ getting a bold a .. 
both are in the unicode math alphabet so a macro package has to support 
both these switch driven inputs and direct unicode math (also because 
cut and paste from a pdf should work)


(the way macro packages implement that can be fundamental different)

(there is a font project under way that will provide monospaced math 
characters for editing)



Also, in script/calligraphic, STIX2 seems to have is the other way around 
relative stix-two-math.lfg: setting the feature 'ss01' yields the traditional 
English script style, whereas the default is the AMS calligraphic style.


that's also a design issue


Not anymore, perhaps, as some mathematicians seem to think of them as different 
semantic styles.


if so, then that will be reflected in unicode alphabets (just make a 
string case for it)



On most other features, the STIX2 default seems to what I think of as 
traditional.


personally i'd never use stix for something


I used STIX because it came around, and, also, the AMS has been involved. It 
good there are other fonts, though.


finally came around .. but it's not a pretty font


(one can use texgyre pagella or termes)


What is the advantage of those?


a palatino based font looks imo better than stix

(as open type font they are around a bit longer and we have a bit more 
influence on their development)


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] frac font feature doesn't work as expected

2017-04-05 Thread Ulrike Fischer

Am Wed, 5 Apr 2017 13:00:29 +0200 schrieb luigi scarso:


> if you see
> fonts   > otf chain > feature 'frac', type
> 'gsub_contextchain', chain lookup 's_s_7':  is not yet supported (1)
> then ... it need to be supported.

Yes, that's what I see ;-(.
-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___
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] Problem loading a DLL with the latest Ctx beta

2017-04-05 Thread Procházka Lukáš Ing .

 > used backend: pdf (backend for directly generating pdf output)
mkiv lua stats  > jobdata time: 0.000 seconds saving, 0.000 seconds loading
mkiv lua stats  > callbacks: 139 direct, 248 indirect, 387 total
mkiv lua stats  > loaded patterns: en::2, load time: 0.000
mkiv lua stats  > result saved in file: WinTest.pdf, compresslevel 3, 
objectcompresslevel 3
mkiv lua stats  > loaded fonts: 2 files: latinmodern-math.otf, 
lmroman12-regular.otf
mkiv lua stats  > font engine: otf 3.028, afm 1.512, tfm 1.000, 4 instances, 
load time 0.152 seconds
mkiv lua stats  > used platform: mswin, type: windows, binary subtree: 
texmf-mswin
mkiv lua stats  > luatex banner: this is luatex, version 1.0.5 (tex live 
2017/w32tex)
mkiv lua stats  > control sequences: 45005 of 65536 + 10
mkiv lua stats  > lua properties: engine: lua, used memory: 41 MB (ctx: 40 MB), 
hash type: lua, hash chars: min(32,40), symbol mask: utf (¤ä╬Á¤ç)
mkiv lua stats  > runtime: 0.46 seconds, 1 processed pages, 1 shipped pages, 
2.174 pages/second

mtx-context | fatal error: return code: 1
"

- And WinText.mkiv has the following content:


\startluacode
  require "WinCon"
\stopluacode

\starttext
  A
\stoptext


Strange thing is that WonCon.dll with Ctx used to work for several years... 
What is the problem now?

I attached also the WinCon.dll (built with VS 2008 - Release version; zipped 
and ZIP renamed to PIZ).

Do I have to rebuild the WinCon.dll source?

Any answer would be appreciated...

Best regards,

Lukas


--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz | 
IDDS:nrpt3sn
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751 (+420 720 951 172)
Fax: +420 244 461 038

WinTest.log
Description: Binary data


WinTest.mkiv
Description: Binary data


WinCon~.piz
Description: Binary data
___
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] frac font feature doesn't work as expected

2017-04-05 Thread luigi scarso

On Wed, Apr 5, 2017 at 10:15 AM, Ulrike Fischer <ne...@nililand.de> wrote:
> \starttext
>
> \font\test={file:linlibertine_r.otf:+frac}
> \test 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100
> \stoptext
>
> gives as output
>
> ½ 3¾ 5⅚ 7⅜ 9/10 1⅟12 31415/27182 1000/100


\usetypescriptfile[libertine]
\setupbodyfont[libertine,12pt]
\definefontfeature[frac][frac=yes]

\starttext

{\addff{frac}  1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100}
\stoptext

if you see
fonts   > otf chain > feature 'frac', type
'gsub_contextchain', chain lookup 's_s_7':  is not yet supported (1)
then ... it need to be supported.

( I have a local patch (by Hnas) that gives
¹⁄₂ ³⁄₄ ⁵⁄₆ ⁷⁄₈ ⁹⁄₁₀ ¹¹⁄₁₂ ³¹⁴¹⁵⁄₂₇₁₈₂ ¹⁰⁰⁰⁄₁₀₀
with the otf fonts from
http://www.ctan.org/tex-archive/fonts/libertine
)

-- 
luigi
___
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] OSX fonts

2017-04-03 Thread Henning Hraban Ramm

Am 2017-04-03 um 16:07 schrieb Andrea Valle <va...@di.unito.it>:

> I have a question which is really basic. MacOSX here.
> I looked at the wiki, but the whole matter is a bit far from my knowledge.
> Is there a way to use system fonts? I *think* I remember something like 
> simpletypescript package

See http://wiki.contextgarden.net/Fonts_in_LuaTeX

Depends a bit on the actual fonts.
Usually it’s no problem to use system fonts.

You need to setup the variable OSFONTDIR as a path to your font directories, 
e.g.:

export 
OSFONTDIR="/System/Library/Fonts//:/Library/Fonts//:~/Library/Fonts//:~/Library/texmf/fonts//:~/FontExplorer\\
 X/Font\\ Library//"

Put this in ~/.bashrc, ~/.bash_profile or ~/.profile (don’t know any more which 
is default).

Then reload the font database:

mtxrun --script fonts --reload

Try, if your desired font is already known, e.g.

\setupbodyfont[gentium,rm,10pt]

Or check if there is a typescript in the distribution (look for the font name 
in the source browser).

If not, then you should setup a typescript. I attached examples.

If that doesn’t help, ask with details.


Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD



type-alegreya.tex
Description: Binary data


type-devroye.tex
Description: Binary data
___
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] A question about Lucida fonts

2017-03-30 Thread Hans Hagen


On 3/30/2017 2:01 PM, Otared Kavian wrote:



On 30 Mar 2017, at 13:52, Hans Hagen <pra...@wxs.nl> wrote:

opentype of course .. more complete, features and easier to use ... also most 
value for money


Thanks Hans for your quick reply!
I guess the file type-imp-lucida-opentype.mkiv is there to take care of 
everything when using the font: so once I have the fonts, and ConTeXt knows 
where they are,
can I use them just by saying
\setupbodyfont[lucida]


\setupbodyfont[lucidaot]


or are there other commands to issue?

Many thanks for your precious help: OK
___
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] A question about Lucida fonts

2017-03-30 Thread Otared Kavian

> On 30 Mar 2017, at 13:52, Hans Hagen <pra...@wxs.nl> wrote:
> 
> opentype of course .. more complete, features and easier to use ... also most 
> value for money

Thanks Hans for your quick reply! 
I guess the file type-imp-lucida-opentype.mkiv is there to take care of 
everything when using the font: so once I have the fonts, and ConTeXt knows 
where they are,
can I use them just by saying
\setupbodyfont[lucida]
or are there other commands to issue?

Many thanks for your precious help: OK
___
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] A question about Lucida fonts

2017-03-30 Thread Hans Hagen


On 3/30/2017 1:43 PM, Otared Kavian wrote:

Hi,

I would like to buy the set of Lucida fonts from TUG
https://www.tug.org/store/lucida/index.html
but I am wondering which flavor, Open Type or Type 1, is supposed to
work smoothly (and easily…) with ConTeXt mkiv. Actually a very long time
ago I bought those fonts from yandy.com <http://yandy.com>, but those
were designed to work only on a Mac OS 9 (yes I am so that old… :-).

Since I am sure some people on the mailing list have an experience and
good advices to share, I would appreciate having their opinion.


opentype of course .. more complete, features and easier to use ... also 
most value for money


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
___

< 9 10 11 12 13 14 15 16 17 18 >

1301 - 1400 of 6755 matches

Mail list logo