<td>The LCID is an identification number used by Windows to uniquely identify locales and languages. See Microsoft Word 2010 Help or the MSDN Library at <a href="http://msdn.microsoft.com/"> http://msdn.microsoft.com</a> for a listing of LCIDs.</td>
</tr>
<tr>
<td style="text-align:center">2</td>
<td>Source unit name</td>
<td>Text</td>
<td>km</td>
<td> </td>
</tr>
<tr>
<td style="text-align:center">3</td>
<td>Source description</td>
<td>Text</td>
<td>kilometer</td>
<td>You can use the ô&ö character to define access keys in the description text. For example, ôkilo&meterö will set ômö as the access key for this conversion rule.</td>
</tr>
<tr>
<td style="text-align:center">4</td>
<td>Space between source unit and number</td>
<td>ôYesö or ôNoö</td>
<td>Yes</td>
<td> </td>
</tr>
<tr>
<td style="text-align:center">5</td>
<td>Is the source unit name case sensitive?</td>
<td>ôYesö or ôNoö</td>
<td>No</td>
<td> </td>
</tr>
<tr>
<td style="text-align:center">6</td>
<td>Destination unit name</td>
<td>Text</td>
<td>mi</td>
<td> </td>
</tr>
<tr>
<td style="text-align:center">7</td>
<td>Destination description</td>
<td>Text</td>
<td>mile</td>
<td>You can use the ô&ö character to define access keys in the description text. For example, ômi&leö will set ôlö as the access key for this conversion rule.</td>
</tr>
<tr>
<td style="text-align:center">8</td>
<td>Space between destination unit and number</td>
<td>ôYesö or ôNoö</td>
<td>Yes</td>
<td> </td>
</tr>
<tr>
<td style="text-align:center">9</td>
<td>Rounding precision (number of decimal places in the target)</td>
<td>Integer value ranging from 0 to 9</td>
<td>3</td>
<td> </td>
</tr>
<tr>
<td style="text-align:center">10</td>
<td>Conversion ratio or formula reference</td>
<td>
<ol style="list-style-type:lower-alpha">
<li>Float value ranging from 0.00000000000001 to 1000000. The value must not include
a comma.</li>
<li>ôCTOFö (Celsius to Fahrenheit)</li>
<li>ôFTOCö (Fahrenheit to Celsius)</li>
<li>ôKTOSPö (kilograms to stones and pounds). If the formula reference is KTOSP, then
the Destination Unit Name contains two strings delimited by ô|ö: ôstones|pounds.ö</li>
</ol>
</td>
<td>0.6213712</td>
<td> </td>
</tr>
</table>
<p>
Measurement Converter always supports conversion rules that have ôAllö
in Field #1. In addition to these rules, Measurement Converter also supports rules with an
LCID value that matches the user locale of your Windows Language and Regional Options.
For example, if the user locale on your system is set to Russian, Measurement Converter
will load conversion rules marked ôAllö and ô1049ö in Field #1.
</p>
<p>
Field #2 (ôSource unit nameö) contains the recognizable strings; that is,
strings that Measurement Converter will detect and tag in a Word document. You can add comments
in the metconv.txt on a new line as long as they are preceded by the ô//ö delimiter.
</p>
<p>
<b>Note:</b> New rules can be added anywhere in the metconv.txt file.
</p>
<p>
<b>Number formats</b> Measurements in international documents may use various decimal
separators and grouping symbols. Measurement Converter recognizes numbers
that use dot or comma as the decimal separator and numbers that use dot, comma, or space as the grouping
symbol. If the correct format cannot be determined from the measurement value alone,
Measurement Converter will check the current user locale in Regional and Language Options,
and it will assume that the measurement uses the format defined there. For example, if the
measurement is ô2,234 kmö and the user locale is French, the value is interpreted
as ôtwo point two hundred thirty-four kilometers.ö If the same measurement is recognized
on a system with user locale set to English, it is interpreted as ôtwo thousand
two hundred thirty-four kilometers.ö Measurement Converter only recognizes numbers where digits
