Sounds like you've got it working, but just to provide an alternative
that should* work, according to the sources:
\setuplanguage[cz]
[compoundhyphen=-,%Or, to keep the \setuphyphenmark
rightcompoundhyphen=-,% configuration mentioned in Taco's link:
leftcompoundhyphen
] [protrusion=quality]
\setupalign[hanging]
\setuptolerance[horizontal,strict]
\setuphyphenmark [sign=small]
\showframe [text] [text]
\starttext
\dorecurse{21}{Multisyllabic||words||separated||by||hyphens. }
\stoptext
Is this expected behavior? Can it be changed
):
\setuppapersize[monarch]
\definefontfeature [default] [protrusion=quality]
\setupalign[hanging]
\setuptolerance[horizontal,strict]
\setuphyphenmark [sign=small]
\showframe [text] [text]
\starttext
\dorecurse{21}{Multisyllabic||words||separated||by||hyphens
a *normal* hyphen is
\setuphyphenmark[sign=normal]
Yes, this is the correct method. It should be enabled by default. If
somebody wants a larger hyphen (for some mysterious reasen), he/she can set it
up with
\setuphyphenmark[sign=wide]
If the output is not correct it's a bug.
Yes
for this purpose. And two
hyphens (or an en-dash) is too large. I've never seen the advice in a
typography book to kern two hyphens. I don't know why this is
implemented like this.
2. The correct method to get a *normal* hyphen is
\setuphyphenmark[sign=normal]
Yes, this is the correct
test||test
\setuphyphenmark[sign=normal]
test||test
test|-|test
\stoptext
Sure, my fault. This works. There _was_ a bug with the hyphen appearing
on the start of the next line. This is fixed. Thank you. I thought you
would also fix the »wrong« hyphenation sign, so I didn't check, just
(or hyphen from a different font) or maybe to
»correct« the font instead of altering settings of the typesetting
system.
Concerning the hyphen sign, '\setuphyphenmark[sign=normal]' works as
expected on my system (= normal hyphen sign).
But it was (is?) not usable because, in case of a line break
* hyphen is
\setuphyphenmark[sign=normal]
If the output is not correct it's a bug.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl
) is too large. I've never seen the advice in a
typography book to kern two hyphens. I don't know why this is
implemented like this.
2. The correct method to get a *normal* hyphen is
\setuphyphenmark[sign=normal]
Yes, this is the correct method. It should be enabled by default. If
somebody wants
\compoundhyphen{-} instead of
\setuphyphenmark. It seems to work (mkii).
Thomas
Yes, it works also in MKIV. This is a better workaround than mine. But
Hans said he'll fix it next beta. So I hope I'll not need it.
Nevertheless thanks for this snippet. It produces exactly the behaviour
I expect.
Marco
: hyphenated, but an en-dash is used,
% not a hyphen, so [sign=wide] seems to be the default
composed|-|word\blank % wrong: hyphenated, but the hyphen is at the
start of % the next line
\setuphyphenmark [sign=normal]% For hyphenation a hyphen
,
% not a hyphen, so [sign=wide] seems to be the default
composed|-|word\blank % wrong: hyphenated, but the hyphen is at the start of
% the next line
\setuphyphenmark [sign=normal] % For hyphenation a hyphen is used,
% not an endash
composed
Using || instead of |-| works like expected, so using it in combination
with \setuphyphenmark[sign=normal] could be considered a workaround.
Sadly, that produces the same bad result. :-(
Here's a minimal example:
%\setuphyphenmark[sign=normal]
\starttext
\hsize 1em
longer|-|word
{-}}{}{\hbox{-}}\prewordbreak}
However, \setuphyphenmark[sign=normal] still does not work correctly.
Regards,
olli
--
Oliver Heins he...@sopos.orghttp://oliverheins.net/
http://blog.overheins.net/ F27A BA8C 1CFB B905 65A8
http://scriptorium-adp.de/ 2544 0F07 B675 9A00 D827
1024D
on the page.
Thanks in advance,
Tom
(Greetings from Lake Léman)
Here is a some kind of a minimal (not very proper nor cleaned, but it
compiles on context-live and it shows what i'm talking about):
% coding: utf-8
\enableregime [utf]
\useencoding[fde]
\mainlanguage[de]
\setuphyphenmark[sign
Am 23.11.2008 um 07:10 schrieb Yue Wang:
Hi, Hans:
\setuphyphenmark[sign=-] is not working again, it still gives en-dash
between ||.
would you please have a check?
http://wiki.contextgarden.net/Composed_words
Wolfgang
Thank you, Wolfgang. but why not make it fully compatible with
previous versions?
On Sun, Nov 23, 2008 at 8:26 AM, Wolfgang Schuster
[EMAIL PROTECTED] wrote:
Am 23.11.2008 um 07:10 schrieb Yue Wang:
Hi, Hans:
\setuphyphenmark[sign=-] is not working again, it still gives en-dash
between
Hi, Hans:
\setuphyphenmark[sign=-] is not working again, it still gives en-dash
between ||.
would you please have a check?
Yue Wang
___
If your question is of interest to others as well, please add an entry
).
In french, the hyphenmark is « - », not « – » (endash).
So I tried \setuphyphenmark [sign = -] but no effect, I still get a « – ».
This syntax : « composed|-|word » works.
\definetextmodediscretionary {}
{\hyphenliketextmodediscretionary\defaultdiscretionaryhyphen\defaultdiscretionaryhyphen
after
the dash, maybe it's only a french rule).
In french, the hyphenmark is « - », not « – » (endash).
So I tried \setuphyphenmark [sign = -] but no effect, I still get a « – ».
This syntax : « composed|-|word » works.
\definetextmodediscretionary {}
{\hyphenliketextmodediscretionary
in the manual.
(Strange that context can't know that he can cut composed words after
the dash, maybe it's only a french rule).
In french, the hyphenmark is « - », not « – » (endash).
So I tried \setuphyphenmark [sign = -] but no effect, I still get a « – ».
This syntax : « composed|-|word » works
is « - », not « – » (endash).
So I tried \setuphyphenmark [sign = -] but no effect, I still get a « – ».
This syntax : « composed|-|word » works.
\definetextmodediscretionary {}
{\hyphenliketextmodediscretionary\defaultdiscretionaryhyphen\defaultdiscretionaryhyphen\empty
\setuphyphenmark [sign = -] but no effect, I still get a « – ».
This syntax : « composed|-|word » works.
Cheers,
Olivier.
--
[Message tapé sur un clavier Bépo : http://www.clavier-dvorak.org ]
http://nemolivier.blogspot.com
|pagenumber]
\setupheadnumber[section][number|+number|-number]
\setupheads[options]
\setupheadtext[language code][name=text]
\setuphyphenmark[sign=-|--|---|( )|=|/]
\setupindentations[names][options]
\setupindenting[none|small|medium|big|next|first|normal|odd|even|dimension]
\setupinmargin[left|right|number
|| configurable for pre-break,
post-break, and no-break character? I think it might be generic enough
for most languages.
Say, we would have
\setuphyphenmark[.. = ..]
sign ... (for backwards compatibility, would set up all the following)
presign ...
postsign ...
nosign ...
D.A.
--
I am not a researcher
[this is going to bounce, because I'm posting from my travel account.
forward only if you feel it necessary]
Hans Hagen said this at Sat, 14 Jun 2003 10:57:13 +0200:
\setuphyphenmark[sign=-]
(This relates to an issue I mentioned earlier: anyone notice how these
compound word marks *don't
Ed L Cashin said this at Fri, 13 Jun 2003 17:12:13 -0400:
I always use explicit hyphen like this:
Don't second|-|guess me.
If it really is always, you can save a little effort with:
\setuphyphenmark[sign=-]
(This relates to an issue I mentioned earlier: anyone notice how these
compound word
27 matches
Mail list logo
