Skip to content

Commit

Permalink
put para around empha
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.osgeo.org/postgis/trunk@13113 b70326c6-7e19-0410-871a-916f4a2858ee
  • Loading branch information
robe2 committed Oct 25, 2014
1 parent 402027a commit 085201a
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions doc/extras_address_standardizer.xml
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ into includes in the future for easier maintenance.</para></listitem>

<refsection id="rule_input_tokens"><title>Input Tokens</title>
<para>Each rule starts with a set of input tokens followed by a terminator <code>-1</code>. Valid input tokens excerpted from <ulink url="http://www.pagcgeo.org/docs/html/pagc-12.html#ss12.2">PAGC Input Tokens</ulink> are as follows:</para>
<emphasis role="bold">Form-Based Input Tokens</emphasis>
<para><emphasis role="bold">Form-Based Input Tokens</emphasis></para>
<variablelist>
<varlistentry>
<term>AMPERS</term>
Expand Down Expand Up @@ -238,7 +238,7 @@ into includes in the future for easier maintenance.</para></listitem>
</varlistentry>
</variablelist>

<emphasis role="bold">Function-based Input Tokens</emphasis>
<para><emphasis role="bold">Function-based Input Tokens</emphasis></para>
<variablelist>
<varlistentry>
<term>BOXH</term>
Expand Down Expand Up @@ -304,7 +304,7 @@ into includes in the future for easier maintenance.</para></listitem>
</varlistentry>
</variablelist>

<emphasis role="bold">Postal Type Input Tokens</emphasis>
<para><emphasis role="bold">Postal Type Input Tokens</emphasis></para>
<variablelist>
<varlistentry>
<term>QUINT</term>
Expand Down Expand Up @@ -335,7 +335,7 @@ into includes in the future for easier maintenance.</para></listitem>
</varlistentry>
</variablelist>

<emphasis role="bold">Stopwords</emphasis>
<para><emphasis role="bold">Stopwords</emphasis></para>
<para>STOPWORDS combine with WORDS. In rules a string of multiple WORDs and STOPWORDs will be represented by a single WORD token.</para>
<variablelist>
<varlistentry>
Expand Down

0 comments on commit 085201a

Please sign in to comment.