Value delimiters: configuration of using quotes or force always curly braces?

[koppor]

@kubovy introduced configration of value delimiters in 4f9fb0b, @mortenalver removed the configuration option in 74e7296. I remember that there was an issue regarding escaping the " in Strings delimited with "" and therefore the choice was just disabled.

The user had the choice between "..." and {...} as value delimiters. Currently, only {...} are used.

Regarding our discussion at #116 and that " is really seldomly used in the wild, I would propose to remove net.sf.jabref.JabRefPreferences.VALUE_DELIMITERS2 and all transitive dependencies.

[stefan-kolb]

👍

[simonharrer]

👍 for deleting code :-)

[oscargus]

See this for a discussion. The only examples given support that {...} is the better choice (or at least not worse).

However, it can be noted that Tame the BeaST -- The B to X of BibTeX uses "..." in all their examples (except the one talking about the two alternatives).

Google Scholar generates entries with {...}.

Still, I guess that it would be good if JabRef can read .bib-files that use "..." and possibly warn that they will be written back using {...}.

I would vote for completely removing support for "..." too. I do not see any use case where it would be beneficial to use "..." compared to {...}.

[kubovy]

👍

[lenhard]

Parsing works with quotes instead of curly braces as well (see the test implemented in 4a93387).

I think there is a consensus here, so I am closing this issue.