From: Yanrui Li <liyanrui.m2@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with the 'scrp-cjk.lua'
Date: Sun, 29 Nov 2009 21:02:44 +0800 [thread overview]
Message-ID: <c3f901470911290502u5d9b606fh1e41965ce03008a0@mail.gmail.com> (raw)
In-Reply-To: <c3f901470911290453n7275fe68o7cb4277a23b85293@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1744 bytes --]
2009/11/29 Yanrui Li <liyanrui.m2@gmail.com>
>
>
> 2009/11/29 Hans Hagen <pragma@wxs.nl>
>
> Yanrui Li wrote:
>>
>>> Hi Hans,
>>>
>>> In the *hanzi* part of scrp-cjk.lua, there is:
>>>
>>> local injectors = { -- [previous] [current]
>>> ... ... ...
>>> full_width_close = {
>>> ... ... ...
>>> chinese = nobreak_shrink_break_stretch,
>>> ... ... ...
>>>
>>> This causes that lines can not be broken after some Chinese punctuations
>>> in 'full_width_close' category. I think it should be:
>>>
>>> local injectors = { -- [previous] [current]
>>> ... ... ...
>>> full_width_close = {
>>> ... ... ...
>>> chinese = stretch_break,
>>> ... ... ...
>>>
>>>
>>> The same problem also arises here:
>>>
>>> local injectors = { -- [previous] [current]
>>> ... ... ...
>>> half_width_close = {
>>> ... ... ...
>>> chinese = nobreak_shrink_break_stretch,
>>> ... ... ...
>>>
>>> It seems like it should be:
>>>
>>> local injectors = { -- [previous] [current]
>>> ... ... ...
>>> full_width_close = {
>>> ... ... ...
>>> chinese = stretch_break,
>>> ... ... ...
>>>
>>
>> i have no problem patching that but can you also make a test file then so
>> that we have some benchmark / reference?
>>
>>
> Please see the attachment file which includes a test.tex and two pdf
> files. One is 'patched-test.pdf' shows some line-break after some Chinese
> punctations. The other is 'no-patched-test.pdf' which seems like there is no
> line-break after any punctation forever.
>
>
Oh, sorry for my attachment file is too big. I deleted the
'no-patched-test.pdf'. Please see this attachment.
--
Best regards,
Li Yanrui
[-- Attachment #1.2: Type: text/html, Size: 2715 bytes --]
[-- Attachment #2: test.tar.gz --]
[-- Type: application/x-gzip, Size: 41352 bytes --]
[-- Attachment #3: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-11-29 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 8:14 Yanrui Li
2009-11-29 12:20 ` Hans Hagen
[not found] ` <c3f901470911290453n7275fe68o7cb4277a23b85293@mail.gmail.com>
2009-11-29 13:02 ` Yanrui Li [this message]
2009-11-29 14:49 ` Hans Hagen
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=c3f901470911290502u5d9b606fh1e41965ce03008a0@mail.gmail.com \
--to=liyanrui.m2@gmail.com \
--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).