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

### Headings

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

### Quotes and punctuation

1) Keep punctuation style consistent with existing Traditional Chinese docs (they often mix English terms like “FastAPI” with Chinese text).

- MsWordExtractor
- MsExcelExtractor
- MsPowerPointExtractor
- TextExtractor

**Test Count**: 8 tests

**Key Scenarios**:
- ✅ Successful extraction closes resources properly
- ✅ Failed extraction includes descriptive error messages
- ✅ Null input stream validation
- ✅ Error messages include file type context

---

### 2. FilenameExtractorEnhancedTest.java
**Purpose**: Test FilenameExtractor edge cases and new documentation.

### Grammar and tone

1) Use polite, instructional Japanese (です/ます調).
2) Keep the tone concise and technical (match existing Japanese FastAPI docs).

### Headings

1) Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
2) Do not add a trailing period at the end of headings.

### Quotes

1) Prefer Japanese corner brackets 「」 in normal prose when quoting a term.

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

### Headings

1) Follow existing Simplified Chinese heading style (short and descriptive).
2) Do not add trailing punctuation to headings.
3) If a heading contains only the name of a FastAPI feature, do not translate it.

### Quotes and punctuation

        } catch (final CrawlerSystemException e) {
            assertEquals("The inputstream is null.", e.getMessage());
        }
    }

    /**
     * Test that ZipExtractor provides descriptive error message for invalid archive.
     */
    public void test_ZipExtractor_invalidArchive_throwsWithDescriptiveMessage() {
        final InputStream invalidStream = new ByteArrayInputStream("not a valid zip file".getBytes());

        assertNotNull(result.getContent());
        assertTrue("Should contain test content", result.getContent().contains("テスト"));
    }

    /**
     * Test that error message format is consistent and descriptive.
     */
    public void test_errorMessage_formatIsDescriptive() {
        final InputStream errorStream = new InputStream() {
            @Override
            public int read() throws IOException {

* Edit the text of the PR title to start in "imperative", like giving an order. So, instead of `Adding support for teleporting` use `Add support for teleporting`.
* Try to make the title descriptive about what it achieves. If it's a feature, try to describe it, for example `Add support for teleporting` instead of `Create TeleportAdapter class`.
* Do not finish the title with a period (`.`).

          <version>3.0.0+</version>
          <required>true</required>
          <description>The full name of the project.</description>
          <type>String</type>
        </field>
        <field>
          <name>description</name>
          <version>3.0.0+</version>
          <description>A detailed description of the project, used by Maven whenever it needs to

        "externalDocs": {
            "description": "External API documentation.",
            "url": "https://docs.example.com/api-general",
        },
        "paths": {
            "/api_route": {
                "get": {
                    "responses": {
                        "200": {
                            "description": "Successful Response",

        == response2.json()
        == [
            {"name": "Plumbus", "description": None, "sub": None},
            {
                "name": "Portal Gun",
                "description": "Device to travel through the multi-rick-verse",
                "sub": None,
            },
        ]
    )


def test_read_items():
    client = get_app_client()
    client_no = get_app_client(separate_input_output_schemas=False)