Hello everyone,

I have noted in my bib database that JabRef does not save properly the author 
name or article title when these have a LaTeX command. Here is an example:

This my original entry:
--------------------------------------------------
@ARTICLE{crnjaric-2004,
  author = {{N}elida {\v{C}}rnjari{\'{c}}},
  title = {{T}he $\nabla\cdot\mathbf{B}=0$ constraint},
  journal = {{J}ournal of {C}omputational {S}tuff},
  year = {2034},
  volume = {234},
  pages = {1234-1328},
  number = {4},
  file = {crnjaric-2004.pdf:crnjaric-2004.pdf:PDF}
}

Here is what JabRef does when saving and I restart the application:
--------------------------------------------------
@ARTICLE{crnjaric-2004,
  author = {{N}elida {\vC}rnjari{\'{c}}},
  title = {{T}he $\nabla\cdot\mathbfB=0$ constraint},
  journal = {{J}ournal of {C}omputational {S}tuff},
  year = {2034},
  volume = {234},
  pages = {1234-1328},
  number = {4},
  file = {crnjaric-2004.pdf:crnjaric-2004.pdf:PDF}
}

Observe please see the changes in author (\v{C} -> \vC) and in the title 
(\mathbf{B} -> \mathbfB). Naturally, at compilation time, LaTeX will generate 
errors, commands not defined (in this case \cV and \mathbfB). 

I solve temporaly this writing (\v{C} -> \v C) and (\mathbf{B} -> \mathbf B).

There is a way that JabRef does not change the entry values in these cases 
where LaTeX commands are presents?

Thank you very much. Great Job you have done with JabRef.

Jonatan

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Jabref-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jabref-users

Reply via email to