b[len(s)] = 0
	}

	// Some buggy readers treat regular files with a trailing slash
	// in the V7 path field as a directory even though the full path
	// recorded elsewhere (e.g., via PAX record) contains no trailing slash.
	if len(s) > len(b) && b[len(b)-1] == '/' {
		n := len(strings.TrimRight(s[:len(b)-1], "/"))
		b[n] = 0 // Replace trailing slash with NUL terminator
	}
}

    int destIndex = 0;
    int unescapedChunkStart = 0;

    while (index < end) {
      int cp = codePointAt(s, index, end);
      if (cp < 0) {
        throw new IllegalArgumentException("Trailing high surrogate at end of input");
      }
      // It is possible for this to return null because nextEscapeIndex() may
      // (for performance reasons) yield some false positives but it must never

[*]

indent_style = space
indent_size = 4

end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true

spelling_languages = en-US

# Markdown files sometimes need trailing whitespaces.
[*.md]
trim_trailing_whitespace = false

[*.{yml,yaml}]
indent_size = 2

[gradle/verification-metadata.xml]
indent_size = 3

[subprojects/launcher/src/main/resources/release-features.txt]

### Headings

- Follow existing Turkish heading style (Title Case where used; no trailing period).

### Quotes

- Keep quote style consistent with existing Turkish docs (typically ASCII quotes in text).
- Never modify quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

    assertThat(letters).containsExactly("a", "", " b", "c").inOrder();
  }

  public void testCharacterSplitWithTrailingDelimiter() {
    String trailing = "a,b,c,";
    Iterable<String> letters = COMMA_SPLITTER.split(trailing);
    assertThat(letters).containsExactly("a", "b", "c", "").inOrder();
  }

  public void testCharacterSplitWithLeadingDelimiter() {
    String leading = ",a,b,c";

- Keep the tone concise and technical (match existing Japanese FastAPI docs).

### Headings

- Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
- Do not add a trailing period at the end of headings.

### Quotes

- Prefer Japanese corner brackets 「」 in normal prose when quoting a term.
- Do not change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Address the reader naturally (commonly using “你/你的”).

### Headings

- Follow existing Simplified Chinese heading style (short and descriptive).
- Do not add trailing punctuation to headings.
- If a heading contains only the name of a FastAPI feature, do not translate it.

### Quotes and punctuation

### Headings

- Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
- Do not add trailing punctuation to headings.

### Quotes

- Keep quote style consistent with the existing Korean docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

    public void test_buildDefaultUrl_withTrailingSlash() throws Exception {
        // Test that trailing slash is handled correctly
        SamlAuthenticator authenticator = new SamlAuthenticator();

        DynamicProperties systemProperties = ComponentUtil.getSystemProperties();
        try {
            // Set custom base URL with trailing slash
            systemProperties.setProperty("saml.sp.base.url", "https://fess.example.com/");

        assertTrue("Single word query should produce BoolQuery", result instanceof BoolQueryBuilder);

        String queryString = result.toString();
        // Should contain a prefix query for the last word (since no trailing space)
        assertTrue("Should contain prefix query", queryString.contains("prefix"));
        assertTrue("Should query reading_0", queryString.contains("reading_0"));
    }

    @Test