ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Yue Wang" <yuleopen@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Thank you for the Chinese support, but still one question.
Date: Sat, 25 Oct 2008 00:09:04 +0800	[thread overview]
Message-ID: <68bfdc900810240909m3456ea85hd769d011ea257003@mail.gmail.com> (raw)
In-Reply-To: <c3f901470810240643i32297a5al6629c49dedea89c6@mail.gmail.com>

I think this is a problem concerning the improper variables in the font:(
The em space should not get from the chinese fonts, but directly from
the font size the user invoked (for example, for 30pt font 1em=30pt ).

On Fri, Oct 24, 2008 at 9:43 PM, Yanrui Li <liyanrui.m2@gmail.com> wrote:
> 2008/10/24 Yue Wang <yuleopen@gmail.com>:
>
>> Oh, btw, Yanrui Li also has a problem concerning the space between
>> chinese and english (different space skips when use different chinese
>> fonts). He is also in the list so I think it is better to leave to him
>> to describe the problem.
>
> I have ever report the problem in the mail,
> http://www.ntg.nl/pipermail/ntg-context/2008/035084.html, with an
> example for test. Wolfgang gave me a temporary solution which is
> "\spaceskip .25em plus .25em \relax". But it can only works in
> bodyfont. To make the text appeared in chapter or title display
> normally, I had to do as follows:
>
> \def\WordSkip{\spaceskip .25em plus .25em \relax}
> \setuphead[chapter][textcommand=\WordSkip]
>
> --
> Best wishes,
> Li Yanrui
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-10-24 16:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  3:21 Yanrui Li
2008-10-24 12:02 ` Yue Wang
2008-10-24 13:02   ` Hans Hagen
2008-10-24 13:14     ` Yue Wang
2008-10-24 13:19       ` Yue Wang
2008-10-24 13:43         ` Yanrui Li
2008-10-24 16:09           ` Yue Wang [this message]
     [not found] <68bfdc900808072340v4462a9f8y22060e0e7516fd13@mail.gmail.com>
2008-08-08  9:55 ` Hans Hagen
2008-08-11  5:13   ` Longmin Wang
2008-08-11  9:07     ` Hans Hagen
2008-08-11 10:17     ` Hans Hagen
2008-08-11 13:55       ` Longmin Wang

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=68bfdc900810240909m3456ea85hd769d011ea257003@mail.gmail.com \
    --to=yuleopen@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).