From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Clean Machine, MacTeX 2013 installed, ConTeXt problem
Date: Wed, 18 Sep 2013 19:55:16 +0200 [thread overview]
Message-ID: <5239E904.2050506@wxs.nl> (raw)
In-Reply-To: <0A07BB90-DDB6-47D3-8E59-268F9F538F52@rna.nl>
On 9/18/2013 4:53 PM, Gerben Wierda wrote:
> On 18 Sep 2013, at 11:18, Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 9/18/2013 10:47 AM, Gerben Wierda wrote:
>>> As my computer died I had to set up a clean one. I installed MacTeX 2013
>>> and tried to compile a ConTeXt project, but this failed:
>>>
>>> texexec --pdf --mode=editor --once .../products/prd_book.tex
>>>
>>> resolvers | caches | path
>>> '/Users/gerben/Library/texlive/2013/texmf-var'
>>> created/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in
>>> `require':
>>> /usr/local/texlive/2013/texmf-dist/scripts/context/ruby/base/switch.rb:501:
>>> invalid multibyte escape: /\xFF/ (SyntaxError)
>>> from
>>> /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in
>>> `require'
>>> from
>>> /usr/local/texlive/2013/texmf-dist/scripts/context/ruby/texexec.rb:11:in
>>> `<main>'
>>>
>>> It seems a problem in a ruby file in MacTeX 2013. Can someone help me
>>> get this working?
>>
>> Maybe something utf in the latest ruby ... can you try to replace the \xFF with \xFFFC and see what happens?
>
> Same thing happens. Now it says \xFFFC is an invalid multibyte escape
it runs ok with \xFF here in 1.9
in 2.0 i need to patch in that file:
series.each_char do |key| # was .each but there is no alias to each_char
any longer
does the top of switch.rb mention:
#encoding: ASCII-8BIT
(i do have a prototype of texexec in lua but no time to finish that now
but i fear at some moment i have to do it as i cannot foresee ruby 2.0
compatibility issues)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-18 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 8:47 Gerben Wierda
2013-09-18 9:18 ` Hans Hagen
2013-09-18 14:53 ` Gerben Wierda
2013-09-18 17:15 ` Hans Hagen
2013-09-18 17:21 ` Rajeesh K Nambiar
2013-09-18 17:31 ` Hans Hagen
2013-09-18 20:23 ` Gerben Wierda
2013-09-19 7:15 ` Hans Hagen
2013-09-18 17:55 ` Hans Hagen [this message]
2013-09-18 23:36 ` Mica Semrick
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=5239E904.2050506@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).