LaTeX.org

Hi again Egon and thanks for your time! Your suggestions are always inspiring. :)

I can just add that I TOTALLY agree with your point. I also was a little afraid for the \chaptermark breakable code. About the duplicated code, actually I didn't think about that! I could have been smarter...

I'm ...

Ok,

I've got the answer to the second STUPID question.
Sorry for that.
I didn't realized that the code is executed BEFORE the evaluated variable is set in the main file. Again, sorry for that.

My first question still remains.
Thanks,
F.

Hi 5gon12eder,
thanks for your kind reply.

As soon as I submitted my question I realized that adding code to \chapter would make no sense. Indeed it is not so obvious that every chapter has at least a figure.

That said, I read your suggestion and implemented your code: it worked like a charm. The ...

Hi all,

I've searched the forum and the Internet for clues about this point but, as far as I've searched, I didn't resolve my problem.

I want to had the chapter titles, along with their numbers, in the LoF and LoT. I've found the two commands to do this. Unfortunately none of them suits my needs ...

Ok,

I've removed the
\MakeUppercase
command from the fancy header definition and everything works perfectly. It is really a pleasure to see that I've coded everything the right way. It is also a pain to think that, such simple command, screwed everything. :?

But anyway, again, thank you so ...

Thanks for the super-fast answer!

So the point is all in the headings. I do not need to worry about the footnotes. That's good. :)

As I said, I've used fancy header in the real file...and I have to check for the options I've chosen. Probably capitalized text anyway, since the warning is the same ...

It cost me sweat and toil but I think I've found the minimal example. Indeed, it is quite interesting (for my knowledge of LaTeX, at least!).

Basically it seems that there's some kind of clashing between the headings (also the basic ones not the fancy stuff), the footnotes and my stupid command. I ...

Indeed, it also work for me.
Probably the warning is caused by something else. I'll try to slice my code, section by section. If I would find something, I'll share it.

Thanks for your time!
F.

Hi Stefan,
thanks for the kind reply!

You're right about the warning given to me. Anyway, I have the same warning even if I set the font/series/shape used as substitution font, i.e.
\newcommand{\command}{{\fontfamily{cmr}\fontseries{m}\fontshape{n}\selectfont *text*}}
gives me the warning:
Font ...

Hi all,

first of all, my deepest apologies for my bad English.
I hope that this is the right place to post and, most of all, the right way of posting!

I have an annoying warning while using the command to change the default font.
Basically I have defined the following command:

\newcommand ...