ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: S Barmeier <severinbarmeier@googlemail.com>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (Xe)ConTeXt and CJK support
Date: Tue, 14 Sep 2010 02:28:04 +0200	[thread overview]
Message-ID: <AANLkTik8CBZVCu4TMDpZQ3MnHeTP6arue6Yi273QX34-@mail.gmail.com> (raw)
In-Reply-To: <38055BE7-739B-4C6C-9D48-A7EE92DC83C9@gmail.com>

Thank you all for your detailed answers. Wolfgang's suggestion does
not produce any errors and seems like the perfect solution except that
I have trouble loading any of my installed CJK fonts. I have tried to
play with \definefontsynonym for ConTeXt to find the font files. I
have
- OpenType fonts IPAMincho and IPAGothic as ipam.ttf and ipag.ttf
- TrueType font KanjiStrokeOrders as KanjiStrokeOrders_v2.014.ttf
- a bunch of *.tfm, *.vf, and *.pfb files for a font family called
Wadalab, of which half of them seem to be only suited for JIS
encoding, whilst the other half is suited for Unicode.

I hope you don't find it too basic a question, but the font system is
not very transparent and I'd be most grateful if someone could outline
how I would write the preamble in order to set up the CJK in a way I
can use them for the \setcjk....font commands and (as an exercise)
redefine the Latin font to Palatino.

I envision something like

\usemodule[simplefonts]
\definefontsynonym[Palatino][uplr8t]
\setupbodyfont[Palatino,11pt]				% See 1.
\definefontsynonym[WadalabMincho][???]	% See 2.
\setcjkmainfont[WadalabMincho]
\setcjksansfont[IPAGothic]				% See 3.
\setcjkmonofont[KanjiStrokeOrders]		% See 4.
\starttext
Hello! 今日は!
\stoptext

1. Calling upon the name like this doesn't change anything.
2. How do I know which *.tfm/*.vf/*.pfb file to call here? I think the
*.pfb files are Type1 for JIS encoding and thus are not of interest,
but there are still about 30 *.tmf files for Unicode to choose from.
3. I have an OpenType font with this font name, but again, calling it
like this does not work. I have tried to
$ export OSFONTDIR="/path/to/font/directory"
and then
$ mtxrun --script fonts --reload
$ context --generate
The files are recognized by mtxrun, but, again, the font names don't
enable simplefonts to load them correctly.
4. This somehow seems to work. This is the font name (at least it's
not the filename) and the font is TrueType. However, trying to load a
different font here, like Sazanami Mincho, does *not* work, although
it, too, should not go unnoticed during compilation. Could this be
because of the space in the font name?

I'm grateful for any sort of answer.

Again, many thanks.
Severin

On 9/12/10, Wolfgang Schuster <schuster.wolfgang@googlemail.com> wrote:
>
> Am 09.09.2010 um 10:21 schrieb S Barmeier:
>
>> 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.
>
> With MkIV you can set different fonts for Japanese with the fontfallback
> mechanism, there is not documentation about it but you can on the net
> a few examples how to use it:
>
> -
> http://liyanrui.is-programmer.com/2009/10/21/not-just-for-chinese.12264.html
> - http://liyanrui.is-programmer.com/posts/5737.html
> -
> http://blogs.gnome.org/happyaron/2009/11/02/font-fallback-in-context-mininals/
>
> The simplefonts modules provides a fontspec inspired interface to use
> the mechanism in a simpler way:
>
> \usemodule[simplefonts]
>
> \setcjkmainfont[IPAMincho]
> \setcjksansfont[IPAGothic]
> \setcjkmonofont[KanjiStrokeOrders]
>
> \starttext
> ...
> \stoptext
>
> Wolfgang
>
>
>
___________________________________________________________________________________
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:[~2010-09-14  0:28 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
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 [this message]
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=AANLkTik8CBZVCu4TMDpZQ3MnHeTP6arue6Yi273QX34-@mail.gmail.com \
    --to=severinbarmeier@googlemail.com \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@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).