ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ulrike Fischer <news2@nililand.de>
To: ntg-context@ntg.nl
Subject: Partly OT: some luatex questions
Date: Wed, 13 Aug 2008 16:50:12 +0200	[thread overview]
Message-ID: <xi4vhyzmh6ah.dlg@nililand.de> (raw)

I'm currently trying if I can use luatex on my miktex installation and
together with LaTeX. 

I have downloaded the executable (Version snapshot-0.29.0-2008071816)
from the context-minimals and made a simple texmf.cnf and build some
formats (the formats don't contain something luatex specific, they
simply load latex.ltx). Things works quite fine, my (pdf)lualatex is
running and is finding all the ressources (fonts, styles etc) from my
miktex-trees. 

But I have some problems I don't know how to solve.

1. In the following document there is no space between the a and the y:

\documentclass{article}
\begin{document}
\noindent a\\y 

\bigskip  

a\par y
\end{document}

It looks as if the lines have only the depth from their content. 

2. I found here some code to use truetype and opentype fonts:
http://luatex.bluwiki.com/go/Use_a_TrueType_font

But while testing the code I run in two two problems:
a) I tested it with a latin modern font and arial and with both fonts
all lines of a text are printed one above the other. It looks as if none
of the lines have a height and a depth. 

b) I also tried MnSymbol5.otf and there I get an error "invalid
character". (I tried to get an "A"). With xetex the font works fine. 

I would be quite grateful if someone could tell me how to solve this
problems. 

-- 
Ulrike Fischer 

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2008-08-13 14:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 14:50 Ulrike Fischer [this message]
2008-08-13 21:07 ` Arthur Reutenauer
2008-08-14  7:48   ` Ulrike Fischer
2008-08-14  7:58     ` Wolfgang Schuster
2008-08-14  8:11       ` Hans Hagen
2008-08-14 12:25         ` Ulrike Fischer
2008-08-14 14:27           ` Hans Hagen
2008-08-14  9:07       ` Ulrike Fischer
2008-08-14  9:44         ` Wolfgang Schuster
2008-08-14 11:53           ` Ulrike Fischer
2008-08-14 13:49             ` Arthur Reutenauer
2008-08-14 14:28               ` Ulrike Fischer
2008-08-14 20:08                 ` Hans Hagen
2008-08-14 21:24                   ` Intraword spacing proof of concept Charles P. Schaum
2008-08-15  7:49                     ` Hans Hagen
2008-08-15 15:50                       ` Charles P. Schaum
2008-08-15 17:40                         ` AUCTeX issues not necessarily ConTeXt-related Charles P. Schaum
2008-08-15 20:53                           ` Peter Münster

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=xi4vhyzmh6ah.dlg@nililand.de \
    --to=news2@nililand.de \
    --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).