ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: distinguish different characters from different languages
Date: Mon, 10 Jun 2013 12:00:55 +0200	[thread overview]
Message-ID: <51B5A3D7.10008@wxs.nl> (raw)
In-Reply-To: <COL127-W33A9CCBAE07BFC44AC2EE5A9840@phx.gbl>

On 6/10/2013 9:34 AM, Tim Li wrote:
> @hwitloc
> I don't think this is only an interword question, especially when
> you are typesetting a book like `The Joy of Chinese` which will involve
> many paragraphs containing many English words nested in Chinese sentences.
> So if users pay more attention to insert spaces when switcting different
> languages, they will pay less attention to the contents they are
> typesetting. In this case, we need ConTeXt to do this task (insert
> spaces when switching to English from Chinese) automatically.
>
> @Hans
> Which file or Which files should I read in the subpath of `scripts`? All?
>
>
>
>
>  > Date: Mon, 10 Jun 2013 07:57:50 +0900
>  > From: hwitloc@gmail.com
>  > To: ntg-context@ntg.nl
>  > Subject: Re: [NTG-context] distinguish different characters from
> different languages
>  >
>  >
>  > 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?

it helps to know what can be downloaded from the website

http://www.pragma-ade.com/download-1.htm

the test suite has examples

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2013-06-10 10:00 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
2013-06-10  7:34   ` Tim Li
2013-06-10 10:00     ` 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=51B5A3D7.10008@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).