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: Ruby 1.9.1 and non-ascii char parsing in .tui file
Date: Mon, 10 Aug 2009 15:10:56 +0200	[thread overview]
Message-ID: <4A801C60.8030501@wxs.nl> (raw)
In-Reply-To: <1781d7210908092015n2d57ae21n6f09fd66729e41ac@mail.gmail.com>

Jose Augusto wrote:
> Hi all,
> 
> Ok, here it goes. Atached are the files used in the test.
> 
> The problem as reported in the >> previous email << used
> the file with the offending chars wrapped in a main file, which was just:
> 
> \starttext
> \input zzz.tex
> \stoptext
> 
> That is, the offending chars were in zzz.tex.
> 
> In that example I noticed the error because the cross-refs
> in the equation numbering were not working.
> The parsing of the .tui file by ruby 1.9.1 failed. Then I saw the errors.

ruby 1.9 internally is no longer 8 bit clean i.e. there is always an 
encoding (file as well as internal); there is no way to enforce this 
(there is the -E option but that is useless for 1.8)

i now open some files explicitly in binary mode; maybe that helps; i 
have no clue what happens with string manipulations later on

i always liked ruby but such fundamental changes (encoding, dropping 
functions etc) without renaming the program are a showstopper for me as 
one cannot predict what will be on the user's system

it looks like i have to convert the texutil part to lua (takes a few 
days and since i mostly use luatex it has a low priority)

i uploaded a beta for testing

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
___________________________________________________________________________________


  reply	other threads:[~2009-08-10 13:10 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 [this message]
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
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=4A801C60.8030501@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).