-
mortenalver committed revision 3134 to the JabRef SVN repository, changing 5 files.
2009-11-06 18:32:07 UTC in JabRef
-
I found more information about the format here: http://www.docbook.org/tdg/en/html/authorgroup.html
so you can ignore my previous question.
2009-11-06 18:26:20 UTC in JabRef
-
Thank you for reporting this! JabRef normally handles names formatted in this way correctly in all operations. For the Docbook export it turns out a formatter is run before the name formatting, that replaces the comma by an XML sequence, which makes the name handling routine misunderstand the contents.
I am fixing this for the next version. However, I also see that there is no handling of...
2009-11-06 18:20:17 UTC in JabRef
-
Thank you for reporting this! I have modified the search dialog so it automatically previews the first record. If a search gives no hits, the preview is hidden.
2009-11-06 17:52:57 UTC in JabRef
-
mortenalver committed revision 3133 to the JabRef SVN repository, changing 4 files.
2009-11-06 17:52:20 UTC in JabRef
-
The previous comment was mine (forgot login).
2009-11-06 08:27:59 UTC in JabRef
-
The file type should be given by its name, not its file extension. Try "\begin{file}\format[FileLink(powerpoint)]{\file}\end{file}" and see if that works.
Looking at the code, it seems you may need to specify it in lower case only, so "PowerPoint" might not work.
2009-11-06 08:00:00 UTC in JabRef
-
Thank you for reporting this! It seems to be related to the autowrapping of the meta-comments. Removing a single letter from one of the keywords in the last comment makes the line breaks consistent, so perhaps it fails in some way when the last line turns out to be of a certain length.
I'll look into it.
2009-11-05 11:53:56 UTC in JabRef
-
I haven't thought of it that way before. The database is marked as changed whenever you make a change to the contents in memory. In the case where you accept all external changes this still changes the contents, although as you say it has the net effect of bringing the database in sync with the version on disk.
2009-11-05 10:21:53 UTC in JabRef
-
I see what you mean. The cause of this is that the function comparing different database versions doesn't take order into account in any way. This scenario has simply not been considered. I'll have to think about whether and how it can be solved.
2009-11-05 10:02:36 UTC in JabRef
