Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

fouriernc.sty Encoding Warnings

40 views
Skip to first unread message

Randy Yates

unread,
Oct 28, 2006, 7:40:47 PM10/28/06
to
When I add the package \usepackage{fouriernc} to my document, I begin
getting the string of encoding warnings listed at the end of this
message. I don't get these warnings if I use CM fonts or txfonts
instead.

Can someone tell me why I'm getting this and/or how to "fix" my
setup so they don't occur?

Here's a minimal example:

\documentclass[10pt]{article}

\usepackage{fouriernc}

\begin{document}

\section{Introduction}

This is a font encoding test minimal example.

\end{document}

--Randy Yates


LaTeX Font Warning: Encoding `OT1' has changed to `T1' for symbol font
(Font) `operators' in the math version `normal' on input line 50.


LaTeX Font Warning: Encoding `OT1' has changed to `T1' for symbol font
(Font) `operators' in the math version `bold' on input line 50.


LaTeX Font Warning: Encoding `OML' has changed to `FML' for symbol font
(Font) `letters' in the math version `normal' on input line 59.


LaTeX Font Warning: Encoding `OML' has changed to `FML' for symbol font
(Font) `letters' in the math version `bold' on input line 59.


LaTeX Font Warning: Encoding `OMS' has changed to `FMS' for symbol font
(Font) `symbols' in the math version `normal' on input line 113.


LaTeX Font Warning: Encoding `OMS' has changed to `FMS' for symbol font
(Font) `symbols' in the math version `bold' on input line 113.


LaTeX Font Warning: Encoding `OMX' has changed to `FMX' for symbol font
(Font) `largesymbols' in the math version `normal' on input line 1
14.


LaTeX Font Warning: Encoding `OMX' has changed to `FMX' for symbol font
(Font) `largesymbols' in the math version `bold' on input line 114
.

--
% Randy Yates % "Watching all the days go by...
%% Fuquay-Varina, NC % Who are you and who am I?"
%%% 919-577-9882 % 'Mission (A World Record)',
%%%% <ya...@ieee.org> % *A New World Record*, ELO
http://home.earthlink.net/~yatescr

Randy Yates

unread,
Oct 28, 2006, 7:47:31 PM10/28/06
to
Randy Yates <ya...@ieee.org> writes:
> [...]

I should add that this is TeXLive 2005 under Linux/FC4.
--
% Randy Yates % "Remember the good old 1980's, when
%% Fuquay-Varina, NC % things were so uncomplicated?"
%%% 919-577-9882 % 'Ticket To The Moon'
%%%% <ya...@ieee.org> % *Time*, Electric Light Orchestra
http://home.earthlink.net/~yatescr

Jean-Côme Charpentier

unread,
Oct 28, 2006, 9:11:53 PM10/28/06
to
Randy Yates a écrit :

> When I add the package \usepackage{fouriernc} to my document, I begin
> getting the string of encoding warnings listed at the end of this
> message. I don't get these warnings if I use CM fonts or txfonts
> instead.
>
> Can someone tell me why I'm getting this and/or how to "fix" my
> setup so they don't occur?

It's not error messages, it's just warning messages. Maybe it would
be better that LaTeX displays Info messages for that.

You can't easily stop these messages. They are displayed by the LaTeX
core. If you want absolutely the silent, you can try:

\documentclass[10pt]{article}
\makeatletter
\let\@font@warningori\@font@warning
\newcommand\shutup{\def\@font@warning##1{}}
\newcommand\youcanspeak{\let\@font@warning\@font@warningori}
\makeatother

\shutup
\usepackage{fouriernc}
\youcanspeak

\begin{document}
Hello.
\end{document}

Jean-Côme Charpentier

Randy Yates

unread,
Oct 29, 2006, 12:24:21 AM10/29/06
to
Jean-Côme Charpentier <Jean-Come....@wanadoo.fr> writes:

Thanks for the "cover-up" fix, Jean-Come, but perhaps it would be
better to know why it's breaking?
--
% Randy Yates % "The dreamer, the unwoken fool -
%% Fuquay-Varina, NC % in dreams, no pain will kiss the brow..."
%%% 919-577-9882 %
%%%% <ya...@ieee.org> % 'Eldorado Overture', *Eldorado*, ELO
http://home.earthlink.net/~yatescr

Jean-Côme Charpentier

unread,
Oct 29, 2006, 12:44:54 AM10/29/06
to
Randy Yates a écrit :
> [...]

> Thanks for the "cover-up" fix, Jean-Come, but perhaps it would be
> better to know why it's breaking?

The problem is that nothing is breaking :-)

As I said, these messages are not error messages, they are just info
messages (though they are displayed as warning messages).

fourier changes the math encoding for some math alphabets in some math
versions. That's all.

Jean-Côme Charpentier

Randy Yates

unread,
Oct 29, 2006, 6:23:04 PM10/29/06
to
Jean-Côme Charpentier <Jean-Come....@wanadoo.fr> writes:

> Randy Yates a écrit :
>> [...]
>> Thanks for the "cover-up" fix, Jean-Come, but perhaps it would be
>> better to know why it's breaking?
>
> The problem is that nothing is breaking :-)

When a half-dozen extraneous messages reach my eyes, something is
broken. The computer exists to serve man, not vice-versa.

> As I said, these messages are not error messages, they are just info
> messages (though they are displayed as warning messages).
>
> fourier changes the math encoding for some math alphabets in some math
> versions. That's all.

Then would it not be preferable to change the fourier encodings so that
this doesn't happen?

By the way, after about a hundred thousand lines of code, I am aware
of the difference between a warning and an error, and despite your
numerous admonitions on the issue, I have not ever referred to it as
an error.
--

Will Robertson

unread,
Oct 29, 2006, 6:37:59 PM10/29/06
to
Randy Yates wrote:

> Jean-Côme Charpentier <Jean-Come....@wanadoo.fr> writes:
> > The problem is that nothing is breaking :-)
>
> When a half-dozen extraneous messages reach my eyes, something is
> broken.

That's just semantics. The thing is, that package (and others) use
LaTeX's built-in methods to provide maths support. When this part of
LaTeX was written, I guess it was considered sufficiently rare that
this would happen that the user would like to know about it.

> Then would it not be preferable to change the fourier encodings so that
> this doesn't happen?

That's a solution that doesn't really make sense, if you think about
it. In my package that deals with similar things, I make the
redefinitions locally (similar to Jean-Côme's), but the best thing to
do would be to patch the LaTeX kernel, which is a possibility since
this change wouldn't break any previous code. (Or it shouldn't, at
least.)

I'm motivated enough to submit a bug report, so we'll see how it goes.

Will

Randy Yates

unread,
Oct 29, 2006, 7:10:56 PM10/29/06
to
"Will Robertson" <wsp...@gmail.com> writes:

Hi Will,

I admit ignorance on the issues you and Jean-Come speak. Even so, it
is difficult to understand why hundreds (thousands?) of other fonts
have no such messages, and yet it is necessary or convenient that
these do.

It is also simply a pain to deal with sifting through the
"non-serious" messages each and every time I run LaTeX in order to
find the "serious" ones. I'm sure you both can understand that.
--
% Randy Yates % "My Shangri-la has gone away, fading like
%% Fuquay-Varina, NC % the Beatles on 'Hey Jude'"
%%% 919-577-9882 %
%%%% <ya...@ieee.org> % 'Shangri-La', *A New World Record*, ELO
http://home.earthlink.net/~yatescr

Will Robertson

unread,
Oct 29, 2006, 7:32:56 PM10/29/06
to
Randy Yates wrote:
> I admit ignorance on the issues you and Jean-Come speak. Even so, it
> is difficult to understand why hundreds (thousands?) of other fonts
> have no such messages, and yet it is necessary or convenient that
> these do.

The difference here is that the maths fonts are changing too.
There aren't so many packages that do that...

> It is also simply a pain to deal with sifting through the
> "non-serious" messages each and every time I run LaTeX in order to
> find the "serious" ones. I'm sure you both can understand that.

Definitely, I dislike it too and I've seen it be a point of confusion
for ages now (seemingly).
I hope to file the bug report tonight, unless Morten's listening and
would like to add his 0.02 Euro :)

Will

Randy Yates

unread,
Oct 29, 2006, 7:45:42 PM10/29/06
to
"Will Robertson" <wsp...@gmail.com> writes:

> Randy Yates wrote:
>> I admit ignorance on the issues you and Jean-Come speak. Even so, it
>> is difficult to understand why hundreds (thousands?) of other fonts
>> have no such messages, and yet it is necessary or convenient that
>> these do.
>
> The difference here is that the maths fonts are changing too.
> There aren't so many packages that do that...

Aren't the math fonts simply another set of font files (.tfms)? And
isn't the "problem" that LaTeX expects one encoding but these fonts
use another encoding? If those two conjectures are true, then I don't
understand why you wouldn't simply re-encode the fourier math fonts to
give LaTeX what it wants.
--
% Randy Yates % "She has an IQ of 1001, she has a jumpsuit
%% Fuquay-Varina, NC % on, and she's also a telephone."
%%% 919-577-9882 %
%%%% <ya...@ieee.org> % 'Yours Truly, 2095', *Time*, ELO
http://home.earthlink.net/~yatescr

Will Robertson

unread,
Oct 29, 2006, 9:34:11 PM10/29/06
to

Randy Yates wrote:
> Aren't the math fonts simply another set of font files (.tfms)? And
> isn't the "problem" that LaTeX expects one encoding but these fonts
> use another encoding? If those two conjectures are true, then I don't
> understand why you wouldn't simply re-encode the fourier math fonts to
> give LaTeX what it wants.

Without looking too deeply into what exactly fourier is doing, and
presuming that the fourier designer(s) would have used the standard
encoding if they could, I surmise that the reason they use a different
encoding is because they provide different/more characters than those
provided by Knuth's fonts. So it wouldn't be a lossless conversion with
respect to what you could obtain from the fourier fonts.

To re-iterate, it's not because fourier is using another encoding when
LaTeX expects something else, it's that the package changes what
encoding is used for various fonts. The problem is that LaTeX is rather
verbose about when this happens, needlessly, and if you like
overloading the meaning of the word "warning".

Cheers,
Will

Joachim Schrod

unread,
Oct 31, 2006, 6:44:57 AM10/31/06
to
Randy Yates wrote:
> When I add the package \usepackage{fouriernc} to my document, I begin
> getting the string of encoding warnings listed at the end of this
> message. I don't get these warnings if I use CM fonts or txfonts
> instead.

That's because they use a different math encoding, the default math
encoding and fonts have already been oaded earlier, and they are
substituted at this point. I know of no method to prevent the
earlier loading of the default (cmm) fonts, which would be needed to
quiet down the warning messages; but I have to admit that I have
also not investigated it in more detail. Maybe I ask Frank when I
see him the next time, if one can stop this somehow.

If you use fouriernc please note that it scales down New Century
Schoolbook to have the same x-height as the Fourier math fonts, and
not the other way round. (That's in t1fnc.fd and ts1fnc.fd.) YMMV
how that looks when math is embedded in normal text.

When I commissioned the LaTeX support for these fonts from Micheal,
I couldn't convince him that it might be a better idea to scale the
math fonts up, he foresaw problems with line thickness at fractions
and such. Well, even though he couldn't convince me concerning these
problems, he was the author and so it's scaling text fonts down and
not math fonts up.

Just FYI,

Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jsc...@acm.org
Roedermark, Germany

Alan Ristow

unread,
Oct 31, 2006, 9:34:32 AM10/31/06
to
Joachim Schrod wrote:
> Randy Yates wrote:
>> When I add the package \usepackage{fouriernc} to my document, I begin
>> getting the string of encoding warnings listed at the end of this
>> message. I don't get these warnings if I use CM fonts or txfonts
>> instead.
>
> That's because they use a different math encoding, the default math
> encoding and fonts have already been oaded earlier, and they are
> substituted at this point. I know of no method to prevent the earlier
> loading of the default (cmm) fonts, which would be needed to quiet down
> the warning messages; but I have to admit that I have also not
> investigated it in more detail. Maybe I ask Frank when I see him the
> next time, if one can stop this somehow.

Perhaps \RequirePackage{fouriernc} *before* \documentclass? I haven't
specifically checked whether this quells the warning messages (I set up
my editor to stop flagging them before I started using this method), but
I have frequently used this construction with fourier.sty in order to
set certain dimensions that would otherwise be based on CM metrics. I
admit I have no idea whether it works by *preventing* the loading of CM
in the first place or by simply loading a new font *after* CM but
*prior* to the class declarations, but I suppose it would need to be the
former in order to stop the warnings. The fact that I occasionally have
a CM glyph slip into a document suggests that CM certainly is (or can
be) loaded at *some* point, even with \RequirePackage before \documentclass.

Just a thought.

Alan

0 new messages