that are being validated and certified for FIPS-140 use.
The file x.txt (for example, inprocess.txt, certified.txt)
defines the meaning of the FIPS version alias x, listing
the exact version to use.

The zip files are created by cmd/go/internal/fips140/mkzip.go.
The fips140.sum file lists checksums for the zip files.

/**
 * Form for uploading search request files to the Fess search engine.
 * This form is used in the admin interface to upload search request configuration files
 * that define search behaviors and request handling.
 */
public class UploadForm {

    /**
     * The multipart file containing the search request configurations to be uploaded.
     * This file should contain search request definitions and configurations.
     */

        final File repository = createRepositoryFile();
        return DiskFileItemFactory.builder().setBufferSize(sizeThreshold).setFile(repository).get();
    }

    protected int getSizeThreshold() {
        return ComponentUtil.getFessConfig().getHttpFileuploadThresholdSizeAsInteger();
    }

    protected File createRepositoryFile() {
        return new File(getRepositoryPath());
    }

/**
 * Form for uploading elevate word files to the Fess search engine.
 * Elevate words are terms that should be promoted or given higher ranking in search results.
 * This form is used in the admin interface to upload elevate word configuration files.
 */
public class UploadForm {

    /**
     * The multipart file containing the elevate word configurations to be uploaded.

bekreftes",requiredField:"Dette er et obligatorisk felt",requiredFields:"Du har ikke besvart alle obligatoriske felt",wrongFileDim:"Ukorrekte bildedimensjoner,",wrongFileSize:"Bildet du prøver å laste opp er for stort (max %s)",wrongFileType:"Kun filer av type %s er tillatt"}})}(a,window)});...

In fact, those blocks of code are not written inside the Markdown, they are Python files in the `./docs_src/` directory.

And those Python files are included/injected in the documentation when generating the site.

### Docs for tests

Most of the tests actually run against the example source files in the documentation.

This helps to make sure that:

* The documentation is up-to-date.

import org.lastaflute.web.validation.Required;

/**
 * Form for uploading character mapping files to the Fess search engine.
 * Character mapping allows for normalization and transformation of characters during text analysis.
 * This form is used in the admin interface to upload custom character mapping dictionary files.
 */
public class UploadForm {

    /**

import org.lastaflute.web.validation.Required;

/**
 * Form for uploading synonym files to the Fess search engine.
 * Synonyms are words or phrases that should be treated as equivalent during search operations.
 * This form is used in the admin interface to upload custom synonym dictionary files.
 */
public class UploadForm {

    /**

import java.io.BufferedWriter;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.OutputStreamWriter;
import java.io.Reader;
import java.io.Writer;
import java.nio.file.Files;
import java.nio.file.Path;
import java.util.List;
import java.util.stream.Collectors;

import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.codelibs.core.concurrent.CommonPoolUtil;

								<group>${packaging.fess.group}</group>
							</mapper>
						</data>
						<!-- Add configuration files -->
						<data>
							<type>files</type>
							<paths>
								<path>${project.basedir}/src/main/assemblies/files/tomcat_config.properties</path>
								<path>${project.basedir}/src/main/assemblies/files/logging.properties</path>
							</paths>
							<dst>${packaging.fess.conf.dir}</dst>
							<mapper>