Enrico Forestieri wrote: > Sorry for stepping in so late, but I think that it is useful to directly > see on screen the info provided by MarkBoth. I had already solved the > bug but forgot to share the solution. Shame on me.
No problem. > I propose to add the following to the preamble: > > % Note: the following fixes a bug with older versions of babel > % http://www.latex-project.org/cgi-bin/ltxbugs2html?pr=babel/3238 > \DeclareRobustCommand{\FOREIGNLANGUAGE}[1]{\lowercase{\foreignlanguage{#1}} >} Of course, this lowercase solution fails for any language that has a capital in the name (currently only "USenglish" and "UKenglish", so maybe just a theroretical problem). > % More recent babel versions already have the above definition, but > introduce % yet another related bug. Using these versions, when you change > the language, % you have to accordingly substitute both 'ENGLISH' and > 'english' below. [EMAIL PROTECTED]@english > > See the attached sample .lyx file. A drawback is that when changing the > document language to something else than english, say "american", one > has to update the above line to read > [EMAIL PROTECTED]@american > but maybe it is better than having to write the \markboth command > in the preamble. > > I didn't try hard to find an automatic solution along the lines of the > \DeclareRobustCommand above, but I really don't have time to go > through the babel code. Maybe someone else could do it. > > Josè, let me know if you prefer the solution above to having \markboth > in the preamble. A general problem I see is the following: I assume (but I'm not sure) IEEETran.cls is mostly used by people who actually want to submit a LaTeX file to an IEEE journal. In this case it might be relevant that your solution produces a significantly "uglier" LaTeX file just for the sake of displaying MakeBoth on screen. I'm not sure if this is worth it. If you think it is, then I suggest to add the preamble definitions to the MarkBoth definition in the layout file, so that it is only inserted if MarkBoth is actually used. And then document the pros and cons of both solutions, especially for people who want to submit their file to a journal. Jürgen
