Received Pronunciation Features Lookup

Independently documented RP variety/source feature reference, not accent identification. Exact independently verified context/edition key, not live or embedded reference data. Caller establishes language, dialect, method and reference context; no automatic identity or universal language-wide claim.

Description

Received Pronunciation references describe a particular accent model or documented variety.

Received Pronunciation references describe a particular accent model or documented variety.1

Editions and speaker populations can differ in the features they include. The tool retrieves your supplied source-specific notice for one exact key; it contains no built-in or live reference database.

When to use Received Pronunciation Features Lookup

Use this tool to calculate or review the supplied observations under the stated rules. Specify the language variety, analysis, source edition and population or inventory definition.

How to use Received Pronunciation Features Lookup and understand its results

  1. Specify the language variety, analysis, source edition and population or inventory definition.
  2. Enter callerVerifiedRpFeatureKeys, callerVerifiedRpFeatureNotices, queryRpFeatureKey, using the field meanings and rules below, then run the tool.
  3. Read matchedCallerNotice, using the output meanings and calculation rules below. Confirm that the exact matched record is the one whose source and context apply.
  4. Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
Input fieldMeaningValue typeRequirement
callerVerifiedRpFeatureKeysCaller verified rp feature keyslist of stringRequired
callerVerifiedRpFeatureNoticesCaller verified rp feature noticeslist of stringRequired
queryRpFeatureKeyQuery rp feature key; use the exact reference token or coordinate domain stated belowstringRequired

Supply nonempty aligned unique nonblank context keys and nonblank notices, then query one exact existing key. Matching is case-sensitive without trimming or normalization. Return its original notice unchanged; unknown keys fail. No data is fetched or independently verified.

notice=notices[indexOf(keys,exactQuery)]

Use the matching field units and the exact boundary, ordering and reference rules above.

Output fieldMeaningValue type
matchedCallerNoticeMatched caller noticestring
json
{
  "input": {
    "callerVerifiedRpFeatureKeys": [
      "context-a/edition-a",
      "context-a/edition-b"
    ],
    "callerVerifiedRpFeatureNotices": [
      "independent reference a",
      "independent reference b"
    ],
    "queryRpFeatureKey": "context-a/edition-b"
  },
  "output": {
    "matchedCallerNotice": "independent reference b"
  }
}

Limitations and assumptions

The language variety, analytical definitions and reference scope are supplied by the caller. No corpus, speech or complete/current linguistic registry is analyzed automatically. Reference records and their claimed verification are supplied by the caller; the tool does not retrieve or verify them.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above.

Alternative or Complementary methods

For a related step, use General American Features Lookup: General American references describe an accent model or documented set of varieties. For a complementary comparison, use Australian English Vowel Shift Lookup: Australian English vowel descriptions depend on accent variety and phonetic context.

References

  1. Received Pronunciation Features Lookup — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies