File encoding - Mastering Windows PowerShell Scripting

File encoding Windows editors, including ISE, tend to save files using what is commonly known as ANSI encoding; this is more correctly known as Windows-1252 ... Skiptomaincontent MasteringWindowsPowerShellScripting-SecondEditionbyChrisDent,BrentonJ.W.Blawat GetfullaccesstoMasteringWindowsPowerShellScripting-SecondEditionand60K+othertitles,withfree10-daytrialofO'Reilly. There'salsoliveonlineevents,interactivecontent,certificationprepmaterials,andmore. Startyourfreetrial Windowseditors,includingISE,tendtosavefilesusingwhatiscommonlyknownasANSIencoding;thisismorecorrectlyknownasWindows-1252. AsWindows-1252isaMicrosoftnativeformat,itmaybemoreappropriatetosavefilesinauniversallyacceptedformatsuchasUTF8. Editordefaults PowerShellISEdefaultstosavingfilesinUTF8withaByteOrderMark(BOM). VisualStudioCodesavesfilesusingUTF8(withoutaBOM)bydefault.ThesettingmaybechangedinUserSettingsbyadding"files.encoding":"utf8bom". GetMasteringWindowsPowerShellScripting-SecondEditionnowwiththeO’Reillylearningplatform. O’Reillymembersexperienceliveonlinetraining,plusbooks,videos,anddigitalcontentfromnearly200publishers. Startyourfreetrial Don’tleaveempty-handed GetMarkRichards’sSoftwareArchitecturePatternsebooktobetterunderstandhowtodesigncomponents—andhowtheyshouldinteract. It’syours,free. Getitnow Close