[#4076] Ruby/DL — Jamis Buck <jamis_buck@...>

I recently used Ruby/DL to create bindings to the SQLite3 embedded

40 messages 2005/01/03
[#4096] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/04

On Tue, Jan 04, 2005 at 02:53:49AM +0900, Jamis Buck wrote:

[#4099] Re: Ruby/DL — ts <decoux@...> 2005/01/04

>>>>> "P" == Paul Brannan <pbrannan@atdesk.com> writes:

[#4119] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/05

On Wed, Jan 05, 2005 at 03:05:48AM +0900, ts wrote:

[#4120] Re: Ruby/DL — ts <decoux@...> 2005/01/05

>>>>> "P" == Paul Brannan <pbrannan@atdesk.com> writes:

[#4125] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/05

On Thu, Jan 06, 2005 at 01:10:34AM +0900, ts wrote:

[#4116] Test::Unit::Collector::Dir won't work with code that modifies $LOAD_PATH — Eric Hodel <drbrain@...7.net>

Any test code that depends upon modifications of $: fails when used

10 messages 2005/01/05

[#4146] The face of Unicode support in the future — Charles O Nutter <headius@...>

Hello Rubyists!

47 messages 2005/01/06
[#4152] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/07

Hi,

[#4167] Re: The face of Unicode support in the future — Christian Neukirchen <chneukirchen@...> 2005/01/09

Yukihiro Matsumoto <matz@ruby-lang.org> writes:

[#4175] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/10

Hi,

[#4186] Re: The face of Unicode support in the future — Paul Brannan <pbrannan@...> 2005/01/11

On Mon, Jan 10, 2005 at 11:53:48PM +0900, Yukihiro Matsumoto wrote:

[#4192] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/12

Hi,

[#4269] Re: The face of Unicode support in the future — Wes Nakamura <wknaka@...>

19 messages 2005/01/18
[#4270] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/18

Hi,

[#4275] Re: The face of Unicode support in the future — Wes Nakamura <wknaka@...> 2005/01/19

[#4323] test/unit doesn't rescue a Exception — Tanaka Akira <akr@...17n.org>

test/unit doesn't rescue a Exception in a test method, as follows.

14 messages 2005/01/27
[#8773] Re: test/unit doesn't rescue a Exception — Tanaka Akira <akr@...> 2006/09/02

In article <87is5jb46q.fsf@serein.a02.aist.go.jp>,

[#8776] Re: test/unit doesn't rescue a Exception — "Nathaniel Talbott" <ntalbott@...> 2006/09/03

On 9/1/06, Tanaka Akira <akr@fsij.org> wrote:

[#8777] Re: test/unit doesn't rescue a Exception — Eric Hodel <drbrain@...7.net> 2006/09/03

On Sep 2, 2006, at 6:34 PM, Nathaniel Talbott wrote:

Re: The face of Unicode support in the future

From: Joao Pedrosa <joaopedrosa@...>
Date: 2005-01-12 23:20:41 UTC
List: ruby-core #4206
Hi,

On Thu, 13 Jan 2005 08:05:27 +0900, Mathieu Bouchard <matju@sympatico.ca> wrote:
> 
> On Fri, 7 Jan 2005, Yukihiro Matsumoto wrote:
> > |Do I need to submit a RCR for those, or should I go for two of them ?
> > I think a fixnum is not enough since a character may not be
> > represented by a single codepoint, e.g. character composition, or
> > surrogation. Besides that, a character is represented by combination
> > of codepoint(s) and
> 
> questions:
> 
> 1. are those features of unicode ?
> 
> 2. are those required for a support of Japanese that make sense ?
> 
> Those are not rhetorical questions. I don't have the answers nor the
> background to attempt tackling them. I didn't know that those features
> were important to you, and I barely ever hear about them.
> 
> Character composition, as I know it, is a hack to make accented letters,
> underlining, bold, and such, by interleaving the special code 8
> (backspace) between characters to be composed, destined to be used with
> daisy printers and TTY's, and already became dated when TTY's got replaced
> by CRT monitors during the 1970's. It stemmed from previous usual practice
> in trying to type French on an American typewriter (and other similar
> situations in other countries)
> 
> ISO-Latin-1 (that I normally use) contains all the self-contained
> codepoints necessary to write in many European languages, and as such, you
> never need composition in those languages with that charset, and as far as
> I can tell, all other charsets are designed with that in mind, including
> unicode. So it is difficult for me to believe composition is required.
> 
> Is this because of the way Japanese works? (then if it's so specific to
> Japanese, why hasn't Ruby gotten that feature a decade ago ?? I'm _really_
> puzzled)

Matz has talked about this in the past. comp.lang.ruby should have
something archived, for example.

The problem is split:
1) How to support new encodings.
2) How to maintain backward compatibility.

So, Matz worries about those two. Many of us worry only with "1". The
reason is that Japanese, Chinese, and other languages need some
backward compatibility with what has been written in these languages.

Cheers,
Joao

In This Thread