Windows Language Code Identifier (LCID) Reference

Each language identifier is composed of a primary language identifier indicating the language and a sublanguage identifier indicating the ... Skiptomaincontent Thisbrowserisnolongersupported. UpgradetoMicrosoftEdgetotakeadvantageofthelatestfeatures,securityupdates,andtechnicalsupport. DownloadMicrosoftEdge Moreinfo Contents Exitfocusmode Save Edit Share Twitter LinkedIn Facebook Email Tableofcontents [MS-LCID]:WindowsLanguageCodeIdentifier(LCID)Reference Article 06/24/2021 4minutestoread Isthispagehelpful? Pleaserateyourexperience Yes No Anyadditionalfeedback? FeedbackwillbesenttoMicrosoft:Bypressingthesubmitbutton,yourfeedbackwillbeusedtoimproveMicrosoftproductsandservices.Privacypolicy. Submit Thankyou. Inthisarticle DescribeslocalizableinformationinWindows.Itlistsall languagecodeidentifiers(LCIDs)availableinallversionsofWindows. Thispageandassociatedcontentmaybe updatedfrequently.WerecommendyousubscribetotheRSS feedtoreceiveupdatenotifications. PublishedVersion Date ProtocolRevision RevisionClass Downloads 6/25/2021 15.0 Major PDF |DOCX |Diff Click heretodownloadazipfileofallPDFfilesforWindowsProtocols. PreviousVersions Date ProtocolRevision RevisionClass Downloads 4/7/2021 14.1 Minor PDF |DOCX |Errata |Diff 3/4/2020 14.0 Major PDF |DOCX |Diff 3/13/2019 13.0 Major PDF |DOCX |Diff 9/12/2018 12.0 Major PDF |DOCX |Errata |Diff 12/1/2017 11.0 Major PDF |DOCX |Errata |Diff 9/15/2017 10.0 Major PDF |DOCX |Errata |Diff 6/1/2017 9.0 None PDF |DOCX |Errata |Diff 3/16/2017 9.0 Major PDF |DOCX |Diff 7/14/2016 8.0 Major PDF |DOCX |Diff 10/16/2015 7.0 None PDF |DOCX 6/30/2015 7.0 Major PDF |DOCX 5/15/2014 6.1 None PDF |DOCX 2/13/2014 6.1 None PDF |DOCX 11/14/2013 6.1 Minor PDF |DOCX 8/8/2013 6.0 Major PDF |DOCX 1/31/2013 5.0 None 10/25/2012 5.0 None 7/12/2012 5.0 Major 3/30/2012 4.0 None 12/16/2011 4.0 Major 9/23/2011 3.2 None 6/17/2011 3.2 Minor 5/6/2011 3.1.3 None 3/25/2011 3.1.3 None 2/11/2011 3.1.3 None 1/7/2011 3.1.3 None 11/19/2010 3.1.3 None 10/8/2010 3.1.3 None 8/27/2010 3.1.3 None 7/16/2010 3.1.3 None 6/4/2010 3.1.3 Editorial 4/23/2010 3.1.2 Editorial 3/12/2010 3.1.1 Editorial 1/29/2010 3.1 Minor 12/18/2009 3.0.2 Editorial 11/6/2009 3.0.1 Editorial 9/25/2009 3.0 Major 8/14/2009 2.4.3 Editorial 7/2/2009 2.4.2 Editorial 5/22/2009 2.4.1 Editorial 4/10/2009 2.4 Minor 2/27/2009 2.3.2 Editorial 1/16/2009 2.3.1 Editorial 12/5/2008 2.3 Minor 10/24/2008 2.2.1 Editorial 8/29/2008 2.2 Minor 7/25/2008 2.1.6 Editorial 6/20/2008 2.1.5 Editorial 3/14/2008 2.1.4 Editorial 2/14/2008 2.1.3 Editorial PreviewVersions Fromtimetotime,Microsoftmay publishapreview,orpre-release,versionofanOpenSpecificationstechnical documentforcommunityreviewandfeedback.Tosubmitfeedbackforapreview versionofatechnicaldocument,pleasefollowanyinstructionsspecifiedfor thatdocument.Ifnoinstructionsareindicatedforthedocument,please providefeedbackbyusingtheOpenSpecificationForums. Thepreviewperiodforatechnicaldocumentvaries. Additionally,noteverytechnicaldocumentwillbepublishedforpreview. Apreviewversionofthisdocumentmaybe availableontheWindows Protocols-PreviewDocumentspage.Afterthepreviewperiod,the mostcurrentversionofthedocumentisavailableonthispage. DevelopmentResources Find resourcesforcreatinginteroperablesolutionsforMicrosoftsoftware, services,hardware,andnon-Microsoftproducts: Plugfests andEvents,TestTools, Development Support,andOpenSpecifications DevCenter. IntellectualPropertyRightsNoticeforOpenSpecificationsDocumentation TechnicalDocumentation.MicrosoftpublishesOpen Specificationsdocumentation(“thisdocumentation”)forprotocols,file formats,dataportability,computerlanguages,andstandardssupport. Additionally,overviewdocumentscoverinter-protocolrelationshipsand interactions. Copyrights.ThisdocumentationiscoveredbyMicrosoft copyrights.Regardlessofanyothertermsthatarecontainedinthetermsof usefortheMicrosoftwebsitethathoststhisdocumentation,youcanmake copiesofitinordertodevelopimplementationsofthetechnologiesthatare describedinthisdocumentationandcandistributeportionsofitinyour implementationsthatusethesetechnologiesorinyourdocumentationas necessarytoproperlydocumenttheimplementation.Youcanalsodistributein yourimplementation,withorwithoutmodification,anyschemas,IDLs,orcode samplesthatareincludedinthedocumentation.Thispermissionalsoappliesto anydocumentsthatarereferencedintheOpenSpecificationsdocumentation. NoTradeSecrets.Microsoftdoesnotclaimanytrade secretrightsinthisdocumentation. Patents.Microsofthaspatentsthatmightcoveryour implementationsofthetechnologiesdescribedintheOpenSpecifications documentation.NeitherthisnoticenorMicrosoft'sdeliveryofthis documentationgrantsanylicensesunderthosepatentsoranyotherMicrosoft patents.However,agivenOpenSpecificationsdocumentmightbecoveredbythe MicrosoftOpenSpecifications PromiseortheMicrosoftCommunity Promise.Ifyouwouldpreferawrittenlicense,orifthe technologiesdescribedinthisdocumentationarenotcoveredbytheOpen SpecificationsPromiseorCommunityPromise,asapplicable,patentlicensesare [email protected]. LicensePrograms.Toseealloftheprotocolsinscope underaspecificlicenseprogramandtheassociatedpatents,visitthePatentMap. Trademarks.Thenamesofcompaniesandproductscontained inthisdocumentationmightbecoveredbytrademarksorsimilarintellectual propertyrights.Thisnoticedoesnotgrantanylicensesunderthoserights. ForalistofMicrosofttrademarks,visitwww.microsoft.com/trademarks. FictitiousNames.Theexamplecompanies,organizations, products,domainnames,emailaddresses,logos,people,places,andeventsthat aredepictedinthisdocumentationarefictitious.Noassociationwithanyreal company,organization,product,domainname,emailaddress,logo,person, place,oreventisintendedorshouldbeinferred. ReservationofRights.Allother rightsarereserved,andthisnoticedoesnotgrantanyrightsotherthanas specificallydescribedabove,whetherbyimplication,estoppel,orotherwise. Tools. TheOpenSpecificationsdocumentationdoesnotrequiretheuseofMicrosoft programmingtoolsorprogrammingenvironmentsinorderforyoutodevelopan implementation.IfyouhaveaccesstoMicrosoftprogrammingtoolsand environments,youarefreetotakeadvantageofthem.CertainOpen Specificationsdocumentsareintendedforuseinconjunctionwithpublicly availablestandardsspecificationsandnetworkprogrammingartand,assuch, assumethatthereadereitherisfamiliarwiththeaforementionedmaterialor hasimmediateaccesstoit. Support. Forquestionsandsupport,[email protected]. Inthisarticle