Skip to content

Main content

Resource Language Availability Bit Tool

Calculate resource language availability bit from explicit caller-supplied inputs.

Loading tool…

Description

Check requestedLanguage membership in languages, either literally or after full-string Unicode lowercasing of both sides according to caseSensitive.

Extension-service records track resources, attendance, feedback and permission assertions. Distinct people and repeated records have different denominators, and a complete record does not prove valid consent or a high-quality service. Names such as verified describe caller-supplied evidence flags.

Check requestedLanguage membership in languages, either literally or after full-string Unicode lowercasing of both sides according to caseSensitive.

When to use this tool

Use Resource Language Availability Bit when checking the stated extension-service record, participation or permission convention.

How to use the tool and how it works

  1. Enter requestedLanguage, languages, caseSensitive. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read available. Inspect available before interpreting the associated values.

Check requestedLanguage membership in languages, either literally or after full-string Unicode lowercasing of both sides according to caseSensitive.1

Code points, UTF-16 code units, canonical decomposition and case conversion are different operations. This helper follows its explicit local convention rather than linguistic analysis or rendered-text measurement.2

Input fieldMeaning and unitsAccepted input
requestedLanguageRequested LanguageRequired. Text; maximum UTF-16 length 8192.
languagesLanguagesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
caseSensitiveCase SensitiveRequired. Boolean.
Output fieldInterpretationReturned shape
availableAvailableRequired. Boolean.
json
{
  "input": {
    "requestedLanguage": "EN",
    "languages": [
      "en",
      "fr"
    ],
    "caseSensitive": false
  },
  "output": {
    "available": true
  }
}

Limitations and assumptions

  • No language-tag canonicalization, translation, resource retrieval or actual availability verification occurs.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review original service and participant records and the applicable permission/organizational rules for actual use or reporting decisions.

References

  1. Calculation and input contract: agricultural-extension/resource-language-availability-bit — tool.io

  2. Unicode 17.0: encoding and normalization conventions — Unicode Consortium

Similar or alternative tools