New tags introduced in HTML5 now have basic support in mPDF, and will thus support CSS style references.

The following are treated as block elements similar to <div>:

<article> <aside> <details> <figure> <figcaption> <footer> <header> <hgroup> <nav> <section> <summary>

The following are treated as in-line elements:

<time> <mark>

Mark is set by default to highlight in yellow in config.php using $defaultCSS e.g. mark

Progress and meter are discussed below:

Progress: accepts the attributes value and max. A progress element without a value is called an indeterminate progress bar. Text between the opening and closing tags is not displayed.

CSS styles properties can be applied: display, visibility, margin, padding, border, vertical-align, width, height and opacity. HTML attributes width and height are supported, although not officially part of the spec.

Example:

<progress value="5" max="10">50%</progress>

• Indeterminate
• Progress: 0%
• Progress: 100%
• Progress: 57%

Meter: accepts the attributes min, max, value, optimum, low, and high. Text between the opening and closing tags is not displayed.

CSS styles properties can be applied: display, visibility, margin, padding, border, vertical-align, width, height and opacity. HTML attributes width and height are supported, although not officially part of the spec.

Example:

<meter value="5" max="10" min="1" low="2" high="8" optimum="5.6">5</meter>

• Meter: full
• Preferred usage
• Too much traffic
• Much too much traffic

Custom appearances for <meter> and <progress>

Meter (and to a lesser extent progress) can be used with custom appearances e.g. by using optimum to display the average, and low/high to indicate 90th centiles

Custom appearances can be written by editing the script in classes/meter.php - Use a custom attribute of type="anyname" which is passed to the class as a variable e.g.

<meter type="2" value="612.7" optimum="580.4" min="517.0 " max="642.7" low="542" high="600">612.7</meter>

min-height, min-width, max-height and max-width are now supported in CSS style sheets for <img> (only).

background: url(data:image/gif;base64,...) is now supported in CSS style sheets (gif, png and jpeg).

The script handling Arabic text (RTL) was rewritten in mPDF 5.5 with improved support for Pashto/Sindhi/Urdu/Kurdish, especially for joining characters and added new presentation forms.

Some characters in Pashto/Sindhi/Urdu/Kurdish do not have Unicode values for the final/initial/medial forms of the characters. However, some fonts include glyphs for these characters "un-mapped" to Unicode (including XB Zar and XB Riyaz, which are bundled with mPDF).

By editing config_fonts.php and adding:

\'unAGlyphs\' => true,

to appropriate fonts, this will force mPDF to use unmapped glyphs. It requires the font file to include a Format 2.0 POST table which references the glyphs by name as e.g. uni067C.med or uni067C.medi

XB Riyaz, XB Zar, Arabic Typesetting (MS), Arial (MS) all contain this table. NB If you want to know if a font file is suitable, you can open a .ttf file in a text editor and search for "uni067C.med" - if it exists, it may work!

Using "unAGlyphs" forces subsetting of fonts, and will not work with SIP/SMP fonts (using characters beyond the Unicode BMP Plane).

mPDF maps these characters to part of the Private Use Area allocated by Unicode U+F500-F7FF. This could interfere with correct use if the font already utilises these codes (unlikely).