ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "黄复雄 via ntg-context" <ntg-context@ntg.nl>
To: ntg-context <ntg-context@ntg.nl>
Cc: 黄复雄 <aahuaang@gmail.com>
Subject: Can't no break between a close punctuation and a open punctuation
Date: Tue, 2 Aug 2022 15:06:30 +0800	[thread overview]
Message-ID: <CAHN0TNhrnQP7kFR5FU1MSuR7rO5GJWueiaJo-Q18oAmuxeRW+g@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1735 bytes --]

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.

doc for example:

```lmtx
\setscript[hanzi]
\usetypescriptfile[mscore]
\usebodyfont   [mschinese,20pt]

\showframe

\starttext

\dorecurse{5}{“好?!;”“:,。”} % linebreak sutck

\dorecurse{30}{“我”} % linebreak sutck

\dorecurse{30}{我} % linebreak work

\dorecurse{30}{我。} % linebreak work

\stoptext
```

What I see between any two consecutive punctuations are

<penalty userpenalty>       10000
<glue userskip>             0       0       655500
<penalty userpenalty>       10000
<glue userskip>             0       655500  0

so nowhere to linebreak.

Thanks.

                              Huang Fusyong(黄复雄)

___________________________________________________________________________________
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
__________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 2239 bytes --]

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2022-08-02  7:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  7:06 黄复雄 via ntg-context [this message]
2022-08-02  8:36 ` Hans Hagen via ntg-context
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=CAHN0TNhrnQP7kFR5FU1MSuR7rO5GJWueiaJo-Q18oAmuxeRW+g@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=aahuaang@gmail.com \
    /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).