Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 77311 - Support for using UTF-8 as input encoding in LaTeX documents
Support for using UTF-8 as input encoding in LaTeX documents
Status: CLOSED DUPLICATE of bug 71498
Product: Red Hat Linux
Classification: Retired
Component: tetex (Show other bugs)
i586 Linux
medium Severity low
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-11-04 18:50 EST by Need Real Name
Modified: 2007-04-18 12:48 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-04 18:50:58 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 Need Real Name 2002-11-04 18:50:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Please provide the ucs.sty package or a simular one.

The mentioned package contains support for using UTF-8
as input encoding in LaTeX documents.

The simplest use of that package is to add


to the LaTeX source instead of the traditionally


after editing the document with UTF-8 input.

The most recent version of the package can 
be found at


Happy TeX'ing.

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

How reproducible:

Steps to Reproduce:
1. Enter UTF-8 characters (try the Scandinavian 'f', 'x', 'e') in 
   a LaTeX document from Emacs.
2. Run latex document.tex and, after hitting return on the error, 
   try to view it in xdvi.

Actual Results:  Bad DVI encoding.

Additional info:

With the ucs.sty package installed and mentioned 
in the LaTeX document everything's working fine.
Comment 1 Tim Waugh 2002-11-05 06:56:23 EST

*** This bug has been marked as a duplicate of 71498 ***

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