Take the 2-minute tour ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

I'm having the following problem:

My document compiles properly before running bibtex. When I try to recompile after running the bibtex command it gave this compiling error:

    Runaway argument?
    \MakeLowercase {os estilos de aprendizaje: procedimientos de diagn\IeC \ETC.
    ! File ended while scanning use of \blx@mkcp@end.
    <inserted text> 
    \par 
    <*> these

I checked the bibfile and there is an entry with this title:

   @book{alonso1991,
   Address = {Bilbao, Espa{\~n}a},
   Author = {Alonso, C. M. and Gallego, D. J. and Honey, P.},
   Publisher = {Complutense},
   Title = {Los estilos de aprendizaje: procedimientos de diagn{\'\o}stico y mejora},
   Year = {2007}}         

It seemed ok to me.

I'm using biblatex, before using biblatex this problem wasn't happening.

share|improve this question
1  
You'll need to give more information than this. The bib record itself is unlikely to be the problem. (Make a simple document which just cites this bib item and prints the bibliography and you should find that it works.) The problem is more likely to be caused by code around where you are doing the cite command itself. Again, make a minimal working document that shows the problem. Or try removing all the .aux files, latex your file again and then run bibtex again. –  Alan Munn May 11 '11 at 16:46
    
Please always provide a minimal working example. So it's much easier to locate your problem. –  Thorsten May 11 '11 at 16:47
1  
This compiles fine for me. Are you sure you mean diagn{\'\o}stico? This compiles as ø with an accent on it... –  Seamus May 11 '11 at 16:51
    
Hi, thanks for your help. I try in a new document and it works. I don't how to track what is messing up the things in the large document... thanks for you help! –  Rafael May 11 '11 at 19:05
    
Make a copy of your document, comment out more and more code until the problem goes away. Once it has gone away, the last thing you commented out was the problem. If you still can't figure out, update your question with the (hopefully) few lines that are left. Usually the first thing that can go is all of the content. –  TH. May 12 '11 at 1:32
show 1 more comment

closed as not a real question by lockstep, Alan Munn, Joseph Wright Jul 15 '11 at 21:58

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.