Рейтинг: 5.0/5.0 (1905 проголосовавших)Категория: Windows: Конверторы
Promoted by
Save Your DOC File as DOCXOpen your DOC file in Microsoft Word. Make sure your version is 2007 or later. Click the "File" tab to open the Word Backstage view. Click "Save As." Select the folder where you want to save your document or "Browse" to choose a folder that is not displayed. The "Save As" dialog window will open. In the "Save as type" menu, select the "Word Document (.docx)" option. Click the "Save" button, and a copy of your file will be saved in DOCX format.
Notes on Converting DocumentsSaving your DOC file in DOCX creates a new copy of your file. Your original DOC file will not be significantly changed.
The conversion to DOCX format may cause minor formatting changes to your document. Before you continue, review it and fix any formatting issues you see.
You can also convert your documents online using your Web browser. Zamzar, Online-Convert and Office Converter provide free online document conversion. If you have a large number of documents you need to convert, Office Converter allows you to convert several documents at once in batches.
Batch Doc to Docx Conversion — Doc to Docx Batch Conversion Utility
Want to Convert Doc to Docx format? Office Upgrade is the one stop solution to convert Old MS Word (.doc) file into newer version (.docx) format. Perform Batch Doc to Docx conversion with the latest and advanced Office Upgrade software. Its executes advance options to convert single or multiple DOC, XLS and PPT format data to the Latest versions like Docx, XLSX and PPTX safely without losing your data. Doc to Docx Batch Conversion software is useful program to access upgraded documents into Office 2013 file format. Try the demo edition of Doc to Docx Batch conversion software free of cost, but demo edition converts only single file from Doc to Docx format. Purchase Office Upgrade software releasing only 49 USD to completely upgrade Doc to Docx, XLS to XLSX and PPT to PPTX files format safely. More: www.wordrecovery.net/batch-doc-to-docx-conversion.html
Convert all docx (.docx) documents from a folder to doc (.doc) documents in Word
Supposing you want to convert all docx documents from a folder as shown in the below screenhot to doc documents, you can quickly convert all docx documents from a folder to doc documents as follows:
1. Open your Office Word applications, and then applying this utility by clicking Click Enterprise > Doc / Docx. In the Document Format Convert dialog box, please configure the settings as shown in the below screenshot.
A. Please select a folder which contatins the docx documents you want to convert to doc documents by clicking the 
button from the Source file folder section..
B. Please select a folder to save the documents after converting by clicking the button from the Save to section.
2. Click Start button to begin converting. You will see all results as show in the below screenshots.
Microsoft has a bulk conversion utility that can convert multiple DOC files to DOCX files. This blog post presents very basic information on its use. This utility has been around for a while, but a fair number of people don’t know of its existence. Because it’s a powerful tool designed to convert all files on a server (or even a bunch of servers), its use is a little cryptic. This is fine for IT professionals, but if all you want to do is bulk convert a single directory of DOC files, this post shows what you need to do.
This blog is inactive.
Blog TOC Before you can use this tool, you need to install the Microsoft Office Compatibility Pack. While the compatibility pack is primarily used with Office 2003 to allow it to load and save Open XML files, in essence, the compatibility pack is comprised of file format converters, which the Office File Converter (OFC) uses. To use OFC, you need to install the compatibility pack even if you only have Office 2007 installed. Download the compatibility pack here .
Next, you need to download and install the Microsoft Office Migration Planning Manager (OMPM). This contains a bunch of stuff, but for bulk file conversion, we are primarily interested in just one tool, OFC.EXE. Download the Microsoft Office Migration Planning Manager here .
When installing, as usual, you will select the installation directory. OFC.EXE is in the Tools directory under the installation directory. In addition, in that directory, there is a sample OFC.INI file. To run OFC.EXE, you need to create an OFC.INI, and place it in the directory where you run OFC.EXE from.
For my simple example, I want to convert all DOC files found in the C:UsersericwhitDocuments 8-09-19-Doc, and place the converted DOCX files in C:UsersericwhitDocuments 8-09-19-Docx. Here is the OFC.INI file for this scenario:
LogDestinationPath=C:UsersericwhitDocuments 8-09-19-Conversion-Log
TimeOut = 3
[ConversionOptions]
; FullUpgradeOnOpen: if set to 1, Word documents will be fully converted to the OpenXML format
; if set to 0 (default), Word documents will be saved in the OpenXML format in compatibility mode
FullUpgradeOnOpen=1
MacroControl=0
[FoldersToConvert]
fldr=C:UsersericwhitDocuments 8-09-19-Doc
[ConversionInfo]
SourcePathTemplate=********************
DestinationPathTemplate=C:UsersericwhitDocuments 8-09-19-Docx
The SourcePathTemplate and DestinationPathTemplate provide extremely flexible configuration for bulk conversion of a large number of directories. They allow an IT professional to, say, convert files from one entire server, place the converted files on a different server, and use various sub-paths of the path of the source document to form the path where the DOCX will be placed. Fully configuring SourcePathTemplate and DestinationPathTemplate is beyond the scope of this blog post. The configuration above basically specifies to just take all of the DOC files in the specified fldr directory, and place them in the specified DestinationPathTemplate directory.
So, place a modified version of the above INI file in some directory, and run OFC.EXE from that directory. You will see something like this:
Your newly created DOCX files will be in the directory you specified in DestinationPathTemplate.
Batch DOC and DOCX Converter Doc to Docx and Docx to Doc Batch Converter. Docx to Doc and Doc to Docx Batch Converter convert Word 2003 to/from Word 2007.
Batch DOC AND DOCX Converter is a Word DOC to DOCX, DOCX to DOC Batch Converter that can convert Word DOC to DOCX and DOCX to DOC easily. Batch DOC TO DOCX Converter supports powerful search for a lot of files. A DOC and DOCX converter for Word.
Batch DOC AND DOCX Converter supports project and command line. Batch DOC AND DOCX Converter has a friendly GUI so it is used very easily. Batch DOC AND DOCX Converter Drag and Explorer Context supported.
Batch DOC AND DOCX Converter supports an efficient Multi-Thread conversion engine. So you could control the conversion action very easily. You can stop or pause and continue it in any time.
You can save your conversion work in a project file (.batch-doc2doc) for re-use. You can run the batch-doc2doc project in Microsoft Windows Explorer or command line directly.
The main features of Batch DOC and DOCX Converter :
CNET editors' review 
http://download.cnet.com/Batch-DOCX-to-DOC-Converter/3000-18483_4-10909592.html
Batch DOCX To DOC Converter provides an impressively simple way to convert Word files. Its setup ensures that users of all skill level will find success.
At first, we needed to visit the program's Help file, as its interface was almost too basic. Its layout has very few command icons and, after reading the help file, it only took a few minutes to master. We quickly grew to appreciate the program's lack of diversions and have confidence that users of any skill level would feel equally comfortable. Batch DOCX To DOC Converter allowed us to choose single files, multiple files, or entire folders with equal ease by surfing through its file tree. All our chosen files were listed with their file location and type on the main screen. Our .doc files were then quickly converted to the newer .docx format and vice versa. We were pleased to find the files appeared in the appropriate destination with all their data intact. The program's best feature was its search engine, which helped track down files the locations of which we didn't know exactly. Overall, this amazingly simple program provided a precise function and did it very well.
Batch DOCX To DOC Converter has a 7-day trial. While we were initially concerned about its interface, this simple program won us over and we recommend it.
Reviewed by: CNET staff on October 05, 2009
Keywords that are used most of the time to find www.docx2doc.com website are these: Os x that are also used to find www.docx2doc.com in search engines.
The importance of a keyword refers to the relevance of the keyword appearing on a page. Several elements may influence the importance of the keyword. The presence of the keywords in the tags and titles is analyzed by search engines and bold and italic tags are evaluated as well, the percentage of the keywords in the texts and on pages is calculated.
In the event of calculating the relevance of the keyword, website internal elements such as presence of the keywords in meta tags (Keywords Description and tags) and also in H1, H2 and H3 heading tags are also considered. Internal linking, document form, used technologies are taken into account.
For what reason are these data so valuable?
The following table shows the analysis of the main page of www.cnn.com It was suggested that and how search engines could rank and crawl the mentioned website by using data about the internal factors of the domain.
It is how we obtained the list of keywords that will represent the main page of the website in SERPs. Afterwards, keywords importance was used to assess websites competitiveness for the concerned keyword. As to the keyword cost, it was raised by using public available data as well.
The table is meant to help webmasters improve their sites and to make the most of advertisement gains.
Create and manipulate Word documents programmatically using DocX.
In a recent post, I extolled the virtues of a wonderful OSS library I had found for working with Excel data programmatically, LinqToExcel . In that post, I also mentioned a fantastic library for working with Word docs as well, and promised to discuss it in my next post. This is that post.
The big pain point in working with MS Word documents programmatically is. the Office Interop. To get almost anything done with Word (including simply pulling the text out of the document, you pretty much need to use Interop, which also means you have to have Word installed on the local machine which is consuming your application. Additionally, my understanding is that there are issues with doing Word automation on the server side.
Interop is essentially a giant wrapper around the ugliness that is COM, and the abstraction layer is thin indeed. If you need to automate MS Office applications, Interop (or going all the way down to the COM level) is pretty much the only way to do it, and obviously, you need to have Office installed on the client machine for it to work at all.
Often times though, we don't so much need to automate the office application directly so much as get at the contents of Office file (such as Word or Excel files). Dealing with all that Interop nastiness makes this more painful than it needs to be.
Thankfully, the open source D ocX by Cathal Coffey solves both problems nicely, and unlike Interop, presents an easy-to-use, highly discoverable API for performing myriad manipulations/extractions against the Word document format (the .docx format, introduced as of Word 2007). Best of all, DocX does not require that Word or any other Office dependencies be installed on the client machine! The full source is available from Coffey's Codeplex repo . or you can add DocX to your project using Nuget.
10/2/2013 - NOTE: It has been noted by several commentors on Reddit and elsewhere that the MS official library OpenXml serves the same purpose as Docx, and after all, is the "official" library. I disagree - the OpenXml library "does more" but is inherently more complex to use. While it most certainly offers additional functionality not present in DocX, the DocX library creates a much simpler and more meaningful abstraction for what I find to be the most common use-cases working with Word documents programmatically. As always, the choice of libraries is a matter of preference, and to me, one of "Right tool for the job."
1/23/2014 - NOTE: I mentioned in the opening paragraph the OSS project LinqToExcel, which is a fantastic library. However, LinqToExcel takes a dependency on the Access Database Engine, which can create issues when (for example) deploying to a remote server or other environment where administrative privileges may be limited. I discovered another OSS library with no such dependencies. You can read about it at Use Cross-Platform/OSS ExcelDataReader to Read Excel Files with No Dependencies on Office or ACE
In this post, we will look at a few of the basics for using this exceptionally useful library. Know that under the covers and with a little thought, there is a lot of functionality here beyond what we will look at in this article.
Add DocX to your project using NugetNOTE: When adding Nuget packages to your project, consider keeping source control bloat down by using Nuget Package Restore so that packages are downloaded automatically on build rather than cluttering up your repo.
As with LinqToExcel, you can add the DocX library to your Visual Studio solution using the Nuget Package Manager Console by doing:
Install DocX using the Nuget Package Manager Console:Alternatively, you can use the Solution Explorer. Right-click on the Solution, select "Manager Nuget Packages for Solution," and type "DocX in the search box (make sure you have selected "Online" in the left-hand menu). When you have located the DocX package, click Install:
Install DocX using the Nuget Package Manager GUI in VS Solution Explorer: Getting Started – Create a Word Document Using the DocX LibraryWanna Quickly create a Word-compatible. docx format document on the fly from your code? Do this (I am assuming you have Word installed on your local machine):
A Really Simple Example:Note in the above we need to add using Novacode; to our namespace imports at the top of the file. The DocX library is contained within this namespace. If you run the code above, a word document should open like this:
Output of Really Simple Example Code:What we did in the above example was:
Until we execute the Save() method, we are working with the XML representation of our new document in memory. Once we save the file to disc, we find a standard Word-compatible file in our Documents/ directory.
Use DocX to Add Formatted Paragraphs – A More Useful ExampleA slightly more useful example might be to create a document with some more complex formatted text:
Create Multiple Paragraphs with Basic Formatting:Here, we have created some Formatting objects in advance, and then passed them as parameters to the InsertParagraph method for each of the two paragraphs we create in our code. When the code executes, Word opens and we see this:
Output from Creating Multiple Formatted ParagraphsIn the above, the FontFamily and Size properties of the Formatting object are self-evident. The Position property determines the spacing between the current paragraph and the next.
We can also grab a reference to a paragraph object itself and adjust various properties. Instead of creating a Formatting object for our headline like we did in the previous example, we could grab a reference as the return from the InsertParagraph method and muck about:
Applying Formatting to a Paragraph Using the Property Accessors:This time, when the program executes, we see THIS:
OH NO YOU DID NOT!
Yes, yes I DID print that headline in Comic Sans. Just, you know, so you could see the difference in formatting.
There is a lot that can be done with text formatting in a DocX document. Headers/Footers, paragraphs, and individual words and characters. Importantly, most of the things you might go looking for are easily discoverable – in other words, the author has done a great job building out his API.
Find and Replace Text Using DocX - Merge Templating, Anyone?Of course, one of the most common things we might want to do is scan a pre-existing document, and replace certain text. Think templating here. For example, performing a standard Word Merge is not very doable on your web server, but using DocX, we can accomplish the same thing. The following example is simple due to space constraints, but you can see the possibilities:
First, just for kicks, we will create an initial document programmatically in one method, then write another method to find and replace certain text in the document:
Create a Sample Document:See the %APPLICANT% placeholder? That is my replacement target (a poor-man's merge field, if you will). Now that we have a private method to generate a document template of sorts, let's add a public method to perform a replacement action:
Find and Replace Text in a Word Document Using DocX:Now, when we run the code above, our output is thus:
Obviously, the preceding example was a little contrived and overly simple. But you can see the potential. If our letter contained additional "merge fields, we could just as easily pass in a Dictionary<string, string> , where the Dictionary contains one or more Key Value Pairs containing a replacement target and a replacement value. Then we could iterate, using the Dictionary Keys as the search string, and replace with the Dictionary values.
DocX Exposes Many of the Most Useful Parts of the Word Object ModelIn this quick article, we have only scratched the surface. DocX exposes most of the stuff we commonly wish we could get to within a Word document (Tables, Pictures, Headers, Footers, Shapes, etc.) without forcing us to navigate the crusty Interop model. This also saves us from some of the COM de-referencing issues which often arise when automating Word within an application. Ever had a bunch of "orphaned" instances of Word (or Excel, etc.) running in the background, visible only in the Windows Task Manager? Yeah, I thought so.
If you need to generate or work with Word documents on a server, this is a great tool as well. No dependencies on MS Office, no need to have Word running. You can generate Word documents on the fly, and/or from templates, ready to be downloaded.
I strongly recommend you check out the project on Codeplex. Also, the project author, Cathal Coffey, discusses much of the DocX functionality on his own blog. If you dig DocX, drop by and let him know. He's really done a fantastic job.
Additional Resources/Items of InterestThe answer is structured to convert all documents, not just Word documents.
Say you got tons of Excel sheets, PowerPoint presentations and Word documents on your computer that were written in Office XP or 2003. How do you convert all these files to the new Office 2007 format.
One option is that you open all of them in the associated Office program and manually save them in the newer (docx, xlsx or pptx) format. Or follow these steps and convert all documents in one go.
Step 1: Download Migration Manager kit and extract it into a new folder - say: c:\office.
office-pack
Step 2: Download and install the Office Pack - this step is required even if you have Microsoft Office 2007 already installed on your computer.
Step 3: Assuming that you extracted the Office Manager files in c:\office directory, go c:\office\tools, open ofc.ini using notepad and add the following line.
fldr=c:\users\labnol\documents
This refers to the folder location that holds your office files. I am pointing this to my Documents folder but it could be different on your machine.
Step 4: Open command prompt and go to c:\office\tools. There you’ll see a utility called ofc.exe - this is the Office File Converter that will convert all old Office files to the new 2007 Office document format in bulk. Run.
convert-docs
Immediately all old Office files in that folder (and sub-folders) will get converted to the new format and are saved in a new folder.
This utility works with Word (doc to docx), Access databases, PowerPoint (ppt to pptx), Visio diagrams, Excel (xls to xlsx) and Microsoft Project files. The conversion may however fail for password protected documents.
