Re: [NTG-context] Hyphenation LuaTeX

[Pablo Rodriguez]

On 1/17/20 12:05 PM, MANUEL GONZALEZ SUAREZ wrote:
> Hi:
> When I compile a document with the following preamble:
> [...]
> \usemodule[simplefonts]

Hi Manuel,

as Hraban and Thomas mentioned, the module has been deprecated.

The commands \definefallbackfamily, \definefontfamily and \setupbodyfont
are standard ConTeXt commands, they don’t require any module.

> \definefallbackfamily [mainface] [serif] [Old Standard]
> [range={greekandcoptic, greekextended}, force=yes, rscale=auto]

"preset=range:greek" might replace "range={greekandcoptic, greekextended}".

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] typing+framedtext: different behaviour between TL2017 and 2019

[Tomas Hala]

# # This should fix it:
# # \setupstartstop
# #   [DefaultSnippet]
# #   [before=,
# #    after=,
# #    style=]
# # Wolfgang
# 
# Unfortunately not, I tried it in preamble (with no effect)
# as well as after the \starttext (with no effect + text of parameters were 
pushed to the document).

Your code works, thank you for the help.

The no-effect-problem was caused by some invisible characters (0xc2a0)
inside, they disrupted the token processing.
 
Tomáš
___
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] typing+framedtext: different behaviour between TL2017 and 2019

[Tomas Hala]

Fri, Jan 17, 2020 ve 08:48:47PM +0100 Wolfgang Schuster napsal(a):
# This should fix it:
# 
# \setupstartstop
#   [DefaultSnippet]
#   [before=,
#    after=,
#    style=]
# Wolfgang

Unfortunately not, I tried it in preamble (with no effect)
as well as after the \starttext (with no effect + text of parameters were 
pushed to the document).

Tomáš

___
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] typing+framedtext: different behaviour between TL2017 and 2019

[Wolfgang Schuster]

Tomas Hala schrieb am 17.01.2020 um 20:32:

Hi Wolfgang,

two files with the difference are attached.

I thought about the current beta -- it could be good way for me but
unfortunately it does not suit for my students.


This should fix it:

\setupstartstop
  [DefaultSnippet]
  [before=,
   after=,
   style=]

Wolfgang

___
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] typing+framedtext: different behaviour between TL2017 and 2019

[Tomas Hala]

Hi Wolfgang, 

two files with the difference are attached.

I thought about the current beta -- it could be good way for me but 
unfortunately it does not suit for my students.

Tomáš

Fri, Jan 17, 2020 ve 07:40:57PM +0100 Wolfgang Schuster napsal(a):
# Tomas Hala schrieb am 17.01.2020 um 15:18:
# >Hi all,
# >
# >if I compile the following (minimised) code with ConTeXt from TL2017,
# >I receive expected result -- one framed gray box with correct width.
# >
# >\starttext\showframe
# 
>\defineframedtext[MPT][background=color,backgroundcolor=gray,width=\makeupwidth,frame=on,offset=1cc,]
# >\setuptyping[MP][before={\startMPT},after={\stopMPT},]
# >\startMP bla \stopMP
# >\stoptext
# >
# >Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as 
TL2019)
# >and I have got _two_ boxes -- the outer one is correct and frames the typing 
environment
# >as in the past whereas the new box frames the text inside the typing.
# 
# Your example works fine with the current beta and since you don't
# show the differences between the different installations there is
# nothing which can be done.
# 
# Wolfgang


typing-tl17.pdf
Description: Adobe PDF document


typing-tl19.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] Quotation dash issues with semantic markup

[Wolfgang Schuster]

Hans Hagen schrieb am 30.12.2019 um 10:19:

On 12/30/2019 5:03 AM, Sam May wrote:


\setuplanguage[en]
[leftquotation=\quotedash~,
rightquotation=~\quotedash,
leftsentence=\removeunwantedspaces~\endash\space,
midsentence=\removeunwantedspaces~\endash\space,
%    leftsentence=\endash~,
%    midsentence=~\endash,
rightsentence=~\endash]
\define\quotedash{\emdash\endash}

%\setupbackend[export=yes]

\starttext

\startsection[title=Introduction]
Any of you able to help me get my quotation dashes into line when 
automatically
inserted by the semantic commands?  I'm sure a number of you look at 
this style
and cringe, but \cap{A.} I'm not looking for grammatical input, and 
\cap{B.}
I'm intending this for a non-English language where the quotation dash 
(though

still not most common) isn't as out of place.
\stopsection

\startsection[title=Desired rendering]
\quotedash~Speech should always have a dash at the start, but none at 
the end

of a paragraph.

\quotedash~Dialog asides should not duplicate dashes,~\endash\ he
said.~\quotedash\ Also, this doesn't reflect the spacing mentioned in 
section

\in[extra].  \quotedash~nor, as above, add ones at the end of paragraphs.
\endash~he continued.
\stopsection

\startsection[title=Actual output]
\speech{Speech should always have a dash at the start, but none at the 
end of a

paragraph.}

\speech{Dialog asides should not duplicate dashes, \aside{he said.}} 
Also, note
the spacing isn't removed despite \type{\removeunwantedspaces}, but 
instead

duplicated.  \speech{nor, as above, add ones at the end of paragraphs.
\aside{he continued.}}
\stopsection

\startsection[title=Additional considerations and 
observations,reference=extra]
It would also be nice if a quote ending in a period carried the 
\quote{broad}

spacing to the other side of the (ending) quote dash |=| the dash before
\quote{Also} above would be packed on the left and broad on the right. 
I know

this might be a lot trickier to code, and only consider it a bonus.

The issue with \type{\removeunwantedspaces} only seems to affect the 
command
forms.  When inserted directly |<| as here |>| the spacing acts as 
desired in
the \cap{PDF} (as expected, the \cap{XML} doesn't understand the 
order).  Also,

the right \type{|>|} doesn't require either of the explicit spacing
instructions (beyond being non-breaking) while the others do; try 
switching the

commented lines and re-rendering.

The quotation dash itself only \emph{looks} as I want it; when I 
highlight and
copy the text or export it to the \cap{XML} backend, it's still two 
dashes next
to each other.  Instead, I'd like it to be the Unicode bar U+2015.  
I'm not
sure if \TEX/\LUATEX\ allows that difference between appearance and 
interaction
(I do know \cap{PDF} does), so if there's some way of adding a new 
glyph to the
font |<| one that mimics the other dashes even if the font changes |>| 
I'd love
to actually use the proper codepoint.  As is, that doesn't work in the 
standard

font(s): [\char"2015].
\stopsection

\stoptext

I bet that Wolfgang has the answers to the speech setup so I'll do the 
font part.


It's possible to use leaders to remove multiple dashes and also dashes 
at the end of a paragraph but this will only work for the PDF. A 
limitation is that you can't use the existing \speech and \aside 
commands because they use groups which prevents the removal of unwanted 
dashes.


\unprotect

\def\speech_dash
  {\setbox\scratchbox\hbox{\texthorizontalbar\space}%
   \leaders\copy\scratchbox\hskip\wd\scratchbox}

\def\speech_left
  {\ifhmode
 \removeunwantedspaces
   \else
 \dontleavehmode
   \fi
   \space\speech_dash}

\def\speech_right
  {\removeunwantedspaces
   \space\speech_dash}

%\define[1]\speech
%  {\speech_left#1\speech_right}

\unexpanded\def\speech
  {\speech_left
   \bgroup
   \aftergroup\speech_right
   \let\next=}

\def\aside_dash
  {\setbox\scratchbox\hbox{\endash\space}%
   \leaders\copy\scratchbox\hskip\wd\scratchbox}

\def\aside_left
  {\ifhmode
 \removeunwantedspaces
   \else
 \dontleavehmode
   \fi
   \space\aside_dash}

\def\aside_right
  {\space\aside_dash}

%\define[1]\aside
%  {\aside_left#1\aside_right}

\unexpanded\def\aside
  {\aside_left
   \bgroup
   \aftergroup\aside_right
   \let\next=}

\protect

\setupbodyfont[pagella]

\starttext

\speech{first speech} \speech{second speech}

\speech{first speech} no speech \speech{second speech}

\speech{first speech\aside{aside}} \speech{second speech}

\speech{speech \aside{aside}} no speech

\stoptext

Wolfgang

___
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] typing+framedtext: different behaviour between TL2017 and 2019

[Otared Kavian]

Hi Wolfgang,Indeed the sample sent by Tomas works fine with recent lmtx and mkiv, but with the mkiv version in TeXLive2019 one gets the result attached.This means that Tomas has to update to a newer version of ConTeXt…Best regards: OK

typing-and-framedtext.pdf
Description: Adobe PDF document
On 17 Jan 2020, at 19:40, Wolfgang Schuster  wrote:Tomas Hala schrieb am 17.01.2020 um 15:18:Hi all,if I compile the following (minimised) code with ConTeXt from TL2017,I receive expected result -- one framed gray box with correct width.\starttext\showframe\defineframedtext[MPT][background="" class="">\setuptyping[MP][before={\startMPT},after={\stopMPT},]\startMP bla \stopMP\stoptextNow I tried it with ConTeXt from TL2019 (TL2018 produces the same result as TL2019)and I have got _two_ boxes -- the outer one is correct and frames the typing environmentas in the past whereas the new box frames the text inside the typing.Your example works fine with the current beta and since you don't show the differences between the different installations there is nothing which can be done.Wolfgang___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-contextwebpage  : http://www.pragma-ade.nl / http://context.aanhet.netarchive  : 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] Epub export css buglets

[Rik Kabel]

On 1/10/2020 10:59, Rik Kabel wrote:

Here ya go, about as minimal as I can imagine:

\setupbackend [export=yes]
\setupexport  []
\starttext
!
\stoptext

and in the resulting export styles directory, I get:

g:\yoiks-export\styles>grep "namespace\|weight.*italic\|text-width" *.css
yoiks-defaults.css:@namespace context 
url('http://www.pragma-ade.com/context/export') ;
yoiks-defaults.css: font-weight : italic ;
yoiks-images.css:@namespace context url('%namespace%') ;
yoiks-styles.css:@namespace context url('%namespace%') ;
yoiks-styles.css:text-width : justify !important ;
yoiks-templates.css:@namespace context url('%namespace%') ;

So:

  * three unexpanded %namespace%s,
  * one invalid property (text-width),
  * and one incorrect property (font-weight should be font-style).

The *namespace* and *text-width* issues are now fixed, but the 
*font-weight : italic* fault in default.css remains.


I also note that the W3C CSS validator reports for styles.css:

   11     document, div.document     inherited is not a hyphens value :
   inherited

That validator (and others) also report a number of issues for the 
@counter-style rule, which seems to have changed significantly since 
this CSS was developed. Validators report a number of smaller issues as 
well.


I understand that export output is a low-priority feature.

--
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] typing+framedtext: different behaviour between TL2017 and 2019

[Wolfgang Schuster]

Tomas Hala schrieb am 17.01.2020 um 15:18:

Hi all,

if I compile the following (minimised) code with ConTeXt from TL2017,
I receive expected result -- one framed gray box with correct width.

\starttext\showframe
\defineframedtext[MPT][background=color,backgroundcolor=gray,width=\makeupwidth,frame=on,offset=1cc,]
\setuptyping[MP][before={\startMPT},after={\stopMPT},]
\startMP bla \stopMP
\stoptext

Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as 
TL2019)
and I have got _two_ boxes -- the outer one is correct and frames the typing 
environment
as in the past whereas the new box frames the text inside the typing.


Your example works fine with the current beta and since you don't show 
the differences between the different installations there is nothing 
which can be done.


Wolfgang

___
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] Hyphenation LuaTeX

[Arthur Reutenauer]

On Fri, Jan 17, 2020 at 03:44:58PM +0100, Henning Hraban Ramm wrote:
> Thank you for the clarification!

  You’re welcome :-)

> That means, I can mix e.g. {de,agr,ru} but not {de,en}, right?

  Exactly.  In the latter case, even with both languages marked up, the
mix of two completely different pattern sets is likely to be a disaster
(actually, even the full set of US English patterns contains some later
additions and isn’t completely consistent with itself ...)

> But apparently the combined patterns didn’t work for the OP.

  That’s of course a problem, but no insight into that, sorry Manuel.

Best,

Arthur
___
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] Hyphenation LuaTeX

[Henning Hraban Ramm]

> Am 2020-01-17 um 15:36 schrieb Arthur Reutenauer 
> :
> 
> On Fri, Jan 17, 2020 at 01:51:42PM +0100, Henning Hraban Ramm wrote:
>> Just \mainlanguage[es] and \language[agr] (= \agr) where you need it should 
>> be enough.
> 
>  As Thomas said, that shouldn’t be necessary.
> 
>> You can’t expect ConTeXt to auto-detect your language, even if that maybe 
>> would work for Greek.
>> (My texts are usually in German, thus I have \mainlanguage[de] and use \en 
>> or \fr to markup foreign quotes.
>> 
>> Correct me if I miss something.
> 
>  Since the two patterns sets Manuel wants to load use two different
> writing systems, you can mix them without risking bad interactions.  It
> effectively means using a pattern set that is the union of the Spanish
> and Ancient Greek patterns, the former are used when hyphenating Spanish
> words without affecting the Greek text, and vice-versa.  No language
> detection (or markup) is necessary.

Thank you for the clarification!

That means, I can mix e.g. {de,agr,ru} but not {de,en}, right?


But apparently the combined patterns didn’t work for the OP.
Of course, no MWE to check…


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Hyphenation LuaTeX

[Arthur Reutenauer]

On Fri, Jan 17, 2020 at 01:51:42PM +0100, Henning Hraban Ramm wrote:
> Just \mainlanguage[es] and \language[agr] (= \agr) where you need it should 
> be enough.

  As Thomas said, that shouldn’t be necessary.

> You can’t expect ConTeXt to auto-detect your language, even if that maybe 
> would work for Greek.
> (My texts are usually in German, thus I have \mainlanguage[de] and use \en or 
> \fr to markup foreign quotes.
> 
> Correct me if I miss something.

  Since the two patterns sets Manuel wants to load use two different
writing systems, you can mix them without risking bad interactions.  It
effectively means using a pattern set that is the union of the Spanish
and Ancient Greek patterns, the former are used when hyphenating Spanish
words without affecting the Greek text, and vice-versa.  No language
detection (or markup) is necessary.

Best,

Arthur
___
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] typing+framedtext: different behaviour between TL2017 and 2019

[Tomas Hala]

Hi all,

if I compile the following (minimised) code with ConTeXt from TL2017,
I receive expected result -- one framed gray box with correct width.

\starttext\showframe
\defineframedtext[MPT][background=color,backgroundcolor=gray,width=\makeupwidth,frame=on,offset=1cc,]
\setuptyping[MP][before={\startMPT},after={\stopMPT},]
\startMP bla \stopMP
\stoptext

Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as 
TL2019)
and I have got _two_ boxes -- the outer one is correct and frames the typing 
environment
as in the past whereas the new box frames the text inside the typing.

Unfortunately, both boxes seems to be controlled by the \defineframedtext[MPT]
which caused that the inner box runs outside the typesetting area, i.e. the
left offset value is applied twice.

I found out that it is related with the given name MP.
Therefore, I renamed it to another name (it was ok) but after adding
"option=mp" I came across the same problem.

Is there any way how to define behaviour of both boxes in the existing \startMP
environment apart? Or is it not possible?

Best wishes,

Tomáš
___
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] Hyphenation LuaTeX

[Thomas A. Schmitz]

On 17.01.20 12:55, Henning Hraban Ramm wrote:

I suspect "patterns" understands only one file, as far as I understood the 
source, but don’t trust me on this.

When you mark your Greek passages with {\agr ἡ Ἑλληνικὴ γλῶσσα} (or 
\language[agr] instead of \agr), you should get the right pattern without that 
setup.


No, since the patterns for Spanish and Greek are utf8, they can 
co-exist, there's no need to mark the Greek passages.




The module simplefonts is obsolete since 2013.


Yes, that's right.

I get both Spanish and Greek hyphenation in a test file:

\mainlanguage[es]
\setuplanguage[es][patterns={es,agr}]
\setupbodyfont[gentium,11pt]

\starttext
\hyphenatedword{ἄνθρωπος selección}
\stoptext

If this fails for OP, he will have to produce a real example, taking out 
irrelevant parts and telling us which version he uses. In the original 
example, there was only "..." which of course doesn't hyphenate.


Thomas
___
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] Hyphenation LuaTeX

[Henning Hraban Ramm]

> Am 2020-01-17 um 13:04 schrieb MANUEL GONZALEZ SUAREZ 
> :
> 
> Thanks very much, but if the module simplefonts is obsolete, What should I 
> indicate in the preamble to write with both languages?

Your font setup should be good without trying to load that module (that doesn’t 
do anything anymore anyway).

Just \mainlanguage[es] and \language[agr] (= \agr) where you need it should be 
enough.
You can’t expect ConTeXt to auto-detect your language, even if that maybe would 
work for Greek.
(My texts are usually in German, thus I have \mainlanguage[de] and use \en or 
\fr to markup foreign quotes.

Correct me if I miss something.


> When you mark your Greek passages with {\agr ἡ Ἑλληνικὴ γλῶσσα} (or 
> \language[agr] instead of \agr), you should get the right pattern without 
> that setup.
> 
> The module simplefonts is obsolete since 2013.
> 
> Greetlings, Hraban
> ---
> https://www.fiee.net
> http://wiki.contextgarden.net
> https://www.dreiviertelhaus.de
> GPG Key ID 1C9B22FD


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Hyphenation LuaTeX

[Henning Hraban Ramm]

> Am 2020-01-17 um 12:05 schrieb MANUEL GONZALEZ SUAREZ 
> :
> 
> Hi:
> When I compile a document with the following preamble:
> 
> \mainlanguage[es]
> %\setuphyphenation[method=traditional]
> \usemodule[simplefonts]
> \setuplanguage[es][patterns={es,agr}]
> \definefallbackfamily [mainface] [serif] [Old Standard] 
> [range={greekandcoptic, greekextended}, force=yes, rscale=auto]
> \definefontfamily [mainface] [serif] [TeX Gyre Schola]
> \setupbodyfont[mainface,11pt]

I suspect "patterns" understands only one file, as far as I understood the 
source, but don’t trust me on this.

When you mark your Greek passages with {\agr ἡ Ἑλληνικὴ γλῶσσα} (or 
\language[agr] instead of \agr), you should get the right pattern without that 
setup.

The module simplefonts is obsolete since 2013.

Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Hyphenation LuaTeX

[MANUEL GONZALEZ SUAREZ]

Hi:
When I compile a document with the following preamble:


\mainlanguage[es]

%\setuphyphenation[method=traditional]

\usemodule[simplefonts]

\setuplanguage[es][patterns={es,agr}]

\definefallbackfamily [mainface] [serif] [Old Standard] [range={greekandcoptic, 
greekextended}, force=yes, rscale=auto]

\definefontfamily [mainface] [serif] [TeX Gyre Schola]

\setupbodyfont[mainface,11pt]



\starttext

...

\stoptext

with Context LuaTeX, hyphenation patterns work for Greek, but not for Spanish. 
I do the compilation with Mac. Any ideas to solve it?

Thanks
Manuel González.
___
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] characterspacing not always working in LMTX

[Henning Hraban Ramm]

> Am 2020-01-17 um 09:41 schrieb Thomas Savary :
> 
> Hraban :
> > Since the current CG Journal is still "in progress", another article is
> > welcome!
>  
> Thank you for this offer. As I don’t like half-measures, I really want to do 
> it well, so I’m going to need a lot of time to collect historical as well as 
> recent examples, quotations, etc. and to write this article. Unfortunately, I 
> am pretty busy right now and probably won’t have time to start before March.

Then maybe prepare a talk for the next context meeting?

Looking at my/our progress with the journal and my calendar I guess it would be 
still in time if you deliver somewhen end of March.
(Mid March is Leipzig book fair, we’ll have a booth and I need to finish two 
books and our catalogue before; after the fair I must send out the new 
releases, and then’s DANTE meeting in Lübeck…)


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] characterspacing not always working in LMTX

[Thomas Savary]

Hraban :
> Since the current CG Journal is still "in progress", another article is
> welcome!

Thank you for this offer. As I don’t like half-measures, I really want to do it 
well, so I’m going to need a lot of time to collect historical as well as 
recent examples, quotations, etc. and to write this article. Unfortunately, I 
am pretty busy right now and probably won’t have time to start before March.

Greetings

Thomas Savary
1 le Grand-Plessis
F-85340 L’Île-d’Olonne
Tél. 06 22 82 61 34
https://compo85.fr/

mercredi 15 janvier 2020, à 16:16:21 CET, Henning Hraban Ramm a écrit :
> > Am 2020-01-15 um 16:10 schrieb Thomas Savary :
> > 
> > Exactly. And this is precisely the thin space still required in French
> > publications. The main disagreement among French typographs (about twenty
> > years ago, at least) was about the fixed vs relative width of this thin
> > space : put in TeX’s terms, should it be proportional to the glue or to
> > the font ?
> > 
> > I think I’d better write an article about this, with quotes and visual
> > examples.
> Since the current CG Journal is still "in progress", another article is
> welcome!
> 
> Best, Hraban
> 
> 
> ___ 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
___