From: S Barmeier <severinbarmeier@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: \setscript[hanzi] and kana (Wolfgang Schuster)
Date: Fri, 24 Jun 2011 03:23:12 +0900 [thread overview]
Message-ID: <4E038490.8050100@googlemail.com> (raw)
In-Reply-To: <mailman.1720.1308843585.4231.ntg-context@ntg.nl>
On 06/24/2011 12:39 AM, ntg-context-request@ntg.nl wrote:
>> > japanese is not yet defined; we need entries in scrp-ini and scrp-cjk for that, character categories and initializations and we need japanese expertise for that
> Japanese is supported (it?s only a few extra chars for the chinese code) and worked till February 2011 and I was no able to narrow it down.
>
> The function scripts.preprocess in scrp-ini.lua has at line 381
>
> if originals then c = originals[c] or c end
>
> which change the real character value to 65533 (REPLACEMENT CHARACTER), when i comment the line there is a line break (see attachment).
>
> Wolfgang
Japanese was working more or less a few months ago. I guess vertical
typesetting is a little more involved, but as far as horizontal
typesetting goes, most of the spacing is coded into the font already
(monospacing). When the Latin alphabet enters, as is becoming more and
more common, especially in technical literature, the monospacing breaks
down, and common practice is to just typeset paragraphs in block form,
adding the necessary spacing.
Typescripts are already working wonderfully in ConTeXt (thank you!), so
for now it should be only a matter of supporting the characters.
I don't know what character categories and initializations are, but if I
can be of any help, please let me know.
Severin
___________________________________________________________________________________
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 parent reply other threads:[~2011-06-23 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1720.1308843585.4231.ntg-context@ntg.nl>
2011-06-23 18:23 ` S Barmeier [this message]
2011-06-23 18:52 ` Wolfgang Schuster
2011-06-23 19:11 ` Hans Hagen
2011-06-23 21:23 ` Wolfgang Schuster
2011-06-23 21:30 ` 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=4E038490.8050100@googlemail.com \
--to=severinbarmeier@googlemail.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).