From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setuptex changes in minimals
Date: Sun, 10 May 2009 17:35:16 +0200 [thread overview]
Message-ID: <4A06F434.3000301@wxs.nl> (raw)
In-Reply-To: <68bfdc900905090857l39067d1co939465e39fe4eb2d@mail.gmail.com>
Yue Wang wrote:
> - It is ugly to produce a paragraph whose last line only consists one
> Chinese character. In order to avoid that, tex82 programmers should
> write very complicated macros. So many developers here tend to ignore
> this problem. However, in LuaTeX, this is quite easy. It is simple to
> scan the position before the punctuation and \par in lua, and insert a
> line break penalty there.
ok, but it might even be more clever, like minimum number of glyphs on
last line or so (and words in case of other scripts)
> - Punctuation compression. In the past this is not easy to do (a lot
> of macros should be defined), and because each Chinese fonts are so
> distinctly designed, their punctuations' positions in the character
> box are different. So different parameters should be applied when
> different fonts are involved in typesetting. However, LuaTeX make it
> possible to calculate character bounding box information, so
> punctuation compression is as easy as re-setting the punctuation
> width.
i had code for that but removes it as fonts are pretty inconsistent; i
will look into that again when we have (1) a couple of reference fonts
without bugs in the tex distribution and (2) wiki pages with info about
the quality of fonts (can later become a database); otherwise we end up
in messy support situations
> But we (me, Li Yanrui, Chen Zhichu) as the board members of the
> Chinese TeX Society, will try our best to organized the typesetting
> discussion on local forums, taking different opinions into
> consideration, and later provide a complete specification as long as
> we can.
that would be very helpful
> pace, we will have a very prospective solution near luatex 1.0:)
sure
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-05-10 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 11:19 setuptex changes in minimals (was: bugs in beta) Mojca Miklavec
2009-05-08 12:16 ` Yanrui Li
2009-05-08 17:43 ` Mojca Miklavec
2009-05-08 18:17 ` Yanrui Li
2009-05-08 18:20 ` Yanrui Li
2009-05-09 1:57 ` Yue Wang
2009-05-09 8:02 ` setuptex changes in minimals Hans Hagen
2009-05-09 11:44 ` Yanrui Li
2009-05-09 15:57 ` Yue Wang
2009-05-10 15:35 ` Hans Hagen [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=4A06F434.3000301@wxs.nl \
--to=pragma@wxs.nl \
--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).