On 5/9/07, Koichiro Ohba <[EMAIL PROTECTED]> wrote:
Dear Thomas
At Fri, 27 Apr 2007 18:59:50 -0500,
Thomas E Enebo wrote:
>
> SOS...SOS
...snip..
> JRUBY-309: Implement IConv Exception classes (e.g.
> Iconv::IllegalSequence and friends)
> JRUBY-310: Implement Iconv instance methods iconv, close
> JRUBY-788: Implement IConv#open
>
> These last three are probably meant for one person (and 309 may
> actually be done...we just need someone to verify that).
I reimplemented Iconv to be more compatible with CRuby 1.8.5.
Please check the attached patch and test cases.
The following problems are still not fixed.
--- RubyIconv.java ---
>> // FIXME: We are assuming that original string will be raw bytes. If -Ku is
provided
>> // this will not be true, but that is ok for now. Deal with that when
someone needs it.
----------------------
I think this was the last task in your SOS message.
Is there any other task to try? :)
Super work....I was worried we would not get these solved for 1.0!
How about this one:
JRUBY-867: Iconv character set options (//ignore, //translit) not supported
That is last known iconv bug for 1.0.0.
Here is a bigger one, but it sure would be nice to have done as well:
JRUBY-26: Various special globals should be thread specific and not
shared by all threads
This involves making these variables that are purely global to be
variables in ThreadContext.
We appreciate your time helping us...
-Tom
Thanks,
--
___/_ __/ ___/ ITOCHU TECHNO-SOLUTIONS Corp.
/ / / Advanced Technology Team - Koichiro Ohba
____/ __/ ____/ mailto:[EMAIL PROTECTED]
--
Blog: http://www.bloglines.com/blog/ThomasEEnebo
Email: [EMAIL PROTECTED] , [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
