> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/cong-windows-lie-yin.md).

# 從 Windows 列印

預設設定 Windows 與 macOS 使用相同的印表機。可按照常用的方式從 Windows 應用程式進行列印。

{% hint style="info" %}
**注意**：由於 macOS Sonoma 14 有所變更，若 Parallels Desktop 19 裝載於 Macs 的 Sonoma 上，其中的列印功能將會進行變更，且本指南會在 Sonoma 正式發行後反映此變更。
{% endhint %}

您還可設定 Windows 使用不同的印表機。以下為幾種在 Windows 中設定列印的方法：

* 共用任何與 Mac 連接的印表機。
* 連接到網路印表機。
* 直接連接 USB 印表機到 Windows。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/cong-windows-lie-yin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.