* The translation doesn't seem to change the original content, for example with obvious additional documentation sections.
* The translation doesn't use different Markdown structures, for example adding HTML tags when the original didn't have them.
* The "admonition" sections, like `tip`, `info`, etc. are not changed or translated. For example:

```
/// tip

This is a tip.

///

```

 *
 * <p>Repositories can be configured at various levels:</p><ol>
 * <li>POM: Repositories can be specified in the {@code pom.xml} file under the {@code <repositories>} and {@code <pluginRepositories>} sections.</li>
 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

 *
 * <p>Repositories can be configured at various levels:<ol>
 * <li>POM: Repositories can be specified in the {@code pom.xml} file under the {@code <repositories>} and {@code <pluginRepositories>} sections.</li>
 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

    @Override
    public boolean usesFastPath() {
      return true;
    }

    /*
     * non-private so that our `-source 8` build doesn't need to generate a synthetic accessor
     * method, whose mention of VarHandle would upset WriteReplaceOverridesTest under Java 8.
     */
    static final VarHandle HANDLE = byteArrayViewVarHandle(long[].class, LITTLE_ENDIAN);
  }

  /**

 |                 ${maven.installation.conf}/toolchains.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -it /path/to/installation/toolchains.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation.
 |-->

Mais vous pouvez toujours les documenter comme décrit dans [Additional Responses in OpenAPI](additional-responses.md){.internal-link target=_blank}.

        IllegalArgumentException ex = assertThrows(IllegalArgumentException.class, () -> RequestParam.valueOf(badName));
        assertTrue(ex.getMessage().contains(badName), "Exception message should mention the bad name");
    }

    // Edge/Invalid: empty string is invalid for valueOf
    @ParameterizedTest
    @EmptySource
    @DisplayName("valueOf(\"\") throws IllegalArgumentException for empty input")

    }
    return dummy;
  }

  /**
   * Similar to the above, but keeps a boolean flag rather than checking for the string accumulated
   * so far being empty. As a result, it does not have the above-mentioned bug.
   */
  @Benchmark
  int booleanIfFirst(int reps) {
    int dummy = 0;
    for (int i = 0; i < reps; i++) {
      StringBuilder sb = new StringBuilder();
      boolean append = false;

    }

    public void test_messageWithSpecialCharacters() {
        // Setup
        final String message = "Query error: field:\"test value\" AND category:[A TO Z] OR tag:#hashtag @mention $special %wildcard";
        final VaMessenger<FessMessages> messageCode = messages -> messages.addErrorsInvalidQueryUnknown(UserMessages.GLOBAL_PROPERTY_KEY);

                Strings.getOEMBytes(TEST_STRING, mockConfig);
            });

            assertTrue(exception.getMessage().contains("Unsupported OEM encoding"), "Exception should mention unsupported encoding");
            assertTrue(exception.getCause() instanceof UnsupportedEncodingException, "Cause should be UnsupportedEncodingException");
        }
    }

    @Nested