Well, that's sort of how I imagined this would play out. And from a
code writers ascii-centric outlook I agree it makes sense to have
unicode as a special case brought in only when the pesky data requires
it. What about using the icu api to make things easier when the
formatter changes?
Mike
At 12:21 AM + 1/16/04, Tim Bunce wrote:
On Thu, Jan 15, 2004 at 05:15:05PM -0500, Dan Sugalski wrote:
At 2:39 PM -0500 1/15/04, Dan Sugalski wrote:
>At 8:31 PM +0100 1/15/04, Michael Scott wrote:
>>Is this relevant?
>>http://oss.software.ibm.com/icu/userguide/formatNumbers.html
>>
>>I'm s
On Thu, Jan 15, 2004 at 05:15:05PM -0500, Dan Sugalski wrote:
> At 2:39 PM -0500 1/15/04, Dan Sugalski wrote:
> >At 8:31 PM +0100 1/15/04, Michael Scott wrote:
> >>Is this relevant?
> >>http://oss.software.ibm.com/icu/userguide/formatNumbers.html
> >>
> >>I'm still not clear in my mind what the pl
At 2:39 PM -0500 1/15/04, Dan Sugalski wrote:
At 8:31 PM +0100 1/15/04, Michael Scott wrote:
Is this relevant?
http://oss.software.ibm.com/icu/userguide/formatNumbers.html
I'm still not clear in my mind what the plan is with regard to ICU.
Is it intended eventually to be:
a) an always-there pa
At 8:31 PM +0100 1/15/04, Michael Scott wrote:
Is this relevant? http://oss.software.ibm.com/icu/userguide/formatNumbers.html
I'm still not clear in my mind what the plan is with regard to ICU.
Is it intended eventually to be:
a) an always-there part of parrot, or
b) just a sometimes-there thi
Is this relevant?
http://oss.software.ibm.com/icu/userguide/formatNumbers.html
I'm still not clear in my mind what the plan is with regard to ICU. Is
it intended eventually to be:
a) an always-there part of parrot, or
b) just a sometimes-there thing that gets linked in if you mess with
unico
