blocks|key|1604532|text|打印机打印纸张和页，因此副本在某个阶段转换为页。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1604533|您获得的通知数据取决于打印应用程序以及处理假脱机和呈现的系统和驱动程序组件。根据我的经验，不能依赖数据，最好的数据是通过解析假脱机文件获得的。这可能包含也可能不包含副本的数量。|1604534|很长一段时间以来，Word一直存在着“复制问题”。。有一个修复这个问题的补丁，但另一个观点是它使用了一个不寻常的印刷方式。我将在这里引用一些链接内容：|offset|length|1604535|使用臭名昭著的单词复制计数错误…dmCopies文件在SHD中为1。正确的值在SPL文件中的DEVMODE记录中找到(如果它是EMF假脱机)。
我发现的唯一其他方法是，当作业被发送到打印机时，监视JOB_INFO_2结构的JOB_INFO_2字段，并查看它是否是TotalPages的倍数。
..。
所发生的不是一个字错误，而是一个Windows错误。Word总是将副本设置为1来调用startDoc，然后调用DocumentProperties并在dmCopies中进行更改，并调用ResetDC进行更新。这是一种奇怪的印刷方式，但并没有错。问题是shd文件和printer_info不是用这些信息更新的，只是在StartDoc调用中设置了Devmode。
但是，对生成新ResetDC的DevMode的调用保留在SPL文件上。如果您挂起DocumentProperties+API调用，您也可以获得该信息。|blockquote|1604536|entityMap|0|LINK|mutability|MUTABLE|url|http://comp.os.ms-windows.programmer.win32.narkive.com/TyyGPB1Q/no-chance-to-get-the-correct-copies-amount-for-a-printjob|1|https://support.microsoft.com/en-us/kb/919736|2|http://www.undocprint.org/formats/winspool/shd^0|0|0|0|P|0|T|9|1|1G|8|2|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]|$F|12|G|13|1|14]|$F|15|G|16|1|17]]|A|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]|U|$5|N|O|P|A|$Q|V]]]]

A printer prints sheets and pages, so copies is converted to pages at some stage.

The notification data you get depends on both the application that is printing and the system and driver components handling the spooling and rendering. In my experience the data cannot be relied on, and the best data is obtained by parsing the spool file. This may or may not contain the number of copies.

<a href="http://comp.os.ms-windows.programmer.win32.narkive.com/TyyGPB1Q/no-chance-to-get-the-correct-copies-amount-for-a-printjob" rel="nofollow">Word has had the "copies problem" for a long time</a>. There was a <a href="https://support.microsoft.com/en-us/kb/919736" rel="nofollow">patch to supposedly fix this</a>, but another opinion is that it's because it uses an <a href="http://www.undocprint.org/formats/winspool/shd" rel="nofollow">unusual way of printing</a>. I'll quote some of the link contents here:

<blockquote>
 With the infamous Word Copy Count bug… the dmCopies filed is 1 in the
 SHD. The correct value is found in the DEVMODE record in the SPL file
 (if it's an EMF spool).
 
 The only other way i found was to monitor the PrintedPages field of
 the JOB_INFO_2 structure, when the job has been sent to the printer,
 and see if it is a multiple of TotalPages.
 
 [...]
 
 What happens is not a Word bug, but a Windows bug. Word calls startDoc
 always with copies set to 1. After that calls DocumentProperties and
 makes the change in dmCopies and calls ResetDC to make the update. It
 is a strange way of printing but not wrong. The problem is that the
 shd file and printer_info is not updated with this information, just
 keeps the Devmode info set on the StartDoc call.
 
 But the call to the ResetDC generating a new DevMode is kept on the
 SPL file. You can get that info too if you hook DocumentProperties
 API calls.
</blockquote>

blocks|key|2357732|text|谢谢你的回答。当文档属性发生更改时，是否有一种捕获这些属性的方法？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2357733|JOB_INFO_2结构确实具有与pages_printed相同的total_pages。因此，这不是一个解决办法。|2357734|SPL文件确实包含了我测试过的打印机的QTY，它是正确的。但是我们在很多打印机上进行了测试，我们发现质量并不总是固定的。所以不是百分之百的解决方案。但已经是个不错的退路了。|2357735|因此，如果我可以在不调用SPL文件的情况下捕获文档属性，那就太棒了，因为我想这就是一切都正确的地方。难到不是么？|2357736|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Thank you for the answer. Is there a way of catching the document properties when they change?

The JOB_INFO_2 structure does have the same total_pages as pages_printed. So that is not a solution.

The SPL File does contain the QTY for the printer i tested on which is correct. BUT we tested on a lot of printers and we see the QTY is not Always set. So not a 100% solution. But already a good fallback.

So if i can catch the document properties without calling the SPL file that would be wonderful because i guess that's where everything is correct. Isn't it?

I really could use some help, this is a question that alot of people are asking on the internet. I have different setups, tried different ways of testing, it's very frustrating.

First setup:

<ul>
<li>local printers</li>
<li>local running code</li>
<li>print from pdf or notepad: SUCCES (number of copies are 2)</li>
<li>print from word: FAILED (numberof copies is 1)</li>
</ul>

Second setup:

<ul>
<li>local printers that are shared</li>
<li>local running code</li>
<li>print from other computer to shared printers</li>
<li>number of copies isalways 1</li>
</ul>

Sowhat is everyone missing? What happens that some fields are missing while the printer still should know what to print? What does word that also happen when you print from another computer? Can someone tell me why somethings in windows are so terrible? Everythingshould pass the spooler, sowhy isthedata wrong?

Kinds regards!

Printer spooler api number of copies

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我真的需要一些帮助，这是很多人在网上提出的问题。我有不同的设置，尝试过不同的测试方法，这很令人沮丧。第一次设置：本地打印机本地运行代码从pdf或记事本打印: SUCCES (拷贝数为2)从文字打印:失败(拷贝数为1)第二次设置：共享的本地打印机本地运行代码从其他计算机打印到共享打印机拷贝数总是1那么每个人都少了什么？当...

问打印机假脱机程序api拷贝数
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问打印机假脱机程序api拷贝数EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问打印机假脱机程序api拷贝数
EN