From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX on Mac OS X
Date: Tue, 02 Oct 2007 15:23:38 +0200 [thread overview]
Message-ID: <4702465A.9090607@wxs.nl> (raw)
In-Reply-To: <386812B2-3AD4-44AF-8133-60066FCA119F@mac.com>
Dalyoung Jeong wrote:
> Dear Hans,
>
> Thank you for the reply.
>
> Here is the codes of luatools.lua from line number 1106 -
>
> %%%%%%%%%%%%%%%
> 1106: if md5 then do
>
> 1107: local function convert(str,fmt)
> 1108: return (string.gsub(md5.sum(str),".",function(chr)
> return string.format(fmt,string.byte(chr)) end))
> 1109: end
>
> if not md5.HEX then function md5.HEX(str) return convert(str,"%
> 02X") end end
> if not md5.hex then function md5.hex(str) return convert(str,"%
> 02x") end end
> if not md5.dec then function md5.dec(str) return convert(stt,"%
> 03i") end end
>
> end end
>
> %%%%%%%%%%%%%
>
> Since most people didn't have the problem in installation. it
> reminded me a problem when I installed the XeTeX a long time ago.
> After installed files of XeTeX, I tried to make a format, but I
> couldn't succeed. I reported the error message to XeTeX mailing list,
> but every one had no problem to install and to make a format. They
> said that it was good in their system.
> Finally Jonathan found that it was related with my OSX(OSX korean
> version) even though I put english at the top priority in the
> preference panel.
> He installed korean in his system to locate the problem and removed
> the problems.
>
> Is this problem related with my OSX?
how do your paths look like? do they contain non ascii chars?
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-10-02 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 12:27 Dalyoung Jeong
2007-10-02 12:52 ` Henning Hraban Ramm
2007-10-02 13:27 ` Hans Hagen
2007-10-02 13:23 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-08 1:44 Dalyoung Jeong
2007-10-06 3:47 Jeong Dalyoung
2007-10-06 6:53 ` Thomas A. Schmitz
2007-10-04 9:12 Dalyoung Jeong
2007-10-04 10:02 ` Mojca Miklavec
2007-10-03 1:13 Jeong Dalyoung
2007-10-03 1:22 ` Arthur Reutenauer
2007-10-03 6:14 ` Taco Hoekwater
2007-10-01 21:31 Otared Kavian
2007-10-02 6:36 ` Dalyoung Jeong
2007-10-02 7:56 ` Hans Hagen
2007-10-02 11:12 ` Wolfgang Schuster
2007-10-02 17:53 ` Thomas A. Schmitz
2007-10-04 6:28 ` Otared Kavian
2007-10-04 6:43 ` Thomas A. Schmitz
2007-10-04 8:24 ` Mojca Miklavec
[not found] ` <859EA456-9317-4AEB-9AE2-52AA0BFF57D6@mac.com>
2007-10-11 19:26 ` Otared Kavian
2007-10-11 19:34 ` Hans Hagen
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=4702465A.9090607@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).