ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texexec in ConTeXt Standalone does not work
Date: Sat, 29 Oct 2016 00:11:37 +0200	[thread overview]
Message-ID: <11ff69ed-ad97-0d50-4d3f-f11845ea9ee2@wxs.nl> (raw)
In-Reply-To: <428878d9-12da-d224-c924-8a109907c4dd@gmx.es>

On 10/28/2016 9:06 PM, Pablo Rodriguez wrote:
> On 10/28/2016 08:35 PM, Asim ConTeXt wrote:
>> Thank you.
>> I want to use MkII because, as far as I know, MkII uses pdfTeX; which is
>> stable. While MkIV uses LuaTeX; which is yet in development. Further,
>> pdfTeX is better at microtypography.

In what respect better? The mechanism in Luatex is mostly the same as in 
pdftex but has been improved a bit (cleaner pdf code, more efficient 
font usage i.e. no duplicate fonts, etc.) and the mkiv support is 
probably a bit better than mkii too.

>> Am I correct at these two points? I would like to hear from you.
>
> Hi Asim,
>
> I’m only an average user. But I guess LuaTeX is pretty stable (version 1
> was released recently).
>
> I have no complain about LuaTeX microtypography. I mean, I use both font
> expansion and character protrusion, and they work fine for me.
>
> But I’m not a LaTeX user. If you took the data from
> http://mirrors.ctan.org/macros/latex/contrib/microtype/microtype.pdf#page=7,
> please don’t forget that the LuaTeX version included in that table is old.
>
> Maybe you find interesting this thread about microtypography in ConTeXt:
> https://mailman.ntg.nl/pipermail/ntg-context/2016/084990.html.
>
>> I found that my system fonts are located at c:\windows\fonts, so I added
>> this address in front of OSFONTDIR in texmf.cnf file. But it still is
>> not working, although the previous warning message has now gone. ConTeXt
>> now silently stops the processing and does not give any output file.
>
> I’d rather use MkIV. But if you want to stick to MkII, consider the
> following variants:
>
>     OSFONTDIR = $SystemRoot/Fonts
>     OSFONTDIR = c:/Windows/Fonts
>
> I cannot remember, but I think using "\" is problematic with TeX (even
> for path names).
>
> Just in case it might help,
>
>
> Pablo
>


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-10-28 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 21:02 Asim ConTeXt
2016-10-27 22:34 ` Mica Semrick
2016-10-28 18:35   ` Asim ConTeXt
2016-10-28 18:55     ` Jean-Pierre Delange
2016-10-28 19:06     ` Pablo Rodriguez
2016-10-28 22:11       ` Hans Hagen [this message]
2016-10-29  9:18         ` Asim ConTeXt
2016-10-29  9:50           ` Pablo Rodriguez
2016-10-29 19:36             ` Hans Hagen
2016-10-29 23:12               ` Asim ConTeXt
2016-10-27 21:17 Asim ConTeXt

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=11ff69ed-ad97-0d50-4d3f-f11845ea9ee2@wxs.nl \
    --to=pragma@wxs.nl \
    --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).