From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: "黄复雄 via ntg-context" <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Can't no break between a close punctuation and a open punctuation
Date: Tue, 2 Aug 2022 10:36:53 +0200 [thread overview]
Message-ID: <2fd0db42-28aa-4036-545c-85376c3132e8@freedom.nl> (raw)
In-Reply-To: <CAHN0TNhrnQP7kFR5FU1MSuR7rO5GJWueiaJo-Q18oAmuxeRW+g@mail.gmail.com>
On 8/2/2022 9:06 AM, 黄复雄 via ntg-context wrote:
> I sent this email four days ago and it may not have been delivered?
> ---------------------------------------------------------------------------------------
>
> Dear Hans,
>
> I found that ConTeXt injected two infinity penalties between a close
> punctuation and a open punctuation, for example between `”` and `“`, or
> between `:` and `“`, so can not break at these places, as showed in
> following doc. But actually, we may sometimes need to do so. Please note
> that there is no space around full width punctuations in Chinese document.
you can try this in scrp-cjk.lua (remake the format)
local chinese_8 = {
jami_initial = nobreak_shrink_break_stretch,
korean = nobreak_autoshrink_break_stretch,
chinese = stretch_break, -- nobreak_autoshrink_break_stretch,
hiragana = stretch_break, -- nobreak_autoshrink_break_stretch,
katakana = stretch_break, -- nobreak_autoshrink_break_stretch,
half_width_open = nobreak_autoshrink_break_stretch_nobreak_autoshrink,
half_width_open = stretch_break,
half_width_close = nobreak_autoshrink_nobreak_stretch,
full_width_open = nobreak_autoshrink_break_stretch_nobreak_shrink,
full_width_close = nobreak_autoshrink_nobreak_stretch,
full_width_punct = nobreak_autoshrink_nobreak_stretch,
hyphen = nobreak_autoshrink_break_stretch,
non_starter = nobreak_autoshrink_break_stretch,
other = nobreak_autoshrink_break_stretch,
}
> doc for example:
>
> ```lmtx
> \setscript[hanzi]
> \usetypescriptfile[mscore]
> \usebodyfont [mschinese,20pt]
can you upgrade the chiese section in that file for windows 10+ as the
old fonts are gone
(i tested with \definedfont[file:mingliu.ttc*chinese @ 10pt])
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-08-02 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 7:06 黄复雄 via ntg-context
2022-08-02 8:36 ` Hans Hagen via ntg-context [this message]
2022-08-02 14:08 ` 黄复雄 via ntg-context
2022-08-02 16:25 ` Hans Hagen via ntg-context
2022-09-03 0:31 ` 黄复雄 via ntg-context
2022-09-03 7:27 ` 黄复雄 via ntg-context
-- strict thread matches above, loose matches on Subject: below --
2022-07-29 13:41 黄复雄 via ntg-context
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=2fd0db42-28aa-4036-545c-85376c3132e8@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).