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 19:39:01 +0200	[thread overview]
Message-ID: <4A805B35.8020602@wxs.nl> (raw)
In-Reply-To: <1781d7210908101020y1fd9611du529f65cc6553bc4c@mail.gmail.com>

Jose Augusto wrote:

> Meanwhile I don't think that the magic string
> # encoding: ASCII-8BIT
> solves the problem. This string indicates that the script is written in
> ASCII-8BIT,
> but when is reading the strings from the .tex or .tui files ruby 1.9.1
> considers
> them as US-ASCII regardless of the encoding declared in # encoding: ...

not when opened as 'rb' (which i do in the latest texexec.rb) so i 
wonder why that does not work at your place

(http://blog.nuclearsquid.com/writings/ruby-1-9-encodings)

i run ruby 1.8.6 (and on a couple of servers even older versions and i'm 
not going to touch ruby on these machines (i don't want to patch scripts 
that are supposed to run another 5-10 years) but i might update context 
and texexec)

> I introduced " # encoding: ASCII-8BIT  " in texmfstart.rb, tex.rb and
> texutil.rb
> and the problem didn't disapeer :-(

hm, it worked here

> Of course I may be wrong. But the experiments I did make me think this way.
> Also, I don't have Linux at my disposal (I mean, with context installed) and
> there
> the behavior perhaps is different...

that's my biggest fear ... introducing more problems


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 17:39 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 [this message]
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=4A805B35.8020602@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).