From: Taco Hoekwater <taco@elvenkind.com>
To: hajtmar@gyza.cz, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: <CRLF> is interpreted as a Greek letter in LuaLaTeX
Date: Tue, 08 Jun 2010 08:51:45 +0200 [thread overview]
Message-ID: <4C0DE881.2090108@elvenkind.com> (raw)
In-Reply-To: <4C0DE656.5030203@gyza.cz>
Hi Jaroslav,
Jaroslav Hajtmar wrote:
> Hi,
> When I want to write in LuaLaTeX by "tex.print" command some text string
I do not want to sound unfriendly, but this is a ConTeXt mailing list,
not a LuaLaTeX mailing list. It would be better if you would direct
lualuatex questions to the general luatex list <luatex@tug.org>.
> that is defined in an external lua-file, so <crlf> characters in
> LuaLaTeX appear as the Greek letter "omega". The Greek letter omega has
> in the font CM code 0x0A, which is a line feed. It seems that the end of
> the line is interpreted not as the end of the line, but a letter.
Exactly. lua input files are much more sane than tex files: if you write
a newline, you get a newline. The Omega is a side-effect of the font
you use.
> When I define a text string directly in the source file, everything is OK.
> Please do not know how to solve this problem?
postprocess the string with string.gsub.
Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-06-08 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 6:42 Jaroslav Hajtmar
2010-06-08 6:51 ` Taco Hoekwater [this message]
2010-06-08 7:03 ` Jaroslav Hajtmar
2010-06-08 19:11 ` Khaled Hosny
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=4C0DE881.2090108@elvenkind.com \
--to=taco@elvenkind.com \
--cc=hajtmar@gyza.cz \
--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).