That means in the new version of JabRef all groups are dynamic?
All the best
Josef
>
> [email protected] hat am 12. Juni 2016 um 16:31 geschrieben:
>
>
> Dear Haines,
>
> I'm sorry for the problems you have with the way Jabref handles groups in
> the new version. Let me explain what happened:
> Previously, the group membership was stored at the end of the file in one
> of these Jabref comments. This behaviour had some disadvantages, so we changed
> it. Now Jabref rembers the group information in the bibtex entry itself
> (BibEntry). So your entries now have a groups field (have a look at the bibtex
> source), where the names of the static groups are saved.
> Because only the names of the groups are stored in this new field, JabRef
> can no longer differentiate between groups with the same name. This might be a
> bit inconvienent, but you can fix it easily by giving the groups different
> names and then manually correcting the assignments.
>
> I hope this helps for now. If you still experience problems, please post
> them on github. https://github.com/JabRef/jabref/issues
> Best, Tobias
>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Jabref-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jabref-users
