Scott, The bug would appear while converting a numeric or timestamp data type to a String. I believe phone numbers are Strings.
-Adrian --- On Fri, 6/27/08, Scott Gray <[EMAIL PROTECTED]> wrote: > From: Scott Gray <[EMAIL PROTECTED]> > Subject: Re: Potential OFBiz Localization Bugs > To: [email protected] > Date: Friday, June 27, 2008, 2:02 PM > Phone numbers? I haven't checked if there's a > problem, it's just the first > thing that came to mind. > > Regards > Scott > > 2008/6/28 Adrian Crum <[EMAIL PROTECTED]>: > > > In the trunk rev 658045 I committed some localization > work. My intention > > was to fix all of the quirky localization issues that > keep popping up. > > > > I took the shotgun approach and localized all numeric > and date-time > > conversions - believing that the majority of those > conversions should be > > localized. The exceptions could be handled on a > case-by-case basis. > > > > That commit solved a number of localization issues, > but (as was pointed out > > on the user ml today) it introduced a bug in order > number and invoice number > > generation. IDs were being localized. IDs are one of > the exceptions to > > localization. I fixed that issue in rev 672343. > > > > If anyone can think of any other exceptions, please > let me know and I will > > take care of it. > > > > -Adrian > > > >
