/**
     * Constructs a new creator for stemmer override dictionaries.
     * It sets the file pattern to match files starting with "stemmer_override"
     * and ending with ".txt".
     */
    public StemmerOverrideCreator() {
        super("stemmer_override.*\\.txt");
    }

    /**
     * Registers this creator with the dictionary manager upon initialization.

```jinja hl_lines="7"
{!../../docs_src/templates/templates/item.html!}
```

### 템플릿 컨텍스트 값

다음과 같은 HTML에서:

{% raw %}

```jinja
Item ID: {{ id }}
```

{% endraw %}

...이는 전달한 "컨텍스트" `dict`에서 가져온 `id`를 표시합니다:

```Python
{"id": id}
```

예를 들어, ID가 `42`일 경우, 이는 다음과 같이 렌더링됩니다:

```html
Item ID: 42
```

### 템플릿 `url_for` 인수

        @DisplayName("Reads structure size 4 and returns 4 for various start indexes")
        void returnsFour_whenStructureSizeIsFour(int start) throws Exception {
            // Arrange: build a buffer that has the little-endian value 4 at 'start'
            int len = start + 2; // need at least two bytes from start
            byte[] buffer = new byte[len + 3];
            SMBUtil.writeInt2(4, buffer, start);

{!../../docs_src/templates/templates/item.html!}
```

### Valores de contexto do template { #template-context-values }

No código HTML que contém:

{% raw %}

```jinja
Item ID: {{ id }}
```

{% endraw %}

...aparecerá o `id` obtido do "context" `dict` que você passou:

```Python
{"id": id}
```

Por exemplo, dado um ID de valor `42`, aparecerá:

```html
Item ID: 42
```

        buf.enc_ndr_small(5); /* RPC version */
        buf.enc_ndr_small(0); /* minor version */
        buf.enc_ndr_small(ptype);
        buf.enc_ndr_small(flags);
        buf.enc_ndr_long(0x00000010); /* Little-endian / ASCII / IEEE */
        buf.enc_ndr_short(length);
        buf.enc_ndr_short(0); /* length of auth_value */
        buf.enc_ndr_long(call_id);
    }

{!../../docs_src/templates/templates/item.html!}
```

### Template-Kontextwerte { #template-context-values }

Im HTML, welches enthält:

{% raw %}

```jinja
Item ID: {{ id }}
```

{% endraw %}

... wird die `id` angezeigt, welche dem „Kontext“-`dict` entnommen wird, welches Sie übergeben haben:

```Python
{"id": id}
```

Mit beispielsweise einer ID `42` würde das wie folgt gerendert werden:

    @DisplayName("accept: name-based filter handles normal, empty, and null names")
    void accept_nameBasedFilter_handlesEdgeNames(String name, boolean expected) throws Exception {
        // Arrange: filter that accepts non-empty names ending with .txt
        SmbFileFilter filter = f -> {
            String n = f.getName();
            return n != null && !n.isEmpty() && n.endsWith(".txt");
        };
        when(smbFile.getName()).thenReturn(name);

    /*
     * These arrays are set up to test that the comparator compares bytes within a word in the
     * correct order—in order words, that it doesn't mix up big-endian and little-endian. The first
     * array has a smaller element at one index, and then the second array has a smaller element at
     * the next.
     */
    byte[] a0 = {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 99, 15, 16, 17};

 [[3]] in a "groupId/artifactId/version" snapshot artifact directory: metadata describes <<<groupId>>>, <<<artifactId>>>, <<<version>>> (base version, i.e. ending in <<<-SNAPSHOT>>>) and
       <<<versioning>>> element that gives data about snapshot (<<<snapshot>>>, <<<lastUpdated>>> and <<<snapshotVersions>>> list). Notice that a

    /**
     * Constructs a new creator for synonym dictionaries.
     * It sets the file pattern to match files starting with "synonym"
     * and ending with ".txt".
     */
    public SynonymCreator() {
        super("synonym.*\\.txt");
    }

    /**
     * Registers this creator with the dictionary manager upon initialization.