labels.bad_word_list=Liste des mots interdits
labels.backup_list=Liste des sauvegardes
labels.access_token_list=Liste des jetons d'accès
labels.suggest_search_log_enabled=Suggérer à partir des termes de recherche
labels.suggest_documents_enabled=Suggérer à partir des documents
labels.purge_suggest_search_log_day=Supprimer les anciennes informations de suggestion
labels.crawling_info_title=Informations sur l'exploration

				"application/vnd.dynageo",
				"application/vnd.ecdis-update",
				"application/vnd.ecowin.chart",
				"application/vnd.ecowin.filerequest",
				"application/vnd.ecowin.fileupdate",
				"application/vnd.ecowin.series",
				"application/vnd.ecowin.seriesrequest",
				"application/vnd.ecowin.seriesupdate",
				"application/vnd.emclient.accessrequest+xml",
				"application/vnd.enliven",
				"application/vnd.epson.esf",

 * practice. Typically HTTP applications use other mechanisms for user identification and
 * authentication.
 *
 * ### Host
 *
 * The host identifies the webserver that serves the URL's resource. It is either a hostname like
 * `square.com` or `localhost`, an IPv4 address like `192.168.0.1`, or an IPv6 address like `::1`.
 *

   * more convenient.
   *
   * <p>Builder instances can be reused - it is safe to call {@link #buildOrThrow} multiple times to
   * build multiple maps in series. Each map is a superset of the maps created before it.
   *
   * @since 2.0
   */
  public static class Builder<K, V> extends ImmutableMap.Builder<K, V> {
    private transient @Nullable Object[] keys;

 *  New: `Challenge` includes all authentication parameters.
 *  New: Upgrade to BouncyCastle 1.60, Conscrypt 1.4.0, and Okio 1.15.0. We don't yet require
    Kotlin-friendly Okio 2.x but OkHttp works fine with that series.

    ```kotlin
    implementation("org.bouncycastle:bcprov-jdk15on:1.60")
    implementation("org.conscrypt:conscrypt-openjdk-uber:1.4.0")
    implementation("com.squareup.okio:okio:1.15.0")
    ```

     * ensure that completed write operations performed by other threads are noticed. For most
     * purposes, the "count" field, tracking the number of elements, serves as that volatile
     * variable ensuring visibility. This is convenient because this field needs to be read in many
     * read operations anyway:
     *