Introduction .windows.net



[MS-UCODEREF]: Windows Protocols Unicode ReferenceIntellectual Property Rights Notice for Open Specifications DocumentationTechnical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit trademarks. Fictitious Names. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.Revision SummaryDateRevision HistoryRevision ClassComments2/14/20082.0.1EditorialChanged language and formatting in the technical content.3/14/20082.0.2EditorialChanged language and formatting in the technical content.5/16/20082.0.3EditorialChanged language and formatting in the technical content.6/20/20083.0MajorUpdated and revised the technical content.7/25/20083.0.1EditorialChanged language and formatting in the technical content.8/29/20083.0.2EditorialChanged language and formatting in the technical content.10/24/20083.0.3EditorialChanged language and formatting in the technical content.12/5/20083.1MinorClarified the meaning of the technical content.1/16/20093.1.1EditorialChanged language and formatting in the technical content.2/27/20093.1.2EditorialChanged language and formatting in the technical content.4/10/20093.1.3EditorialChanged language and formatting in the technical content.5/22/20093.1.4EditorialChanged language and formatting in the technical content.7/2/20094.0MajorUpdated and revised the technical content.8/14/20094.0.1EditorialChanged language and formatting in the technical content.9/25/20094.1MinorClarified the meaning of the technical content.11/6/20095.0MajorUpdated and revised the technical content.12/18/20096.0MajorUpdated and revised the technical content.1/29/20107.0MajorUpdated and revised the technical content.3/12/20107.0.1EditorialChanged language and formatting in the technical content.4/23/20107.0.2EditorialChanged language and formatting in the technical content.6/4/20107.0.3EditorialChanged language and formatting in the technical content.7/16/20107.0.3NoneNo changes to the meaning, language, or formatting of the technical content.8/27/20107.0.3NoneNo changes to the meaning, language, or formatting of the technical content.10/8/20107.0.3NoneNo changes to the meaning, language, or formatting of the technical content.11/19/20107.0.3NoneNo changes to the meaning, language, or formatting of the technical content.1/7/20117.0.3NoneNo changes to the meaning, language, or formatting of the technical content.2/11/20117.0.3NoneNo changes to the meaning, language, or formatting of the technical content.3/25/20117.0.3NoneNo changes to the meaning, language, or formatting of the technical content.5/6/20117.0.3NoneNo changes to the meaning, language, or formatting of the technical content.6/17/20117.1MinorClarified the meaning of the technical content.9/23/20117.1NoneNo changes to the meaning, language, or formatting of the technical content.12/16/20118.0MajorUpdated and revised the technical content.3/30/20129.0MajorUpdated and revised the technical content.7/12/20129.0NoneNo changes to the meaning, language, or formatting of the technical content.10/25/20129.0NoneNo changes to the meaning, language, or formatting of the technical content.1/31/20139.0NoneNo changes to the meaning, language, or formatting of the technical content.8/8/20139.1MinorClarified the meaning of the technical content.11/14/20139.1NoneNo changes to the meaning, language, or formatting of the technical content.2/13/201410.0MajorUpdated and revised the technical content.5/15/201410.0NoneNo changes to the meaning, language, or formatting of the technical content.6/30/201511.0MajorSignificantly changed the technical content.10/16/201511.0No ChangeNo changes to the meaning, language, or formatting of the technical content.Table of ContentsTOC \o "1-9" \h \z1Introduction PAGEREF _Toc432488277 \h 61.1Glossary PAGEREF _Toc432488278 \h 61.2References PAGEREF _Toc432488279 \h 71.2.1Normative References PAGEREF _Toc432488280 \h 71.2.2Informative References PAGEREF _Toc432488281 \h 81.3Overview PAGEREF _Toc432488282 \h 81.4Applicability Statement PAGEREF _Toc432488283 \h 81.5Standards Assignments PAGEREF _Toc432488284 \h 82Messages PAGEREF _Toc432488285 \h 102.1Transport PAGEREF _Toc432488286 \h 102.2Message Syntax PAGEREF _Toc432488287 \h 102.2.1Supported Codepage in Windows PAGEREF _Toc432488288 \h 102.2.2Supported Codepage Data Files PAGEREF _Toc432488289 \h 172.2.2.1Codepage Data File Format PAGEREF _Toc432488290 \h 172.2.2.1.1WCTABLE PAGEREF _Toc432488291 \h 182.2.2.1.2MBTABLE PAGEREF _Toc432488292 \h 192.2.2.1.3DBCSRANGE PAGEREF _Toc432488293 \h 193Protocol Details PAGEREF _Toc432488294 \h 213.1Client Details PAGEREF _Toc432488295 \h 213.1.1Abstract Data Model PAGEREF _Toc432488296 \h 213.1.2Timers PAGEREF _Toc432488297 \h 213.1.3Initialization PAGEREF _Toc432488298 \h 213.1.4Higher-Layer Triggered Events PAGEREF _Toc432488299 \h 213.1.5Message Processing Events and Sequencing Rules PAGEREF _Toc432488300 \h 213.1.5.1Mapping Between UTF-16 Strings and Legacy Codepages PAGEREF _Toc432488301 \h 213.1.5.1.1Mapping Between UTF-16 Strings and Legacy Codepages Using CodePage Data File PAGEREF _Toc432488302 \h 213.1.5.1.1.1Pseudocode for Accessing a Record in the Codepage Data File PAGEREF _Toc432488303 \h 213.1.5.1.1.2Pseudocode for Mapping a UTF-16 String to a Codepage String PAGEREF _Toc432488304 \h 223.1.5.1.1.3Pseudocode for Mapping a Codepage String to a UTF-16 String PAGEREF _Toc432488305 \h 243.1.5.1.2Mapping Between UTF-16 Strings and ISO 2022-Based Codepages PAGEREF _Toc432488306 \h 273.1.5.1.3Mapping between UTF-16 Strings and GB 18030 Codepage PAGEREF _Toc432488307 \h 273.1.5.1.4Mapping Between UTF-16 Strings and ISCII Codepage PAGEREF _Toc432488308 \h 273.1.5.1.5Mapping Between UTF-16 Strings and UTF-7 PAGEREF _Toc432488309 \h 273.1.5.1.6Mapping Between UTF-16 Strings and UTF-8 PAGEREF _Toc432488310 \h 273.1.5.2Comparing UTF-16 Strings by Using Sort Keys PAGEREF _Toc432488311 \h 273.1.5.2.1Pseudocode for Comparing UTF-16 Strings PAGEREF _Toc432488312 \h 273.1.5.2.2CompareSortKey PAGEREF _Toc432488313 \h 283.1.5.2.3Accessing the Windows Sorting Weight Table PAGEREF _Toc432488314 \h 293.1.5.2.3.1Windows Sorting Weight Table PAGEREF _Toc432488315 \h 303.1.5.2.4GetWindowsSortKey Pseudocode PAGEREF _Toc432488316 \h 303.1.5.2.5TestHungarianCharacterSequences PAGEREF _Toc432488317 \h 413.1.5.2.6GetContractionType PAGEREF _Toc432488318 \h 423.1.5.2.7CorrectUnicodeWeight PAGEREF _Toc432488319 \h 423.1.5.2.8MakeUnicodeWeight PAGEREF _Toc432488320 \h 433.1.5.2.9GetCharacterWeights PAGEREF _Toc432488321 \h 433.1.5.2.10GetExpansionWeights PAGEREF _Toc432488322 \h 443.1.5.2.11GetExpandedCharacters PAGEREF _Toc432488323 \h 453.1.5.2.12SortkeyContractionHandler PAGEREF _Toc432488324 \h 463.1.5.2.13Check3ByteWeightLocale PAGEREF _Toc432488325 \h 503.1.5.2.14SpecialCaseHandler PAGEREF _Toc432488326 \h 503.1.5.2.15GetPositionSpecialWeight PAGEREF _Toc432488327 \h 543.1.5.2.16MapOldHangulSortKey PAGEREF _Toc432488328 \h 543.1.5.2.17GetJamoComposition PAGEREF _Toc432488329 \h 543.1.5.2.18GetJamoStateData PAGEREF _Toc432488330 \h 563.1.5.2.19FindNewJamoState PAGEREF _Toc432488331 \h 563.1.5.2.20UpdateJamoSortInfo PAGEREF _Toc432488332 \h 573.1.5.2.21IsJamo PAGEREF _Toc432488333 \h 573.1.5.2.22IsCombiningJamo PAGEREF _Toc432488334 \h 573.1.5.2.23IsJamoLeading PAGEREF _Toc432488335 \h 583.1.5.2.24IsJamoVowel PAGEREF _Toc432488336 \h 583.1.5.2.25IsJamoTrailing PAGEREF _Toc432488337 \h 583.1.5.2.26InitKoreanScriptMap PAGEREF _Toc432488338 \h 593.1.5.3Mapping UTF-16 Strings to Upper Case PAGEREF _Toc432488339 \h 603.1.5.3.1ToUpperCase PAGEREF _Toc432488340 \h 603.1.5.3.2UpperCaseMapping PAGEREF _Toc432488341 \h 603.1.5.4Unicode International Domain Names PAGEREF _Toc432488342 \h 603.1.5.4.1IdnToAscii PAGEREF _Toc432488343 \h 603.1.5.4.2IdnToUnicode PAGEREF _Toc432488344 \h 633.1.5.4.3IdnToNameprepUnicode PAGEREF _Toc432488345 \h 633.1.5.4.4PunycodeEncode PAGEREF _Toc432488346 \h 643.1.5.4.5PunycodeDecode PAGEREF _Toc432488347 \h 653.1.5.4.6IDNA2008+UTS46 NormalizeForIdna PAGEREF _Toc432488348 \h 663.1.5.4.7IDNA2003 NormalizeForIdna PAGEREF _Toc432488349 \h 673.1.5.5Comparing UTF-16 Strings Ordinally PAGEREF _Toc432488350 \h 683.1.5.5.1CompareStringOrdinal Algorithm PAGEREF _Toc432488351 \h 683.1.6Timer Events PAGEREF _Toc432488352 \h 683.1.7Other Local Events PAGEREF _Toc432488353 \h 684Protocol Examples PAGEREF _Toc432488354 \h 695Security PAGEREF _Toc432488355 \h 705.1Security Considerations for Implementers PAGEREF _Toc432488356 \h 705.2Index of Security Parameters PAGEREF _Toc432488357 \h 706Appendix A: Product Behavior PAGEREF _Toc432488358 \h 717Change Tracking PAGEREF _Toc432488359 \h 778Index PAGEREF _Toc432488360 \h 78Introduction XE "Introduction" XE "Introduction"This document is a companion reference to the protocol specifications. It describes how Unicode strings are compared in Windows protocols and how Windows supports Unicode conversion to earlier codepages. For example:UTF-16 string comparison: Provides linguistic-specific comparisons between two Unicode strings and provides the comparison result based on the language and region for a specific user.Mapping of UTF-16 strings to earlier ANSI codepages: Converts Unicode strings to strings in the earlier codepages that are used in older versions of Windows and the applications that are written for these earlier codepages.Glossary XE "Glossary" The following terms are specific to this document:code page: An ordered set of characters of a specific script in which a numerical index (code-point value) is associated with each character. Code pages are a means of providing support for character sets (1) and keyboard layouts used in different countries. Devices such as the display and keyboard can be configured to use a specific code page and to switch from one code page (such as the United States) to another (such as Portugal) at the user's request.double-byte character set (DBCS): A character set (1) that can use more than one byte to represent a single character. A DBCS includes some characters that consist of 1 byte and some characters that consist of 2 bytes. Languages such as Chinese, Japanese, and Korean use DBCS.IDNA2003: The IDNA2003 specification is defined by a cluster of IETF RFCs: IDNA [RFC3490], Nameprep [RFC3491], Punycode [RFC3492], and Stringprep [RFC3454].IDNA2008: The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework [RFC5890], Internationalized Domain Names in Applications (IDNA) Protocol [RFC5891], The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) [RFC5892], and Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) [RFC5893]. There is also an informative document: Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale [RFC5894].IDNA2008+UTS46: The IDNA2008+UTS46 citation refers to operations that comply with both the and the Unicode IDNA Compatibility Processing [TR46] specifications.single-byte character set (SBCS): A character encoding in which each character is represented by one byte. Single-byte character sets are limited to 256 characters.sort key: Numerical representations of a sort element based on locale-specific sorting rules. A sort key consists of several weighted components that represent a character's script, diacritics, case, and additional treatment based on locale.Unicode: A character encoding standard developed by the Unicode Consortium that represents almost all of the written languages of the world. The Unicode standard [UNICODE5.0.0/2007] provides three forms (UTF-8, UTF-16, and UTF-32) and seven schemes (UTF-8, UTF-16, UTF-16 BE, UTF-16 LE, UTF-32, UTF-32 LE, and UTF-32 BE).UTF-16: A standard for encoding Unicode characters, defined in the Unicode standard, in which the most commonly used characters are defined as double-byte characters. Unless specified otherwise, this term refers to the UTF-16 encoding form specified in [UNICODE5.0.0/2007] section 3.9.MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.ReferencesLinks to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata. Normative References XE "References:normative" XE "Normative references" We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact dochelp@. We will assist you in finding the relevant information. [CODEPAGEFILES] Microsoft Corporation, "Windows Supported Code Page Data Files.zip", 2009, [ECMA-035] ECMA International, "Character Code Structure and Extension Techniques", 6th edition, ECMA-035, December 1994, [GB18030] Chinese IT Standardization Technical Committee, "Chinese National Standard GB 18030-2005: Information technology - Chinese coded character set", Published in print by the China Standard Press, [ISCII] Bureau of Indian Standards, "Indian Script Code for Information Exchange - ISCII", [MSDN-SWT/Vista] Microsoft Corporation, "Windows Vista Sorting Weight Table.txt", [MSDN-SWT/W2K3] Microsoft Corporation, "Windows NT 4.0 through Windows Server 2003 Sorting Weight Table.txt", [MSDN-SWT/W2K8] Microsoft Corporation, "Windows Server 2008 Sorting Weight Table.txt", [MSDN-SWT/Win7] Microsoft Corporation, "Windows 7 through Server 2008 R2 Sorting Weight Table.txt", [MSDN-SWT/Win8] Microsoft Corporation, "Sorting Weight Table", [MSDN-UCMT/Win8] Microsoft Corporation, "Windows 8 Upper Case Mapping Table", [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, [RFC2152] Goldsmith, D., and David, M., "UTF-7 A Mail-Safe Transformation Format of Unicode", RFC 2152, May 1997, [TR46] Davis, M., and Suignard, M., “Unicode IDNA Compatibility Processing”, Unicode Technical Standard #46, September 2012, "", [UNICODE-BESTFIT] The Unicode Consortium, "WindowsBestFit", 2006, [UNICODE-COLLATION] The Unicode Consortium, "Unicode Technical Standard #10 Unicode Collation Algorithm", March 2008, [UNICODE-README] The Unicode Consortium, "Readme.txt", 2006, [UNICODE5.0.0/CH3] The Unicode Consortium, "Unicode Encoding Forms", 2006, [UNICODE] The Unicode Consortium, "The Unicode Consortium Home Page", 2006, References XE "References:informative" XE "Informative references" None.Overview XE "Overview (synopsis)" XE "Overview"This document describes the following protocols when dealing with Unicode strings on the Windows platform:UTF-16 string comparison: This string comparison is used to provide a linguistic-specific comparison between two Unicode strings. This scenario provides a string comparison result based on the expectations of users from different languages and different regions.The mapping of UTF-16 strings to earlier codepages: This scenario is used to convert between Unicode strings and strings in the earlier codepage, which are used by older versions of Windows and applications written for these earlier codepages.Applicability Statement XE "Applicability" XE "Applicability"This reference document is applicable as follows:To perform UTF-16 character comparisons in the same manner as Windows. This document only specifies a subset of Windows behaviors that are used by other protocols. It does not document those Windows behaviors that are not used by other protocols.To provide the capability to map between UTF-16 strings and earlier codepages in the same manner as Windows.Standards Assignments XE "Standards assignments" XE "Standards assignments"The following standards assignments are used by the Windows Protocols Unicode Reference.ParameterValueReferenceCodepage Data File?(section?2.2.2)Various[UNICODE-BESTFIT]Messages XE "Messages:overview"The following sections specify how Windows Protocols Unicode Reference messages are transported and Windows Protocols Unicode Reference message syntax.Transport XE "Transport" XE "Messages:transport"Message SyntaxSupported Codepage in Windows XE "Codepage:supported in Windows" XE "Messages:supported codepage in Windows"Windows assigns an integer, called code page ID, to every supported codepage.Based on the usage, the codepage supported in Windows can be categorized in the following:ANSI codepageWindows codepages are also sometimes referred to as active codepages or system active codepages. Windows always has one currently active Windows codepage. All ANSI Windows functions use the currently active codepage.The usual ANSI codepage ID for US English is codepage 1252.Windows codepage 1252, the codepage commonly used for English and other Western European languages, was based on an American National Standards Institute (ANSI) draft. That draft eventually became ISO 8859-1, but Windows codepage 1252 was implemented before the standard became final, and is not exactly the same as ISO 8859-1.OEM codepageExtended codepageThese codepages cannot be used as ANSI codepages, or OEM codepages. Windows can support conversions between Unicode and these codepages. These codepages are generally used for information exchange purpose with international/national standard or legacy systems. Examples are UTF-8, UTF-7, EBCDIC, and Macintosh codepages.The following table shows all the supported codepages by Windows. The Codepage ID lists the integer number assigned to a codepage. ANSI/OEM codepages are in bold face. The Codepage Description column describes the codepage. The Codepage notes column lists the category of a codepage and the relevant protocol section in this document to find protocol information.Codepage IDCodepage descriptionsCodepage notes37IBM EBCDIC US-CanadaExtended codepage; for processing rules, see section 3.1.5.1.1.437OEM United StatesOEM codepage; for processing rules, see section 3.1.5.1.1.500IBM EBCDIC InternationalExtended codepage; for processing rules, see section 3.1.5.1.1.708Arabic (ASMO 708)Extended codepage; for processing rules, see section 3.1.5.1.1.720Arabic (Transparent ASMO); Arabic (DOS)Extended codepage; for processing rules, see section 3.1.5.1.1.737OEM Greek (formerly 437G); Greek (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.775OEM Baltic; Baltic (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.850OEM Multilingual Latin 1; Western European (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.852OEM Latin 2; Central European (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.855OEM Cyrillic (primarily Russian)OEM codepage; for processing rules, see section 3.1.5.1.1.857OEM Turkish; Turkish (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.858OEM Multilingual Latin 1 + Euro symbolOEM codepage; for processing rules, see section 3.1.5.1.1.860OEM Portuguese; Portuguese (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.861OEM Icelandic; Icelandic (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.862OEM Hebrew; Hebrew (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.863OEM French Canadian; French Canadian (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.864OEM Arabic; Arabic (864)OEM codepage; for processing rules, see section 3.1.5.1.1.865OEM Nordic; Nordic (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.866OEM Russian; Cyrillic (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.869OEM Modern Greek; Greek, Modern (DOS)OEM codepage; for processing rules, see section 3.1.5.1.1.870IBM EBCDIC Multilingual/ROECE (Latin 2); IBM EBCDIC Multilingual Latin 2Extended codepage; for processing rules, see section 3.1.5.1.1.874ANSI/OEM Thai (same as 28605, ISO 8859-15); Thai (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.875IBM EBCDIC Greek ModernExtended codepage; for processing rules, see section 3.1.5.1.1.932ANSI/OEM Japanese; Japanese (Shift-JIS)ANSI/OEM codepage; for processing rules, see section 3.1.5.1.1.936ANSI/OEM Simplified Chinese (PRC, Singapore); Chinese Simplified (GB2312)ANSI/OEM codepage; for processing rules, see section 3.1.5.1.1.949ANSI/OEM Korean (Unified Hangul Code)ANSI/OEM codepage; for processing rules, see section 3.1.5.1.1.950ANSI/OEM Traditional Chinese (Taiwan; Hong Kong SAR, PRC); Chinese Traditional (Big5)ANSI/OEM codepage; for processing rules, see section 3.1.5.1.1.1026IBM EBCDIC Turkish (Latin 5)Extended codepage; for processing rules, see section 3.1.5.1.1.1047IBM EBCDIC Latin 1/Open SystemExtended codepage; for processing rules, see section 3.1.5.1.1.1140IBM EBCDIC US-Canada (037 + Euro symbol); IBM EBCDIC (US-Canada-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1141IBM EBCDIC Germany (20273 + Euro symbol); IBM EBCDIC (Germany-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1142IBM EBCDIC Denmark-Norway (20277 + Euro symbol); IBM EBCDIC (Denmark-Norway-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1143IBM EBCDIC Finland-Sweden (20278 + Euro symbol); IBM EBCDIC (Finland-Sweden-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1144IBM EBCDIC Italy (20280 + Euro symbol); IBM EBCDIC (Italy-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1145IBM EBCDIC Latin America-Spain (20284 + Euro symbol); IBM EBCDIC (Spain-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1146IBM EBCDIC United Kingdom (20285 + Euro symbol); IBM EBCDIC (UK-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1147IBM EBCDIC France (20297 + Euro symbol); IBM EBCDIC (France-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1148IBM EBCDIC International (500 + Euro symbol); IBM EBCDIC (International-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1149IBM EBCDIC Icelandic (20871 + Euro symbol); IBM EBCDIC (Icelandic-Euro)Extended codepage; for processing rules, see section 3.1.5.1.1.1200Unicode UTF-16, little-endian byte order (BMP of ISO 10646); available only to managed applicationsNot used in Windows.1201Unicode UTF-16, big-endian byte order; available only to managed applicationsNot used in Windows.1250ANSI Central European; Central European (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1251ANSI Cyrillic; Cyrillic (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1252ANSI Latin 1; Western European (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1253ANSI Greek; Greek (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1254ANSI Turkish; Turkish (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1255ANSI Hebrew; Hebrew (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1256ANSI Arabic; Arabic (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1257ANSI Baltic; Baltic (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1258ANSI/OEM Vietnamese; Vietnamese (Windows)ANSI codepage; for processing rules, see section 3.1.5.1.1.1361Korean (Johab)Extended codepage; for processing rules, see section 3.1.5.1.1.10000MAC Roman; Western European (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10001Japanese (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10002MAC Traditional Chinese (Big5); Chinese Traditional (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10003Korean (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10004Arabic (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10005Hebrew (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10006Greek (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10007Cyrillic (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10008MAC Simplified Chinese (GB 2312); Chinese Simplified (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10010Romanian (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10017Ukrainian (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10021Thai (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10029MAC Latin 2; Central European (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10079Icelandic (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10081Turkish (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.10082Croatian (Mac)Extended codepage; for processing rules, see section 3.1.5.1.1.12000Unicode UTF-32, little-endian byte order; available only to managed applicationsNot used in Windows.12001Unicode UTF-32, big-endian byte order; available only to managed applicationsNot used in Windows.20000CNS Taiwan; Chinese Traditional (CNS)Extended codepage; for processing rules, see section 3.1.5.1.1.20001TCA TaiwanExtended codepage; for processing rules, see section 3.1.5.1.1.20002Eten Taiwan; Chinese Traditional (Eten)Extended codepage; for processing rules, see section 3.1.5.1.1.20003IBM5550 TaiwanExtended codepage; for processing rules, see section 3.1.5.1.1.20004TeleText TaiwanExtended codepage; for processing rules, see section 3.1.5.1.1.20005Wang TaiwanExtended codepage; for processing rules, see section 3.1.5.1.1.20105IA5 (IRV International Alphabet No. 5, 7-bit); Western European (IA5)Extended codepage; for processing rules, see section 3.1.5.1.1.20106IA5 German (7-bit)Extended codepage; for processing rules, see section 3.1.5.1.1.20107IA5 Swedish (7-bit)Extended codepage; for processing rules, see section 3.1.5.1.1.20108IA5 Norwegian (7-bit)Extended codepage; for processing rules, see section 3.1.5.1.1.20127US-ASCII (7-bit)Extended codepage; for processing rules, see section 3.1.5.1.1.20261T.61Extended codepage; for processing rules, see section 3.1.5.1.1.20269ISO 6937 Non-Spacing AccentExtended codepage; for processing rules, see section 3.1.5.1.1.20273IBM EBCDIC GermanyExtended codepage; for processing rules, see section 3.1.5.1.1.20277IBM EBCDIC Denmark-NorwayExtended codepage; for processing rules, see section 3.1.5.1.1.20278IBM EBCDIC Finland-SwedenExtended codepage; for processing rules, see section 3.1.5.1.1.20280IBM EBCDIC ItalyExtended codepage; for processing rules, see section 3.1.5.1.1.20284IBM EBCDIC Latin America-SpainExtended codepage; for processing rules, see section 3.1.5.1.1.20285IBM EBCDIC United KingdomExtended codepage; for processing rules, see section 3.1.5.1.1.20290IBM EBCDIC Japanese Katakana ExtendedExtended codepage; for processing rules, see section 3.1.5.1.1.20297IBM EBCDIC FranceExtended codepage; for processing rules, see section 3.1.5.1.1.20420IBM EBCDIC ArabicExtended codepage; for processing rules, see section 3.1.5.1.1.20423IBM EBCDIC GreekExtended codepage; for processing rules, see section 3.1.5.1.1.20424IBM EBCDIC HebrewExtended codepage; for processing rules, see section 3.1.5.1.1.20833IBM EBCDIC Korean ExtendedExtended codepage; for processing rules, see section 3.1.5.1.1.20838IBM EBCDIC ThaiExtended codepage; for processing rules, see section 3.1.5.1.1.20866Russian (KOI8-R); Cyrillic (KOI8-R)Extended codepage; for processing rules, see section 3.1.5.1.1.20871IBM EBCDIC IcelandicExtended codepage; for processing rules, see section 3.1.5.1.1.20880IBM EBCDIC Cyrillic RussianExtended codepage; for processing rules, see section 3.1.5.1.1.20905IBM EBCDIC TurkishExtended codepage; for processing rules, see section 3.1.5.1.1.20924IBM EBCDIC Latin 1/Open System (1047 + Euro symbol)Extended codepage; for processing rules, see section 3.1.5.1.1.20932Japanese (JIS 0208-1990 and 0121-1990)Extended codepage; for processing rules, see section 3.1.5.1.1.20936Simplified Chinese (GB2312); Chinese Simplified (GB2312-80)Extended codepage; for processing rules, see section 3.1.5.1.1.20949Korean WansungExtended codepage; for processing rules, see section 3.1.5.1.1.21025IBM EBCDIC Cyrillic Serbian-BulgarianExtended codepage; for processing rules, see section 3.1.5.1.1.21027Ext Alpha LowercaseExtended codepage; for processing rules, see section 3.1.5.1.1. NOTE: Although this codepage is supported, it has no known use.21866Ukrainian (KOI8-U); Cyrillic (KOI8-U)Extended codepage; for processing rules, see section 3.1.5.1.1.28591ISO 8859-1 Latin 1; Western European (ISO)Extended codepage; for processing rules, see section 3.1.5.1.1.28592ISO 8859-2 Central European; Central European (ISO)Extended codepage; for processing rules, see section 3.1.5.1.1.28593ISO 8859-3 Latin 3Extended codepage; for processing rules, see section 3.1.5.1.1.28594ISO 8859-4 BalticExtended codepage; for processing rules, see section 3.1.5.1.1.28595ISO 8859-5 CyrillicExtended codepage; for processing rules, see section 3.1.5.1.1.28596ISO 8859-6 ArabicExtended codepage; for processing rules, see section 3.1.5.1.1.28597ISO 8859-7 GreekExtended codepage; for processing rules, see section 3.1.5.1.1.28598ISO 8859-8 Hebrew; Hebrew (ISO-Visual)Extended codepage; for processing rules, see section 3.1.5.1.1.28599ISO 8859-9 TurkishExtended codepage; for processing rules, see section 3.1.5.1.1.28603ISO 8859-13 EstonianExtended codepage; for processing rules, see section 3.1.5.1.1.28605ISO 8859-15 Latin 9Extended codepage; for processing rules, see section 3.1.5.1.1.38598ISO 8859-8 Hebrew; Hebrew (ISO-Logical)Extended codepage; for processing rules, see section 3.1.5.1.1. Use [CODEPAGEFILES] 28598.txt.50220ISO 2022 Japanese with no halfwidth Katakana; Japanese (JIS)Extended codepage; for processing rules, see section 3.1.5.1.1.50221ISO 2022 Japanese with halfwidth Katakana; Japanese (JIS-Allow 1 byte Kana)Extended codepage; for processing rules, see section 3.1.5.1.2.50222ISO 2022 Japanese JIS X 0201-1989; Japanese (JIS-Allow 1 byte Kana - SO/SI)Extended codepage; for processing rules, see section 3.1.5.1.2.50225ISO 2022 KoreanExtended codepage; for processing rules, see section 3.1.5.1.2.50227ISO 2022 Simplified Chinese; Chinese Simplified (ISO 2022)Extended codepage; for processing rules, see section 3.1.5.1.2.50229ISO 2022 Traditional ChineseExtended codepage; for processing rules, see section 3.1.5.1.2.51949EUC KoreanExtended codepage; for processing rules, see section 3.1.5.1.2. Use [CODEPAGEFILES] 20949.txt.52936HZ-GB2312 Simplified Chinese; Chinese Simplified (HZ)Extended codepage; for processing rules, see section 3.1.5.1.2.54936GB18030 Simplified Chinese (4 byte); Chinese Simplified (GB18030)Extended codepage; for processing rules, see section 3.1.5.1.3.57002ISCII DevanagariExtended codepage; for processing rules, see section 3.1.5.1.4.57003ISCII BengaliExtended codepage; for processing rules, see section 3.1.5.1.4.57004ISCII TamilExtended codepage; for processing rules, see section 3.1.5.1.4.57005ISCII TeluguExtended codepage; for processing rules, see section 3.1.5.1.4.57006ISCII AssameseExtended codepage; for processing rules, see section 3.1.5.1.4.57007ISCII Odia (was Oriya)Extended codepage; for processing rules, see section 3.1.5.1.4.57008ISCII KannadaExtended codepage; for processing rules, see section 3.1.5.1.4.57009ISCII MalayalamExtended codepage; for processing rules, see section 3.1.5.1.4.57010ISCII GujaratiExtended codepage; for processing rules, see section 3.1.5.1.4.57011ISCII PunjabiExtended codepage; for processing rules, see section 3.1.5.1.4.65000Unicode (UTF-7)Extended codepage; for processing rules, see section 3.1.5.1.5.65001Unicode (UTF-8) Extended codepage; for processing rules, see section 3.1.5.1.6.Supported Codepage Data Files XE "Codepage:supported data files:overview" XE "Messages:supported codepage data files"The mapping of UTF-16 strings to codepages relies on codepage data files to provide conversion data. These codepage data files map Unicode characters to characters in a single-byte character set (SBCS) or double-byte character set (DBCS).The data files of supported system codepages are published as specified in [CODEPAGEFILES], [UNICODE], and [UNICODE-BESTFIT]. The location identification uses a simple file-naming convention, which is bestfitxxxx.txt, where xxxx is the codepage number. For example, bestfit950.txt contains the data for codepage 950, and bestfit1252.txt contains the data for codepage 1252.The pseudocode assumes all these codepage files are available. Codepage Data File Format XE "Codepage:supported data files:format"The Readme.txt (as specified in [UNICODE-README]) provides details about the codepages files and the file format. This section specifies information about the pseudocode of mapping UTF-16 strings to earlier codepages by taking the content from the Readme.txt.Each file has sections of keyword tags and records. Any text after ";" is ignored as blank lines. Fields are delimited by one or more space or tab characters. Each section begins with one of the following tags:CODEPAGE ([UNICODE-README])CPINFO ([UNICODE-README])MBTABLE?(section?2.2.2.1.2)WCTABLE?(section?2.2.2.1.1)DBCSRANGE?(section?2.2.2.1.3) (DBCS codepages only)DBCSTABLE (section 2.2.2.1.3) (DBCS codepages only) WCTABLE XE "WCTABLE"The WCTABLE tag marks the start of the mapping from Unicode UTF-16 to MultiByte bytes. It has one field.Field 1: The number of records of Unicode to byte mappings. Note that this field is often more than the number of roundtrip mappings that are supported by the codepage due to Windows best-fit behavior.An example of the WCTABLE tag is:WCTABLE 698The Unicode UTF-16 mapping records follow the WCTABLE section. These mapping records are in two forms: single-byte or double-byte codepages. Both forms have two fields.Field 1: The Unicode UTF-16 code point for the character being converted.Field 2: The single byte that this UTF-16 code point maps to. This can be a best-fit mapping.The following example shows Unicode to byte-mapping records for SBCSs.0x0000 0x00; Null0x0001 0x01; Start Of Heading...0x0061 0x61; Latin Small Letter A0x0062 0x62; Latin Small Letter B0x0063 0x63; Latin Small Letter C...0x221e 0x38; Infinity << Best Fit Mapping...0xff41 0x61; Fullwidth Latin Small Letter A << Best Fit Mapping0xff42 0x62; Fullwidth Latin Small Letter B << Best Fit Mapping0xff43 0x63; Fullwidth Latin Small Letter C << Best Fit Mapping...Field 1: The Unicode UTF-16 code point for the character being converted.Field 2: The byte or bytes that this code point maps to as a 16-bit value. The high byte is the lead byte, and the low byte is the trail byte. If the high byte is 0, this is a single-byte code point with the value of the low byte and no lead byte is emitted.The following example shows Unicode to byte-mapping records for DBCSs.0x0000 0x0000; Null0x0001 0x0001; Start Of Heading...0x0061 0x0061; a0x0062 0x0062; b0x0063 0x0063; c...0x221e 0x8187; Infinity...0xff41 0x8281; Fullwidth a0xff42 0x8282; Fullwidth b0xff43 0x8283; Fullwidth c...MBTABLE XE "MBTABLE"The MBTABLE tag marks the start of the mapping from single-byte bytes to Unicode UTF-16. It has one field.Field 1: The number of records of single-byte to Unicode mappings.An example of the MBTABLE tag is:MBTABLE 196The Unicode UTF-16 mapping records follow the MBTABLE section. These mapping records have two fields.Field 1: The single byte character of the codepage.Field 2: The Unicode UTF-16 code point that the codepage character maps to.The following example shows mapping records for codepage 932.0x00 0x0000; Null0x01 0x0001; Start Of Heading0x02 0x0002; Start Of Text0x03 0x0003; End Of Text0x04 0x0004; End Of Transmission0x05 0x0005; Enquiry0x06 0x0006; Acknowledge0x07 0x0007; Bell0x08 0x0008; Backspace…0xa1 0xff61; Halfwidth Ideographic Period0xa2 0xff62; Halfwidth Opening Corner Bracket0xa3 0xff63; Halfwidth Closing Corner Bracket0xa4 0xff64; Halfwidth Ideographic Comma0xa5 0xff65; Halfwidth Katakana Middle Dot0xa6 0xff66; Halfwidth Katakana Wo0xa7 0xff67; Halfwidth Katakana Small A0xa8 0xff68; Halfwidth Katakana Small I0xa9 0xff69; Halfwidth Katakana Small U0xaa 0xff6a; Halfwidth Katakana Small E0xab 0xff6b; Halfwidth Katakana Small O0xac 0xff6c; Halfwidth Katakana Small YaDBCSRANGE XE "DBCSRANGE"The DBCSRANGE tag marks the start of the mapping from double-byte bytes to Unicode UTF-16. It has one field.Field 1: The number of records of lead byte ranges.An example of the DBCSRANGE tag is:DBCSRANGE 2The Lead Byte Range records follow the DBCSRANGE section. These mapping records have two fields.Field 1: The start of lead byte range.Field 2: The end of lead byte range.The following example shows one of the Lead Byte Range records for codepage 932. In this codepage, it has one range of lead byte, starting from 0x81 (decimal 129) to 0x9f (decimal 159). So there are 31 lead bytes in this example (159 – 129 + 1). Each lead byte will have a corresponding DBCSRANGE.0x81 0x9f; Lead Byte RangeA group of DBCSTABLE sections follows the lead-byte range record. Each lead byte will have a corresponding DBCSTABLE section. In each DBCSTABLE section, it has one field.Field 1: This field is the number of trail byte mappings for the lead byte.The lead byte of the first DBCSTABLE is the first lead byte of the previous Lead Byte Range record. Each subsequent DBCSTABLE is for the next consecutive lead byte value.The following example shows the first DBCSTABLE for codepage 932. This is for lead byte 0x81.DBCSTABLE 147; LeadByte = 0x81The DBCSTABLE record describes the mappings available for a particular lead byte. The comment is ignored but descriptive.Field 1: This field is the trail byte to map from.Field 2: This field is the Unicode UTF-16 code point that this lead byte/trail byte combination map to.The following example shows DBCSTABLE records for codepage 932 for lead byte 0x81.0x40 0x3000; Ideographic Space0x41 0x3001; Ideographic Comma...Protocol Details XE "Protocol Details:overview" The following sections specify details of the Windows Protocols Unicode Reference, including abstract data models and message processing rules.Client DetailsAbstract Data Model XE "Client:data model" XE "Data model - client" XE "Abstract data model - client"This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with what is described in this document.No abstract data model is needed.Timers XE "Client:timers" XE "Timers - client"None.Initialization XE "Client:initialization" XE "Initialization - client"None.Higher-Layer Triggered Events XE "Triggered events - higher-layer - client" XE "Higher-layer triggered events - client" XE "Client:higher-layer triggered events"None.Message Processing Events and Sequencing RulesMapping Between UTF-16 Strings and Legacy CodepagesMapping Between UTF-16 Strings and Legacy Codepages Using CodePage Data File XE "UTF-16 string:mapping between legacy codepages and:using codepage data file" XE "Mapping between UTF-16 strings and legacy codepages:using codepage data file"This process maps between a Unicode string that is encoded in UTF-16 and a string in a specified codepage by using a codepage data file specified in 2.2.2.1.Pseudocode for Accessing a Record in the Codepage Data File XE "UTF-16 string:pseudocode for accessing record in codepage data file" XE "Pseudocode:accessing record in codepage data file"This section contains the pseudocode that is used to read information from the codepage file. The following example is taken from codepage data file 950.txt.OPEN SECTION indicates that queries for records in a specific section are made. To open the following section with the WCTABLE label, the following syntax is used. The OPEN SECTION is accessible by using the WideCharMapping name.OPEN SECTION WideCharMapping where section name is WCTABLE from bestfit950.txtSELECT RECORD assigns a line from the data file to be referenced by the assigned variable name. For example, the following code selects a record from the WideCharMapping section, and the record is accessible by using the MappingData name.SET UnicodeChar to 0x4e00SELECT RECORD MappingData from WideCharMapping where field 1 matches UnicodeCharThe following example selects the line.0x4e00 0xa440Values from selected records are referenced by field number. The following example selects the individual data fields from the selected row.SET MultiByteResult to MappingData.Field2In this example, the value of MultiByteResult is the hexadecimal value 0xa440.CODEPAGE 950 ; Chinese (Taiwan, Hong Kong SAR) - ANSI, OEMCPINFO 2 0x3f 0x003f ; DBCS CP, Default Char = Question Mark...WCTABLE 203210x0000 0x0000; Null 0x0001 0x0001; Start Of Heading 0x0002 0x0002; Start Of Text 0x0003 0x0003; End Of Text 0x0004 0x0004; End Of Transmission 0x0005 0x0005; Enquiry...0x4e00 0xa4400x4e01 0xa4420x4e03 0xa4430x4e07 0xc94Pseudocode for Mapping a UTF-16 String to a Codepage String XE "UTF-16 string:pseudocode for mapping to legacy codepage" XE "Pseudocode:legacy codepage - mapping UTF-16 string to codepage string"COMMENT This algorithm maps a Unicode string encoded in UTF-16 to a string in the specified ANSI codepage. The supported ANSI codepages are limited to those that can be set as system codepage. It requires the following externally specified values:1) CodePage: An integer value to represent an ANSI codepage value. If CodePage value is CP_ACP (0), the system default ANSI codepage from the OS should be used. If CodePage value is CP_OEMCP (1), the sysstem default OEM codepage from the OS should be used.2) UnicodeString: A string encoded in UTF-16. Every Unicode code point is an unsigned 16-bit ("WORD") value. A surrogate pair is not supported in this algorithm.3) UnicodeStringLength: The string length in 16-bit ("WORD") unit for UnicodeString. When UnicodeStringLength is 0, the length is decided by counting from the beginning of the string to a NULL character (Unicode value U+0000), including the null character.4) MultiByteString: A string encoded in ANSI codepage. Every character can be an 8-bit (byte) unsigned value or two 8-bit unsigned values.5) MultiByteStringLength: The length in bytes. This should include the byte for NULL terminator. When MultiByteStringLength is 0, the MultiByteString value will not be used in this algorithm. Instead, the length of the result string in ANSI codepage will be returned.6) lpDefaultChar Optional. Point to the byte to use if a character cannot be represented in the specified codepage. The application sets this parameter to NULL if the function is to use a system default value. The common default value is 0x3f, which is the ASCII value for the question mark.PROCEDURE WideCharToMultiByteFromCodepageDataFileIF CodePage is CP_ACP THEN COMMENT Windows operating system keeps a systemwide value of default ANSI system codepage. It is used to provide a default COMMENT system codepage to be used by legacy ANSI application. SET CodePage to the default ANSI system codepage from the Windows operating system.ELSE IF CodePage is CP_OEMCP THEN COMMENT Windows keeps a systemwide value of default OEM system codepage. It is used to provide a default COMMENT system codepage to be used by legacy console application. SET CodePage to the default OEM system codepage from Windows. ENDIFIF UnicodeStringLength is 0 THEN COMPUTE UnicodeStringLength as the string length in 16-bit units of UnicodeString as a NULL-terminated string, including NULL terminator.ENDIFIF MultiByteStringLength is 0 THEN SET IsCountingOnly to TrueELSE SET IsCountingOnly to FalseENDIFSET ResultMultiByteLength to 0SET CodePageFileName to the concatenation of strings "Bestfit", CodePage as a string, and ".txt"IF lpDefaultChar is null THEN COMMENT No default char is specified by the caller. Read the default COMMENT char from CPINFO in the data file OPEN SECTION CharacterInfo where section name is CPINFO from file with the name of CodePageFileName SET lpDefaultChar to CharacterInfo.Field3ENDIFOPEN SECTION WideCharMapping where section name is WCTABLE from file with the name of CodePageFileNameFOR each Unicode codepoint UnicodeChar in UnicodeString SELECT MappingData from WideCharMapping where field 1 matches UnicodeChar IF MappingData is null THEN COMMENT There is no mapping for this Unicode character, use COMMENT the default character IF IsCountingOnly is False THEN SET MultiByteString[ResultMultiByteLength] to lpDefaultChar ENDIF INCREMENT ResultMultiByteLength CONTINUE FOR loop ENDIF SET MultiByteResult to MappingData.Field2 IF MultiByteResult is less than 256 THEN COMMENT This is a single byte result IF IsCountingOnly is True THEN INCREMENT ResultMultiByteLength ELSE SET MultiByteString[ResultMultiByteLength] to MultiByteResult INCREMENT ResultMultiByteLength ENDIF ELSE COMMENT This is a double byte result IF IsCountingOnly is True THEN COMPUTE ResultMultiByteLength as ResultMultiByteLength added by 2 ELSE SET MultiByteString[ResultMultiByteLength] to MultiByteResult divided by 256 INCREMENT ResultMultiByteLength SET MultiByteString[ResultMultiByteLength] to the remainder of MultiByteResult divided by 256 INCREMENT ResultMultiByteLength ENDIF ENDIFEND FORRETURN ResultMultiByteLength as a 32-bit unsigned integerPseudocode for Mapping a Codepage String to a UTF-16 String XE "UTF-16 string:pseudocode for mapping legacy codepage to" XE "Pseudocode:legacy codepage - mapping codepage string to UTF-16 string"COMMENT This algorithm maps a Unicode string encoded in the specified codepage to UTF-16. It requires the following externally specified values:1) CodePage: An integer value to represent an ANSI codepage value. If CodePage value is CP_ACP (0), the system default ANSI codepage from the OS should be used. If CodePage value is CP_OEMCP (1), the system default OEM codepage from the OS should be used2) MultiByteString: A string encoded in ANSI codepage. Every character can be an 8-bit (byte) unsigned value or two 8-bit unsigned values.3) MultiByteStringLength: The length in bytes. This should include the byte for terminating null character. When MultiByteStringLength is 0, the length is decided by counting from the beginning of the string to a null character (0x00), including the null character.4) UnicodeString: A string encoded in UTF-16. Every Unicode code point is an unsigned 16-bit ("WORD") value. Surrogate pair is not supported in this algorithm.5) UnicodeStringLength: The string length in 16-bit ("WORD") unit for UnicodeString. When UnicodeStringLength is 0, the UnicodeString value will not be used in this algorithm. Instead, the length of the result string in UTF-16 will be returned.PROCEDURE MultiByteToWideCharFromCodepageDataFileIF CodePage is CP_ACP THEN COMMENT Windows keeps a systemwide value of default ANSI system codepage. It is used to provide a default COMMENT system codepage to be used by legacy ANSI application. SET CodePage to the default ANSI system codepage from Windows. ELSE IF CodePage is CP_OEMCP THEN COMMENT Windows keeps a systemwide value of default OEM system codepage. It is used to provide a default COMMENT system codepage to be used by legacy console application. SET CodePage to the default OEM system codepage from Windows. ENDIFIF MultiByteStringLength is 0 THEN COMPUTE UnicodeStringLength as the string length in 8-bit units of MultiByteString as a null-terminated string, including terminating null character.ENDIFIF UnicodeStringLength is 0 THEN SET IsCountingOnly to TrueELSE SET IsCountingOnly to FalseENDIFSET CodePageFileName to the concatenation of CodePage as a string, and ".txt"OPEN SECTION CodePageInfo where section name is CPINFO from file with the name of CodePageFileNameCOMMENT Read the codepage MENT The value for Single Byte Code Page (SBCS) is 1COMMENT The value for Double Byte Code Page (DBCS) is 2SET CodePageType to CodePageInfo.Field1SET DefaultUnicodeChar to CodePageInfo.Field3OPEN SECTION SingleByteMapping where section name is MBTABLE from file with the name of CodePageFileNameSET MultiByteIndex = 0WHILE MultiByteIndex <= to MultiByteStringLength - 1 SET MultiByteChar = MultiByteString[MultiByteIndex] IF CodePageType is 1 THEN COMMENT SBCS codepage COMMENT Select a record which contains the mapping data SELECT MappingData from SingleByteMapping where field 1 matches MultiByteChar IF MappingData is null THEN COMMENT There is no mapping for this single-byte character, use COMMENT the default character IF IsCountingOnly is False THEN SET MultiByteString[ResultUnicodeLength] to DefaultUnicodeChar ENDIF INCREMENT ResultMultiByteLength INCREMENT MultiByteIndex CONTINUE WHILE loop ENDIF IF IsCountOnly is False THEN SET UnicodeString[ResultUnicodeLength] to MappingData.Field2 ENDIF INCREMENT ResultUnicodeLength ELSE COMMENT DBCS codepage COMMENT First, try if this is a single-byte mapping SELECT MappingData from SingleByteMapping where field 1 matches MultiByteChar IF MappingData is not null THEN COMMENT This byte is a single-byte character IF IsCountOnly is False THEN SET UnicodeString[ResultUnicodeLength] to MappingData.Field2 ENDIF INCREMENT ResultUnicodeLength ELSE COMMENT Not a single-byte character COMMENT Check if this is a valid lead byte for double byte mapping OPEN SECTION DBCSRanges where section name is DBCSRANGE from file with the name of CodePageFileName COMMENT Read the count of DBCS Range count SET DBCSRangeCount to DBCSRanges.Field1 SET ValidDBCS to False COMMENT Enumerate through every DBCSRange record to see if COMMENT the MultiByteChar is a leading byte FOR Counter i = 1 to DBCSRangeCount COMMENT Select the current record SELECT DBCSRangeRecord from DBCSRanges SET LeadByteStart to DBCSRangeRecord.Field1 SET LeadByteEnd to DBCSRangeRecord.Field2 IF MultiByteChar is larger or equal to LeadByteStart AND MultiByteChar is less or equal to LeadByteEnd THEN COMMENT This is a valid lead byte COMMENT Now check if there is a following valid trailing byte SET LeadByteTableCount = MultiByteChar – LeadByteStart COMMENT Select the current DBCSTABLE section OPEN SECTION DBCSTableSection from DBCSRanges where section name is DBCSTABLE COMMMENT Advance to the right DBCSTABLE section FOR LeadByteIndex = 0 to LeadByteTableCount ADVANCE SECTION DBCSTableSection NEXTFOR COMMENT Check if the trailing byte is valid IF MultiByteIndex + 1 is less than MultiByteStringLength THEN SET TrailByteChar to MultiByteString[MultiByteIndex + 1] SELECT MappingData FROM DBCSTABLE Where field 1 matches TrailgByteChar IF MappingData is not null THEN COMMENT Valid trailing byte SET ValidDBCS to True IF IsCountingOnly is FALSE THEN SET UnicodeString[ResultUnicodeLength] to MappingData.Field2 ENDIF INCREMENT ResultUnicodeLength COMMENT Increment the MultiByteIndex. COMMENT Note that the MultiByteIndex will COMMENT be incremented again for the WHILE loop INCREMENT MultiByteIndex EXIT FOR loop ENDIF ENDIF ENDIF COMMENT No valid lead byte is found. Advance to next record ADVANCE DBCSRangeRecord NEXTFOR IF ValidDBCS is FALSE THEN COMMENT There is no valid leading byte/trailing byte sequence If IsCountingOnly is FALSE THEN SET UnicodeString[ResultUnicodeLength] to DefaultUnicodeChar ENDIF INCREMENT MultiByteIndex INCREMENT ResultUnicodeLength ENDIF ENDIF ENDIF INCREMENT MultiByteIndexENDWHILERETURN ResultMultiByteLength as a 32-bit unsigned integerMapping Between UTF-16 Strings and ISO 2022-Based Codepages XE "UTF-16 string:mapping between legacy codepages and:mapping between UTF-16 strings and ISO 2022-based codepages" XE "Mapping between UTF-16 strings and legacy codepages:ISO 2022-based codepages"[ECMA-035] defines the standard that is fully identical with International Standard ISO/IEC 2022:1994. EUC (Extended Unix Code) is based on ISO-2022 standard.For more information, see [ECMA-035].Mapping between UTF-16 Strings and GB 18030 Codepage XE "UTF-16 string:mapping between legacy codepages and:mapping between UTF-16 strings and GB 18031 codepage" XE "Mapping between UTF-16 strings and legacy codepages:GB 18031 codepage"Windows implements GB-18030 based on [GB18030].For more information, please see [GB18030].Mapping Between UTF-16 Strings and ISCII Codepage XE "UTF-16 string:mapping between legacy codepages and:mapping between UTF-16 strings and ISCII codepage" XE "Mapping between UTF-16 strings and legacy codepages:ISCII codepage"Windows implements ISCII-based codepage based on [ISCII].For more information, see [ISCII].Mapping Between UTF-16 Strings and UTF-7 XE "UTF-16 string:mapping between legacy codepages and:mapping between UTF-16 strings and UTF-7 codepage" XE "Mapping between UTF-16 strings and legacy codepages:UTF-7 codepage"Windows implements UTF-7 codepage based on [RFC2152].For more information, see [RFC2152].Mapping Between UTF-16 Strings and UTF-8 XE "UTF-16 string:mapping between legacy codepages and:mapping between UTF-16 strings and UTF-8 codepage" XE "Mapping between UTF-16 strings and legacy codepages:UTF-8 codepage"Windows implements UTF-8 codepage based on [UNICODE5.0.0/CH3].For more information, see [UNICODE5.0.0/CH3].Comparing UTF-16 Strings by Using Sort Keys XE "UTF-16 string:sort keys for comparing"To compare strings, a sort key is required for each string. A binary comparison of the sort keys can then be used to arrange the strings in any order.Pseudocode for Comparing UTF-16 Strings XE "UTF-16 string:pseudocode for comparing"This algorithm compares two UTF-16 strings by using linguistically appropriate rules.This algorithm compares two Unicode strings using linguisticappropriate rules. It requires the following externally specifiedvalues: 1) StringA: A string encoded in UTF-16 2) StringB: A string encoded in UTF-16CALL GetWindowsSortKey WITH StringA RETURNING SortKeyACALL GetWindowsSortKey WITH StringB RETURNING SortKeyBCALL CompareSortKeys WITH SortKeyA, SortKeyB RETURNING ResultIF Result is "SortKeyA is equal to SortKeyB" THEN StringA is considered equal to StringBELSE IF Result is "SortKeyA is less than SortKeyB" THEN StringA is sorted prior to StringBELSE StringA is sorted after StringBENDIFCompareSortKey XE "UTF-16 string:CompareSortKey"This algorithm generates sort keys for two strings and uses the sort keys to provide a linguistically appropriate string MENT CompareSortKeysCOMMENT On Entry: SortKeyA - An array of bytes returned fromCOMMENT GetWindowsSortKeyCOMMENT SortKeyB - An array of bytes returned fromCOMMENT GetWindowsSortKeyCOMMENTCOMMENT On Exit: Result - A value indicating if SortKeyACOMMENT is less than, equal to, or greaterCOMMENT than SortKeyBPROCEDURE CompareSortKeysSET index to 0WHILE index is less than Length(SortKeyA) and index is also less than Length(SortKeyB) IF SortKeyA[index] is less than SortKeyB[index] THEN SET Result to "SortKeyA is less than SortKeyB" RETURN ENDIF IF SortKeyA[index] is greater than SortKeyB[index] THEN SET Result to "SortKeyA is greater than SortKeyB" RETURN ENDIFINCREMENT indexENDWHILEIF Length(SortKeyA) is equal to Length(SortKeyB) THEN SET Result to "SortKeyA is equal to SortKeyB"ELSE IF Length(SortKeyA) is less than Length(SortKeyB) THEN SET Result to "SortKeyA is less than SortKeyB"ELSE assert Length(SortKeyA) must be greater than Length(SortKeyB) SET Result to "SortKeyA is greater than SortKeyB"ENDIFRETURNAny sorting mechanism can be used to arrange these strings by comparing their sort keys.Accessing the Windows Sorting Weight Table XE "UTF-16 string:accessing Windows sorting weight table"Windows gets its sorting data from a data table (see section 3.1.5.2.3.1). Code points are labeled by using UTF-16 values. The file is arranged in sections of tab-delimited field records. Optional comments begin with a semicolon. Each section contains a label and can have a subsection label. HYPERLINK \l "Appendix_A_1" \h <1>Note that labels are any field that does not begin with a numerical (0xNNNN) value. Blank lines and characters that follow a ";" are ignored.This document uses the following notation to specify the processing of the file.OPEN indicates that queries are made for records in a specific section. To open the preceding section with the SORTKEY label and DEFAULT sublabel, the following syntax is used. The OPEN SECTION is accessible by using the DefaultTable name.OPEN SECTION DefaultTable where name is SORTKEY\DEFAULT from unisort.txtSELECT assigns a line from the data file to be referenced by the assigned variable name. To select the highlighted row preceding, this document uses this notation. The selected row is accessible by using the name CharacterRow.SET UnicodeChar to 0x0041SELECT RECORD CharacterRow FROM DefaultTable WHERE field 1 matches UnicodeCharValues from selected records are referenced by field number. The following pseudo code selects the individual data fields from the selected row.SET CharacterWeight.ScriptMember to CharacterRow.Field2SET CharacterWeight.PrimaryWeight to CharacterRow.Field3SET CharacterWeight.DiacriticWeight to CharacterRow.Field4SET CharacterWeight.CaseWeight to CharacterRow.Field5To select the record for characters 0x0043 and 0x0068 with LCID 0x0405, the following notation is used. HYPERLINK \l "Appendix_A_2" \h <2>SET Character1 to 0x0043SET Character2 to 0x0068SET SortLocale to 0x0405OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\TWO from unisort.txtSELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches Character1 and field 2 matches Character2SET CharacterWeight.ScriptMember to ContractionRow.Field3SET CharacterWeight.PrimaryWeight to ContractionRow.Field4SET CharacterWeight.DiacriticWeight to ContractionRow.Field5SET CharacterWeight.CaseWeight to ContractionRow.Field6Windows Sorting Weight Table XE "Sorting weight table" XE "Windows sorting weight table"This section contains links to detailed character weight specifications that permit consistent sorting and comparison of Unicode strings. The data is not used by itself but is used as one of the inputs to the comparison algorithm. The layout and format of data in this file is also specified there.Windows NT 4.0 operating system through Windows Server 2003 operating system [MSDN-SWT/W2K3]Windows Vista operating system [MSDN-SWT/Vista]Windows Server 2008 operating system [MSDN-SWT/W2K8]Windows 7 operating system and Windows Server 2008 R2 operating system [MSDN-SWT/Win7]Windows 8 operating system and Windows Server 2012 operating system [MSDN-SWT/Win8]GetWindowsSortKey Pseudocode XE "UTF-16 string:GetWindowsSortKey pseudocode"This algorithm specifies the generation of sort keys for a specific UTF-16 string.STRUCTURE CharacterWeightType( ScriptMember: 8 bit integer PrimaryWeight: 8 bit integer DiacriticWeight: 8 bit integer CaseWeight: 8 bit integer)STRUCTURE UnicodeWeightType( ScriptMember: 8 bit integer PrimaryWeight: 8 bit integer ThirdByteWeight: 8 bit integer)STRUCTURE SpecialWeightType( Position: 16 bit integer ScriptMember: 8 bit integer PrimaryWeight: 8 bit integer)STRUCTURE ExtraWeightType( W6: 8 bit integer W7: 8 bit integer)SET constant LCID_KOREAN to 0x0412SET constant LCID_KOREAN_UNICODE_SORT to 0x010412SET constant LCID_HUNGARIAN to 0x040eSET constant SORTKEY_SEPARATOR to 0x01SET constant SORTKEY_TERMINATOR to 0x00SET global KoreanScriptMap to InitKoreanScriptMap//// Script Member Values.//SET constant UNSORTABLE to 0SET constant NONSPACE_MARK to 1SET constant EXPANSION to 2SET constant EASTASIA_SPECIAL to 3SET constant JAMO_SPECIAL to 4SET constant EXTENSION_A to 5SET constant PUNCTUATION to 6SET constant SYMBOL_1 to 7SET constant SYMBOL_2 to 8SET constant SYMBOL_3 to 9SET constant SYMBOL_4 to 10SET constant SYMBOL_5 to 11SET constant SYMBOL_6 to 12SET constant DIGIT to 13SET constant LATIN to 14SET constant KANA to 34SET constant IDEOGRAPH to 128IF Windows version is Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 THENSET constant MAX_SPECIAL_CASE to SYMBOL_6ELSESET constant MAX_SPECIAL_CASE to SYMBOL_5ENDIF COMMENT Set the constant for fhe first script member of the Unicode COMMENT Private Use Area (PUA) range SET constant PUA3BYTESTART to 0xA9 COMMENT Set the constant for the last script member of the Unicode COMMENT Private Use Area (PUA) range SET constant PUA3BYTEEND to 0xAF COMMENT Set the constant for the first script member of CJK COMMENT(Chinese/Japanese/Korean) 3 byte weight range SET constant CJK3BYTESTART to 0xC0 COMMMENT Set the constant for the last script member of CJK COMMENT (Chinese/Japanese/Korean) 3 byte weight range SET constant CJK3BYTEEND to 0xEFENDIFSET constant FIRST_SCRIPT to LATINSET constant MAX_SCRIPTS to 256//// Values for CJK Unified Ideographs Extension A range.// 0x3400 thru 0x4dbf//SET constant SCRIPT_MEMBER_EXT_A to 254 // SM for Extension ASET constant PRIMARY_WEIGHT_EXT_A to 255 // AW for Extension A//// Lowest weight values.// Used to remove trailing DW and CW values.// Also used to keep illegal values out of sort keys.//SET constant MIN_DW to 2SET constant MIN_DW to 2//// Bit mask values.//// Case Weight (CW) - 8 bits:// bit 0 => width// bit 1,2 => small kana, sei-on// bit 3,4 => upper/lower case// bit 5 => kana// bit 6,7 => contraction// SET constant CONTRACTION_8_MASK to 0xc0 SET constant CONTRACTION_7_MASK to 0xc0 SET constant CONTRACTION_6_MASK to 0xc0 SET constant CONTRACTION_5_MASK to 0x80 SET constant CONTRACTION_4_MASK to 0x80 SET constant CONTRACTION_3_MASK to 0x40 SET constant CONTRACTION_2_MASK to 0x40 SET constant CONTRACTION_MASK to 0xc0ELSE COMMENT Otherwise, only 2-character or 3-character contractions are supported.SET constant CONTRACTION_3_MASK to 0xc0 // Bit-mask to check 2 character contraction or 3 //character contractionSET constant CONTRACTION_2_MASK to 0x80 // Bit-mask to check 2 character contractionENDIFSET constant CASE_UPPER_MASK to 0xe7 // zero out case bitsSET constant CASE_KANA_MASK to 0xdf // zero out kana bitSET constant CASE_WIDTH_MASK to 0xfe // zero out width bit//// Masks to isolate the various bits in the case weight.//// NOTE: Bit 2 must always equal 1 to avoid getting// a byte value of either 0 or 1.//SET constant CASE_EXTRA_WEIGHT_MASK to 0xc4SET constant ISOLATE_KANA to (~CASE_KANA_MASK) | CASE_EXTRA_WEIGHT_MASKSET constant ISOLATE_WIDTH to (~CASE_WIDTH_MASK) | CASE_EXTRA_WEIGHT_MASK//// Values for East Asia special case primary weights.//SET constant PW_REPEAT to 0SET constant PW_CHO_ON to 1SET constant MAX_SPECIAL_PW to PW_CHO_ON//// Values for weight 5 - East Asia Extra Weights.//SET constant WT_FIVE_KANA to 3SET constant WT_FIVE_REPEAT to 4SET constant WT_FIVE_CHO_ON to 5//// PW Mask for Cho-On:// Leaves bit 7 on in PW, so it becomes Repeat// if it follows Kana N.//SET constant CHO_ON_PW_MASK to 0x87//// Special weight values//SET constant MAP_INVALID_WEIGHT to 0xff//// Some Significant Values for Korean Jamo.// The L, V & T syllables in the 0x1100 Unicode range// can be composed to characters in the 0xac00 range.// See The Unicode Standard for details.//SET constant NLS_CHAR_FIRST_JAMO to 0x1100 // Begin Jamo rangeSET constant NLS_CHAR_LAST_JAMO to 0x11f9 // End Jamo rangeSET constant NLS_CHAR_FIRST_VOWEL_JAMO to 0x1160 // First Vowel JamoSET constant NLS_CHAR_FIRST_TRAILING_JAMO to 0x11a8 // First Trailing JamoSET constant NLS_JAMO_VOWEL_COUNT to 21 // Number of vowel Jamo (V)SET constant NLS_JAMO_TRAILING_COUNT to 28 // Number of trailing Jamo (L)SET constant NLS_HANGUL_FIRST_COMPOSED to 0xac00 // Begin composed range//// Values for Unicode Weight extra weights (e.g. Jamo (old Hangul)).// The following uses SM for extra UW weights.//SET constant ScriptMember_Extra_UnicodeWeight to 255// Leading Weight / Vowel Weight / Trailing Weight// according to the current Jamo class.//STRUCTURE JamoSortInfoType( // true for an old Hangul sequence OldHangulFlag : Boolean // true if U+1160 (Hangul Jungseong Filler) used FillerUsed : Boolean // index to the prior modern Hangul syllable (L) LeadingIndex : 8 bit integer // index to the prior modern Hangul syllable (V) VowelIndex : 8 bit integer // index to the prior modern Hangul syllable (T) TrailingIndex : 8 bit integer // Weight to offset from other old hangul (L) LeadingWeight : 8 bit integer // Weight to offset from other old hangul (V) VowelWeight : 8 bit integer // Weight to offset from other old hangul (T) TrailingWeight : 8 bit integer)// This is the raw data record type from the data tableSTRUCTURE JamoStateDataType( // true for an old Hangul sequence OldHangulFlag : Boolean // index to the prior modern Hangul syllable (L) LeadingIndex : 8 bit integer // index to the prior modern Hangul syllable (V) VowelIndex : 8 bit integer // index to the prior modern Hangul syllable (T) TrailingIndex : 8 bit integer // weight to distinguish from old Hangul ExtraWeight : 8 bit integer // number of additional records in this state TransitionCount : 8 bit integer // Current record in unisort.txt Jamo table: JamoRecord : data record // SORTTABLES\JAMOSORT\[Character] section )COMMENT GetWindowsSortKeyCOMMENTCOMMENT On Entry: SourceString - Unicode String to compute aCOMMENT sort key forCOMMENT SortLocale - Locale to determine correct COMMENT linguistic sortCOMMENT Flags - Bit Flag to control behaviorCOMMENT of sort key generation. COMMENT COMMENT NORM_IGNORENONSPACE Ignore diacritic weightCOMMENT NORM_IGNORECASE: Ignore case weightCOMMENT NORM_IGNOREKANATYPE: Ignore Japanese Katakana/HiragaCOMMENT differenceCOMMENT NORM_IGNOREWIDTH: Ignore Chinese/Japanese/KoreanCOMMENT half-width and full-width MENTCOMMENT On Exit: SortKey - Byte array containing theCOMMENT computed sort MENTPROCEDURE GetWindowsSortKey(IN SourceString : Unicode String, IN SortLocale : LCID, IN Flags : 32 bit integer, OUT SortKey : BYTE String)COMMENT Compute flags for sort conditionsCOMMENT Based on the case/kana/width flags,COMMENT turn off bits in case mask when comparing case weight.SET CaseMask to 0xffIf (NORM_IGNORECASE bit is on in Flags) THEN SET CaseMask to CaseMask LOGICAL AND with CASE_UPPER_MASKENDIFIf (NORM_IGNOREKANATYPE bit is on in Flags) THEN SET CaseMask to CaseMask LOGICAL AND with CASE_KANA_MASKENDIFIf (NORM_IGNOREWIDTH bit is on in Flags) THEN SET CaseMask to CaseMask LOGICAL AND with CASE_WIDTH_MASKENDIFCOMMENT Windows 7 and Windows Server 2008 R2 use 3-byte (instead of 2-byte) sequence for COMMENT Unicode WeightsCOMMENT for Private Use Area (PUA) and some Chinese/Japanese/Korean (CJK) script MENT Does this sort have a 3-byte Unicode Weight (CJK sorts)?IF Windows version is Windows 7 and Windows Server 2008 R2 THEN COMMENT Check if the locale can have 3-byte Unicode weight SET Is3ByteWeightLocale to CALL Check3ByteWeightLocale(SortLocale)ENDIFIF Windows version is Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 THEN COMMENT For Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, COMMENT the algorithm COMMENT does not remap the script for Korean locale SET IsKoreanLocale to falseELSE IF SortLocale is LCID_KOREAN or SortLocale is LCID_KOREAN_UNICODE_SORT THEN SET IsKoreanLocale to true IF KoreanScriptMap is null THEN CALL InitKoreanScriptMap ELSE SET IsKoreanLocale to false ENDIFENDIF//// Allocate buffer to hold different levels of sort key weights.// UnicodeWeights/ExtraWeights/SpecialWeights will be eventually// to be collected together, in that order, into the returned// Sortkey byte string.//// Maximum expansion size is 3 times the input size//// Unicode Weight => 4 word (16 bit) length// (extension A and Jamo need extra words)SET UnicodeWeights to new empty string of UnicodeWeightTypeSET DiacriticWeights to new empty string of BYTESET CaseWeights to new empty string of BYTE// Extra Weight=>4 byte length (4 weights, 1 byte each) FE SpecialSET ExtraWeights to new empty string of ExtraWeightType// Special Weight => dword length (2 words each of 16 bits)SET SpecialWeights to new empty string of SpecialWeightType//// Go through the string, code point by code point,// testing for contractions and Hungarian special character sequence//// loop presumes 0 based index for source stringFOR SourceIndex is 0 to Length(SourceString) -1 // // Get weights // CharacterWeight will contain all of the weight information // for the character tested. // SET CharacterWeight to CALL GetCharacterWeights WITH (SortLocale, SourceString[SourceIndex]) SET ScriptMember to CharacterWeight.ScriptMember // Special case weights have script members less than // MAX_SPECIAL_CASE (11) IF ScriptMember is greater than MAX_SPECIAL_CASE THEN // // No special case on character, but must check for // contraction characters and Hungarian special character sequence // characters. // SET HasHungarianSpecialCharacterSequence to CALL TestHungarianCharacterSequences WITH (SortLocale, SourceString, SourceIndex) SET Result to CALL GetContractionType WITH (CharacterWeight) CASE Result OF "3-character Contraction": COMMENT This is only possible for Windows versions that are Windows NT 4.0 COMMENT through Windows Server 2003 Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 3, UnicodeWeights, DiacriticWieghts, CaseWeights) IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ENDIF IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ENDIF COMMENT If no contraction is found, fall through into the additional cases. FALLTHROUGH "2-character Contraction": COMMENT This is only possible for Windows versions that are Windows NT 4.0 COMMENT through Windows Server 2003 Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 2, UnicodeWeights, DiacriticWieghts, CaseWeights) IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ENDIF COMMENT If no contraction is found, fall through into the OTHER case. COMMENT Since "3-character contraction" or "2-character contraction" are the COMMENT only two possible values for COMMENT Windows NT 4.0 through Windows Server 2003, all calls to COMMENT SortkeyContractionHandler will return false. COMMENT So, the fallthrough will go directly to the OTHERS section FALLTHROUGH "6-character contraction, 7-character contraction, or 8-character contraction": Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 8, UnicodeWeights, DiacriticWieghts, CaseWeights) IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ELSE Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 7, UnicodeWeights, DiacriticWieghts, CaseWeights) ENDIF IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ELSE Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 6, UnicodeWeights, DiacriticWieghts, CaseWeights) ENDIF IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ENDIF COMMENT If no contraction is found, fall through into additional cases. FALLTHROUGH "4-character contraction or 5-character contraction": Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 5, UnicodeWeights, DiacriticWieghts, CaseWeights) IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ELSE Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 4, UnicodeWeights, DiacriticWieghts, CaseWeights) ENDIF IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ENDIF COMMENT If no contraction is found, fall through into additional cases. FALLTHROUGH "2-character contraction or 3-character contraction": Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 3, UnicodeWeights, DiacriticWieghts, CaseWeights) IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ELSE Set ContractionFound to CALL SortkeyContractionHandler WITH (SortLocale, SourceString, SourceIndex, HasHungarianSpecialCharacterSequence, 2, UnicodeWeights, DiacriticWieghts, CaseWeights) ENDIF IF ContractionFound is true THEN COMMENT Break out of the case statement BREAK ENDIF COMMENT If no contraction is found, fall through into additional cases. FALLTHROUGH OTHERS : IF Windows version is greater than Windows Server 2008 R2 or Windows 7 THEN COMMENT In Windows Server 2008 R2 or Windows 7, Private Use Area (PUA) code COMMENT points COMMENT and some CJK (Chinese/Japanese/Korean) sorts may need 3 byte COMMENT weights COMMENT Store normal Unicode weight first. Note that there is no COMMENT adjustment of Korean weight anymore. SET UnicodeWeight to CorrectUnicodeWeight(CharacterWeight, FALSE) COMMENT Assume 3-byte Unicode Weight is not used first. The alogorithm will COMMENT check this later. SET UnicodeWeight.ThirdByteWeight to 0 IF (ScriptMember is equal to or greater than PUA3BYTESTART) AND (ScriptMember is less than or equal to PUA3BYTEEND) THEN SET IsScriptMemberPUA3BYTEWeight to true ELSE SET IsScriptMemberPUA3ByteWeight to false ENDIF IF (ScriptMember is equal to or greater than CJK3BYTESTART) AND (ScriptMember is less than or equal to CJK3BYTEEND) THEN SET IsScriptMemberCJK3ByteWeight to true ELSE SET IsScriptMemberCJK3ByteWeight to false ENDIF IF (IsScriptMemberPUA3ByteWeight is true) OR (Is3ByteWeightLocale AND IsScriptMemberCJK3ByteWeight is true) THEN COMMENT PUA code points and some CJK sorts need 3 byte weights SET UnicodeWeight.ThirdByteWeight to CharacterWeight.DiacriticWeight ELSE COMMENT Normal Diacritic Weight APPEND CharacterWeight.DiacriticWeight to DiacriticWeights as a BYTE ENDIF APPEND UnicodeWeight to UnicodeWeights SET CaseWeight to GetCaseWeight(CharacterWeight) APPEND CharacterWeight.CaseWeight to CaseWeights as a BYTE ELSE SET UnicodeWeight to CorrectUnicodeWeight(CharacterWeight, IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights APPEND CharacterWeight.DiacriticWeight to DiacriticWeights as a BYTE SET CaseWeight to GetCaseWeight(CharacterWeight) APPEND CharacterWeight.CaseWeight to CaseWeights as a BYTE ENDIF ENDCASE ELSE CALL SpecialCaseHandler WITH (SourceString, SourceIndex, UnicodeWeights, ExtraWeights, SpecialWeights, SortLocale, IsKoreanLocale) ENDIFENDFOR//// Store the Unicode Weights in the destination buffer.//FOR each UnicodeWeight in UnicodeWeights // // Copy Unicode weight to destination buffer. // APPEND UnicodeWeight.ScriptMember to SortKey as a BYTE APPEND UnicodeWeight.PrimaryWeight to SortKey as a BYTE IF Windows version is greater than Windows Server 2008 R2 or Windows 7 THEN IF UnicodeWeight.ThirdByteWeight is not 0 THEN COMMENT When 3-byte Unicode Weight is used, append the additional BYTE into COMMENT SortKey APPEND UnicodeWeight.ThirdByteWeight to SortKey as a BYTE ENDIF ENDIFENDFOR//// Copy Separator to destination buffer.//APPEND SORTKEY_SEPARATOR to SortKey as a BYTE//// Store Diacritic Weights in the destination buffer.//IF (NORM_IGNORENONSPACE bit is not turned on in Flags) THEN IF (IsReverseDW is TRUE) THEN // // Reverse diacritics: // - remove diacritics from left to right. // - store diacritics from right to left. // FOR each DiacriticWeight in DiacriticWeights in the "first in first out" order IF DiacriticWeight <= MIN_DW THEN REMOVE DiacriticWeight from DiacriticWeights ELSE BREAK from the current FOR loop ENDIF ENDFOR FOR each DiacriticWeight in DiacriticWeights in the "last in first out" order // // Copy Unicode weight to destination buffer. // APPEND DiacriticWeight to SortKey as a BYTE ENDFOR ELSE // // Regular diacritics: // - remove diacritics from right to left. // - store diacritics from left to right. FOR each DiacriticWeight in DiacriticWeights in the "last in first out" order IF DiacriticWeight <= MIN_DW THEN REMOVE DiacriticWeight from DiacriticWeights ELSE BREAK from the current FOR loop ENDIF ENDFOR FOR each DiacriticWeight in DiacriticWeights in the order of "first in first out" // // Copy Unicode weight to destination buffer. // APPEND DiacriticWeight to SortKey as a BYTE ENDFOR ENDIFENDIF//// Copy Separator to destination buffer.//APPEND SORTKEY_SEPARATOR to SortKey as a BYTE//// Store case Weights//// - Eliminate minimum CW.// - Copy case weights to destination buffer.//IF (NORM_IGNORECASE bit is not turned on in Flags OR NORM_IGNOREWIDTH bit is not turned on in Flags) THEN FOR each CaseWeight in CaseWeights in the "last in first out" order IF CaseWeight <= MIN_CW THEN REMOVE CaseWeight from CaseWeights ELSE BREAK from the current FOR loop ENDIF ENDFOR FOR each CaseWeight in CaseWeights // // Copy Unicode weight to destination buffer. // APPEND CaseWeight to SortKey as a BYTE ENDFORENDIF//// Copy Separator to destination buffer.//APPEND SORTKEY_SEPARATOR to SortKey as a BYTE//// Store the Extra Weights in the destination buffer for// EAST ASIA Special.//// - Eliminate unnecessary XW.// - Copy extra weights to destination buffer.//IF Length(ExtraWeights) is greater than 0 THEN IF (NORM_IGNORENONSPACE bit is turned on in Flag) THEN APPEND 0xff to SortKey as a BYTE APPEND 0x02 to SortKey as a BYTE ENDIF // Append W6 group to SortKey // Trim unused values from the end of the string SET EndExtraWeight to Length(ExtraWeights) - 1 WHILE EndExtraWeight greater than 0 and ExtraWeightSeparator[EndExtraWeight].W6 == 0xe4 DECREMENT EndExtraWeight ENDWHILE SET ExtraWeightIndex to 0 WHILE ExtraWeightIndex is less than or equal to EndExtraWeight APPEND ExtraWeightSeparator[ExtraWeightIndex].W6 to SortKey as a BYTE INCREMENT ExtraWeightIndex ENDWHILE // Append W6 separator APPEND 0xff to SortKey as a BYTE // Append W7 group to SortKey // Trim unused values from the end of the string SET EndExtraWeight to Length(ExtraWeights) - 1 WHILE EndExtraWeight greater than 0 and ExtraWeightSeparator[EndExtraWeight].W7 == 0xe4 DECREMENT EndExtraWeight ENDWHILE SET ExtraWeightIndex to 0 WHILE ExtraWeightIndex is less than or equal to EndExtraWeight APPEND ExtraWeightSeparator[ExtraWeightIndex].W7 to SortKey INCREMENT ExtraWeightIndex ENDWHILE // Append W7 separator APPEND 0xff to SortKey as a BYTEENDIF//// Copy Separator to destination buffer.//APPEND SORTKEY_SEPARATOR to SortKey as a BYTE//// Store the Special Weights in the destination buffer.//// - Copy special weights to destination buffer.//FOR each SpecialWeight in SpecialWeights // High byte (most significant) SET Byte1 to SpecialWeight.Position >> 8 // Low byte (least significant) SET Byte2 to SpecialWeight.Position & 0xff APPEND Byte1 to SortKey as a BYTE APPEND Byte2 to SortKey as a BYTE APPEND SpecialWeight.Script to SortKey as a BYTE APPEND SpecialWeight.Weight to SortKey as a BYTEENDFOR//// Copy terminator to destination buffer.//APPEND SORTKEY_TERMINATOR to SortKeyRETURN SortKeyTestHungarianCharacterSequences XE "UTF-16 string:TestHungarianCharacterSequences"This algorithm checks if the specified UTF-16 string has a Hungarian special-character sequence for the specified locale in the specific string index.Hungarian contains special character sequences in which the first character of the string designates a string that is equivalent to the last three characters of the string. For example, the string "ddzs" is actually treated as the string "dzsdzs" for the purposes of generating the sort key. This function checks to see if the specified locale is Hungarian, and it also checks to see if the next two characters starting in the specified index are the same. If so, this indicates that it is a likely Hungarian special-character MENT TestHungarianCharacterSequencesCOMMENTCOMMENT On Entry: SortLocale - Locale to use for linguistic dataCOMMENT SourceString - Unicode String to look for HungarianCOMMENT special character sequence inCOMMENT SourceIndex - Index of character in string toCOMMENT look for start ofCOMMENT Hungarian special character sequenceCOMMENTCOMMENT On Exit: Result - Set to true if a Hungarian specialCOMMENT character sequenceCOMMENT was foundCOMMENT PROCEDURE TestHungarianCharacterSequences(IN SortLocale : LCID, IN SourceString : Unicode String, IN SourceIndex : 32 bit integer, OUT Result : Boolean)// Hungarian special character sequence only happen to Hungarian// Note that this can be found in unisort.txt in the // SORTTABLES\DOUBLECOMPRESSION section, however since// there's only 1 locale just hard code it here.IF SortLocale not equal to LCID_HUNGARIAN) THEN SET Result to false RETURNENDIF// first test to make sure more data is available IF SourceIndex + 1 is greater than or equal to Length(SourceString) THEN SET Result to false RETURNENDIF// CMP_MASKOFF_CW (e7) is not necessary// since it was already masked offSET FirstWeight to CALL GetCharacterWeights WITH (SortLocale, SourceString[SourceIndex])SET SecondWeight to CALL GetCharacterWeights WITH (SortLocale, SourceString[SourceIndex + 1])IF FirstWeight is equal to SecondWeight THEN SET Result to trueELSE SET Result to falseENDIFRETURNGetContractionType XE "UTF-16 string:GetContractionType"This algorithm specifies the checking of the type of contraction based on the character weight. Contraction is defined by [UNICODE-COLLATION] section 3.2.For instance, "ll" acts as a single unit in Spanish so that it comes between l and m. This is a two-character contraction. Similarly, "dzs" acts as a single unit in Hungarian, so it is a three-character contraction.These functions specify if the weights will not be at the beginning of a contraction, the beginning of a two-character contraction, or the beginning of a three-character MENT GetContractionTypeCOMMENTCOMMENT On Entry: CharacterWeight - Weights structure to test forCOMMENT a contractionCOMMENTCOMMENT On Exit: Result - Type of contraction found:COMMENT "No contraction"COMMENT "3-character contraction"COMMENT "2-character contraction"COMMENT The following results are only possible for COMMENT Windows Vista, Windows Server 2008, Windows 7, and COMMENT Windows Server 2008 R2COMMENT "6-character contraction, 7-character contraction or COMMENT 8-character contraction"COMMENT "4-character contraction or 5-character contraction"COMMENT "2-character contraction or 3-character contraction"PROCEDURE GetContractionType(IN CharacterWeight : CharacterWeightType, OUT Result) IF Windows version is Windows NT 4.0 to Windows 2003 THEN CASE CharacterWeight.CaseWeight & CONTRACTION_3_MASK OF CONTRACTION_3_MASK : SET Result = "3-character contraction" CONTRACTION_2_MASK : SET Result = "2-character contraction" OTHERS : SET Result = "No contraction" ENDCASE ELSE COMMENT Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 CASE CharacterWeight.CaseWeight & CONTRACTION_MASK OF CONTRACTION_6_MASK : SET Result = "6-character contraction, 7- character contraction or 8-character contraction" CONTRACTION_4_MASK : SET Result = "4-character contraction or 5- character contraction" CONTRACTION_2_MASK : SET Result = "2-character contraction or 3- character contraction" OTHERS : SET Result = "No contraction" ENDCASE ENDIFRETURNCorrectUnicodeWeight XE "UTF-16 string:CorrectUnicodeWeight"This algorithm specifies the processing of the corrected Unicode weight for the specific character weight, and whether the locale is a Korean MENT CorrectUnicodeWeightCOMMENTCOMMENT On Entry: CharacterWeight - Weights structure to get UnicodeCOMMENT weight ofCOMMENT IsKoreanLocale - True if this locale needsCOMMENT adjustment forCOMMENT Korean mapped scripts MENTCOMMENT On Exit: UnicodeWeight - Corrected Unicode WeightCOMMENTPROCEDURE CorrectUnicodeWeight(IN CharacterWeight : CharacterWeightType, IN IsKoreanLocale : boolean, OUT UnicodeWeight : UnicodeWeightType)SET UnicodeWeight to CALL MakeUnicodeWeight WITH (CharacterWeight.ScriptMember, CharacterWeight.PrimaryWeight, IsKoreanLocale)RETURN UnicodeWeightMakeUnicodeWeight XE "UTF-16 string:MakeUnicodeWeight"This algorithm specifies the generation of the Unicode weight based on the script member, the primary weight, and whether the locale is a Korean MENT MakeUnicodeWeightCOMMENTCOMMENT On Entry: ScriptMember - Script member to use forCOMMENT Unicode weightCOMMENT PrimaryWeight - Primary weight to use for COMMENT Unicode weightCOMMENT IsKoreanLocale - True if this locale needsCOMMENT adjustment for Korean mappedCOMMENT scripts MENTCOMMENT On Exit: UnicodeWeight - Corrected Unicode WeightCOMMENTPROCEDURE MakeUnicodeWeight(IN ScriptMember : 8 bit byte, IN PrimaryWeight : 8 bit byte, IN IsKoreanLocale : boolean, OUT UnicodeWeight : UnicodeWeightType)IF IsKoreanLocale is true THEN SET UnicodeWeight.ScriptMember to KoreanScriptMap[ScriptMember]ELSE SET UnicodeWeight.ScriptMember to ScriptMember ENDIFSET UnicodeWeight.PrimaryWeight to PrimaryWeightRETURN UnicodeWeightGetCharacterWeights XE "UTF-16 string:GetCharacterWeights"This algorithm specifies the retrieval of the character weight based on the specified locale and the specified UTF-16 code MENT GetCharacterWeightsCOMMENTCOMMENT On Entry: SortLocale - Locale to use for linguisticCOMMENT dataCOMMENT SourceCharacter - Unicode Character to returnCOMMENT weight forCOMMENTCOMMENT On Exit: Result - A structure containing theCOMMENT weights for this characterCOMMENTPROCEDURE GetCharacterWeights(IN SortLocale : LCID, IN SourceCharacter : Unicode Character, OUT Result : CharacterWeightType)// Search for the character in the exception tableOPEN SECTION ExceptionTable where name is SORTTABLES\EXCEPTION\LCID[SortLocale] from unisort.txtSELECT RECORD CharacterRow FROM ExceptionTable WHERE field 1 matches SourceCharacterIF CharacterRow is null THEN // Not found, search for the character in the default table OPEN SECTION DefaultTable where name is SORTKEY\DEFAULT from unisort.txt SELECT RECORDCharacterRow from DefaultTable where field 1 matches SourceCharacter IF CharacterRow is null THEN // Not found in default table either, check expansions SET Expansion to GetExpandedCharacters(SourceCharacter) IF Expansion is not null THEN // Has an expansion, set appropriate weights SET Result.ScriptMember to EXPANSION ELSE // No expansion, set appropriate weights SET Result.ScriptMember to UNSORTABLE ENDIF SET Result.PrimaryWeight to 0 SET Result.DiacriticWeight to 0 SET Result.CaseWeight to 0 RETURN Result ENDIFENDIFSET Result.ScriptMember to CharacterRow.Field2SET Result.PrimaryWeight to CharacterRow.Field3SET Result.DiacriticWeight to CharacterRow.Field4SET Result.CaseWeight to CharacterRow.Field5RETURN ResultGetExpansionWeights XE "UTF-16 string:GetExpansionWeights"This algorithm specifies the generation of a character weight for the specified character that has the expansion behavior, as defined in [UNICODE-COLLATION] section 3.MENT GetExpansionWeightsCOMMENTCOMMENT On Entry: SourceCharacter - Character to look upCOMMENT expansions forCOMMENT SortLocale - Locale to get sort weights forCOMMENTCOMMENT On Exit: Weights - String of 2 or 3 weights forCOMMENT this characterCOMMENTPROCEDURE GetExpansionWeights(IN SourceCharacter : Unicode Character, IN SortLocale : LCID, OUT Weights : CharacterWeightType String)SET Weights to new empty string of CharacterWeightTypeSET ExpandedCharacters to CALL GetExpandedCharacters WITH (SourceCharacter)// Append first weightSET Weight to CALL GetCharacterWeights WITH (SortLocale, ExpandedCharacters[0])APPEND Weight to Weights// Get second weight, it may expand againSET Weight to CALL GetCharacterWeights WITH (SortLocale, ExpandedCharacters[1])IF Weight.ScriptMember is EXPANSION THEN // second weight expands again, get new expansion // note that this can only happen once, as it does // with the U=fb03 (ffi ligature) SET ExpandedCharacters to CALL GetExpandedCharacters(ExpandedCharacters[1]) // Append second expansion's first weight SET Weight to CALL GetCharacterWeights WITH (SortLocale, ExpandedCharacters[0]) APPEND Weight to Weights // Get second weight for second expansion, it will not expand again SET Weight to CALL GetCharacterWeights WITH (SortLocale, ExpandedCharacters[1])ENDIF// Finish appending second weight to weights stringAPPEND Weight to WeightsRETURN ResultGetExpandedCharacters XE "UTF-16 string:GetExpandedCharacters"This algorithm specifies the generation of the array of expanded characters, if the specified character can be MENT GetExpandedCharactersCOMMENTCOMMENT On Entry: SourceCharacter - Character to look for inCOMMENT expansion tableCOMMENTCOMMENT On Exit: Result - Array of two unicode charactersCOMMENT for the expansion or null if noCOMMENT expansion foundCOMMENTCOMMENT NOTE: Look for default table characters first, some entriesCOMMENT in the expansion table are only used in exception tablesCOMMENT for some locales (ie: 0x00c4 ?)PROCEDURE GetExpandedCharacters(IN SourceCharacter : Unicode Character, OUT Result : Unicode Character[2])// Search for the expansion in the expansion tableOPEN SECTION ExpansionTable where name is SORTTABLES\EXPANSION from unisort.txtSELECT RECORD ExpansionRow FROM ExceptionTable WHERE field 1 matches SourceCharacterIF ExpansionRow is null THEN SET Result to null RETURN ResultENDIFSET Result[0] to ExpansionRow.Field2SET Result[1] to ExpansionRow.Field3RETURN ResultSortkeyContractionHandler XE "UTF-16 string:SortkeyContractionHandler"This algorithm checks if the next few characters in the specified string and index have an 8-character, 7-character, 6-character, 5-character, 4-character, 3-character, or 2-character contraction sequence. If true, these characters are given just one character weight. This algorithm also handles the Hangiran special character MENT SortkeyContractionHandler COMMENTCOMMENT On Entry: SourceString – Source Unicode StringCOMMENT SourceIndex – Current index within source stringCOMMENT HasHungarianSpecialCharacterSequence: Is the character that the current COMMENT index points toCOMMENT the starting of the Hungarian special character sequenceCOMMENT ContractionType: The contraction type, from 2-character to 8-character COMMENT contraction, to be checked againstCOMMENT UnicodeWeights - String of UnicodeWeightType to COMMENT append additional weight(s) toCOMMENT DiacriticWeights - String of Diacritic Weight to COMMENT append extra weight(s) to if COMMENT neededCOMMENT CaseWeights - String of Case Weight to COMMENT append special weight(s) toCOMMENT if neededCOMMENTCOMMENT On Exit: Result: a string to indicate the type of contraction from the specified COMMENT stringCOMMENT UnicodeWeights - The UnicodeWeight of theCOMMENT processed character(s) is COMMENT appended to this MENT DiacriticWeights - The Diacritic weight, if any, of COMMENT the processed character(s) is COMMENT appended to this MENT CaseWeights - The Case Weight, if any, COMMENT of the processed character(s) COMMENT is appended to this MENTPROCEDUE SortkeyContractionHandler (IN SortLocale: LCID, IN SourceString: Unicode String, IN SourceIndex: 32-bit integer, IN HasHungarianSpecialCharacterSequence: boolean IN ContractionType: integer number from 2 to 8 INOUT UnicodeWeights: string of UnicodeWeightType INOUT DiacriticWeights: string of BYTE INOUT CaseWeights: string of BYTE)Result: CharacterWeightTypeIF HasHungarianSpecialCharacterSequence is true THEN COMMENT The beginning of Hungarian special character sequence, COMMENT advance one character before starting to check for contraciton sequence SET SourceIndex to SourceIndex + 1ENDIFIF SourceIndex + ContractionType is greater than or equal to SourceString.Length THEN SET Result to null RETURN falseENDIFCOMMENT Search for the character in the character contraction tableCOMMENT Search for contraction section based on ContractionTypeCASE ContractionType "8":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\EIGHT from unisort.txt "7":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\SEVEN from unisort.txt "6":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\SIX from unisort.txt "5":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\FIVE from unisort.txt "4":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\FOUR from unisort.txt "3":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\THREE from unisort.txt "2":OPEN SECTION ContractionTable where name is SORTTABLES\COMPRESSION\LCID[SortLocale]\TWO from unisort.txt ENDCASECOMMENT Contraction table may not be found if locale doesn't have themIF ContractionTable is null THEN SET Result to null RETURN falseENDIFCASE ContractionType "8": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] and WHERE field 3 matches SourceString[SourceIndex + 2] and WHERE field 4 matches SourceString[SourceIndex + 3] and WHERE field 5 matches SourceString[SourceIndex + 4] and WHERE field 6 matches SourceString[SourceIndex + 5] and WHERE field 7 matches SourceString[SourceIndex + 6] and WHERE field 8 matches SourceString[SourceIndex + 7] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field9 SET Result.PrimaryWeight to ContractionRow.Field10 SET Result.DiacriticWeight to ContractionRow.Field11 SET Result.CaseWeight to ContractionRow.Field12 "7": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] and WHERE field 3 matches SourceString[SourceIndex + 2] and WHERE field 4 matches SourceString[SourceIndex + 3] and WHERE field 5 matches SourceString[SourceIndex + 4] and WHERE field 6 matches SourceString[SourceIndex + 5] and WHERE field 7 matches SourceString[SourceIndex + 6] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field8 SET Result.PrimaryWeight to ContractionRow.Field9 SET Result.DiacriticWeight to ContractionRow.Field10 SET Result.CaseWeight to ContractionRow.Field11 "6": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] and WHERE field 3 matches SourceString[SourceIndex + 2] and WHERE field 4 matches SourceString[SourceIndex + 3] and WHERE field 5 matches SourceString[SourceIndex + 4] and WHERE field 6 matches SourceString[SourceIndex + 5] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field7 SET Result.PrimaryWeight to ContractionRow.Field8 SET Result.DiacriticWeight to ContractionRow.Field9 SET Result.CaseWeight to ContractionRow.Field10 "5": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] and WHERE field 3 matches SourceString[SourceIndex + 2] and WHERE field 4 matches SourceString[SourceIndex + 3] and WHERE field 5 matches SourceString[SourceIndex + 4] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field6 SET Result.PrimaryWeight to ContractionRow.Field7 SET Result.DiacriticWeight to ContractionRow.Field8 SET Result.CaseWeight to ContractionRow.Field9 "4": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] and WHERE field 3 matches SourceString[SourceIndex + 2] and WHERE field 4 matches SourceString[SourceIndex + 3] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field5 SET Result.PrimaryWeight to ContractionRow.Field6 SET Result.DiacriticWeight to ContractionRow.Field7 SET Result.CaseWeight to ContractionRow.Field8 "3": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] and WHERE field 3 matches SourceString[SourceIndex + 2] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field4 SET Result.PrimaryWeight to ContractionRow.Field5 SET Result.DiacriticWeight to ContractionRow.Field6 SET Result.CaseWeight to ContractionRow.Field7 "2": SELECT RECORD ContractionRow FROM ContractionTable WHERE field 1 matches SourceString[SourceIndex] and WHERE field 2 matches SourceString[SourceIndex + 1] COMMENT If this sequence isn't a contraction then one will not be found IF ContractionRow is null THEN SET Result to null RETURN false ENDIF COMMENT Found a contraction, get its weights SET Result.ScriptMember to ContractionRow.Field3 SET Result.PrimaryWeight to ContractionRow.Field4 SET Result.DiacriticWeight to ContractionRow.Field5 SET Result.CaseWeight to ContractionRow.Field6ENDCASESET UnicodeWeight to CorrectUnicodeWeight(Result, IsKoreanLocale)APPEND UnicodeWeight to UnicodeWeightsAPPEND Result.DiacriticWeight to DiacriticWeights as a BYTEAPPEND Result.CaseWeight to CaseWeights as a BYTECOMMENT Advance the source indexSET SourceIndex to SourceIndex + ContractionTypeRETURN trueCheck3ByteWeightLocale XE "UTF-16 string:Check3ByteWeightLocale"This algorithm checks if the specified locale is a CJK (Chinese/Japanese/Korean) sorting locale that uses third byte in Unicode MENT Check3ByteWeightLocaleCOMMENTCOMMENT On Entry: SortLocale – Locale to use for linguistic sorting dataCOMMENTCOMMENT On Exit: Result: Set to true if the specified locale is a CJK COMMENT (Chinese/Japanese/Korean) locale that uses third byte in Unicode weightCOMMENTSET Result to falseCASE SortLocale "0x0404": // Taiwan (Stroke Count) "0x0804": // China (Pronunciation) "0x0c04": // Hong Kong (Stroke Count) "0x1004": // Singapore (pronunciation) "0x1404": // Macau (pronunciation) "0x20804": // China (Stroke Count) "0x21004": // Singapore (Stroke Count) "0x21404": // Macau (Stroke Count) "0x30404": // Taiwan (Bopomofo) "0x40411": // Japanese (Radical / Stroke) SET Result to trueENDCASERETURN ResultSpecialCaseHandler XE "UTF-16 string:SpecialCaseHandler"This algorithm specifies the special processing that is required based on a different script member MENT SpecialCaseHandlerCOMMENTCOMMENT On Entry: SourceString - Source Unicode StringCOMMENT SourceIndex - Current Index within source COMMENT stringCOMMENT UnicodeWeights - String of UnicodeWeightType to COMMENT append additional weight(s) toCOMMENT ExtraWeights - String of ExtraWeightType to COMMENT append extra weight(s) to if COMMENT neededCOMMENT SpecialWeights - String of SpecialWeightType to COMMENT append special weight(s) toCOMMENT if neededCOMMENT SortLocale - Locale to use for linguistic COMMENT sorting dataCOMMENT IsKoreanLocale - True if this locale needs COMMENT Korean special casing of the COMMENT ScriptMember valueCOMMENT On Exit: SourceIndex - Index of last character COMMENT processed, caller will need to COMMENT loop increment to continue COMMENT Korean Jamo cases can increment COMMENT this beyond its input valueCOMMENT UnicodeWeights - The UnicodeWeight of theCOMMENT processed character(s) is COMMENT appended to this MENT ExtraWeights - The ExtraWeight, if any, of COMMENT the processed character(s) is COMMENT appended to this MENT SpecialWeights - The Special Weight, if any, COMMENT of the processed character(s) COMMENT is appended to this MENTPROCEDURE SpecialCaseHandler (IN SourceString : Unicode StringINOUT SourceIndex : 32 bit integerINOUT UnicodeWeights : UnicodeWeightType String,INOUT ExtraWeights : ExtraWeightType String,INOUT SpecialWeights : SpecialWeightType String,IN SortLocale : LCID,IN IsKoreanLocale : boolean)// Get the weight for the current characterSET CharacterWeights to CALL GetCharacterWeights WITH (SortLocale, SourceString[SourceIndex])CASE CharacterWeight.ScriptMember OF UNSORTABLE : // Character is unsortable, so skip it RETURN NONSPACE_MARK : // Character is a nonspace mark, so only store the // diacritic weight. If (Length(DiacriticWeights) is greater than 0) THEN SET last DiacriticWeight in DiacriticWeights to DiacriticWeight + CharacterWeights.DiacrticWeight ELSE APPEND CharacterWeights.DiacriticWeight to DiacriticWeights as a BYTE ENDIF RETURN EXPANSION : // Expansion character, each character has 2 weights, store // each weight separately SET Weights to CALL GetExpansionWeights WITH (SourceString[SourceIndex], SortLocale) // Store the appropriate weights, there should be 2 or 3 FOR each Weight in Weights // Store the weight of the first character of the // expansion SET UnicodeWeight to CALL CorrectUnicodeWeight WITH (Weights, IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights APPEND Weights.DiacriticWeight to DiacriticWeights as a BYTE APPEND Weights.CaseWeight to CaseWeights as a BYTE ENDFOR RETURN PUNCTUATION : SET Position to Length(UnicodeWeights) as 16 bit integer APPEND Position into SpecialWeights as 16 bit integer SET SpecialWeight to CALL MakeUnicodeWeight WITH (CharacterWeight.ScriptMember, CharacterWeight.PrimaryWeight, False) APPEND SpecialWeight to SpecialWeights as 16 bit integer RETURN SYMBOL_1 : SYMBOL_2 : SYMBOL_3 : SYMBOL_4 : SYMBOL_5 : SYMBOL_6 : // Character is a symbol, store Unicode Weights SET UnicodeWeight to CALL CorrectUnicodeWeight WITH (Weights[0], IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights APPEND CharacterWeights.DiacriticWeight to DiacriticWeights as a BYTE APPEND CharacterWeights.CaseWeight to CaseWeights as a BYTE RETURN EASTASIA_SPECIAL : // Get the primary and case weight of the current code point SET PrimaryWeight to UnicodeWeight.PrimaryWeight SET ExtraWeight to UnicodeWeight.CaseWeight // Mask off the bits that are not required SET ExtraWeight to (ExtraWeight & CaseMask) | CASE_EXTRA_WEIGHT_MASK // Special case Repeat and Cho-On // PrimaryWeight = 0 => Repeat // PrimaryWeight = 1 => Cho-On // PrimaryWeight = 2+ => Kana IF PrimaryWeight is less than or equal to MAX_SPECIAL_PW THEN // If the script member of the previous character is // invalid, then give the special character // invalid weight (highest possible weight) so that it // will sort AFTER everything else. SET PreviousIndex to SourceIndex - 1 SET UnicodeWeight.ScriptMember to MAP_INVALID_WEIGHT SET UnicodeWeight.PrimaryWeight to MAP_INVALID_WEIGHT WHILE PreviousIndex is greater than or equal to 0 SET PreviousWeight to CALL GetCharacterWeights WITH (SortLocale, SourceString[PreviousIndex]) IF PreviousWeight.ScriptMember is less than EASTASIA_SPECIAL THEN IF PreviousWeight.ScriptMember is not equal to EXPANSION THEN // UNSORTABLE or NONSPACE_MARK // Ignore these to get the // previous ScriptMember/PrimaryWeight DECREMENT PreviousIndex CONTINUE WHILE PreviousIndex ENDIF ELSE IF PreviousWeight.ScriptMember is equal to EASTASIA_SPECIAL THEN IF PreviousWeight.PrimaryWeight is less than or equal to MAX_SPECIAL_PW THEN // Handle case where two special chars follow // each other. Keep going back in the string DECREMENT PreviousIndex CONTINUE WHILE PreviousIndex ENDIF SET UnicodeWeight to CALL MakeUnicodeWeight WITH (KANA, PreviousWeight.PrimaryWeight, IsKoreanLocale) // Only build weights W6 & W7 if the previous // character is KANA. // ignores W4 & W5 // Always: // W6 = previous CW & ISOLATE_KANA SET PreviousExtraWeight to PreviousWeight.CaseWeight // Mask off the bits that aren't required SET PreviousExtraWeight to CASE_EXTRA_WEIGHT_MASK | (PreviousExtraWeight & CaseMask) // Ignore kana and width // so these are merely CASE_EXTRA_WEIGHT_MASK SET ExtraWeight.W6 to CASE_EXTRA_WEIGHT_MASK SET ExtraWeight.W7 to CASE_EXTRA_WEIGHT_MASK // Repeat is already done, which is: // UW = previous UW (set above) // W5 = ignored // W7 = previous CW & ISOLATE_WIDTH (done above) IF PrimaryWeight is not equal to PW_REPEAT THEN // Cho-On: // UW = previous UW & CHO_ON_UW_MASK // W5 = ignored // W7 = current CW & ISOLATE_WIDTH (done above) SET UnicodeWeight.PrimaryWeight to UnicodeWeight.PrimaryWeight & CHO_ON_PW_MASK ENDIF // Append the calculated ExtraWeight // APPEND ExtraWeight to ExtraWeights ELSE // The previous weight is not EASTASIA_SPECIAL, so just // store the previous weight SET UnicodeWeight to CorrectUnicodeWeight (PreviousWeight, IsKoreanLocale) // Append the weight that was found APPEND UnicodeWeight to UnicodeWeights ENDIF ENDWHILE ELSE // Kana // ScriptMember = KANA // PrimaryWeight = current PrimaryWeight // W4 = current CaseWeight & ISOLATE_SMALL // W5 = WT_FIVE_KANA // W6 = current CaseWeight & ISOLATE_KANA // W7 = current CaseWeight & ISOLATE_WIDTH SET UnicodeWeight to CALL MakeUnicodeWeight WITH ( KANA, CharacterWeight.PrimaryWeight, IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights SET TempExtraWeight.W4 to ExtraWeight & ISOLATE_SMALL SET TempExtraWeight.W5 to WT_FIVE_KANA SET TempExtraWeight.W6 to ExtraWeight & ISOLATE_KANA SET TempExtraWeight.W7 to ExtraWeight & ISOLATE_WIDTH APPEND TempExtraWeight to ExtraWeights ENDIF APPEND CharacterWeight.DiacriticWeight to DiacriticWeights as a BYTE APPEND MIN_CW to CaseWeights as a BYTE RETURN JAMO_SPECIAL : // See if it's a leading Jamo IF (CALL IsJamoLeading(SourceString[SourceIndex])) is true THEN // If the characters beginning at SourceIndex are a valid // old Hangul composition, create the SortKey // according to the old Hangul rule SET OldHangulCount to CALL MapOldHangulSortKey WITH (SourceString, SourceIndex, SortLocale, UnicodeWeights, IsKoreanLocale) IF OldHangulCount is greater than 0 THEN // Decrement OldHangulCount because the caller's loop // will increment the SourceIndex as well DECREMENT OldHangulCount SET SourceIndex to SourceIndex + OldHangulCount RETURN ENDIF ENDIF // Otherwise, fall back to the normal behavior // No special case on the character, so store the Jamo's // weights. // Store the real script member in the diacritic weight // in the tables since both the diacritic weight and the // case weight are not used in Korean // For example, from unisort.txt: // 0x1101 4 84 83 2 ; Choseong Ssangkiyeok // Field 2 has a value of 4 to trigger the code case for JAMO_SPECIAL. // Field 3 (84) is the real primary weight for this Jamo. // Field 4 (83) is the real script member for this Jamo. SET UnicodeWeight to CALL MakeUnicodeWeight WITH (CharacterWeight.DiacriticWeight, CharacterWeight.PrimaryWeight, IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights APPEND MIN_DW to DiacriticWeights as a BYTE APPEND MIN_CW to DiacriticWeights as a BYTE RETURN EXTENSION_A : // Extension A gives us two weights // UnicodeWeight = SM_EXT_A, AW_EXT_A, AW, DW // First Weight SET UnicodeWeight to CALL MakeUnicodeWeight WITH (SCRIPT_MEMBER_EXT_A, PRIMARY_WEIGHT_EXT_A, IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights // Since the script member is our flag for this EXTENSION_A special // case, the real weights are in fields 2 & 3. // Example: // From unisort.txt: // 0x3400 5 16 2 2 ; ? CJK Unified Ideographs Extension A // Field 2 is the script member. // Field 3 is the primary weight. // Second Weight SET UnicodeWeight to CALL MakeUnicodeWeight WITH (CharacterWeight.PrimaryWeight, CharacterWeight.DiacriticWeight, false) APPEND UnicodeWeight to UnicodeWeights APPEND MIN_DW to DiacriticWeights as a BYTE APPEND MIN_CW to DiacriticWeights as a BYTE RETURNENDCASEGetPositionSpecialWeight XE "UTF-16 string:GetPositionSpecialWeight"This algorithm specifies the retrieval of special weight based on the source MENT GetPositionSpecialWeightCOMMENTCOMMENT On Entry: Position - Position to calculate weight forCOMMENTCOMMENT On Exit: Weight - Resulting weightCOMMENTPROCEDURE GetPositionSpecialWeight(IN Position : 32 bit integer, OUT Weight : 16 bit integer)// Add some bits (0x8003) to adjust the weight and because// some bits are expected. Since setting 0x3 is required, rotate the source// index 2 bits so as to not lose the precision.// Note that if SourceIndex is larger than 0x1FFF, then some bits // will be lost on the conversion to 16 bits. Presumably if a string // is over 8191 characters long, they will differ well before this // point, so the lost information is irrelevant.SET Weight to (SourceIndex << 2) | 0x8003RETURN WeightMapOldHangulSortKey XE "UTF-16 string:MapOldHangulSortKey"This algorithm specifies the generation of Unicode weight based on the strings at the specified index that have a special Old Hangul sequence. HYPERLINK \l "Appendix_A_3" \h <3>GetJamoComposition XE "UTF-16 string:GetJamoComposition"This algorithm specifies the strings at the specified index that form a valid Old Hangul character that is composed of a Jamo character sequence. HYPERLINK \l "Appendix_A_4" \h <4>COMMENT GetJamoCompositionCOMMENTCOMMENT On Entry: SourceString - Unicode String to testCOMMENT CurrentIndex - Index of leading Jamo to start fromCOMMENT JamoClass - Class of Jamo to look forCOMMENT JamoSortInfo - Information about the current COMMENT sequenceCOMMENT On Exit: JamoSortInfo - Updated with information aboutCOMMENT the new sequenceCOMMENT SourceIndex - Updated to next character if COMMENT Jamo is foundCOMMENT NewJamoClass - New class to look for nextCOMMENTCOMMENT NOTE: This function assumes the character at SourceStringCOMMENT [SourceIndex] is a leading MENT Ie: IsJamo() returned trueCOMMENTPROCEDURE GetJamoComposition (IN SourceString : Unicode String, INOUT CurrentIndex : 32 bit integer, IN JamoClass : enumeration, INOUT JamoSortInfo : JamoSortInfoType, OUT NewJamoClass : enumeration)SET CurrentCharacter to SourceString[CurrentIndex]// Get the Jamo information for the current characterSET JamoStateData to CALL GetJamoStateData WITH (CurrentCharacter)SET JamoSortInfo to CALL UpdateJamoSortInfo WITH (JamoClass, JamoStateData, JamoSortInfo)// Move on to the next characterINCREMENT CurrentIndexWHILE CurrentIndex is less than Length(SourceString) SET CurrentCharacter to SourceString[CurrentIndex] IF CALL IsJamo WITH (CurrentCharacter) is not true THEN // The current character is not a Jamo, // Done checking for a Jamo composition SET NewJamoClass to "Invalid Jamo Sequence" RETURN ENDIF IF CurrentCharacter is equal to 0x1160 THEN SET JamoSortInfo.FillerUsed to true ENDIF // Get the Jamo class of it IF CALL IsJamoLeading WITH (CurrentCharacter) is true THEN SET NewJamoClass to "Leading Jamo Class" ELSE IF CALL IsJamoTrailing WITH (CurrentCharacter) is true THEN SET NewJamoClass to "Trailing Jamo Class" ELSE SET NewJamoClass to "Vowel Jamo Class" ENDIF IF JamoClass is not equal to NewJamoClass THEN RETURN NewJamoClass ENDIF // Push the current Jamo (SourceString[CurrentIndex]) // into the state machine to check if it is a valid // old Hangul composition. During the check also // update the sortkey result in: JamoSortInfo // Find the new record SET JamoStateData to CALL FindNewJamoState WITH (CurrentCharacter, JamoStateData) // A valid old Hangul composition was not found for the current // character so return the current Jamo class // (JamoClass and NewJamoClass are identical) IF JamoStateData is null THEN RETURN NewJamoClass ENDIF // A match has been found, so update our info. SET JamoSortInfo to CALL UpdateJamoSortInfo WITH (JamoClass, JamoStateData, JamoSortInfo) // Still in a valid old Hangul composition. //Go check the next character. INCREMENT CurrentIndexENDWHILE CurrentIndexSET NewJamoClass to "Invalid Jamo Sequence"RETURN NewJamoClassGetJamoStateData XE "UTF-16 string:GetJamoStateData"This algorithm specifies the retrieval of state machine information to check if the specified Jamo sequence forms a valid Old Hangul character. HYPERLINK \l "Appendix_A_5" \h <5>FindNewJamoState XE "UTF-16 string:FindNewJamoState"This algorithm specifies retrieval of a new state from the state machine for Jamo processing. HYPERLINK \l "Appendix_A_6" \h <6>COMMENT FindNewJamoState COMMENTCOMMENT On Entry: JamoCharacter - Unicode Character to get JamoCOMMENT information forCOMMENT JamoStateData - Current Jamo state informationCOMMENT COMMENT On Exit: JamoStateData - New Jamo state record from theCOMMENT data file, null if anCOMMENT appropriate state record isCOMMENT not MENTPROCEDURE FindNewJamoState(IN JamoCharacter : Unicode Character, INOUT JamoStateData : JamoStateDataType)// The current JamoStateData.DataRecord points to the base record.// There are JamoStateData.TransitionCount following records that may// match the input JamoCharacter, the search is for the first oneSET DataRecord to JamoStateData.DataRecordWHILE JamoStateData.TransitionCount is greater than 0 // advance to the next record in the data and test if // it is the correct record for JamoCharacter ADVANCE DataRecord to next record in data table IF DataRecord.Field1 is equal to JamoCharacter THEN // Found a record, get its info and return it // Now gather the information from that record. SET JamoStateData.OldHangulFlag to JamoRecord.Field2 SET JamoStateData.LeadingIndex to JamoRecord.Field3 SET JamoStateData.VowelIndex to JamoRecord.Field4 SET JamoStateData.TrailingIndex to JamoRecord.Field5 SET JamoStateData.ExtraWeight to JamoRecord.Field6 SET JamoStateData.TransitionCount to JamoRecord.Field7 // Remember the record SET JamoStateData.DataRecord to JamoRecord RETURN JamoStateDataENDWHILE// record not found, return nullSET JamoStateData to nullRETURN JamoStateDataUpdateJamoSortInfo XE "UTF-16 string:UpdateJamoSortInfo"This algorithm specifies the update of Jamo sorting information based on the current state of the state machine for Jamo processing. HYPERLINK \l "Appendix_A_7" \h <7>IsJamo XE "UTF-16 string:IsJamo"This algorithm specifies the check for a valid Jamo character. HYPERLINK \l "Appendix_A_8" \h <8>COMMENT IsJamo COMMENTCOMMENT On Entry: SourceCharacter - Unicode Character to testCOMMENTCOMMENT On Exit: Result - true if SourceCharacter is inCOMMENT the Jamo rangeCOMMENTPROCEDURE IsJamoLeading(IN SourceCharacter : Unicode Character, OUT Result: boolean)IF (SourceCharacter is greater than or equal to NLS_CHAR_FIRST_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_JAMO) THEN SET Result to trueELSE SET Result to falseENDIFRETURN ResultIsCombiningJamo XE "UTF-16 string:IsCombiningJamo"This algorithm specifies the check for a valid Jamo character. HYPERLINK \l "Appendix_A_9" \h <9>COMMENT IsCombiningJamo COMMENTCOMMENT On Entry: SourceCharacter - Unicode Character to testCOMMENTCOMMENT On Exit: Result - true if SourceCharacter is inCOMMENT the Jamo rangeCOMMENTPROCEDURE IsJamoLeading(IN SourceCharacter : Unicode Character, OUT Result: boolean)IF ((SourceCharacter is greater than or equal to NLS_CHAR_FIRST_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_JAMO)) Or ((SourceCharacter is greater than or equal to NLS_CHAR_FIRST_EXT_A_LEADING_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_EXT_A_LEADING_JAMO)) Or ((SourceCharacter is greater than or equal to NLS_CHAR_FIRST_EXT_B_VOWEL_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_EXT_B_VOWEL_JAMO)) Or ((SourceCharacter is greater than or equal to NLS_CHAR_FIRST_EXT_B_TRAILING_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_EXT_B_TRAILING_JAMO)) THEN SET Result to trueELSE SET Result to falseENDIFRETURN ResultIsJamoLeading XE "UTF-16 string:IsJamoLeading"This algorithm checks if the specified Jamo character is a leading Jamo. HYPERLINK \l "Appendix_A_10" \h <10>IsJamoVowel XE "UTF-16 string:IsJamoVowel"This algorithm checks whether the specified Jamo character is a vowel Jamo. HYPERLINK \l "Appendix_A_11" \h <11>COMMENT IsJamoVowelCOMMENTCOMMENT On Entry: SourceCharacter - Unicode Character to testCOMMENTCOMMENT On Exit: Result - true if this is a vowel JamoCOMMENTPROCEDURE IsJamoTrailing(IN SourceCharacter : Unicode Character, OUT Result: boolean)IF ((SourceCharacter is greater than or equal to NLS_CHAR_FIRST_VOWEL_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_VOWEL_JAMO)) Or ((SourceCharacter is greater than or equal to NLS_CHAR_FIRST_EXT_B_VOWEL_JAMO) and (SourceCharacter is less than or equal to NLS_CHAR_LAST_LEADING_EXT_B_VOWEL_JAMO)) SET Result to trueELSE SET Result to falseENDIFRETURN ResultIsJamoTrailing XE "UTF-16 string:IsJamoTrailing"This algorithm checks if the specified Jamo character is a trailing Jamo. HYPERLINK \l "Appendix_A_12" \h <12>COMMENT IsJamoTrailingCOMMENTCOMMENT On Entry: SourceCharacter - Unicode Character to testCOMMENTCOMMENT On Exit: Result - true if this is a trailing JamoCOMMENTCOMMENT NOTE: Only call this if the character is known to be a JamoCOMMENT syllable. This function only helps distinguish betweenCOMMENT the different types of Jamo, so only call it ifCOMMENT IsJamo() has returned MENTPROCEDURE IsJamoTrailing(IN SourceCharacter : Unicode Character, OUT Result: boolean)IF SourceCharacter is greater than or equal to NLS_CHAR_FIRST_VOWEL_JAMO THEN SET Result to trueELSE SET Result to falseENDIFRETURN ResultInitKoreanScriptMap XE "UTF-16 string:InitKoreanScriptMap"This algorithm specifies the initialization of a data structure that is required for the special processing of Korean script MENT InitKoreanScriptMapCOMMENTCOMMENT On Entry: global KoreanScriptMap - presumed to be nullCOMMENTCOMMENT On Exit: global KoreanScriptMap - initialized to mapCOMMENT scripts to KoreanCOMMENTCOMMENT This procedure initializes the Korean, causing ideographicCOMMENT scripts to sort prior to other scripts for the MENTPROCEDURE InitKoreanScriptMapSET KoreanScriptMap to new array of 256 null bytes// Initialize the "scripts" prior to first script (Latin, script 14)FOR counter is 0 to FIRST_SCRIPT - 1 SET KoreanScriptMap[counter] to counterENDFOR counter// For Korean the Ideographs sort to the first script,// so start with that indexSET NewScript to FIRST_SCRIPT// Test if the IDEOGRAPH script is part of a multiple weights script// For convenience hard code the information from the// unisort.txt section SORTTABLES\MULTIPLEWEIGHTS// IDEOGRAPHS are 128 through 241,// map them to FIRST_SCRIPT through 127FOR counter is IDEOGRAPH to 241 SET KoreanScriptMap[counter] to NewScript INCREMENT NewScriptENDFOR// Now set the remaining unset scripts the next NewScript valueFOR counter is 0 to MAX_SCRIPTS - 1 // If the value has not been set yet, set it to the next value IF KoreanScriptMap[counter] is null THEN SET KoreanScriptMap[counter] to NewScript INCREMENT NewScript ENDIFENDFORMapping UTF-16 Strings to Upper Case XE "UTF-16 string:mapping to upper case"To map a UTF-16 string to upper case, each UTF-16 code point is looked for in an upper casing table [MSDN-UCMT/Win8]. If an entry is found, the input code point is changed to the output code point.ToUpperCase XE "UTF-16 string:converting with ToUpperCase"This algorithm converts a UTF-16 string to its upper case MENT ToUpperCaseCOMMENT On Entry: inputString – A string encoded in UTF-16COMMENTCOMMENT On Exit: Result - A string encoded in UTF-16 withCOMMENT the output in Upper Case form.PROCEDURE ToUpperCaseSET Result to empty stringSET index to 0WHILE index is less than Length(inputString) SET upperCase to UpperCaseMapping(inputString[index]) APPEND upperCase to ResultINCREMENT indexENDWHILERETURNUpperCaseMapping XE "UTF-16 string:converting to upper case using UpperCaseTable"This algorithm converts a UTF-16 code point to its upper case form using the UpperCaseTable in [MSDN-UCMT/Win8].COMMENT UpperCaseMappingCOMMENT On Entry: SourceCharacter – A UTF-16 code pointCOMMENTCOMMENT On Exit: Result - Upper case UTF-16 code pointPROCEDURE UpperCaseMappingSELECT RECORD caseMapping FROM UpperCaseTable WHERE field 1 matches SourceCharacterIF EXISTS caseMapping SET Result TO caseMapping field 2ELSE SET Result TO SourceCharacterENDIFRETURNUnicode International Domain Names XE "Unicode International Domain Names"International Domain Name support is provided by IdnToNameprepUnicode, IdnToAscii, and IdnToUnicode. The algorithms follow either the IDNA2003 or IDNA2008+UTS46 standards depending on the specific implementation environment. HYPERLINK \l "Appendix_A_13" \h <13>IdnToAsciiCOMMENT IdnToAsciiCOMMENT On Entry: SourceString – Unicode String to get Punycode COMMENT representation MENT Flags - Bit flags to control behaviorCOMMENT of IDN validationCOMMENTCOMMENT IDN_ALLOW_UNASSIGNED: During validation, allow unicodeCOMMENT code points that are not assigned. COMMENT IDN_USE_STD3_ASCII_RULES: Enforce validation of the STD3COMMENT MENT IDN_EMAIL_ADDRESS: Allow punycode encoding of the local partCOMMENT of an email address to tunnel EAICOMMENT addresses through non-Unicode MENTCOMMENT On Exit: Punycode - String containing the Punycode ASCII rangeCOMMENT form of the inputPROCEDURE IdnToAscii(IN SourceString : Unicode String, IN Flags: 32 bit integer, OUT PunycodeString : Unicode String)COMMENT Split input string into email local part and domain parts COMMENT as appropriateIF (IDN_EMAILADDRESS bit is on in Flags) THEN IF (SourceString CONTAINS "@") THEN SET arrayParts = SourceString.Split("@") SET emailLocalString to arrayParts[0] SET domainString to arrayParts[1] ELSE SET emailLocalString to SourceString SET domainString to "" ENDIFELSE SET domainString to SourceString SET emailLocalString to ""ENDIF SET OutputString TO ""IF (emailLocalString IS NOT EMPTY) THEN COMMENT email local part may not contain null character IF (emailLocalString CONTAINS character U+0000) THEN RETURN ERROR ENDIF COMMENT email local part is normalized per Normalization Form C (NFC) COMMENT Defined in Unicode Technical Report #15 (UTR#15) COMMENT ApplyUTR15NormalizationFormC(emailLocalString) IF (emailLocalString CONTAINS character U+0080 through character U+10FFFF) THEN encodedString = PunycodeEncode(emailLocalString) PREPEND "xl--" TO encodedString ELSE SET encodedString TO emailLocalString ENDIF COMMENT email local part may not be > 255 characters even converted IF (LENGTH of encodedString IS GREATER THAN 255) THEN RETURN ERROR ENDIF SET OutputString TO encodedString COMMENT Will need an @ if there is a domain part too IF (domainString IS NOT EMPTY) THEN APPEND "@" TO domainString ENDIFELSE COMMENT Cannot have empty local part in email mode IF (IDN_EMAIL_ADDRESS bit is on in Flags) THEN RETURN ERROR ENDIFENDIFIF (domainString IS NOT EMPTY) THEN (domainString is not empty)) THEN COMMENT See if STD3 rules need tested COMMENT Test for invalid characters in domain name IF ((IDN_USE_STD3_ASCII_RULES bit is on in Flags) AND ((domainString CONTAINS characters U+0000 through ',') OR (domainString CONTAINS character '/') OR (domainString CONTAINS characters ':' through '@') OR (domainString CONTAINS characters '[' through '`') OR (domainString CONTAINS characters '{' through U+007F))) THEN RETURN ERROR ENDIF COMMENT Each Label of the domain name is processed independently DEFINE domainString AS Array OF String IF (domainString CONTAINS ".") THEN SET domainLabels TO domainString.Split(".") ELSE SET domainLabels[0] TO domainString ENDIF SET encodedDomain TO "" FOREACH label IN domainLabels DO SET encodedString TO "" IF (label CONTAINS characters U+0080 THROUGH U+10FFFF) THEN IF Windows version is Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 THEN SET normalizedLabel TO NormalizeForIdna2003(label, flags) ELSE SET normalizedLabel TO NormalizeForIdna2008(label, flags) ENDIF SET encodedString TO PunycodeEncode(normalizedLabel) PREPEND "xn--" TO encodedString ELSE COMMENT ASCII range only, does not need encoding SET encodedString TO label ENDIF COMMENT domain labels may not be empty or > 63 characters even converted IF ((LENGTH OF encodedString IS EMPTY) OR (LENGTH OF encodedString IS GREATER THAN 63)) THEN RETURN ERROR ENDIF COMMENT See if STD3 rules need tested IF (IDN_USE_STD3_ASCII_RULES bit is on in Flags) COMMENT domain labels cannot be empty IF (label IS EMPTY) THEN RETURN ERROR ENDIF COMMENT leading and trailing – are illegal in domain labels IF (label BEGINS WITH "-" OR label END WITH "-") THEN RETURN ERROR ENDIF ENDIF COMMENT Need to retain separators between domain labels IF (label IS NOT LAST VALUE IN domainLabels) THEN APPEND "." to encodedDomain ENDIF ENDFOREACH COMMENT encoded domains may not be > 255 characters. IF (LENGTH OF encodedDomain IS GREATER THAN 255)) THEN RETURN ERROR ENDIF APPEND encodedDomain to OutputStringENDIFRETURN OutputStringIdnToUnicodeCOMMENT IdnToUnicodeCOMMENT On Entry: SourceString – Idn String to get UnicodeCOMMENT representation MENT Flags - Bit flags to control behaviorCOMMENT of IDN validationCOMMENTCOMMENT IDN_ALLOW_UNASSIGNED: During validation, allow unicodeCOMMENT code points that are not assigned. COMMENT IDN_USE_STD3_ASCII_RULES: Enforce validation of the STD3COMMENT MENT IDN_RAW_PUNYCODE: Only decode the punycode, no additionalCOMMENT MENT IDN_EMAIL_ADDRESS: Allow punycode encoding of the local partCOMMENT of an email address to tunnel EAICOMMENT addresses through non-Unicode MENTCOMMENT On Exit: UnicodeString - String containing the Unicode form of theCOMMENT input string.PROCEDURE IdnToUnicode (IN SourceString : Punycode String, IN Flags: 32 bit integer, OUT UnicodeString : Unicode String)UnicodeString = PunycodeDecode(SourceString)COMMENT IDN_RAW_PUNYCODE stops hereIF (IDN_RAW_PUNYCODE bit is on in Flags) THEN return UnicodeStringENDIFCOMMENT Otherwise verify that the result round tripsRoundTripPunycodeString = IdnToAscii(UnicodeString, Flags)IF (RoundTripPunycodeString IS NOT EQUAL TO UnicodeString) return ERRORENDIFreturn UnicodeStringIdnToNameprepUnicodeThis function merely returns the output of what IdnToUnicode(IdnToAscii(InputString)) would MENT IdnToNameprepUnicodeCOMMENT On Entry: SourceString – Unicode String to get nameprep form ofCOMMENT Flags - Bit flags to control behaviorCOMMENT of IDN validationCOMMENTCOMMENT IDN_ALLOW_UNASSIGNED: During validation, allow unicodeCOMMENT code points that are not assigned. COMMENT IDN_USE_STD3_ASCII_RULES: Enforce validation of the STD3COMMENT MENT IDN_EMAIL_ADDRESS: Allow punycode encoding of the local partCOMMENT of an email address to tunnel EAICOMMENT addresses through non-Unicode MENTCOMMENT On Exit: NameprepString -String containing the nameprep form of theCOMMENT input string.PROCEDURE IdnToNameprepUnicode(IN SourceString : Punycode String, IN Flags: 32 bit integer, OUT UnicodeString : Unicode String)SET AsciiString TO IdnToAscii(SourceString, Flags)SET NameprepString TO IdnToUnicode(AsciiString, Flags)return NameprepStringPunycodeEncodePunycodeEncode encodes an input ASCII/Unicode string. If the input contains non-ASCII parts, then punycoded strings are output, prefixed with the xn-- or xl-- labels.PROCEDURE PunycodeEncode(IN UnicodeString : Unicode String, IN Flags: 32 bit integer, OUT PunycodeString : Unicode String)COMMENT Split input string into email local part and domain parts IF (IDN_EMAILADDRESS bit is on in Flags) THEN IF (UnicodeString CONTAINS "@") THEN SET arrayParts = UnicodeString.Split("@") SET emailLocalString TO arrayParts[0] SET domainString TO arrayParts[1] ELSE SET emailLocalString TO UnicodeString SET domainString TO "" ENDIFELSE SET domainString TO PunycodeString SET emailLocalString TO ""ENDIFSET PunycodeString TO ""IF (emailLocalString IS NOT "") THEN IF (emailLocalString CONTAINS U+0080 THROUGH U+10FFFF) THEN SET PunycodeString TO "xl--" COMMENT punycode_encode is described in RFC 3492 COMMENT SET encodedString TO punycode_encode(emailLocalString) APPEND encodedString to PunycodeString ELSE COMMENT Local part of email was not encoded SET PunycodeString TO emailLocalString ENDIFENDIFIF (domainString IS NOT "") THEN IF emailLocalString IS NOT "") THEN APPEND "@" TO PunycodeString ENDIF COMMENT Each Label of the domain name is parsed independently DEFINE domainString AS Array OF String IF (domainString CONTAINS ".") THEN SET domainLabels TO domainString.Split(".") ELSE SET domainLabels[0] TO domainString ENDIF FOREACH label IN domainLabels DO IF (label CONTAINS U+0080 THROUGH U+10FFFF) THEN COMMENT punycode_encode is described in RFC 3492 COMMENT SET encodedLabel TO punycode_encode(label) PREPEND "xn--" TO encodedLabel ELSE SET encodedLabel TO label ENDIF APPEND encodedLabel TO PunycodeString COMMENT Need to retain separators between domain labels IF (label IS NOT LAST VALUE IN domainLabels) THEN APPEND "." TO PunycodeString ENDIF ENDFOREACHENDIFreturn PunycodeStringPunycodeDecodePunycodeDecode decodes an input all-ASCII string. If the input contains the xn-- or xl-- prefix the decoding algorithm is applied.PROCEDURE PunycodeDecode(IN PunycodeString : Unicode String, IN Flags: 32 bit integer, OUT UnicodeString : Unicode String)COMMENT Non-ASCII data is unexpectedIF (PunycodeString CONTAINS U+0080 through U+10FFFF) THEN Return ERRORENDIFCOMMENT Split input string into email local part and domain parts IF (IDN_EMAILADDRESS bit is on in Flags) THEN IF (SourceString CONTAINS "@") THEN SET arrayParts = PunycodeString.Split("@") SET emailLocalString TO arrayParts[0] SET domainString TO arrayParts[1] ELSE SET emailLocalString TO PunycodeString SET domainString to "" ENDIFELSE SET domainString TO PunycodeString SET emailLocalString TO ""ENDIFSET UnicodeString TO ""IF (emailLocalString IS NOT "") THEN IF (emailLocalString BEGINS WITH "xl—") THEN TRIM "xl--" FROM BEGINNING OF emailLocalString COMMENT punycode_decode is described in RFC 3492 COMMENT UnicodeString = punycode_decode(emailLocalString) ELSE COMMENT Local part of email was not encoded UnicodeString = emailLocalString ENDIFENDIFIF (domainString IS NOT "") THEN IF emailLocalString IS NOT "") THEN APPEND "@" TO UnicodeString ENDIF COMMENT Each Label of the domain name is parsed independently DEFINE domainString as Array of String IF (domainString CONTAINS ".") THEN SET domainLabels TO domainString.Split(".") ELSE SET domainLabels[0] TO domainString ENDIF FOREACH label IN domainLabels DO IF (label BEGINS WITH "xn--") THEN TRIM "xn--" FROM BEGINNING OF label COMMENT punycode_decode is described in RFC 3492 COMMENT SET decodedLabel TO punycode_decode(label) ELSE SET decodedLabel TO label ENDIF APPEND decodedLabel TO UnicodeString COMMENT Need to retain separators between domain labels IF (label IS NOT LAST VALUE IN domainLabels) THEN APPEND "." to UnicodeString ENDIF ENDFOREACHENDIFreturn UnicodeStringIDNA2008+UTS46 NormalizeForIdnaNormalizeForIdna prepares the input string for encoding, using the mapping/normalization rules provided by IDNA2008+UTS46 (IDNA2008 with [TR46] applied). HYPERLINK \l "Appendix_A_14" \h <14>COMMENT NormalizeForIdna2008COMMENT On Entry: SourceString – Unicode String to prepare for IDNACOMMENT Flags - Bit flags to control behaviorCOMMENT of IDN validationCOMMENTCOMMENT IDN_ALLOW_UNASSIGNED: During validation, allow unicodeCOMMENT code points that are not assigned. COMMENTCOMMENT On Exit: Punycode - String containing the Punycode ASCII rangeCOMMENT form of the inputPROCEDURE NormalizeForIdna2008 (IN SourceString : Unicode String, IN Flags: 32 bit integer, OUT OutputString : Unicode String)COMMENT Mapping is done per the tables published by Unicode by followingCOMMENT RFC5892 as modified by UTS#46 section 2 "Unicode IDNA Compatibility Processing"COMMENT Appendix A of RFC5892 is NOT MENT Effectively this mapping is merely applying the latest IdnaMappingTable.txtCOMMENT mappings, including the "deviation" mappings from COMMENT Apply UTS#46 Section 4 steps 1 & 2 to the string with the "Transitional Processing"COMMENT option for the four "deviation" characters. Steps 3 and 4 are done by the MENT OPEN mapping FILE ""SET OutputString TO "" FOREACH character IN SourceString FIND RECORD data IN mapping WHERE LINE CONTAINS character IF (data IS EMPTY) THEN IF (IDN_ALLOW_UNASSIGNED bit IS NOT ON in Flags) THEN RETURN ERROR ELSE APPEND character TO OutputString ENDIF ELSE SWITCH (data FIELD statusValue) CASE "valid" CASE "disallowed_STD3_valid" BREAK CASE "ignored" SET character TO "" BREAK CASE "mapped" CASE "disallowed_STD3_valid" CASE "deviation" SET character TO data FIELD mappingValue BREAK ENDSWITCH APPEND character TO OuptutString ENDIFENDFOREACHRETURN OutputStringIDNA2003 NormalizeForIdnaNormalizeForIdna prepares the input string for encoding, using the mapping/normalization rules provided by IDNA2003. HYPERLINK \l "Appendix_A_15" \h <15>COMMENT NormalizeForIdna2003COMMENT On Entry: SourceString – Unicode String to prepare for IDNACOMMENT Flags - Bit flags to control behaviorCOMMENT of IDN validationCOMMENTCOMMENT IDN_ALLOW_UNASSIGNED: During validation, allow unicodeCOMMENT code points that are not assigned. COMMENTCOMMENT On Exit: Punycode - String containing the Punycode ASCII rangeCOMMENT form of the inputPROCEDURE NormalizeForIdna2003 (IN SourceString : Unicode String, IN Flags: 32 bit integer, OUT OutputString : Unicode String)COMMENT Behavior is identical to the results of RFC 3491 ( )COMMENT Make sure to allow unassigned code points if IDN_ALLOW_UNASSIGNED bit is set in FlagsSET OutputString TO ApplyRfc3491(SourceString, Flags)RETURN OutputStringComparing UTF-16 Strings OrdinallyTo do a case-sensitive ordinal comparison of strings, a binary comparison of the UTF-16 code points of the strings is done. To do a case-insensitive ordinal string comparison, ToUpperCase (section 3.1.5.3.1) is done on each string before doing the ordinal pareStringOrdinal AlgorithmThis algorithm compares two UTF-16 strings by doing an ordinal (binary) comparison. Optionally, the caller can request that the comparison be done on the uppercase form of the MENT CompareStringOrdinalCOMMENT On Entry: StringA – A UTF-16 string to be comparedCOMMENT On Entry: StringB – Second UTF-16 string to compareCOMMENT On Entry: IgnoreCaseFlag – TRUE to ignore case when comparingCOMMENTCOMMENT On Exit: Result – A value indicating if StringA is less than,COMMENT equal to, or greater than StringBPROCEDURE CompareStringOrdinalIF IgnoreCaseFlag is TRUE THEN SET StringA TO ToUpperCase(StringA) SET StringB TO ToUpperCase(StringB)ENDIFSET index TO 0WHILE index is less than Length(StringA) and index is also less than Length(StringB) IF StringA[index] is less than StringB[index] THENSET Result TO "StringA is less than StringB"RETURN ENDIF IF StringA[index] is greater than StringB[index] THENSET Result TO "StringA is greater than StringB"RETURN ENDIFINCREMENT indexENDWHILEIF Length(StringA) is equal to Length(StringB) THEN SET Result TO "StringA is equal to StringB"ELSE IF Length(StringA) is less than Length(StringB) THENSET Result TO "StringA is less than StringB"ELSE Assert Length(StringA) must be greater than Length(StringB) SET Result TO "StringA is greater than StringB"ENDIFRETURNTimer Events XE "Timer events - client" XE "Client:timer events"None.Other Local Events XE "Local events - client" XE "Client:local events"None.Protocol Examples XE "Examples - overview"None.Security XE "Security:overview"The following sections specify security considerations for implementers of the Windows Protocols Unicode Reference.Security Considerations for Implementers XE "Security:implementer considerations" XE "Implementer - security considerations" XE "Implementer - security considerations" XE "Security:implementer considerations" None. Index of Security Parameters XE "Security:parameter index" XE "Index of security parameters" XE "Parameters - security index" XE "Parameter index - security" XE "Index of security parameters" XE "Security:parameter index"None.Appendix A: Product Behavior XE "Product behavior" XE "Product behavior"Note: Some of the information in this section is subject to change because it applies to a preliminary product version, and thus may differ from the final version of the software when released. All behavior notes that pertain to the preliminary product version contain specific references to it as an aid to the reader.Windows NT operating systemWindows 2000 operating systemWindows XP operating systemWindows Server 2003 operating systemWindows Vista operating systemWindows Server 2008 operating systemWindows 7 operating systemWindows Server 2008 R2 operating systemWindows 8 operating systemWindows Server 2012 operating systemWindows 8.1 operating systemWindows Server 2012 R2 operating systemWindows 10 operating systemWindows Server 2016 Technical Preview operating systemExceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription. HYPERLINK \l "Appendix_A_Target_1" \h <1> Section 3.1.5.2.3: Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview do not use record count for DEFAULT. HYPERLINK \l "Appendix_A_Target_2" \h <2> Section 3.1.5.2.3: An LCID is used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. HYPERLINK \l "Appendix_A_Target_3" \h <3> Section 3.1.5.2.16: The following MapOldHangulSortKey algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 MENT MapOldHangulSortKeyCOMMENTCOMMENT On Entry: SourceString - Unicode String to testCOMMENT SourceIndex - Index of leading Jamo to start COMMENT fromCOMMENT SortLocale - Locale to use for linguisticCOMMENT sort dataCOMMENT UnicodeWeights - String to store any UnicodeCOMMENT weight foundCOMMENT for this character(s)COMMENTCOMMENT On Exit: CharactersRead - Number of old Hangul found COMMENT UnicodeWeights - Any Unicode weights found are COMMENT appendedCOMMENTPROCEDURE MapOldHangulSortKey(IN SourceString : Unicode String, IN SourceIndex : 32 bit integer, IN SortLocale : LCID, IN OUTUnicodeWeights : String of UnicodeWeightType, IN IsKoreanLocale : Boolean, OUT CharactersRead : 32 bit integer)SET CurrentIndex to SourceIndexSET JamoSortInfo to empty JamoSortInfoType// Get any Old Hangul Leading Jamo composition for our Leading JamoSET JamoClass to CALL GetJamoComposition WITH (SourceString, SourceIndex, "Leading Jamo Class", JamoSortInfo)IF JamoClass is equal to "Vowel Jamo Class" THEN // A Vowel Jamo, try to find an // Old Hangul Vowel Jamo composition. SET JamoClass to CALL GetJamoComposition WITH (SourceString, SourceIndex, "Vowel Jamo Class", JamoSortInfo)ENDIFIF JamoClass is equal to "Trailing Jamo Class" THEN // A Trailing Jamo, try to find an // Old Hangul Trailing Jamo composition. SET JamoClass CALL GetJamoComposition WITH (SourceString, SourceIndex, "Trailing Jamo Class", JamoSortInfo)ENDIF// A valid leading and vowel sequence and this is // old Hangul...IF JamoSortInfo.OldHangulFlag is true THEN // Compute the modern hangul syllable prior to this composition // Users formula from Unicode 3.0 Section 3.11 p54 // "Hangul Syllable Composition" // This converts a U+11.. sequence to a U+AC00 character SET ModernHangul to (JamoSortInfo.LeadingIndex * NLS_JAMO_VOWELCOUNT + JamoSortInfo.VowelIndex) * NLS_JAMO_TRAILING_COUNT + JamoSortInfo.TrailingIndex + NLS_HANGUL_FIRST_SYLLABLE IF JamoSortInfo.FillerUsed is true THEN // If the filler is used, sort before the modern Hangul, // instead of after DECREMENT ModernHangul // If falling off the modern Hangul syllable block... IF ModernHangul is less than NLS_HANGUL_FIRST_SYLLABLE THEN // Sort after the previous character // (Circled Hangul Kiyeok A) SET ModernHangul to 0x326e ENDIF // Shift the leading weight past any old Hangul // that sorts after this modern Hangul SET JamoSortInfo.LeadingWeight to JamoSortInfo.LeadingWeight + 0x80 ENDIF // Store the weights SET CharacterWeight to CALL GetCharacterWeights WITH (ModernHangul) SET UnicodeWeight to CALL CorrectUnicodeWeight WITH (CharacterWeight, IsKoreanLocale) APPEND UnicodeWeight to UnicodeWeights // Add additional weights SET UnicodeWeight to CALL MakeUnicodeWeight WITH (ScriptMember_Extra_UnicodeWeight, JamoSortInfo.LeadingWeight, false) APPEND UnicodeWeight to UnicodeWeights SET UnicodeWeight to CALL MakeUnicodeWeight WITH (ScriptMember_Extra_UnicodeWeight, JamoSortInfo.VowelWeight, false) APPEND UnicodeWeight to UnicodeWeights SET UnicodeWeight to CALL MakeUnicodeWeight WITH (ScriptMember_Extra_UnicodeWeight, JamoSortInfo.TrailingWeight, false) APPEND UnicodeWeight to UnicodeWeights // Return the characters consumed SET CharactersRead to CurrentIndex - SourceIndex RETURN CharactersReadENDIF// Otherwise it isn't a valid old Hangul composition// and don't do anything with itSET CharactersRead to 0RETURN CharactersRead HYPERLINK \l "Appendix_A_Target_4" \h <4> Section 3.1.5.2.17: The GetJamoComposition algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. HYPERLINK \l "Appendix_A_Target_5" \h <5> Section 3.1.5.2.18: The following GetJamoStateData algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 MENT GetJamoStateDataCOMMENTCOMMENT On Entry: Character - Unicode Character to get Jamo COMMENT information forCOMMENT COMMENT On Exit: JamoStateData - Jamo state information from COMMENT the data fileCOMMENTCOMMENT Jamo State information looks like this in the database:COMMENTCOMMENT SORTTABLESCOMMENT ...COMMENT JAMOSORT395COMMENT ...COMMENT 0x11724 COMMENT 0x1172 0x00 0x00 0x11 0x00 0x380x03; U+1172 COMMENT 0x1161 0x01 0x00 0x00 0x00 0x000x01; U+1172,1161 COMMENT 0x1175 0x01 0x00 0x11 0x1b 0x3a0x00; U+1172,1161,1175 COMMENT 0x1169 0x01 0x00 0x11 0x1b 0x3f0x00; U+1172,1169PROCEDURE GetJamoStateData (IN Character : Unicode Character, OUT JamoStateData : JamoStateDateType)// Get the Jamo section for this character.// If Character was 0x1172, this would access the following section:// 0x11724 // 0x1172 0x00 0x00 0x11 0x00 0x38 0x03 ; U+1172 record 0// 0x1161 0x01 0x00 0x00 0x00 0x00 0x01 ; U+1172,1161 record 1// 0x1175 0x01 0x00 0x11 0x1b 0x3a 0x00 ; U+1172,1161,1175 record 2// 0x1169 0x01 0x00 0x11 0x1b 0x3f 0x00 ; U+1172,1169 record 3// | | | | | | | |// Field 1 2 3 4 5 6 7 CommentOPEN SECTION JamoSection where name is SORTTABLES\JAMOSORT\[Character] from unisort.txt// Now open the first recordSELECT RECORD JamoRecord FROM JamoSection WHERE record index is 0// Now gather the information from that record.SET JamoStateData.OldHangulFlag to JamoRecord.Field2SET JamoStateData.LeadingIndex to JamoRecord.Field3SET JamoStateData.VowelIndex to JamoRecord.Field4SET JamoStateData.TrailingIndex to JamoRecord.Field5SET JamoStateData.ExtraWeight to JamoRecord.Field6SET JamoStateData.TransitionCount to JamoRecord.Field7// Remember the recordSET JamoStateData.DataRecord to JamoRecordRETURN JamoStateData HYPERLINK \l "Appendix_A_Target_6" \h <6> Section 3.1.5.2.19: The FindNewJamoState algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. HYPERLINK \l "Appendix_A_Target_7" \h <7> Section 3.1.5.2.20: The following UpdateJamoSortInfo algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 MENT UpdateJamoSortInfoCOMMENTCOMMENT On Entry: JamoClass - The current Jamo ClassCOMMENT JamoStateData - Information about the newCOMMENT character stateCOMMENT JamoSortInfo - Information about the characterCOMMENT stateCOMMENTCOMMENT On Exit: JamoSortInfo - Updated with information aboutCOMMENT the new state based on JamoClassCOMMENT and JamoSortDataCOMMENTPROCEDURE UpdateJamoSortInfo(IN JamoClass : enumeration, IN JamoStateData : JamoStateDataType, INOUT JamoSortInfo : JamoSortInfoType)// Record if this is a Jamo unique to old HangulSET JamoSortInfo.OldHangulFlag to JamoSortInfo.OldHangulFlag | JamoStateData.OldHangulFlag// Update the indices if the new ones are higher than the current// ones.IF JamoStateData.LeadingIndex is greater than JamoSortInfo.LeadingIndex THEN SET JamoSortInfo.LeadingIndex to JamoStateData.LeadingIndex;ENDIFIF JamoStateData.VowelIndex is greater than JamoSortInfo.VowelIndex THEN SET JamoSortInfo.VowelIndex to JamoStateData.VowelIndex;ENDIFIF JamoStateData.TrailingIndex is greater than JamoSortInfo.TrailingIndex THEN SET JamoSortInfo.TrailingIndex to JamoStateData.TrailingIndex;ENDIF// Update the extra weights according to the current Jamo class.CASE JamoClass OF "Leading Jamo Class": IF JamoStateData.ExtraWeight is greater than JamoSortInfo.LeadingWeight THEN SET JamoSortInfo.LeadingWeight to JamoStateData.ExtraWeight ENDIF "Vowel Jamo Class": IF JamoStateData.ExtraWeight is greater than JamoSortInfo.VowelWeight THEN SET JamoSortInfo.VowelWeight to JamoStateData.ExtraWeight ENDIF "Trailing Jamo Class": IF JamoStateData.ExtraWeight is greater than JamoSortInfo.TrailingWeight THEN SET JamoSortInfo.TrailingWeight to JamoStateData.ExtraWeight ENDIFENDCASERETURN JamoSortInfo HYPERLINK \l "Appendix_A_Target_8" \h <8> Section 3.1.5.2.21: The IsJamo algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. HYPERLINK \l "Appendix_A_Target_9" \h <9> Section 3.1.5.2.22: The IsCombiningJamo algorithm is only used in Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview. HYPERLINK \l "Appendix_A_Target_10" \h <10> Section 3.1.5.2.23: The following IsJamoLeading algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 MENT IsJamoLeading COMMENTCOMMENT On Entry: SourceCharacter - Unicode Character to testCOMMENTCOMMENT On Exit: Result - true if SourceCharacter is aCOMMENT leading JamoCOMMENTCOMMENT NOTE: Only call this if the character is known to be a JamoCOMMENT syllable. This function only helps distinguish betweenCOMMENT the different types of Jamo, so only call it ifCOMMENT IsJamo() has returned MENTPROCEDURE IsJamoLeading(IN SourceCharacter : Unicode Character, OUT Result: boolean)IF SourceCharacter is less than NLS_CHAR_FIRST_VOWEL_JAMO THEN SET Result to trueELSE SET Result to falseENDIFRETURN Result HYPERLINK \l "Appendix_A_Target_11" \h <11> Section 3.1.5.2.24: The IsJamoVowel algorithm is only applicable to Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview. HYPERLINK \l "Appendix_A_Target_12" \h <12> Section 3.1.5.2.25: The following IsJamoTrailing algorithm is only used in Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 MENT IsJamoTrailingCOMMENTCOMMENT On Entry: SourceCharacter - Unicode Character to testCOMMENTCOMMENT On Exit: Result - true if this is a trailing JamoCOMMENTCOMMENT NOTE: Only call this if the character is known to be a JamoCOMMENT syllable. This function only helps distinguish betweenCOMMENT the different types of Jamo, so only call it ifCOMMENT IsJamo() has returned MENTPROCEDURE IsJamoTrailing(IN SourceCharacter : Unicode Character, OUT Result: boolean)IF SourceCharacter is greater than or equal to NLS_CHAR_FIRST_VOWEL_JAMO THEN SET Result to trueELSE SET Result to falseENDIFRETURN Result HYPERLINK \l "Appendix_A_Target_13" \h <13> Section 3.1.5.4: Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating system follow IDNA2003.Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview follow the IDNA2008+UTS46 rules. HYPERLINK \l "Appendix_A_Target_14" \h <14> Section 3.1.5.4.6: This version is used in Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 Technical Preview. HYPERLINK \l "Appendix_A_Target_15" \h <15> Section 3.1.5.4.7: This version is used in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2Change Tracking XE "Change tracking" XE "Tracking changes" No table of changes is available. The document is either new or has had no changes since its last release.IndexAAbstract data model - client PAGEREF section_bd026fd3a02048da83bb789c3e4a679e21Applicability PAGEREF section_e454980102f14e6d81d75117ca9f5c258CChange tracking PAGEREF section_9d2d0f2fcc344d0ca91a46016f9f478a77Client data model PAGEREF section_bd026fd3a02048da83bb789c3e4a679e21 higher-layer triggered events PAGEREF section_20352215279e4ee3b5cc49325b09320c21 initialization PAGEREF section_39428142d05c44459170509d1853fceb21 local events PAGEREF section_43376dd0108b406bb2cdd780bf51f35968 timer events PAGEREF section_935af314a183495b8c2abc0df26f139268 timers PAGEREF section_9673bb614e8140f4bfa5b361e62ef0e821Codepage supported data files format PAGEREF section_226ff7f1febc446182bd54bc1c25985717 overview PAGEREF section_d167d7560c584564a0de77c647d367fa17 supported in Windows PAGEREF section_28fefe92d66c4b0390a997b473223d4310DData model - client PAGEREF section_bd026fd3a02048da83bb789c3e4a679e21DBCSRANGE PAGEREF section_01c67a39cb2649d4b81e281a0854234919EExamples - overview PAGEREF section_8fba7a6f9925476194323774c9beec2669GGlossary PAGEREF section_484e8ed3152b430095277efade6d64916HHigher-layer triggered events - client PAGEREF section_20352215279e4ee3b5cc49325b09320c21IImplementer - security considerations PAGEREF section_b592ff9d8cf6443f8b5ed1910846e88070Index of security parameters PAGEREF section_9f42fb1206f04b7d9ed4d030374442e870Informative references PAGEREF section_db8d65f20ef64088bff8f39540f294798Initialization - client PAGEREF section_39428142d05c44459170509d1853fceb21Introduction PAGEREF section_31a967a0c0984a88ac3fdc4a76e2af236LLocal events - client PAGEREF section_43376dd0108b406bb2cdd780bf51f35968MMapping between UTF-16 strings and legacy codepages GB 18031 codepage PAGEREF section_c6e5525d7b9f4b04991a60a4c2ad1fb927 ISCII codepage PAGEREF section_638eb197dac049b2a234dd0b9f99ce5727 ISO 2022-based codepages PAGEREF section_11eb7053fdda4010b03fa4c8f7ed1dea27 using codepage data file PAGEREF section_8334914af53849e99e962e3db28fc72a21 UTF-7 codepage PAGEREF section_83e0c5ad1c38425ca1d686688221e36627 UTF-8 codepage PAGEREF section_9c598542f2f64fd0b1873baf64372a2527MBTABLE PAGEREF section_c1c1ac1784154bae9fd06f979a4722ef19Messages overview PAGEREF section_e2533974b0204d578a92876dfb96d50610 supported codepage data files PAGEREF section_d167d7560c584564a0de77c647d367fa17 supported codepage in Windows PAGEREF section_28fefe92d66c4b0390a997b473223d4310 transport PAGEREF section_8dbe452dc2444c6bbb523861d5b03d9d10NNormative references PAGEREF section_08d5f872659b42bab014d12104d454f07OOverview PAGEREF section_91b9b8a5e26c4a01a94a6bb6a605251e8Overview (synopsis) PAGEREF section_91b9b8a5e26c4a01a94a6bb6a605251e8PParameter index - security PAGEREF section_9f42fb1206f04b7d9ed4d030374442e870Parameters - security index PAGEREF section_9f42fb1206f04b7d9ed4d030374442e870Product behavior PAGEREF section_a6d86942eaf644c68afd1603b3f4f0aa71Protocol Details overview PAGEREF section_778ad592651f4692bbaa4ecb8906e75421Pseudocode accessing record in codepage data file PAGEREF section_9b0a576d045a473897ca383ec500298621 legacy codepage - mapping codepage string to UTF-16 string PAGEREF section_5d543f48e18b482891d469b1488748cf24 legacy codepage - mapping UTF-16 string to codepage string PAGEREF section_5b099932364d4ab48f413d0c8d69b46322RReferences informative PAGEREF section_db8d65f20ef64088bff8f39540f294798 normative PAGEREF section_08d5f872659b42bab014d12104d454f07SSecurity implementer considerations PAGEREF section_b592ff9d8cf6443f8b5ed1910846e88070 overview PAGEREF section_c151d5528afb419ca7fb9c37d1461acd70 parameter index PAGEREF section_9f42fb1206f04b7d9ed4d030374442e870Sorting weight table PAGEREF section_226ad3058a0b469eb30d630c931faad230Standards assignments PAGEREF section_b0c06f1c819346be84d31f60c07528998TTimer events - client PAGEREF section_935af314a183495b8c2abc0df26f139268Timers - client PAGEREF section_9673bb614e8140f4bfa5b361e62ef0e821Tracking changes PAGEREF section_9d2d0f2fcc344d0ca91a46016f9f478a77Transport PAGEREF section_8dbe452dc2444c6bbb523861d5b03d9d10Triggered events - higher-layer - client PAGEREF section_20352215279e4ee3b5cc49325b09320c21UUnicode International Domain Names PAGEREF section_7d326d1dcf6d4ca3b175b6f15ae1d10260UTF-16 string accessing Windows sorting weight table PAGEREF section_227922dcca6e4ed093470a4410d65ba429 Check3ByteWeightLocale PAGEREF section_0316ec39f86e49c1af8bf643ffa052ab50 CompareSortKey PAGEREF section_e0ef0c55f4d54b99ae65c48f2e5aa16e28 converting to upper case using UpperCaseTable PAGEREF section_0588c604692c42979519d36e358d21a360 converting with ToUpperCase PAGEREF section_3c5ba38529c24cc5b525b29e36884ae060 CorrectUnicodeWeight PAGEREF section_53696ac674a94968a8c219631c0fd96542 FindNewJamoState PAGEREF section_e0783685ff5d4671ac57d021ee52d8b256 GetCharacterWeights PAGEREF section_3c79ef6c87b14d7b9bdcd088cf889f7243 GetContractionType PAGEREF section_801cea3a74b04a9a97158568d701936a42 GetExpandedCharacters PAGEREF section_c5e358a52e5947b8904d99133972599745 GetExpansionWeights PAGEREF section_75f0a3ac8e224b908b1f5ee8023d39c044 GetJamoComposition PAGEREF section_78555b0f0e4e4cda93c7b3b52a20273f54 GetJamoStateData PAGEREF section_e1d75ba2e4eb4ce19c969df6db67c25a56 GetPositionSpecialWeight PAGEREF section_a25f2263c18b4c7e9888be6b16554bb354 GetWindowsSortKey pseudocode PAGEREF section_a51f180fdf594e369c006814a628842930 InitKoreanScriptMap PAGEREF section_52fd4d1ee56043c995be5794ff74429759 IsCombiningJamo PAGEREF section_682a41adbb0e47b786b4dca51574faf757 IsJamo PAGEREF section_d27ff90a34a240ff87a2957ffa3cf25557 IsJamoLeading PAGEREF section_fcbb4e93135e4d17987ff59b6e638fcd58 IsJamoTrailing PAGEREF section_78e208c9d64349a28f3de2609e6ca08d58 IsJamoVowel PAGEREF section_2eaa7153e51b4229910edc90cd1560d858 MakeUnicodeWeight PAGEREF section_62073ad30401409fa812ba0316bf8aae43 MapOldHangulSortKey PAGEREF section_6de3cdf635504847a707e4aaf0df289454 mapping between legacy codepages and mapping between UTF-16 strings and GB 18031 codepage PAGEREF section_c6e5525d7b9f4b04991a60a4c2ad1fb927 mapping between UTF-16 strings and ISCII codepage PAGEREF section_638eb197dac049b2a234dd0b9f99ce5727 mapping between UTF-16 strings and ISO 2022-based codepages PAGEREF section_11eb7053fdda4010b03fa4c8f7ed1dea27 mapping between UTF-16 strings and UTF-7 codepage PAGEREF section_83e0c5ad1c38425ca1d686688221e36627 mapping between UTF-16 strings and UTF-8 codepage PAGEREF section_9c598542f2f64fd0b1873baf64372a2527 using codepage data file PAGEREF section_8334914af53849e99e962e3db28fc72a21 mapping to upper case PAGEREF section_1ad259bc24c44f3c878b55b8f2f6972760 pseudocode for accessing record in codepage data file PAGEREF section_9b0a576d045a473897ca383ec500298621 pseudocode for comparing PAGEREF section_7e136459a696456c88a4da2289a364ff27 pseudocode for mapping legacy codepage to PAGEREF section_5d543f48e18b482891d469b1488748cf24 pseudocode for mapping to legacy codepage PAGEREF section_5b099932364d4ab48f413d0c8d69b46322 sort keys for comparing PAGEREF section_065e29446f8a4c7aace450d5de274f6527 SortkeyContractionHandler PAGEREF section_9490a202183940289783f27141c0af1346 SpecialCaseHandler PAGEREF section_27b67aafec6543c6b20adce64b102aba50 TestHungarianCharacterSequences PAGEREF section_8993911b75414f57b557453298330c3441 UpdateJamoSortInfo PAGEREF section_83bde033b22b4c28babec729774b85e757WWCTABLE PAGEREF section_d19806316401428ea49dd71394be7da818Windows sorting weight table PAGEREF section_226ad3058a0b469eb30d630c931faad230 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download