MP4H - A Macro Processeur for HTML Documents

Introduction

The mp4h software is a macro-processor specifically designed to deal with HTML documents. It allows powerful programming constructs, with a syntax familiar to HTML authors.

This software is based on Meta-HTML, written by Brian J. Fox, Even if both syntaxes look similar, source code is completely different. Indeed, a subset of Meta-HTML was used as a part of a more complex program, WML (Website Meta Language) written by Ralf S. Engelschall and which i maintain since january 1999. For licensing reasons, it was hard to hack Meta-HTML and so i decided to write my own macro-processor.

Instead of rewriting it from scratch, i preferred using another macro-processor engine. I chose GNU m4, written by René Seindal, because of its numerous advantages : this software is stable, robust and very well documented. This version of mp4h is derived from GNU m4 version 1.4n, which is a development version.

The mp4h software is not an HTML editor ; its unique goal is to provide an easy way to define its own macros inside HTML documents. There is no plan to add functionalities to automagically produce valid HTML documents, if you want to clean up your code or validate it, simply use a post-processor like tidy.

Command line options

Optional arguments are enclosed within square brackets. All option synonyms have a similar syntax, so when a long option accepts an argument, short option do too.

Syntax call is

mp4h [options] [filename [filename] ...]

Operation modes

Preprocessor features

Limits control

Debugging

Flags are any of:

Description

The mp4h software is a macro-processor, which means that keywords are replaced by other text. This chapter describes all primitives. As mp4h has been specially designed for HTML documents, its syntax is very similar to HTML, with tags and attributes. An important feature has no equivalent in HTML: comments until end of line. All text following three colons is discarded until end of line, like

;;;  This is a comment

Function Macros

The definition of new tags is the most common task provided by mp4h. As with HTML, macro names are case insensitive. In this documentation, only lowercase letters are used. There are two kinds of tags: simple and complex. A simple tag has the following form:

<name [attributes]>

<name [attributs]>
body
</name>

  In macro descriptions below, a slash indicates a complex tag, and a V letter that attributes are read verbatim (without expansion) (see the chapter on macro expansion for further details).

This function lets you define your own tags. First argument is the command name. Replacement text is the function body.

<define-tag foo>bar</define-tag>
<foo>

bar

<define-tag foo>bar</define-tag>

<define-tag foo>
bar
</define-tag>

• whitespace=delete
  Some spaces are suppressed in replacement text, in particular any leading or trailing spaces, and newlines not enclosed within angle brackets.
• endtag=required
  Define a complex tag

  Source
  <define-tag foo>bar</define-tag> <foo>
  Output
  bar

  Source
  <define-tag foo endtag=required>;;; body is: %body</define-tag> <foo>Here it is</foo>
  Output
  body is: Here it is

• attributes=verbatim
  By default attributes are expanded before text is replaced. If this attribute is used, attributes are inserted into replacement text without expansion.

  Source
  <define-tag bar>quux</define-tag> <define-tag foo attributes=verbatim endtag=required> Body: %Ubody Attributes: %Uattributes </define-tag> <foo txt="<bar>">Here we go</foo>
  Output
  Body: Here we go Attributes: txt="<bar>"

This command is similar to the previous one, except that no operation is performed if this command was still defined.

Copy a function. This command is useful to save a macro definition before redefining it.

<define-tag foo>one</define-tag>
<let bar foo>
<define-tag foo>two</define-tag>
<foo><bar>

twoone

Delete a command definition.

<define-tag foo>one</define-tag>
<undef foo>
<foo>

<foo>

Add text to a predefined macro. This mechanism allows modifications of existing macros without having to worry about its type, whether it is complex or not.

<let foo add>
<set-hook foo position=before>
Before</set-hook>
<set-hook foo position=after>
After</set-hook>
<foo 1 2 3 4>

Before10
After

Print current hooks of a macro.

Text inserted with position=before:<get-hook foo position=before>!
Text inserted with position=after:<get-hook foo position=after>!

Text inserted with position=before:
Before!
Text inserted with position=after:
After!

Variables

Variables are a special case of simple tags, because they do not accept attributes. In fact their use is different, because variables contain text whereas macros act like operators. A nice feature concerning variables is their manipulation as arrays. Indeed variables can be considered like newline separated lists, which will allow powerful manipulation functions as we will see below.

This command sets variables.

As above but attributes are read verbatim.

Show variable contents. If a numeric value within square brackets is appended to a variable name, it represents the index of an array. The first index of arrays is 0 by convention.

<set-var version="0.10.1">
This is version <get-var version>

This is version 0.10.1

<set-var foo="0
1
2
3">
<get-var foo[2] foo[0] foo>

200
1
2
3

As above but attributes are not expanded.

<define-tag foo>0.10.1</define-tag>
<set-var version="<foo>">;;;
Here is version <get-var version>
<set-var-verbatim version="<foo>">;;;
Here is version <get-var version>
<set-var-verbatim version="<foo>">;;;
Here is version <get-var-once version>

Here is version 0.10.1
Here is version 0.10.1
Here is version <foo>

All variables are global, there is no variable or macro scope. For this reason a stack is used to preserve variables. When this command is invoked, the first argument is the name of a variable. The value of this variable is put at the top of the stack and this variable is reset to an empty string.

This is the opposite: first argument is a variable name, this variable is set to the value found at the top of the stack, and this value is popped.

Undefine variables.

Returns true when this variable exists.

Increment the variable whose name is the first argument. Default increment is one.

• by=value
  Change increment amount.

<set-var i=10>
<get-var i>
<increment i><get-var i>
<increment i by="-3"><get-var i>

10
11
8

Decrement the variable whose name is the first argument. Default decrement is one.

• by=value
  Change decrement amount.

<set-var i=10>
<get-var i>
<decrement i><get-var i>
<decrement i by="3"><get-var i>

10
9
6

Copie a variable into another.

<set-var i=10>
<copy-var i j>
<get-var j>

10

If this variable is not defined or is defined to an empty string, then it is set to the second argument.

<unset-var title>
<defvar title "Title"><get-var title>
<defvar title "New title"><get-var title>

Title
Title

Show informations on symbols. If it is a variable name, the STRING word is printed as well as the number of lines contained within this variable. If it is a macro name, one of the following messages is printed: PRIM COMPLEX, PRIM TAG, USER COMPLEX or USER TAG

<set-var x="0\n1\n2\n3\n4">
<define-tag foo>bar</define-tag>
<define-tag bar endtag=required>quux</define-tag>
<symbol-info x>
<symbol-info symbol-info>
<symbol-info define-tag>
<symbol-info foo>
<symbol-info bar>

STRING
5
PRIM TAG
PRIM COMPLEX
USER TAG
USER COMPLEX

String Functions

Prints the length of the string.

<set-var foo="0
1
2
3">;;;
<string-length <get-var foo>>
<set-var foo="0 1 2 3">;;;
<set-var l=<string-length <get-var foo>>>;;;
<get-var l>

7
7

Convert to lowercase letters.

<downcase "Does it work?">

does it work?

Convert to uppercase letters.

<upcase "Does it work?">

DOES IT WORK?

Convert to a title, with a capital letter at the beginning of every word.

<capitalize "Does it work?">

Does It Work?

Extracts a substring from a string. First argument is original string, second and third are respectively start and end indexes. By convention first character has a null index.

<set-var foo="abcdefghijk">
<substring <get-var foo> 4>
<substring <get-var foo> 4 6>

efghijk
ef

Replace a regular expression in a string by a replacement text.

<set-var foo="abcdefghijk">
<subst-in-string <get-var foo> "[c-e]">
<subst-in-string <get-var foo> "([c-e])" "\\1 ">

abfghijk
abc d e fghijk

• singleline=true
  when this attribute is used, the ^ symbol represents the beginning of string and $ the end of string. Otherwise they represent the beginning and end of lines.

<set-var foo="abcdefghijk\nabcdefghijk\nabcdefghijk">
<subst-in-string <get-var foo> ".$" "">
<subst-in-string <get-var foo> ".$" "" singleline=true>

abcdefghij
abcdefghij
abcdefghij
abcdefghijk
abcdefghijk
abcdefghij

Performs substitutions inside variable content.

Returns true if first two arguments are equal.

1:<string-eq "aAbBcC" "aabbcc">
2:<string-eq "aAbBcC" "aAbBcC">

1:
2:true

• caseless=true
  Comparison is case insensitive.

1:<string-eq "aAbBcC" "aabbcc" caseless=true>
2:<string-eq "aAbBcC" "aAbBcC" caseless=true>

1:true
2:true

Returns true if the first two arguments are not equal.

1:<string-neq "aAbBcC" "aabbcc">
2:<string-neq "aAbBcC" "aAbBcC">

1:true
2:

• caseless=true
  Comparison is case insensitive.

1:<string-neq "aAbBcC" "aabbcc" caseless=true>
2:<string-neq "aAbBcC" "aAbBcC" caseless=true>

1:
2:

Compares two strings and returns one of the values less, greater or equal depending on this comparison.

1:<string-compare "aAbBcC" "aabbcc">
2:<string-compare "aAbBcC" "aAbBcC">

1:less
2:equal

• caseless=true
  Comparison is case insensitive.

1:<string-compare "aAbBcC" "aabbcc" caseless=true>

1:equal

• caseless=true
  Comparison is case insensitive.
• action=report
  Prints true if string contains regexp.
• action=extract
  Prints the expression matching regexp in string.
• action=delete
  Prints the string without the expression matching regexp in string.
• action=startpos
  Prints the first char of the expression matching regexp in string. If there is no match, returns -1.
• action=endpos
  Prints the last char of the expression matching regexp in string. If there is no match, returns -1.
• action=length
  Prints the length of the expression matching regexp in string.

1:<match "abcdefghijk" "[c-e]+">
2:<match "abcdefghijk" "[c-e]+" action=extract>
3:<match "abcdefghijk" "[c-e]+" action=delete>
4:<match "abcdefghijk" "[c-e]+" action=startpos>
5:<match "abcdefghijk" "[c-e]+" action=endpos>
6:<match "abcdefghijk" "[c-e]+" action=length>

1:true
2:cde
3:abfghijk
4:2
5:5
6:3

Prints an array containing indexes where the character appear in the string.

• caseless=true
  Comparison is case insensitive.

1:<char-offsets "abcdAbCdaBcD" a>
2:<char-offsets "abcdAbCdaBcD" a caseless=true>

1:0
8
2:0
4
8

This command controls which regular expressions are used in the macros described above. There are only two possible values: basic and extended. The former are basic regular expressions and the latter are extended regular expressions. By default extended regular expressions are used.

<set-var foo="abcdefghijk">
<set-regexp-syntax type=basic>
<subst-in-string <get-var foo> "([c-e]+)" ":\\1:">
<subst-in-string <get-var foo> "\\([c-e]\\{1,\\}\\)" ":\\1:">
<set-regexp-syntax type=extended>
<subst-in-string <get-var foo> "([c-e]+)" ":\\1:">
<subst-in-string <get-var foo> "\\([c-e]\\{1,\\}\\)" ":\\1:">

abcdefghijk
ab:cde:fghijk

ab:cde:fghijk
abcdefghijk

Prints actual regexp type.

<get-regexp-syntax>

extended

Arrays

With mp4h one can easily deal with string arrays. Variables can be treated as a single value or as a newline separated list of strings. Thus after defining

<set-var digits="0
1
2
3">

<get-var digits>
<get-var digits[2]>

0
1
2
3
2

Returns an array size which is the number of lines present in the variable.

<array-size digits>

4

Add a value (or more if this value contains newlines) at the end of an array.

<array-push digits "10\n11\n12">
<get-var digits>

0
1
2
3
10
11
12

Remove the toplevel vale of an array and returns this string.

Add a value at the end of an array if this value is not already present in this variable.

<array-add-unique digits 2>
<get-var digits>

0
1
2
3
10
11
12

• caseless=true
  Comparison is case insensitive.

Concatenates all arrays into the first one.

<set-var foo="foo">
<set-var bar="bar">
<array-concat foo bar><get-var foo>

foo
bar

If value is contained in array, returns its index otherwise returns -1.

<array-member digits 11>

5

• caseless=true
  Comparison is case insensitive.

Shifts an array. If offset is negative, indexes below 0 are lost. If offset is positive, first indexes are filled with empty strings.

<array-shift digits 2>
Now: <get-var digits>
<array-shift digits -4>
And: <get-var digits>

Now: 

0
1
2
3
10
11
12

And: 2
3
10
11
12

• start=start
  Change origin of shifts (default is 0).

  Source
  <array-shift digits -2 start=2><get-var digits>
  Output
  2 3 12

Sort lines of an array in place. Default is to sort lines alphabetically.

<sort digits><get-var digits>

12
2
3

• caseless=true
  Comparison is case insensitive.
• numeric=true
  Sort lines numerically

  Source
  <sort digits numeric=true><get-var digits>
  Output
  2 3 12

• sortorder=reverse
  Reverse sort order

  Source
  <sort digits numeric=true sortorder=reverse>;;; <get-var digits>
  Output
  12 3 2

Numerical operators

These operators perform basic arithmetic operations. When all operands are integers result is an integer too, otherwise it is a float. These operators are self-explanatory.

<add 1 2 3 4 5 6>
<add 1 2 3 4 5 6.>

21
21.000000

<define-tag factorial whitespace=delete>
<ifeq %0 1 1 <multiply %0 "<factorial <substract %0 1>>">>
</define-tag>
<factorial 6>

720

Unlike functions listed above the modulo function cannot handle more than 2 arguments, and these arguments must be integers.

<modulo 345 7>

2

Those functions compare two numbers and returns true when this comparison is true. If one argument is not a number, comparison is false.

Returns true if first argument is greater than second.

Returns true if first argument is lower than second.

Returns true if arguments are equal.

Returns true if arguments are not equal.

Relational operators

Returns true if string is empty, otherwise returns an empty string.

Returns the last argument if all arguments are non empty.

Returns the first non empty argument.

Flow functions

This function groups multiple statements into a single one. Some examples will be seen below with conditional operations.

A less intuitive but very helpful use of this macro is to preserve newlines when whitespace=delete is specified.

<define-tag text1>
Text on
3 lines without
whitespace=delete
</define-tag>
<define-tag text2 whitespace=delete>
Text on
3 lines with
whitespace=delete
</define-tag>
<define-tag text3 whitespace=delete>
<group "Text on
3 lines with
whitespace=delete">
</define-tag>
<text1>
<text2>
<text3>

Text on
3 lines without
whitespace=delete

Text on3 lines withwhitespace=delete
Text on
3 lines with
whitespace=delete

Note that newlines are suppressed in text2 and result is certainly unwanted.

• separator=chaîne
  By default arguments are put aside. This attribute define a separator inserted between arguments.

Prints its arguments without expansion. They will never be expanded unless the expand tag is used to cancel this noexpand tag.

Annule l'effet de la balise noexpand.

<subst-in-string "=LT=define-tag foo>bar</define-tag>" "=LT=" "<">
<foo>
<subst-in-string "=LT=define-tag foo>quux</define-tag>" "=LT=" "<noexpand "<">">
<foo>

bar
<define-tag foo>quux</define-tag>
bar

If string is non empty, second argument is evalled otherwise third argument is evalled.

<define-tag test whitespace=delete>
<if %0 "yes" "no">
</define-tag>
<test "string">
<test "">

yes
no

If first two arguments are identical strings, third argument is evalled otherwise fourth argument is evalled.

If first two arguments are not identical strings, third argument is evalled otherwise fourth argument is evalled.

When argument is not empty, its body fuction is evalled.

While condition is true, body function is evalled.

<set-var i=10>
<while <gt <get-var i> 0>>;;;
  <get-var i> <decrement i>;;;
</while>

10 9 8 7 6 5 4 3 2 1 

This macro is similar to the foreach Perl's macro: a variable loops over array values and function body is evalled for each value. first argument is a generic variable name, and second is the name of an array.

<set-var x="1\n2\n3\n4\n5\n6">
<foreach i x><get-var i> </foreach>

1 2 3 4 5 6 

• start=start
  Skips first indexes.

  Source
  <set-var x="1\n2\n3\n4\n5\n6"> <foreach i x start=3><get-var i> </foreach>
  Output
  4 5 6

• end=end
  Stops after index has reached that value.

  Source
  <set-var x="1\n2\n3\n4\n5\n6"> <foreach i x end=3><get-var i> </foreach>
  Output
  1 2 3

• step=step
  Change index increment (default is 1). If step is negative, array is treated in reverse order.

  Source
  <set-var x="1\n2\n3\n4\n5\n6"> <foreach i x step=2><get-var i> </foreach> <foreach i x step=-2><get-var i> </foreach>
  Output
  1 3 5 6 4 2

This command performs multiple conditions with a single instruction.

<set-var i=0>
<define-tag test>
<var-case x=1 <group <increment i> x<get-var i>> x=2 <group <decrement i> x<get-var i>> y=1 <group <increment i> y<get-var i>> y=2 <group <decrement i> y<get-var i>>>
</define-tag>
<set-var x=1 y=2><test>
<set-var x=0 y=2><test>

x1y0


y-1

Breaks the innermost while loop.

<set-var i=10>
<while <gt <get-var i> 0>>;;;
  <get-var i> <decrement i>;;;
  <ifeq <get-var i> 5 <break>>;;;
</while>

10 9 8 7 6 

This command immediately exits from the innermost macro. A message may also be inserted. But this macro changes token parsing so its use may become very hazardous in some situations.

• up=number
  This attribute determines how much levels have to be exited. By default only one level is skipped. If a negative value is put then all current macros are exited from.

Prints a warning on standard error.

Immediately exits program.

• message=string
  Prints a message to the standard error.
• status=rc
  Selects the code returned by the program (-1 by default).

This is a special command: all attributes are stored and will be expanded after end of input.

File functions

Returns a newline separated list of files contained in a given directory.

<directory-contents . matching=".*\\.mp4h$">

mp4h.mp4h

Returns true if file exists.

Returns an array of informations on this file. These informations are: size, type, ctime, mtime, atime, owner and group.

<get-file-properties mp4h.mp4h>

43659
FILE
954610154
954610154
954610155
barbier
users

Read input from another file.

• alt=action
  If file is not found, this alternate action is handled. If this atribute is not set and file is not found, then an error is raised.
• verbatim=true
  File content is included without expansion.

This tag does nothing, its body is simply discarded.

Change comment characters.

Debugging

When constructs become complex it could be hard to debug them. Functions listed below are very useful when you could not figure what is wrong. These functions are not perfect yet and must be improved in future releases.

Prints the replacement text of a user defined macro. For instance, the macro used to generate all examples of this documentation is

<function-def example>

<set-var-verbatim verb-body=%ubody>
<subst-in-var verb-body "&" "&amp;">
<subst-in-var verb-body "<" "&lt;">
<subst-in-var verb-body ">" "&gt;">
<set-var body=%body>
<subst-in-var body "&" "&amp;">
<subst-in-var body "<" "&lt;">
<subst-in-var body ">" "&gt;">
<subst-in-var body "<three-colon>\n[ \t]*" "" singleline=true>
<subst-in-var body "<three-colon>[^;][^\n]*\n[ \t]*" "" singleline=true>
<subst-in-var body "<three-colon>$" "">
<subst-in-var body "^\n+" "" singleline=true>
<table border=2 cellpadding=0 cellspacing=0 width="80%" summary="">
    <tr><th bgcolor="#ccccff"><lang:example-source></th></tr>
    <tr><td bgcolor="#ccff99" width="80%"><dnl>
      <pre><get-var-once verb-body></pre><dnl>
    </td></tr>
    <tr><th bgcolor="#ccccff"><lang:example-output></th></tr>
    <tr><td bgcolor="#ff99cc" width="80%"><dnl>
      <pre><get-var-once body></pre><dnl>
    </td></tr>
</table>

This comand acts like the -d flag but can be ynamically changed.

Selects a file where debugging messages are diverted. If this filename is empty, debugging messages are sent back to standard error, and if it is set to - these messages are discarded.

Note: There is no way to print these debugging messages into the document being processed.

Declare these macros traced, i.e. informations about these macros will be printed if -d flag or debugmode macro are used.

These macros are no more traced.

Miscellaneous

Without argument this macro prints current input filename. With an argument, this macro sets the string returned by future invocation of this macro.

Without argument this macro prints current number line in input file. With an argument, this macro sets the number returned by future invocation of this macro.

This is <__file__>, line <__line__>.

This is mp4h.mp4h, line 1601.

If you closely look at source code you will see that this number is wrong. Indeed the number line is the end of the entire block containing this instruction.

Prints the version of mp4h.

Discard all characters until newline is reached. This macro ensures that following string is a comment and does not depend of the value of comment characters.

<dnl>This is a comment
foo
<dnl>This is a comment
bar

foo
bar

Prints local time according to the epoch passed on argument. If there is no argument, current local time is printed.

<date>
<set-var info=<get-file-properties <__file__>>>
<date <get-var info[2]>>

Sat Apr  1 19:29:15 2000

Sat Apr  1 19:29:14 2000

Prints the time spent since last call to this macro. The printed value is the number of clock ticks, and so is dependant of your CPU.

The number of clock ticks since the beginning of generation of
this documentation by <mp4h> is:
<timer>

The number of clock ticks since the beginning of generation of
this documentation by <b>mp4h</b> is:
user 52
sys 0

Set locale-specific variables. By default, the portable "C" locale is selected.

<mp4h-l10n LC_NUMERIC=fr_FR>
<add 1,2 3,4>

4,600000

Change the output format of floats by setting the number of digits after the decimal point. Default is to print numbers in the "%6.f" format.

<add 1.2 3.4>
<mp4h-output-radix 2>
<add 1.2 3.4>

4.600000

4.60

Macro expansion

This part describes internal mechanism of macro expansion. It must be as precise and exhaustive as possible so contact me if you have any suggestion.

Basics

<define-tag foo>
This is a simple tag
</define-tag>
<define-tag bar endtag=required>
This is a complex tag
</define-tag>
<foo>
<bar>Body function</bar>

This is a simple tag


This is a complex tag

User defined macros may have attributes like HTML tags. To handle these attributes in replacement text, following conventions have been adopted (mostly derived from Meta-HTML):

• Sequence %name is replaced by the command name.
• Attributes are numbered from 0. In replacement text, %0 is replaced by first argument, %1 by the 2nd, etc. As there is no limitation on the number of arguments, %20 is the 21st argument and not the third followed by the 0 letter.

  Source
  <define-tag href> <a href="%0">%1</a> </define-tag> <href http://www.gimp.org "The Gimp">
  Output
  <a href="http://www.gimp.org">The Gimp</a>

• Sequence %# prints number of attributes.
• Sequence %% is replaced by %, which is useful in nested efinitions.

  Source
  <define-tag outer>;;; outer, # attributes: %# <define-tag inner1>;;; inner1, # attributes: %#;;; </define-tag>;;; <define-tag inner2>;;; inner2, # attributes: %%#;;; </define-tag>;;; <inner1 %attributes and some others> <inner2 %attributes and some others> </define-tag> <outer list attributes>
  Output
  outer, # attributes: 2 inner1, # attributes: 2 inner2, # attributes: 5

• Sequence %attributes is replaced by the space separated list of attributes.

  Source
  <define-tag mail1> <set-var %attributes> <get-var name> <get-var mail> </define-tag> <set-var name="" mail=""> <mail1 name="Dr. Foo" mail="hello@foo.com">
  Output
  Dr. Foo hello@foo.com

• Sequence %body is replaced by the body of a complex macro.

  Source
  <define-tag mail2 endtag=required whitespace=delete> <set-var %attributes> <a href="mailto:<get-var mail>">%body</a> </define-tag> <mail2 mail="hello@foo.com"> <img src="photo.png" alt="Dr. Foo" border=0> </mail2>
  Output
  <a href="mailto:hello@foo.com"> <img src="photo.png" alt="Dr. Foo" border=0> </a>

• The two forms above accept modifiers. When %Aattributes or %Abody is used, a newline separated list of attributes is printed.

  Source
  <define-tag show-attributes whitespace=delete> <set-var list="%Aattributes" i=0> <foreach attr list> <group "%<get-var i>: <get-var attr>"> <increment i> </foreach> </define-tag> <show-attributes name="Dr. Foo" mail="hello@foo.com">
  Output
  %0: name=Dr. Foo%1: mail=hello@foo.com

• Another alternate form is obtained by replacing A by U, in which case text is replaced but will not be expanded. This does make sense only when macro has been defined with attributes=verbatim, otherwise attributes are expanded before replacement.

  Source
  <define-tag show1> Before expansion: %Uattributes After expansion: %attributes </define-tag> <define-tag show2 attributes=verbatim> Before expansion: %Uattributes After expansion: %attributes </define-tag> <define-tag bar>and here %attributes</define-tag> <show1 <bar we go>> <show2 <bar we go>>
  Output
  Before expansion: and here we go After expansion: and here we go Before expansion: <bar we go> After expansion: and here we go

• Modifiers A and U can be combined.

Note: Input expansion is completely different in Meta-HTML and in mp4h. With Meta-HTML it is sometimes necessary to use other constructs like %xbody and %qbody. In order to improve compatibity with Meta-HTML, these constructs are recognized and are interpreted like %body. Another feature provided for compatibility reason is the fact that for simple tags %body and %attributes are equivalent. These features are in the current mp4h version but may disappear in future releases.

Attributes

Attributes are separated by spaces, tabulations or newlines, and each attribute must be a valid mp4h entity. For instance with the definitions above, <bar> can not be an attribute since it must be finished by </bar>. But this is valid:

<foo <foo>>

<foo <foo name=src url=ici>>

Under certain circumstances it is necessary to group multiple statements into a single one. This can be done with double quotes or with the group primitive, e.g.

<foo "This is the 1st attribute" <group and the second>>

Note: Unlike HTML single quotes can not replace doube quotes for this purpose.

If double quotes appear in an argument, they must be escaped by a backslash \.

  <set-var text="Text with double quotes \" inside">
  <get-var text>

  
  Text with double quotes " inside

Macro evaluation

Macros are characterized by

• name
• container status (simple or complex)
• if attributes are expanded or not
• function type (primitive or user defined macro)
• for primitives, adress of corresponding code in memory and for user defined macros the replacement text

Characters are read on input until a < is found. Then macro name is read. After that attributes are read, verbatim or not depending on how this macro as been defined. And if this macro is complex, its body is read verbatim. When this is finished, some special sequences in replacement text are replaced (like %body, %attributes, %0, %1, etc.) and resulting text is put on input stack in order to be rescanned.

Note: By default attributes are evalled before any replacement.

Consider the following example, to change text in typewriter font:

<define-tag text-tt endtag=required whitespace=delete>
<tt>%body</tt>
</define-tag>

This definition has a major drawback:

<text-tt>This is an <text-tt>example</text-tt></text-tt>

<tt>This is an <tt>example</tt></tt>

First idea is to use an auxiliary variable to know whether we still are inside such an environment:

<set-var _text:tt=0>
<define-tag text-tt endtag=required whitespace=delete>
<increment _text:tt>
<ifeq <get-var _text:tt> 1 "<tt>">
%body
<ifeq <get-var _text:tt> 1 "</tt>">
<decrement _text:tt>
</define-tag>

<text-tt>This is an <text-tt>example</text-tt></text-tt>

<tt>This is an example</tt>

But if we use simple tags, as in the example below, our definition does not seem to work. It is because attributes are expanded before they are put into replacement text.

<define-tag opt><text-tt>%attributes</text-tt></define-tag>
<opt "This is an <opt example>">

<tt>This is an <tt>example</tt></tt>

If we want to prevent this problem we have to forbid attributes expansion with

<define-tag opt attributes=verbatim>;;;
<text-tt>%attributes</text-tt>;;;
</define-tag>
<opt "This is an <opt example>">

<tt>This is an example</tt>

Author

Denis Barbier <barbier@imacs.polytechnique.fr>

Thanks

Sincere thanks to Brian J. Fox for writing Meta-HTML and Rene Seindal for maintaining this wonderful macro parser called GNU m4.