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 22:01:54 +0100 [thread overview]
Message-ID: <CACmST41gOHN4-_X8AKBuzCpuT2mTdONckXDPmN80Fr8mKO9PsQ@mail.gmail.com> (raw)
In-Reply-To: <6b82595b-8266-4e2f-a210-4706a3ee8fe5@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1886 bytes --]
Thanks for all your input and help, but as said before I don't have the
time to upgrade and than to discover existing things don't work
resulting in a complete new thread to debug these existing things and/or
fix with a new beta installation.
But that is perhaps not my biggest concern with all these beta releases,
ConText is great and for the most part easy to use, I am more worried that
my existing ConText environment (setup) becomes broken, and/or resulting in
complete different PDF output.
I have no way of knowing, apart from visually inspecting a lot of pages of
PDF.
I thought including some code examples via \typefile (with a bit of text in
either Cyrillic, Chinese, Japanese or Korean)
could be achieved with a simple local font switch, or setting a regime or
via \setuptyping but not on a global level
with \definefontsynonym, definefontfallback etc.
My fix is to change the examples a bit and continue.
Again thanks for the help
On Wed, Dec 6, 2017 at 9:25 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 12/6/2017 7:24 PM, Wim Neimeijer wrote:
>
>> I disagree, a version from 2016 is not very old. I have a lot of
>> documents using a ConText setup which works with this version
>> of luatex and context.
>>
>> Last week I tried to use the latest beta with my documents and the beta
>> was unable to run my documents.
>> As it seems it is not backward compatible and I have no time at the
>> moment to debug or test.
>>
> hm, normally updates are backwar dcompatible (apart from very beta
> features) ... what fails?
>
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
[-- Attachment #1.2: Type: text/html, Size: 2798 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-06 21:01 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
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 [this message]
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=CACmST41gOHN4-_X8AKBuzCpuT2mTdONckXDPmN80Fr8mKO9PsQ@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).