From: Hans Hagen <pragma@wxs.nl>
To: severinbarmeier@googlemail.com,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (Xe)ConTeXt and CJK support
Date: Fri, 10 Sep 2010 09:47:33 +0200 [thread overview]
Message-ID: <4C89E295.5050301@wxs.nl> (raw)
In-Reply-To: <4C8898F6.7090809@googlemail.com>
On 9-9-2010 10:21, S Barmeier wrote:
> Dear ConTeXt users,
>
> I am trying to write a document (grammar notes) in English and Japanese
> and so far have used XeTeX (for Unicode support) with tikZ (for
> graphics) quite successfully. However, I wish to convert to (Xe)ConTeXt
> in order to have more control over the page design.
>
> At the moment I am stuck at trying to define English and Japanese fonts.
> In XeTeX I used
>
> \usepackage[BoldFont]{xeCJK}
> \setCJKmainfont{IPAMincho}
> \setCJKsansfont{IPAGothic}
> \setCJKmonofont{KanjiStrokeOrders}
>
> in order to set the three different Japanese fonts I am using.
>
> I haven't found any documentation on how to implement something
> equivalent in ConTeXt and would be most grateful if someone could
> outline how I would best go about converting my XeTeX document to ConTeXt.
>
> Many thanks.
> Kind regards,
> Severin
>
> P.S.: If you think I'm crazy for trying to mix XeTeX, ConTeXt and tikZ,
> please tell me now... =) Also, it feels like ConTeXt MkIV with LuaTeX
> would be the best choice (if the project were just already beyond the
> beta stage), but I don't really know an awful lot about that either. Any
> thoughts on how successfully I might be able to implement the above in
> LuaTeX would also be much appreciated.
There will be no further efforts to support fonts, languages or scripts
in context mkii/xetex (apart from bug fixes) so using mkiv is a better
option
I use mkiv myself and it's quite useable. Actually, I've not been using
mkii for years apart from format generation and an occasional test run.
Mkiv will be beta for a while simply because successively code is been
rewritten / upgraded and because it goes in sync with luatex development.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-09-10 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 8:21 S Barmeier
2010-09-10 7:47 ` Hans Hagen [this message]
2010-09-10 19:03 ` Mojca Miklavec
2010-09-10 19:10 ` Hans Hagen
2010-09-10 19:22 ` Mojca Miklavec
2010-09-12 7:10 ` Wolfgang Schuster
2010-09-14 0:28 ` S Barmeier
2010-09-14 5:54 ` Wolfgang Schuster
2010-09-14 9:10 ` S Barmeier
2010-09-14 10:09 ` Wolfgang Schuster
2010-09-14 10:31 ` S Barmeier
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=4C89E295.5050301@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=severinbarmeier@googlemail.com \
/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).