Re: [NTG-context] Workshop at FrOSCon

2022-06-07 Thread Henning Hraban Ramm via ntg-context
Am 08.06.22 um 07:18 schrieb juh via ntg-context: For the Developer Room we need at least three people willing to attend the whole time at least for one day. If anyone would help me to organize a 2h-Bootstrap Workshop for ConTeXt I would be very happy. Due to my holidays I am only available

[NTG-context] Workshop at FrOSCon

2022-06-07 Thread juh via ntg-context
Dear all, this year there will be a real life FrOSCon in Bonn Sankt Augustin at the Fachhochschule Rhein-Sieg again. https://www.froscon.org/cfp/cfpapers/ I am considering to submit a workshop to bootstrap people with ConTeXt, but I am not the best one to do this. So I would like to discuss if

Re: [NTG-context] Typesetting modern Greek (UTF8) with ConTeXt

2022-06-07 Thread Pablo Rodriguez via ntg-context
On 6/7/22 18:32, Henning Hraban Ramm via ntg-context wrote: > [...] > \installlanguage >[\s!gr] >[\s!patterns=\s!agr] % ok? > > \installlanguage [\s!greek] [\s!gr] > > So it seems that is wrong / incomplete. > > AFAI understand, "el" should be modern greek (post 1982, monotonic), > "grc"

Re: [NTG-context] Typesetting modern Greek (UTF8) with ConTeXt

2022-06-07 Thread Henning Hraban Ramm via ntg-context
Am 07.06.22 um 17:42 schrieb Pablo Rodriguez via ntg-context: On 6/6/22 22:59, Henning Hraban Ramm via ntg-context wrote: I can’t remember where I found the information that el-monoton (synonymous to el and gr) and el-polyton (synonymous to agr and grc) should be available. Hyphenation

Re: [NTG-context] Two minor questions

2022-06-07 Thread Stefan Nedeljkovic via ntg-context
I just found out that it's a tex shorthand for an endash. Is there a way to globally turn that shortcut off? On Tue, Jun 7, 2022 at 5:20 PM Stefan Nedeljkovic wrote: > Yes I may use them. Why is that a problem? Is it some special context > syntax? How do I escape them or turn them off? > > On

Re: [NTG-context] Typesetting modern Greek (UTF8) with ConTeXt

2022-06-07 Thread Pablo Rodriguez via ntg-context
On 6/6/22 22:59, Henning Hraban Ramm via ntg-context wrote: > Am 06.06.22 um 19:14 schrieb Pablo Rodriguez via ntg-context: > >> \language[gr], but beware since it uses patterns for ancient Greek. > > That is documented in the manual languages-mkiv.pdf. This was news to me before reading

Re: [NTG-context] Two minor questions

2022-06-07 Thread Stefan Nedeljkovic via ntg-context
Yes I may use them. Why is that a problem? Is it some special context syntax? How do I escape them or turn them off? On Tue, Jun 7, 2022 at 5:05 PM Wolfgang Schuster < wolfgang.schuster.li...@gmail.com> wrote: > Stefan Nedeljkovic schrieb am 07.06.2022 um 07:25: > > Thank you very much Wolfgang!

Re: [NTG-context] Two minor questions

2022-06-07 Thread Wolfgang Schuster via ntg-context
Stefan Nedeljkovic schrieb am 07.06.2022 um 07:25: Thank you very much Wolfgang! But, there is still something weird going on with the font. I updated the files on Drive. Please see line 19, the last word "and". It is clearly out of alignment with the gid. I tested the alignment in MP and it

Re: [NTG-context] overfull gone?

2022-06-07 Thread Steffen Wolfrum via ntg-context
> Am 28.05.2022 um 14:16 schrieb Hans Hagen via ntg-context > : > > On 5/28/2022 12:43 PM, Steffen Wolfrum via ntg-context wrote: >> Hi, >> in order to easily see overfull lines I used \overfullrule30\points : this >> gave a clear black box in the right margin. >> Is this command

Re: [NTG-context] Two minor questions

2022-06-07 Thread Stefan Nedeljkovic via ntg-context
I tried \setupspacing[fixed] but it didn't help. To prove that the font characters really are half a cell wide I added the line \emdash \dorecurse{39}{ \emdash}. Files on drive are updated. On Tue, Jun 7, 2022 at 7:25 AM Stefan Nedeljkovic wrote: > Thank you very much Wolfgang! But, there is

Re: [NTG-context] Contractions in ligature suppression word list

2022-06-07 Thread Denis Maier via ntg-context
A somewhat more complete testfile with a couple of options is below. My context installation is not current so please double check, but I think it boils down to this: apostrophes seem not to be considered to be part of a word. Once I enable wolfin under \startlanguageoptions[en] it will