Assortment of typos in mappings and concepts

[Jim White]

While making a report on my examination of RelEx I found numerous typographical errors in data/mapping_rules.txt and data/concept_vars.txt.

Make_acquaintance not Make_acquaintance, Dimension not Demension, Characterization not Chacterization, etc.

I've gone through and corrected them all, including checking for agreement with FrameNet spellings.

In concept_vars I've added a number of US spellings in cases where only the UK was given.

In the case of "google" for a number, I just added "googol" rather than remove the new spelling. Of course that may not be right because "to google" is probably more common than misuse of "google" to mean googol.

A few I'm not entirely sure of the correction. I replaced the three lines:

# IF $About($var0,$var1) ^ noun($var0) THEN ^1_Relational_quantity:Denoted_quantity($var0,$var1) ^1_Relational_quantity:Reference_quantity($var0,$var1)
^1_Relational_quantity:Q_prop($About,$var0)
^1_relational_quantity:Degree($About,$var1)

with this (all on one line):

# IF $About($var0,$var1) ^ noun($var0) THEN ^1_Relational_quantity:Denoted_quantity($var0,$var1) ^1_Relational_quantity:Reference_quantity($var0,$var1) ^1_Relational_quantity:Q_prop($About,$var0) ^1_Relational_quantity:Degree($About,$var1)

RelEx has the non-FN relation AsymmetricEvaluativeComparison:StandardItem, but FN doesn't use camel case for FEs (as in Surpassing:Standard_item).

[Jim White (james-paul-white)]

Here's a patch with my corrections for the typos. And I found how to make a bzr send patch for merging.

[linas (linasvepstas)]

I've applied the patch and pushed to the main bzr tree. Thanks!