Bug 86190 - tetex default config inconsistency
tetex default config inconsistency
Status: CLOSED DUPLICATE of bug 50660
Product: Red Hat Linux
Classification: Retired
Component: tetex (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-03-16 13:40 EST by fraczak
Modified: 2007-04-18 12:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:52:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description fraczak 2003-03-16 13:40:47 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
tetex default config inconsistency. 

I have been annoyed by a misconfiguration of tetex in Red Hat for a long
time now. On every system I used I had to run explicitly "texconfig" in
order to change my default page-size for postscript to be letter (and
not default A4). I'm calling it a bug because for xdvi it is US letter
by default so this default configuration will probably work nowhere. The
problem is that probably most of new users will give up on Latex or try
to do some bad things like \voffset ... 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install tetex
2. try to print any ps document generated by latex 
3. the output is not correctly centered on the letter page

Actual Results:  The output is not correctly centered on the letter page.

Expected Results:  Correct printing

Additional info:

There is a very easy workaround. You fix the problem by running texconfig and by
choosing correct paper size.
Comment 1 Leonard den Ottolander 2004-07-01 11:17:09 EDT

*** This bug has been marked as a duplicate of 50660 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:52:12 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.