Click Here to Install Silverlight*
United StatesChange|All Microsoft Sites
Microsoft

National Language Support (NLS) API Reference

About NLSWeb

Select an Operating System:

Note that the following predefined NLSData table is provided only as a reference. This information can be retrieved using Win32 API GetLocaleInfoW and .NET Framework CultureInfo class.

NLS Information for Windows Vista


Go BackSelect another LCID


Sanskrit (India)
044F Codepage info
LCID044F
Locale name Sanskrit (India)
Language-English nameSanskrit
Language-native nameसंस्कृत (भारतम्)
ANSI codepage0
OEM codepage1
044F NLS formatting
Number formatting
Positive number example12,346.00
Negative number example-12,346.00
Decimal separator.
Digits after decimal separator2
Digit grouping3;2;0
Thousands separator,
Negative format symbol-
Number list separator,
Leading and trailing zeros: 0.700 formatted0.70
Standard digits०१२३४५६७८९
System of measurements Metric
Currency formatting
Positive sampleरु 12,346.00
Negative sampleरु 12,346.00
Currency symbolरु
Decimal separator.
Thousand separator,
Digit grouping3;2;0
Time formatting
Time sample12:15:12
Default time formatHH:mm:ss
Time format separator:
AM symbolपूर्वाह्न
PM symbolअपराह्न
All time formatsHH:mm:ss
H:mm:ss
tt hh:mm:ss
tt h:mm:ss
Date formatting
Default short date format23-08-2005
Default long date format23 अगस्त 2005 मङ्गलवासरः
All short date formats23-08-2005
dd-MM-yyyy
dd-MM-yy
d-M-yy
d.M.yy
yyyy-MM-dd
All long date formats23 अगस्त 2005 मङ्गलवासरः
dd MMMM yyyy dddd
d MMMM yyyy
Calendars
CalendarsGregorian(Localized)

Go BackSelect another LCID

Top of pageTop of page

About NLSWeb

How NLSWeb tool was written

NLSWeb originated as a reference tool for testers. When an application is tested to comply to local conventions (defined by user locale), may be handy to have a perfect sample. The etalon can be found by reading the NLS settings from the operating system NLS API. But the most complete information is available under Windows 2000 only - while it may be required when tests are running on Windows 95/98 or Windows Me.

The solution was found: collect the information on a Windows 2000 server and display it to everybody interested through a Web page. No data is collected on the client: perfect NLS information is not related on the platform where the test is run. On the server side, on the other hand, a lot of work has to be done. An ASP page was written.

The information about NLS support is collected at run time, showing the most current status of NLS data on the server. Win32 NLS API is broader then NLS support of VBScript or JavaScript; to get access to those functions, the ASP calls a server-side ATL control. This control calls NLS API when an application is started on the server. When the server running NLSWeb is updated with OS having broader language support the users get the updated information automatically.

NLS data fits well into tree structure of XML; this format leaves room for future expansion if NLS API grows; it is easily built and formatted. The drawback of XML format - it is not supported by all browsers, and those supporting it may be limited in formatting capabilities. That's why NLSWeb receives XML data from the ATL control, formats it using XSL filters, and sends HTML data to the client.

Normally, language-specific information is required for one language at a time; ATL control running on our page collects information for all languages. To keep the user from drawning in all that data, while providing an easy way to access any language information, the ASP used two XSL filters. First - the default one - formats the start page, showing a list of locales that server supports. The second, single-language filter , formats a language-specific page; it receives a single - language subset of the XML data that ATL.

The data sent is multi-lingual and encoded in UTF-8. Certain problems may show up when multi-lingual data is displayed on non-multilingual platforms. To resolve some of those problems, a Unicode font was created from Sylfaen font supplied with Microsoft Windows 2000. This font is embedded into the output HTML, so that you see less "default glyphs" (result of system's failure to find a symbol to display text) in the output. However, this solution works only with Microsoft Internet Explorer 4.0 or better. For more information on this technique and for the tool that generates Web fonts, check the link: http://www.microsoft.com/typography/web/embedding/weft3/default.htm.


Top of pageTop of page

© 2014 Microsoft Corporation. All rights reserved. Contact Us |Terms of Use |Trademarks |Privacy & Cookies