2. **Search/Analysis Support** (40+ languages): Language-specific text analysis for search indexing

Currently supported UI languages: German, English, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Brazilian Portuguese, Russian, Simplified Chinese, and Traditional Chinese.

## File Structure

Language resource files are located in:
```
src/main/resources/

There will be a label for each language using the language code, like `lang-{lang code}`, for example, `lang-es` for Spanish, `lang-fr` for French, etc.

* Add the specific language label.
* Add the label `awaiting-review`.

<abbr title="too long; didn't read - zu lang; hab's nicht gelesen"><strong>TL;DR:</strong></abbr>
```

- If the language to which you translate mostly uses the letters of the ASCII char set (for example Spanish, French, German, but not Russian, Chinese) and if the translation of the full phrase is identical to, or starts with the same letters as the original full phrase, then only give the translation of the full phrase.

Conversion scheme:

        // Execute
        OptionalThing<Locale> result = provider.findBusinessLocale(null, mockRequestManager);

        // Verify
        assertTrue(result.isPresent());
        assertEquals(Locale.FRENCH, result.get());
    }

    // Test findBusinessLocale with hyphen separator
    @Test
    public void test_findBusinessLocale_withHyphenSeparator() {
        // Setup mock config

		t.Fatalf("failed to create user: %v", err)
	}

	// Create languages using real database
	langs := []Language{
		{Code: "en", Name: "English"},
		{Code: "fr", Name: "French"},
	}
	for _, lang := range langs {
		DB.FirstOrCreate(&lang, "code = ?", lang.Code)
	}

	// Test Set + Update with many-to-many association
	assocOp := clause.Association{
		Association: "Languages",

        assertEquals(expectedGradleParams, promote.gradleParams)
    }

    @Test
    fun `publish branch snapshot build type runs three gradle invocations`() {
        val model = setupModelFor("release")
        val nightlySnapshot = model.findBuildTypeByName("Publish Branch Snapshot (from Quick Feedback)")

        val steps = nightlySnapshot.steps.items
        assertEquals(3, steps.size)

 * </dl>
 *
 * <ul>
 * <li>the unreleased <b>major</b>, M+1.0.0 on the `master` branch</li>
 * <li>the unreleased <b>minor</b>,  M.N.0 on the `M.x` (x is literal) branch</li>
 * <li>the unreleased <b>bugfix</b>, M.N.c (c &gt; 0) on the `M.N` branch</li>
 * <li>the unreleased <b>maintenance</b>, M-1.d.e ( d &gt; 0, e &gt; 0) on the `(M-1).d` branch</li>
 * </ul>

                    If change was made on the `release` branch but hasn't yet been published to the baseline version, update the baseline version:
                    <span class="btn btn-info" role="button">Update baseline</span>
                  </summary>
                  <div class="well">
                    Sometimes, the change was made on the `release` branch but hasn't yet been published to the baseline version.

To sign off a single commit:

`git commit --amend --signoff`

To sign off one or multiple commits:

`git rebase --signoff origin/master`

Then force push your branch:

`git push --force origin test-branch`

### Fixing sanity check failures after public API changes

If your PR includes any changes to the Gradle Public API, it will cause the binary compatibility check to fail.

/**
 * The logical branch.
 * For non-merge-queue branches this is the same as {@link #buildBranch}.
 * For merge-queue branches, this is the base branch.
 *
 * For example, for the merge queue branch "gh-readonly-queue/master/pr-12345-1a2b3c4d" the logical branch is "master".
 */
val Project.logicalBranch: Provider<String>