Let me rephrase this: the use of the keyword separator is ambiguous in JabRef.
It is by default set to ,. This leads to:
- StringTokenizer splits on both
, and
- when adding keywords
, is used as a separator
Clearly these two behaviors are just by luck sometimes compatible. Based on 1. it would be better to have , as the default.
In addition, the EntryUtil method for splitting on keywords used by BibEntry totally ignores this.
Relates to #705
( @Siedlerchr 's comment was for the previous wording of this, although it is still relevant.)
I can in this context note that quite a bit of the refactoring I've made recently has been to pass this separator down to the correct methods. Except for the fact that I know that it is bad, I would almost suggest having the separator as a global static variable in model...
Let me rephrase this: the use of the keyword separator is ambiguous in JabRef.
It is by default set to
,. This leads to:,and,is used as a separatorClearly these two behaviors are just by luck sometimes compatible. Based on 1. it would be better to have
,as the default.In addition, the EntryUtil method for splitting on keywords used by BibEntry totally ignores this.
Relates to #705
( @Siedlerchr 's comment was for the previous wording of this, although it is still relevant.)
I can in this context note that quite a bit of the refactoring I've made recently has been to pass this separator down to the correct methods. Except for the fact that I know that it is bad, I would almost suggest having the separator as a global static variable in model...