Конвертация php в word

• addExternalFile()
• embedHTML()

• It is not compatible with LibreOffice, OpenOffice and some DOCX readers
• There is not much flexibility in the rendering options

• The HTML code is translated into native WordML code so the resulting document may be rendered with all DOCX readers and transformed to PDF with the help of the phpdocx conversion plugin (included in the Advanced and Premium versions of the library).
• One may use native Word styles for paragraphs and tables.
• One may filter the HTML content by ids, CSS classes and HTML tags or even by simple XPath expressions.
• One may add the images included in the HTML code within the Word document or as external resources.
• Headings may get included into a Table of Contents.
• It allows the direct insertion of HTML+CSS code or the embedding and preprocessing of an external web page.
• The resulting WordML may be also inserted in headers and footers and other contents.

Simple HTML code

The code needed to insert some plain HTML is as simple as this:

And you will get as a result (download the corresponding document):

Let us first offer a few simple examples that illustrate the most elementary procedures:

And you will get as a result (download the corresponding document):

External HTML source

Sometimes one may need to get the HTML and CSS from existing external files but as we will now show this also turns to be extremely simple.

Let us assume that the HTML code above proceeds from an external HTML page: simpleHTML.html that links to a CSS stylesheet: styles.css.

Then the following code will render exactly the same results:

Notice that the only differences are:

HTML code embedded within a Word table

It may well be that you choose not to embed directly the HTML code into the document but rather insert it within another document element like a table or a header/footer.

This can be achieved in a very simple way using the WordFragment class.

You may modify slightly the previous example:

Obtaining now the following result (download the corresponding Word document):

Embedding images

To include images is equally simple. One may choose to include the images within the document (with the option downloadImages set to true) or keep them as an externally linked resource (in that case you should make sure that the image is available to the final users).

A simple example that makes use of this simple web page with an image reads as follows:

The resulting Word document looks as follows (download the corresponding document):

Notice that, as in this case you have not declared the width and height attributes of the image, phpdocx reads its properties from the image header and inserts it with a resolution of 96 dpi (default resolution). One may, of course, choose custom width and height to obtain the desired results.

Supported HTML tags and attributes

phpdocx parses all the most commonly used HTML tags and attributes.

It is important to take into account that the HTML and OOXML that Word is based on have different goals so at some points the translation from one to the other should include certain compromises that are not universally valid for all applications. Fortunately it is not difficult to find convenient workarounds that offer a close to perfect Word rendering.

The list of currently parsed HTML elements include:

Block type HTML elements

Inline type HTML elements

HTML web form elements

• border: One may introduce combined properties as, for example, «1px solid red». Some comments about units and format:
  • Units: One may use pixels, points or ems.
  • Styles: The available styles are: None, dotted, dashed, solid, double, groove, inset, outset.
  • Colors: One can enter hexadecimal values like #ff0000 or, if it exists, standard CSS colors like «red» (see standard CSS color names list).
• border-[top, right, bottom, left]: Same as above but letting you choose different borders styles for top, right, bottom and left borders.
• border-[top, right, bottom, left]-color: Sets up independently the color for each border.
• border-[top, right, bottom, left]-style: Sets up independently the style (solid, dotted…) for each border.
• border-[top, right, bottom, left]-width: Sets up independently the size (in pixels, points or ems) for each border.
• border-collapse: Allows to collapse or separate.
• background-color: Hexadecimal or standard CSS value.

• margin and padding: One may use pixels, points or ems.
• margin-[top, right, bottom, left] and padding-[top, right, bottom, left]: Same as above but letting you choose different margins and paddings for top, right, bottom and left.

• page-break-after: If set to avoid is equivalent to the Word property of «Keep with next paragraph».
• page-break-inside: If set to avoid is equivalent to the Word property of «Keep lines together».
• page-break-before: If set to always is equivalent to the Word property of «Break page before». If it is set to avoid turns on Word widow/orphan control.

• font: If one uses the shorthand properties one need to preserve the following order: font: font-style font-variant font-weight font-size/line-height font-family.
• font-family: Make sure to include a font family that may be supported by the Word interface (practically all the usual ones). The default value is «serif».
• font-size: The default size is 12pt.
• font-style: May be normal, italic or oblique.
• font-variant: May be normal or small-caps.
• font-weight: Only recognise bold or bolder that are converted into bold in Word.
• line-height: May be set in any of the available units.
• color: Hexadecimal value or standard CSS values.
• text-decoration: May be underline or line-through.
• text-align: The available values are left, center, right or justify.
• text-indent: May be set in any of the available units.
• text-transform: May be set to uppercase.

• float: Can be none, left or right.
• vertical-align: Can be given in pixels, points or ems or like super, sub, top, text-top, middle, baseline, bottom and text-bottom.

The following code illustrates how to create a lower letter and roman style list style and use it with HTML:

• list-style and list-style-type: When any of them is set to none no bullets or numbering is included and the CSS properties on margin and padding are used, for all other lists types the standard Word defaults are used.

HTML Extended, available in Premium licenses, include additional options to generate lists with different styles on its levels.

The following example creates a custom list styles with two different styles for the same level, applied to an HTML:

Using native Word formatting with HTML

One of the nicest features of the embedHTML method is that it allows to apply customized Word formatting for paragraphs and tables.

One may write plain HTML with little or none styling and yet generate a very sophisticated Word document.

The default base template already includes all standard Word styles for headings, paragraphs and tables. You may get all the available styles via the phpdocx parseStyles method.

Of course, you may choose a different base template that better suits your needs or even explicitely import styles from other DOCX via the phpdocx importStyles method.

Another useful functionality of the embedHTML method is the possibility to filter the HTML content included in the Word document.

One may want to reuse HTML code that has been generated with a different goal in your Word document. A typical example is given by the contents of an existing web page from which you just want to extract its contents without menus or navigation that does not really fit into a Word document.

The filtering can be done in two different ways, which are:

Basic expressions

One can select a set of HTML elements by tag, id or class (’’, ‘#myId’ or ‘.myClass’) in a very simple way as follows:

The resulting Word document reads (download the corresponding Word document):

Using XPath expressions

One may choose to filter by more complex expressions that should take the form of valid PHP XPath expressions.

For example, if in the previous example we would have set up the filter option to: //p[@class=»heading2″]|//ul|//table we would have obtained instead a Word document that will only include the paragraph with class heading2, the unordered list and the table.

We obtain this time (download the corresponding Word document):

• ‘parseAnchors’ (boolean): If set to true it will parse the anchors included in the HTML file. Its default value is false.
• ‘parseDivs’ (paragraph, table): Although all CSS properties of div tags are inherited divs themselves are not parsed by default because there is no WordML element that exactly resemble its properties. When set to paragraph the phpdocx parser tries to parse them as standard paragraphs (this may be a useful option for HTML coming from certain WYSIWYG editors). If set to table, it renders the div as a Word table. Its default value is false.
• ‘parseFloats’ (boolean): When set to true phpdocx tries to parse the floating divs and paragraphs as floating tables. Sometimes the results are impredictable, so use with care. Its default values is false.
• ‘baseURL’ (boolean): Forces the base URL of the relative links to the desired value. This option may be particularly useful if the HTML code is obtained via the PHP file_get_contents method or any similar procedure.

Inserting HTML into Word templates

All the preceding examples have their match in the case we are working with templates by means of the replaceVariableByHtml method.

All the available options are the same as before although we have to give two extra pieces of extra info, namely:

A short example will illustrate it better.

HTML Extended and CSS Extended

Premium licenses include HTML Extended and CSS Extended modes to invoke phpdocx methods with custom HTML tags and apply custom styles not supported by standard HTML tags and CSS styles.

Thus, it is possible to insert headers, footers, comments, table of contents, cross-references, sections and many other contents and styles. All of it integrated with the supported HTML tags and CSS styles.

HTML Extended and CSS Extended have an extra set of methods and options designed to make conversions more flexible and efficient:

HTML Extended also allows to customize the tags you are working with. E.g., to use header instead of the default phpdocx_header. All the documentation regarding this feature is available on the HTML Extended page.