|
|
Browse by Tags
All Tags » Printing (RSS)
-
In the Winhec presentation on XPS document performance optimization, a simple program XpsStat is introduced to analyze XPS documents. Given an XPS document, XpsStat generates four or five tables in HTML format: Container Summary Table: information about each type of parts in the document. FixedPage / Remote Resource Dictionary Table: information about each fixed page / remote resource dictionary in the document. Font Resource Table: information about each font resource in the document Image Resource Table: information about each image resource in the document Container Part Table (optional): information about each part in the document The program has three command line options: /x Generate report in XML format instead of the default HTML format /a Generate the optional Container Part Table /d Extract fonts to external files, unobfuscated. The program is written using .Net 3.0 XPS related API and some direct parsing of ZIP container. It supports both interleaved and non-interleaved XPS files. Read More...
|
-
There will be two XPS related sessions at Winhec 2007 tomorrow, focusing on Performance Optimization for XPS Document. The techincal presentation (CLN-T371 ) will be at 8:30am to 9:30am in Room 502AB. Shortly after that (9:45 to 10:45), there will be a chalk talk (CLN-C372) in Room 409A on the same topic. The focus of the talk will be on how to generate the better XPS so that XPS documents can be consumed efficiently. So we will go into great deails about how to measure XPS document for performance and ideas on how to generate better XPS. But we will cover XPS performance issues in general. So even if you're just consuming XPS documents, this presentation should still be very much relevant to you. The reason is that this presentation is written from the viewpoint of a XPS consumer. I'm pretty sure that you will either learn something useful from the presentation and chalk talk, or you can teach the community something about XPS. Optimization XPS document is just part of the story in the Read More...
|
-
Today (May 15, 2007) is the first day of Winhec 2007. If you're application developers, printer/scanner/multi-functional device vendors, you may be interested in the following XPS related sessions. CLN-T370 XPSDrv: Best Practice using Print Verifier, May 15, 3:15pm-4:15pm 515B, Manski & Ashwin CLN-C369 (Chalk Talk) Print Verifier and XPSDrv Driver Development, May 15, 4:30pm-5:30pm 409A, Erhan CLN-T375 HP Photo: Implementation Guidelines, May 16 11:00am-noon, 408AB, Bill Crow CLN-T371 Performance Optimization for XPS Documents, May 17, 8:30am-9:30am 502AB, Feng CLN-C372 (Chalk Talk) XPS Document Optimization and Best Practice, May 17 9:45am-10:45am, 409A, Rod In the self-paced hands-lab, there is a XPSDrv related lab. The following exhibitors are showing their XPS related technologies: Artifex Softaware Inc. www.artifex.com Global Graphics Software Incorporated, www.globalgraphics.com Pagemark Technology, Inc, www.pagemarktechnology.com QualityLogic, www.qualitylogic.com Zoran Corporation, Read More...
|
-
If you write programs in C#, Windows Presentation Foundation in .Net 3.0 provides quite nice API to write, generate and manipulate XPS documents. You can get the same feature if you work with managed C++ in .Net 3.0. Even if you work with .Net 2.0, you can get the basic ZIP stream decoding/encoding support. But if you want to write code in unmamanged world, especially outside of the XPS filter pipeline, there is not enough sample code there. I'm going to write a simple XPS decoder in C++, based on the zlib compression library ( http://www.zlib.net/zlib123-dll.zip ). #include <windows.h> #include <stdio.h> #include <tchar.h> #include "MemFile.h" #include "zip.h" #include "zlib.h" #pragma comment ( lib , "zdll.lib" ) HANDLE CreateDirFile( char * pName, DWORD len, HRESULT & hr); class CXps : CMemoryMappedFile { const CEndCentralDir * m_pEndCentralDir; const CCentralFileHeader * m_pFileHeader; public : HRESULT LoadXps( const wchar_t * pFileName); HRESULT DecodePiece( const Read More...
|
-
XPS is a fixed document format in which pages are pre-formated to a fixed page sixe. On the opposite of the spectrum, WPF provides flow document which can be paginated dynamically in XAML viewer. To bridge the two, WPF provides features to convert a flow document to fixed document in XPS format. Actually, you can convert any WPF Visual content to XPS. While the default conversion is very easy to use, if you want more features, you need to write some code. This acticle shows how to convert WPF flow document to multiple page XPS with page size, margin, and header. When a flow document is loaded in WPF, it returns an IDocumentPaginatorSource object. From it, you can get its DocumentPaginator object. When you're using XpsSerializationManager to convert a loaded flow document to XPS, it accepts a DocumentPaginator object. But the little know fact is that WPF allows you to wrap a new DocumentPaginator around a DocumentPaginator to control the conversion process. Here is our DocumentPaginator Read More...
|
-
Now that the XPS storm has been started, people are generating XPS documents from all kinds of sources. Among different ways of XPS generation, the easily way is still through printing to the Microsoft XPS Document Writer (the MXDW printer driver). If you're printing from your own applications, it's easy to specify MXDW as the printer driver and provide a file name for the XPS document to be saved to. But if you're using certain applications to print a documents, a print dialog box and a file save dialog box could pop up on screen, blocking attempts for fully automatic document conversion. For different document types, you can check Windows registry to find the command to print it. For example, the command to print an HTML page is: rundll32.exe mshtml.dll,PrintHTML "<document>" "<driver>" "<device>" "<port>" So you should be able to print any webpage to any printing device, to any printer/file, fully automatically. But this creates a security risk, so it has since Read More...
|
|
|
|