{"id":52243,"date":"2009-10-15T00:01:00","date_gmt":"2009-10-15T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2009\/10\/15\/hey-scripting-guy-how-can-i-list-the-unique-words-from-a-microsoft-office-word-document\/"},"modified":"2009-10-15T00:01:00","modified_gmt":"2009-10-15T00:01:00","slug":"hey-scripting-guy-how-can-i-list-the-unique-words-from-a-microsoft-office-word-document","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-how-can-i-list-the-unique-words-from-a-microsoft-office-word-document\/","title":{"rendered":"Hey, Scripting Guy! How Can I List the Unique Words from a Microsoft Office Word Document?"},"content":{"rendered":"

\"Bookmark<\/a> <\/p>\n

\"Hey,<\/p>\n

Hey, Scripting Guy! I need to obtain a listing of unique words from a Microsoft Word document. I know that there is the Sort-Object<\/b> cmdlet that can be used to retrieve unique items, and there is the Get-Content<\/b> cmdlet that can read the text of a text file. However, the Get-Content<\/b> cmdlet is not able to read a Microsoft Word document, and I do not think I can use the Sort-Object<\/b> cmdlet to produce a unique listing of words. <\/p>\n

— EM<\/p>\n

\"Hey,<\/p>\n

Hello EM, <\/p>\n

Microsoft Scripting Guy Ed Wilson here. I am listening to the Bourbon Street Rag on my Zune, and was day dreaming a bit about my last trip to New Orleans. The really good news is that Tech∙<\/span>Ed 2010 will be held in New Orleans, and (drum roll please) the Microsoft Scripting Guys already have set aside the budget to be there! “Do you know what it means to miss New Orleans?” the song continues to amble. Now the upbeat sound of Van Halen is coming from my Zune. Quite the segue! It’s a shuffle kind of day. <\/p>\n

I am having a great day today, and I have responded to several really cool questions sent to scripter@microsoft.com<\/font><\/a> e-mail. EM, your question was really interesting, and I decided to write the GetUniqueWordsFromWord.ps1 script that is shown here. <\/p>\n

GetUniqueWordsFromWord.ps1<\/strong><\/font><\/p>\n

$document = “C:fsoWhyUsePs2.docx”
$app = New-Object -ComObject word.application
$app.Visible = $false
$doc = $app.Documents.Open($document)
$words = $doc.words
$outputObject = @()
“There are ” + $words.count + ” words in the document”
For($i = 1 ; $i -le $words.count ; $i ++)
     {
      $object = New-Object -typeName PSObject
       $object |
       Add-Member -MemberType noteProperty -name word -value $words.item($i).text
       $outputObject += $object
     }
$doc.close()
$app.quit()
$outputObject | sort-object -property word -unique<\/p>\n

<\/font><\/font><\/span><\/p>\n

Before jumping into the GetUniqueWordsFromWord.ps1 script, take a look at the Word document seen here:<\/p>\n

\"Image
<\/font><\/a><\/p>\n

As you can see, there are 231 words in the document. Many of these words are unique such as “after,” but some of the words are not unique such as the word “the.” The GetUniqueWordsFromWord.ps1 script will display a list of all the unique words in the Microsoft Word document. <\/p>\n

To display the unique words in the Microsoft Word document, the GetUniqueWordsFromWord.ps1 script begins by using the $document<\/b> variable to hold the path to the Microsoft Word document that is to be analyzed. Next, the word.application<\/b> COM object is used to create an instance of the application object<\/a>. The application<\/b> object is the main object that is used when working with the Microsoft Word automation model. The visible property<\/font><\/a> is set to $false<\/b>, which means the Microsoft Word document will not be visible while the Windows PowerShell script is running. This section of the script is shown here:<\/p>\n

$document = “C:fsoWhyUsePs2.docx”<\/p>\n

<\/font><\/span><\/p>\n

$app = New-Object -ComObject word.application<\/p>\n

<\/font><\/span><\/p>\n

$app.Visible = $false<\/p>\n

<\/font><\/span><\/p>\n

After the application object has been created, the documents property<\/font><\/a> from the application<\/b> object is used to obtain an instance of the documents collection object<\/a>. The open method<\/a> from the documents<\/b> collection object is used to open the document that is specified in the $document<\/b> variable. The open<\/b> method from the documents<\/b> collection object returns a document object<\/font><\/a> that is stored in the $doc<\/b> variable. This line of the script is shown here:<\/p>\n

$doc = $app.Documents.Open($document)<\/p>\n

<\/font><\/span><\/p>\n

The words property<\/font><\/a> of the document<\/b> object is used to return a words collection object<\/a> that represents all of the words in the document. The words<\/b> collection object is stored in the $words<\/b> variable as seen here:<\/p>\n

$words = $doc.words<\/p>\n

<\/font><\/span><\/p>\n

After the words<\/b> collection has been created, it is time to create an empty array that will be used to store the custom object the script will create. It is also time to display a message on the Windows PowerShell console that indicates how many words are in the document. Please note that in most cases, the number of words displayed by the count<\/b> property of the words<\/b> collection object will not correspond with the number that is shown at the bottom of the Microsoft Word document. This is because different characters are considered words by the count<\/b> property than the ones shown in the document. This section of the script is seen here: <\/p>\n

$outputObject = @()<\/p>\n

<\/font><\/span><\/p>\n

“There are ” + $words.count + ” words in the document”<\/p>\n

<\/font><\/span><\/p>\n

The for<\/b> statement is used to set up a loop that will be used to walk through the collection of words stored in the words<\/b> collection object. The loop begins at 1 and continues as long as the value of the variable $i<\/b> is less than or equal to the count of the number of words in the collection. On each pass through the loop, the value of the $i<\/b> variable will be incremented by 1. This is seen here:<\/p>\n

For($i = 1 ; $i -le $words.count ; $i ++) <\/p>\n

<\/font><\/span><\/p>\n

     {<\/p>\n

<\/font><\/span><\/p>\n

Inside each loop, a custom Windows PowerShell PSObject is created by using the New-Object<\/b> cmdlet and the returned PSObject is stored in the $object<\/b> variable. This is shown here:<\/p>\n

      $object = New-Object -typeName PSObject<\/p>\n

<\/font><\/span><\/p>\n

The Add-Member<\/b> cmdlet is used to add a noteProperty<\/b> to the PSObject stored in the $object<\/b> variable. The name of the noteProperty<\/b> is word<\/b>, and the value is the next word in the collection of words. The item method<\/font><\/a> is used to retrieve the word from the words<\/b> collection by index number. This is not a direct retrieval, however, because the item method returns a range object<\/font><\/a> and not a word<\/b> object. The range<\/b> object does have a text property<\/font><\/a> that is used either to get or to set the value of the text in the selected range. Because this range is a single word, the text<\/b> property from the range<\/b> object retrieves the next word from the words<\/b> collection object. This is shown here:<\/p>\n

       $object | <\/p>\n

<\/font><\/span><\/p>\n

       Add-Member -MemberType noteProperty -name word -value $words.item($i).text <\/p>\n

<\/font><\/span><\/p>\n

After the word<\/b> property has been added to the PSObject, the PSObject that is stored in the $object<\/b> variable is added to the $outputObject<\/b> array, as shown here:<\/p>\n

       $outputObject += $object<\/p>\n

<\/font><\/span><\/p>\n

     }<\/p>\n

<\/font><\/span><\/p>\n

The document<\/b> object is closed by using the close method<\/a> and the application<\/b> object is destroyed by calling the quit method<\/a>. This is shown here:<\/p>\n

$doc.close()<\/p>\n

<\/font><\/span><\/p>\n

$app.quit()<\/p>\n

<\/font><\/span><\/p>\n

The array of objects stored in the $outputObject<\/b> variable is piped to the Sort-Object<\/b> cmdlet, where the object is sorted on the word<\/b> property and only unique words are displayed on the Windows PowerShell console. This line of code is shown here:<\/p>\n

$outputObject | sort-object -property word -unique<\/p>\n

<\/font><\/span><\/p>\n

When the script is run, the output shown in the following image is displayed:<\/p>\n

<\/b><\/p>\n

\"Image
<\/font><\/a><\/p>\n

Well, EM, that is about all there is to retrieving unique words from a Microsoft Word document. <\/p>\n

If you want to know exactly what we will be looking at tomorrow, follow us on Twitter<\/font><\/a> or Facebook<\/a>. If you have any questions, send e-mail to us at scripter@microsoft.com<\/font><\/a> or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson and Craig Liebendorfer, Scripting Guys<\/p>\n

<\/span><\/b><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Hey, Scripting Guy! I need to obtain a listing of unique words from a Microsoft Word document. I know that there is the Sort-Object cmdlet that can be used to retrieve unique items, and there is the Get-Content cmdlet that can read the text of a text file. However, the Get-Content cmdlet is not able […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[84,49,3,45],"class_list":["post-52243","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-microsoft-word","tag-office","tag-scripting-guy","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Hey, Scripting Guy! I need to obtain a listing of unique words from a Microsoft Word document. I know that there is the Sort-Object cmdlet that can be used to retrieve unique items, and there is the Get-Content cmdlet that can read the text of a text file. However, the Get-Content cmdlet is not able […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52243","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=52243"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52243\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=52243"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=52243"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=52243"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}