From: Wim Neimeijer <wneimeijer@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typefile with Chinese, Korean or Japanase text
Date: Wed, 6 Dec 2017 00:32:51 +0100 [thread overview]
Message-ID: <CACmST42Dem_3CHno0ZcafLXSDWPRMbK3H9qfNKXn6z5Wt2F10A@mail.gmail.com> (raw)
In-Reply-To: <e4c0b534-8367-e592-ed1b-ab459df34e81@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1178 bytes --]
The thing here is, I am not an ConText expert just an user. I am working on
a manual (200+ pages) where including code snippets
is just a small part of the document and not something isolated. Not sure
what to do next as the wiki explains a lot
but not this.
On Tue, Dec 5, 2017 at 11:53 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 12/5/2017 11:10 PM, Wim Neimeijer wrote:
>
>> I wish it is that simple, but alas, I need to
>> to inform \typefile of the font as well,
>> possibly via setuptyping ?
>>
> if you mix scripts you need to either use font that has the glyphs or you
> have to create a bodyfint with a combination of fonts ... i'm pretty sure
> that the wiki explains this somewhere (fallbacks and such)
>
> Hans
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Nethe
> <https://maps.google.com/?q=Ridderstraat+27+%7C+8061+GH+Hasselt+%7C+The+Nethe&entry=gmail&source=g>
> rlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
[-- Attachment #1.2: Type: text/html, Size: 1919 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-12-05 23:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 20:32 Wim Neimeijer
2017-12-05 20:43 ` luigi scarso
2017-12-05 22:10 ` Wim Neimeijer
2017-12-05 22:53 ` Hans Hagen
2017-12-05 23:32 ` Wim Neimeijer [this message]
2017-12-06 8:53 ` Hans Hagen
2017-12-06 9:14 ` luigi scarso
2017-12-06 9:02 ` Henning Hraban Ramm
2017-12-06 11:00 ` Wolfgang Schuster
2017-12-06 17:16 ` Wim Neimeijer
2017-12-06 18:13 ` Aditya Mahajan
2017-12-06 18:24 ` Wim Neimeijer
2017-12-06 19:07 ` Pablo Rodriguez
2017-12-06 19:20 ` Rik Kabel
2017-12-06 20:25 ` Hans Hagen
2017-12-06 21:01 ` Wim Neimeijer
2017-12-06 21:30 ` Wim Neimeijer
2017-12-06 22:32 ` Wolfgang Schuster
2017-12-06 22:54 ` Alan Braslau
2017-12-06 18:17 ` Pablo Rodriguez
[not found] <mailman.1646.1512595887.1988.ntg-context@ntg.nl>
2017-12-06 23:38 ` Jeong Dal
[not found] <mailman.1637.1512580660.1988.ntg-context@ntg.nl>
2018-02-19 21:15 ` Jeong Dal
2018-02-19 21:43 ` Pablo Rodriguez
2018-02-20 0:12 ` Jeong Dal
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=CACmST42Dem_3CHno0ZcafLXSDWPRMbK3H9qfNKXn6z5Wt2F10A@mail.gmail.com \
--to=wneimeijer@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).