| Groups | Blog | Home |
dotnet internationalization : Override number formatting
I've created my webapp on my local computer, and it all works fine. The numbers are formatted as appropriate for my country (eg. 10 000 for ten thousand). But when I upload to my server in the US, the format changes to the American system (10,000 for ten thousand). I've heard that you can get around this by adding the "culture" tag to Web.config. However, Microsoft's default settings for my country are wrong. If I add culture="en-NZ" to the Web.config, my local computer now uses the wrong settings too. How can I override the settings so that the numbers appear correctly? Thanks Chris
Where is the standard of using a space as the group separator for en-NZ
defined? I have not been able to find such a standard anywhere. The Common Locale Data Repository uniformly displays a comma as the group separator for that locale: http://www.unicode.org/cldr/data/diff/main/en_NZ.html Beth [quoted text, click to view] Chris Mahoney wrote:
> Hi > > I've created my webapp on my local computer, and it all works fine. The > numbers are formatted as appropriate for my country (eg. 10 000 for ten > thousand). But when I upload to my server in the US, the format changes to > the American system (10,000 for ten thousand). > > I've heard that you can get around this by adding the "culture" tag to > Web.config. However, Microsoft's default settings for my country are wrong. > If I add culture="en-NZ" to the Web.config, my local computer now uses the > wrong settings too. > > How can I override the settings so that the numbers appear correctly? > > Thanks > Chris
"New Zealand has adopted the SI or metric units of measurement" (from
http://www.med.govt.nz/buslt/compliance/standards/guide-2001/guide-2001-04.h tml) There is plenty of SI information available via Google, such as "The digits of numerical values having more than four digits on either side of the decimal marker are separated into groups of three using a thin, fixed space counting from both the left and right of the decimal marker. Commas are not used to separate digits into groups of three." (from http://physics.nist.gov/cuu/Units/checklist.html, #16) Anyway, this doesn't answer my question! Chris On 6/8/05 3:07 AM, in article OasWv9cmFHA.1464@TK2MSFTNGP14.phx.gbl, "Beth [quoted text, click to view] N" <eflarup@yahoo.com> wrote:
> Where is the standard of using a space as the group separator for en-NZ > defined? I have not been able to find such > a standard anywhere. The Common Locale Data Repository uniformly > displays a comma as the group separator > for that locale: > http://www.unicode.org/cldr/data/diff/main/en_NZ.html > > Beth > > > Chris Mahoney wrote: >> Hi >> >> I've created my webapp on my local computer, and it all works fine. The >> numbers are formatted as appropriate for my country (eg. 10 000 for ten >> thousand). But when I upload to my server in the US, the format changes to >> the American system (10,000 for ten thousand). >> >> I've heard that you can get around this by adding the "culture" tag to >> Web.config. However, Microsoft's default settings for my country are wrong. >> If I add culture="en-NZ" to the Web.config, my local computer now uses the >> wrong settings too. >> >> How can I override the settings so that the numbers appear correctly? >> >> Thanks >> Chris >>
[quoted text, click to view]
> There is plenty of SI information available via Google, such as "The digits SI has nothing to do with the number formatting.> of numerical values having more than four digits on either side of the > decimal marker are separated into groups of three using a thin, fixed space > counting from both the left and right of the decimal marker. Commas are not > used to separate digits into groups of three." (from > http://physics.nist.gov/cuu/Units/checklist.html, #16) All Europe uses SI for a long time, but the France uses non-breaking-space (or non-breaking-half-of-space if you are to be more catholic than the pope), Germany uses dots and so on. And your quote is from NIST, which is an U.S. thing. So, the question is again: what should it be for NZ ? -- Mihai Nita [Microsoft MVP, Windows - SDK] ------------------------------------------
I came on here and asked how to override the number formatting. Could
someone please answer my question, rather than argue about what's right and what's wrong. Thank you.
Context, please?
It is impossible to determine from the below what you are trying to do, exactly. But if it turns out that what you want to do is not a best practice and it will not be good for the user of whatever you are developing, you should be thanking the people who point it out.... -- MichKa [Microsoft] NLS Collation/Locale/Keyboard Technical Lead Globalization Infrastructure, Fonts, and Tools Blog: http://blogs.msdn.com/michkap This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Chris Mahoney" <chris@nzweb.net> wrote in message news:BF1E4969.488%chris@nzweb.net... >I came on here and asked how to override the number formatting. Could > someone please answer my question, rather than argue about what's right > and > what's wrong. > > Thank you. >
[quoted text, click to view]
> I came on here and asked how to override the number formatting. Could In general I don't like teaching people how to shoot themselves (in the leg > someone please answer my question, rather than argue about what's right and > what's wrong. or otherwise :-) -- Mihai Nita [Microsoft MVP, Windows - SDK] ------------------------------------------
Sorry about the delay in replying.
[quoted text, click to view] > Context, please? > > It is impossible to determine from the below what you are trying to do, > exactly. Sorry, I have a bad habit of not including all the information :) Simple line of VB code: TextBox1.Text = String.Format("{0:c0}", 12345) This results in the TextBox filling with "$12,345" when I want it to say "$12 345". [quoted text, click to view] > But if it turns out that what you want to do is not a best practice and it > will not be good for the user of whatever you are developing, you should be > thanking the people who point it out.... Look at any NZ Government publication (or many other NZ publications) and you'll find a space as the separator. Thanks Chris
You can update the numeric grouping separator in a CultureInfo's
NumberFormatInfo and then use that ci or nfi to do the formatting -- that is the best way to proceed hee, given the code you are using (note the String.Format override that uses an IFormatProvider -- you can pass the NFI right there). -- MichKa [Microsoft] NLS Collation/Locale/Keyboard Technical Lead Globalization Infrastructure, Fonts, and Tools Blog: http://blogs.msdn.com/michkap This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Chris Mahoney" <chris@nzweb.net> wrote in message news:BF2A18D1.499%chris@nzweb.net... > Sorry about the delay in replying. > >> Context, please? >> >> It is impossible to determine from the below what you are trying to do, >> exactly. > > Sorry, I have a bad habit of not including all the information :) > > Simple line of VB code: > TextBox1.Text = String.Format("{0:c0}", 12345) > > This results in the TextBox filling with "$12,345" when I want it to say > "$12 345". > >> But if it turns out that what you want to do is not a best practice and >> it >> will not be good for the user of whatever you are developing, you should >> be >> thanking the people who point it out.... > > Look at any NZ Government publication (or many other NZ publications) and > you'll find a space as the separator. > > Thanks > Chris >
Aha!
After all that trouble, I knew it'd be quite simple to do. Thanks! Chris On 19/8/05 2:46 AM, in article umZMoOApFHA.3544@TK2MSFTNGP15.phx.gbl, [quoted text, click to view] "Michael (michka) Kaplan [MS]" <michkap@microsoft.online.com> wrote:
> You can update the numeric grouping separator in a CultureInfo's > NumberFormatInfo and then use that ci or nfi to do the formatting -- that is > the best way to proceed hee, given the code you are using (note the > String.Format override that uses an IFormatProvider -- you can pass the NFI > right there). >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |