From: "David A. Black" <dblack@...>
Date: 2008-02-28T02:30:04+09:00
Subject: Re: Gems running aground on multibyte char

Hi --

On Wed, 27 Feb 2008, Ryan Davis wrote:

>
> On Feb 26, 2008, at 05:16 , David A. Black wrote:
>
>> The problem is that in 1.9 (tested with 1.9.0-0 and today's trunk),
>> gem has trouble with the archive-tar-minitar gem, because it can't
>> deal with the accented 'a' in Fernandez.
>> 
>> sh-3.2# gem install ruport
>> WARNING:
>> /usr/local/lib/ruby-1.9.0/lib/ruby/gems/1.9.0/specifications/archive-tar-minitar-0.5.1.gemspec:12:
>> invalid multibyte char
>
> That's just a warning... I think the actual issue is:
>
>> /usr/local/lib/ruby-1.9.0/lib/ruby/gems/1.9.0/specifications/archive-tar-minitar-0.5.1.gemspec:12:
>> syntax error, unexpected tIDENTIFIER, expecting keyword_end
>> ...d heavily on Mauricio Fern?ndez's implementation in rpa-base...
>
> Looks like the ruby that is generated for a gem spec isn't escaping the quote 
> character correctly. But it doesn't look like that in my spec:

I don't exactly why it's pointing at the ' but I'm pretty sure it's
the accented 'a' that's causing the problem. If I reduce the
description entry to just that one character and try to build a gem
from it (with 1.9), I get:

$ gem build metadata 
ERROR:  While executing gem ... (ArgumentError)
     broken UTF-8 string


David

-- 
Upcoming Rails training from David A. Black and Ruby Power and Light:
   ADVANCING WITH RAILS, April 14-17 2008, New York City
   CORE RAILS, June 24-27 2008, London (Skills Matter)
See http://www.rubypal.com for details, and stay
tuned for dates in Berlin!