From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ruby 1.9.1 and non-ascii char parsing in .tui file
Date: Mon, 10 Aug 2009 20:20:19 +0200 [thread overview]
Message-ID: <4A8064E3.3020208@wxs.nl> (raw)
In-Reply-To: <1781d7210908101111w29711127g8f362ceaf7f472de@mail.gmail.com>
Jose Augusto wrote:
> Hi Hans,
>
> I ran just now ruby 1.8.6 and the force_encoding() patch worked well.
yes, but if we can avoid adapting all those strings ... i'm pretty sure
that if we follow that route we have to patch a lot
also keep in mind that in 1.9 there are several encodings (external and
internal) so setting up a roundtrip using the string properties involves
more patches)
> Just now I upgrade "--context=current". The banner in the texexec.rb is
> banner = ['TeXExec', 'version 6.2.1', '1997-2009', 'PRAGMA ADE/POD']
> and the date of this script (after updating) is 10-04-2009 (its April..)
>
> I'm running mkii. How do I get mkii beta scripts, as texexec.rb you mention?
it depends: if (on linux) "texexec" is a big file then you need to copy
texexec.rb to texexec, else if it's a stub it should just work (in that
case texmfstart will start texexec.rb)
> All my rubys are compiled from the box with mingw in windows
> (2000 or XP, in 3 different machines). Of course the encoding
> thing is different in Linux, Windows (and DOS prompts, for the matter),
> so there is probably different behavior in ruby/context/tex interaction with
on windows there should be a stub (something texexec.cmd == "ruby
texmfstart texexec ...")
Hans
-----------------------------------------------------------------
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:[~2009-08-10 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 19:16 Jose Augusto
2009-08-09 19:57 ` Hans Hagen
2009-08-10 3:15 ` Jose Augusto
2009-08-10 13:10 ` Hans Hagen
2009-08-10 15:21 ` Jose Augusto
2009-08-10 16:27 ` Hans Hagen
2009-08-10 17:20 ` Jose Augusto
2009-08-10 17:39 ` Hans Hagen
2009-08-10 18:11 ` Jose Augusto
2009-08-10 18:20 ` Hans Hagen [this message]
2009-08-10 15:15 ` Jose Augusto
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=4A8064E3.3020208@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).