After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 569476 - UTF-8 encoded LaTeX output generates warning
UTF-8 encoded LaTeX output generates warning
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export Text
1.9.x
Other All
: Normal trivial
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-01-28 15:37 UTC by fhcarron
Modified: 2009-01-29 06:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description fhcarron 2009-01-28 15:37:23 UTC
I have just activated the preferences option to output UTF-8 encoded text when exporting to latex. When generating the corresponding PDF document with the pdflatex command, the following warning is output:

Package ucs Warning: ***************************
(ucs)                You seem to have loaded inputencoding utf8
(ucs)                (LaTeX kernel UTF-8) instead of utf8x (ucs.sty UTF-8).
(ucs)                Probably you are compiling a document written for a
(ucs)                pre-august-2004 ucs.sty.
(ucs)                ***************************
(ucs)                Please use \usepackage[utf8x]{inputenc} instead of
(ucs)                \usepackage[utf8]{inputenc}.
(ucs)                ***************************
(ucs)                If you should really want to use ucs.sty and kernel's
(ucs)                utf8.def together, use \usepackage[utf8x,utf8]{inputenc}
(ucs)                to disable compatibility mode
(ucs)                ***************************
(ucs)                Activating compatibility mode.
(ucs)                ***************************
(ucs)                 on input line 71.
Comment 1 Andreas J. Guelzow 2009-01-28 17:54:39 UTC
I thought I fixed this already. Perhaps I forgot to commit.
Comment 2 Andreas J. Guelzow 2009-01-29 06:10:50 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.