ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tomas Hala <tomas.hala@mendelu.cz>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Left hanging hyphen
Date: Thu, 5 Mar 2020 16:29:41 +0100	[thread overview]
Message-ID: <20200305152941.GA13929@akela.mendelu.cz> (raw)
In-Reply-To: <20200304195642.61dc09b96064a5721b42af2c@gmail.com>

Hi Wolfgang,

# You can use the default language for the reset:
# 
# \startsetups [language:czech]
#   \setbreakpoints [czcompound]
# \stopsetups
# 
# \startsetups [language:other]
#   \resetbreakpoints
# \stopsetups
# 
# \setuplanguage
#   [cz]
#   [setups=language:czech]
# 
# \setuplanguage
#   [default]
#   [setups=language:other]

I used these definitions and it works really better, the hyphen is not
repeated in other languages anymore, thanks for this setting.
Unfortunately, two side-effects appeared after switching language back to uk:

* after the hyphen, no linebreak seems to be allowed,
* hyphenation patterns have been applied on the composed word, while before switching (default) not.

Tested with TL2019 as well as with the newest.

How can these side-effects be suppressed? 

Tomáš


%%%%%%%%%%%%%%%%%%%%%% MWE
\startluacode
fonts.protrusions.classes.tomas_hala = {
    vector = 'tomas_hala',
    factor = 1,
}

fonts.protrusions.vectors.tomas_hala = table.merged (
    fonts.protrusions.vectors.quality,
    {
        [0x002D] = { 0.4, 0.7 }, -- hyphen
    }
)

\stopluacode

\definebreakpoints [czcompound]
\definebreakpoint [czcompound] [-] [nleft=3,nright=3,type=4]

\startsetups [language:czech]
  \setbreakpoints [czcompound]
\stopsetups
\startsetups [language:other]
  \resetbreakpoints
\stopsetups

\setuplanguage[cz][setups=language:czech]
\setuplanguage[default][setups=language:other]
\definefontfeature [default] [default] [protrusion=tomas_hala]
\setupalign [hz,hanging]

\showframe [text] [text]
\starttext
\hsize=1pt

\mainlanguage [uk] {\bf uk}
	modro-zelený
	\hyphenatedpar{Stratford Stratford-upon-Avon}  

\mainlanguage [cz] {\bf cz}
	modro-zelený
	\hyphenatedpar{Stratford Stratford-upon-Avon}

\mainlanguage [uk] {\bf uk} 
	modro-zelený
	\hyphenatedpar{uk Stratford Stratford-upon-Avon}

\stoptext
%%%%%%%%%%%%%%%%%%%% RESULT
uk
modro-
zelený
Strat-
ford
Stratford-
upon-
Avon
cz
modro-
-ze-
lený
Strat-
ford
Strat-
ford-
-upon-
-Avon
uk
modro-zelený
uk
Strat-
ford
Strat-
ford-upon-Avon
%%%%%%%%%%%%%%%%%% END
___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2020-03-05 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 11:22 Tomas Hala
2020-03-02 16:38 ` Wolfgang Schuster
2020-03-04 18:28   ` Tomas Hala
2020-03-04 18:56     ` Wolfgang Schuster
2020-03-05 15:29       ` Tomas Hala [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200305152941.GA13929@akela.mendelu.cz \
    --to=tomas.hala@mendelu.cz \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).