### Quotes

- Keep quote style consistent with existing Turkish docs (typically ASCII quotes in text).
- Never modify quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style (`...`) consistent with existing Turkish docs.
- Never modify `...` in code, URLs, or CLI examples.

### Consistency

- Use the same translation for the same term throughout the document.

- Do not add trailing punctuation to headings.

### Quotes

- Keep quote style consistent with the existing Korean docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent with existing Korean docs (often `...`).
- Never change `...` in code, URLs, or CLI examples.

### Preferred translations / glossary

### Grammar and tone

- Use clear, concise technical Traditional Chinese consistent with existing docs.
- Address the reader naturally (commonly using “你/你的”).

### Headings

- Follow existing Traditional Chinese heading style (short and descriptive).
- Do not add trailing punctuation to headings.

### Quotes and punctuation

### Quotes and punctuation

- Keep punctuation style consistent with existing Simplified Chinese docs (they often mix English terms like “FastAPI” with Chinese text).
- Never change punctuation inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent within each document, prefer `...` over  `……`.
- Never change ellipsis in code, URLs, or CLI examples.

### Preferred translations / glossary

Doing this provides the following specific benefits:
- **Reduce the API surface** - We no longer need to maintain two methods.
- **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.

## Decision

            String result = icon.getIcon(mockTerminal);
            assertNotNull(result, "Icon result should not be null for " + icon);

            // Result should be consistent with charset's canEncode capability
            boolean canEncode = StandardCharsets.ISO_8859_1.newEncoder().canEncode(icon.getUnicodeChar());

        // Then - should be same instances
        assertSame(config1, config2, "Configuration should be consistent");
        assertSame(dfs1, dfs2, "DFS resolver should be consistent");
        assertSame(cache1, cache2, "Buffer cache should be consistent");
    }

    @Test
    @DisplayName("Context should provide working resource creation")

        assertEquals(0, DialectVersion.SMB302.compareTo(DialectVersion.SMB302));
    }

    @Test
    @DisplayName("Should return consistent ordinal values")
    void testOrdinalValues() {
        // Ordinal values should be consistent with enum declaration order
        assertTrue(DialectVersion.SMB1.ordinal() < DialectVersion.SMB202.ordinal());

* **Inconsistent API surface**: Public APIs with mixed spelling conventions appear less professional and polished
* **Harder for non-native speakers**: Contributors and users for whom English is a second language benefit from a single, consistent convention

While both American and British English are valid, establishing a single standard improves consistency, readability, and maintainability of the codebase.

            assertSame(mockConfig, result, "getConfig() should return the expected configuration");
        }

        @Test
        @DisplayName("Should maintain consistent getConfig return value")
        void shouldMaintainConsistentGetConfigReturn() {
            SmbSession mockSession = mock(SmbSession.class);
            Configuration mockConfig = mock(Configuration.class);