Subject: pkg/21350: enable dvipdfm to create pdf v1.3 files
To: None <gnats-bugs@gnats.netbsd.org>
From: None <brook@biology.nmsu.edu>
List: netbsd-bugs
Date: 04/28/2003 15:14:13
>Number:         21350
>Category:       pkg
>Synopsis:       enable dvipdfm to create pdf v1.3 files
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 28 21:15:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6
>Organization:
Brook G. Milligan                      Internet:  brook@nmsu.edu
Department of Biology
New Mexico State University            Telephone:  (505) 646-7980
Las Cruces, New Mexico  88003  U.S.A.  FAX:        (505) 646-5665
>Environment:
	
	
System: NetBSD viola.nmsu.edu 1.6 NetBSD 1.6 (GENERIC_LAPTOP) #0: Sun Sep 8 19:55:58 UTC 2002 autobuild@tgm.daemon.org:/autobuild/i386/OBJ/autobuild/src/sys/arch/i386/compile/GENERIC_LAPTOP i386
Architecture: i386
Machine: i386
>Description:
	As shipped, dvipdfm is configured to handle at most PDF
version 1.2 files.  However, it is capable of handling v1.3 files.
Thus, the configuration file should be patched to increase the range.
The contention that dvipdfm is able to handle v1.3 files is based on
an exchange with Mark Wicks (dvipdfm author).  It seems that the main
role of the version limit is to prevent a document being stamped as
v1.2 from including 1.3 features via an included image.
>How-To-Repeat:
	Install dvipdfm and try to include a PDF v1.3 image file
within a LaTeX document.  It will complain about the version being out
of range.
>Fix:
	Add the following patch to dvipdfm/patches.

$NetBSD$

--- config.orig	Sat Apr  5 12:28:04 2003
+++ config
@@ -33,7 +33,7 @@ g 1
 
 % PDF version stamp to use in output file and max version of files
 % allowed to be included (2 for 1.2, 3 for 1.3)
-V 2
+V 3
 %
 % Font map files
 %

>Release-Note:
>Audit-Trail:
>Unformatted: