ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: hwitloc@gmail.com
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: distinguish different characters from different languages
Date: Mon, 10 Jun 2013 07:57:50 +0900	[thread overview]
Message-ID: <20130610075750.1220@binki> (raw)
In-Reply-To: Your message of Sun, 9 Jun 2013 14:58:40 +0000 <COL127-W3480A5963DA99C9582242FA99B0@phx.gbl>


This seems to be about inter-word spacing, rather than character sets.

For the phrase:  "据我所知,中国人将typography写作排版"

The intuitive operation for ConTeXt should be to preserve the explict space after the comma, but the word "typography" is not seperated from the rest of the text with spaces.

If you input the text as   "据我所知,中国人将 typography 写作排版"
Then the spaces should be preserved as in English or other languages.
This was not the case once for Japanese, but a (temporary?) fix was put into the ongoing development version, I believe.  The space removal was due to the fact that Chinese and Japanese do not use space between words in normal text.

For now can you use the ~ or some like escape sequence to force a space where you want it?

--------

Tim Li <timli2013@outlook.com> wrote:

> Hi,
> 
> Is there a way in ConTeXt to distinguish (or recognise) different
> characters from different languages, especially distinguishing those
> used in China, Japan and Korea (CJK) from English.
> 
> For example, sentence(1) and its translation (sentence (2)) below are
> mixed English with Chinese characters,
> 
> as far as I know, Chinese write 排版 as typography. (1)
> translation: 据我所知,中国人将typography写作排版。(2)
> 
> If I input this sentence in the ConTeXt source file, how can I
> recognise English characters and Chinese characters respectively so
> that I can insert space (say, 1/4 space) when nesting English words
> into Chinese (the result of sentence (2) in PDF file will look like
> this: 据我所知,中国人将 typography 写作排版。)
> 
> Are there some materials or topics about this?
> 
> Tim
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2013-06-09 22:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 14:58 Tim Li
2013-06-09 17:31 ` Hans Hagen
2013-06-09 22:57 ` hwitloc [this message]
2013-06-10  7:34   ` Tim Li
2013-06-10 10:00     ` 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=20130610075750.1220@binki \
    --to=hwitloc@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).