* Additionally, the escaper escapes the slash character ("/"). While slashes are acceptable in
   * URL paths, they are considered by the specification to be separators between "path segments."
   * This implies that, if you wish for your path to contain slashes, you must escape each segment
   * separately and then join them.
   *

                                       parsed_args.whitelist_prefix):
      continue

    # In Python, MSYS, Linux-like paths are automatically read as Windows paths
    # with forward slashes, e.g. 'C:/Program Files', instead of
    # '/c/Program Files', thus becoming converted simply by virtue of having
    # been read.
    converted_vars[var] = value

  var_str = '\n'.join(f'{k}="{v}"'

   * Additionally, the escaper escapes the slash character ("/"). While slashes are acceptable in
   * URL paths, they are considered by the specification to be separators between "path segments."
   * This implies that, if you wish for your path to contain slashes, you must escape each segment
   * separately and then join them.
   *

    assertThat(
      base
        .newBuilder()
        .addPathSegments("/d")
        .build()
        .encodedPath,
    ).isEqualTo("/a/b/c//d")

    // Add a string with two slashes: resulting URL gains three slashes.
    assertThat(
      base
        .newBuilder()
        .addPathSegments("//")
        .build()
        .encodedPath,
    ).isEqualTo("/a/b/c///")
    assertThat(

type FileHeader struct {
	// Name is the name of the file.
	//
	// It must be a relative path, not start with a drive letter (such as "C:"),
	// and must use forward slashes instead of back slashes. A trailing slash
	// indicates that this file is a directory and should have no data.
	Name string

	// Comment is any arbitrary user-defined string shorter than 64KiB.
	Comment string

     *   <li>Other sources may not support resolution and return null</li>
     * </ul>
     * <p>
     * The implementation must handle:
     * <ul>
     *   <li>Both forward and back slashes as path separators</li>
     *   <li>Parent directory references (..)</li>
     *   <li>Both file and directory targets</li>
     * </ul>
     *
     * @param relative path to resolve relative to this source

        /// details | Preview
        »»»

    Result:

        «««
        /// details | Vista previa
        »»»


### Tab blocks

There are special blocks surrounded by four slashes («////»). They mark text, which will be rendered as part of a tab in the final document. The scheme is:

    //// tab | {tab title}
    {tab content, may span many lines}
    ////

   *
   * <ul>
   *   <li>empty string becomes .
   *   <li>. stays as .
   *   <li>fold out ./
   *   <li>fold out ../ when possible
   *   <li>collapse multiple slashes
   *   <li>delete trailing slashes (unless the path is just "/")
   * </ul>
   *
   * <p>These heuristics do not always match the behavior of the filesystem. In particular, consider

 * Both the unnecessary port specification (`:80`) and the absent trailing slash (`/`) cause URI to
 * bucket the two URLs separately. This harms URI's usefulness in collections. Any application that
 * stores information-per-URL will need to either canonicalize manually, or suffer unnecessary
 * redundancy for such URLs.
 *
 * Because they don't attempt canonical form, these classes are surprisingly difficult to use

// The file contents will be compressed using the [Deflate] method.
// The name must be a relative path: it must not start with a drive
// letter (e.g. C:) or leading slash, and only forward slashes are
// allowed. To create a directory instead of a file, add a trailing
// slash to the name. Duplicate names will not overwrite previous entries
// and are appended to the zip file.
// The file's contents must be written to the [io.Writer] before the next