Repeated cleaning of % sign in abstract field results in \\% which gives a LaTeX error

[bernhard-kleine]

JabRef 3.8.1
windows 7 6.1 amd64
Java 1.8.0_66

I noticed after an errorneous biber compilation that cleaning the % sign is not without risk: I found in the bib-file doublebackslashed % (\\%) which do help since they have the meaning of a new line and and a % sign. Obviously the cleaning does not discriminate between \% and %.

Steps to reproduce:

1. a bibentry with a % sign in the abstract like PMID 27151464
2. run Quality > Cleanup Entries ( with abstract: Latex cleanup added) twice

I may be wrong since a cannot reproduce this, but I know for sure that yesterday I found the backslash doubled and I did not anything but the cleanup.

BTW I noted also that between the % sign and the following dot a misplaced white space was added.

Perhaps someone can reproduce this issue.

[matthiasgeiger]

Hi Bernhard!
Sorry, that I have not seen your post in the forum earlier - I think this problem has already been fixed in #2445 (which is a fix for a similar reported problem #2426) - can you please check using a development build from https://builds.jabref.org/master

Thanks!

[bernhard-kleine]

Actually I cannot repeat it, therefore I don't know what to do. Even the cleaning of a % sign does not work. I am stymied.

[Siedlerchr]

Hi, I tested this in 4b65c3b
and encountered the following behaviour (only in biblatex mode)

Add: abstract: Latex Cleanup
First Cleanup run: The % sign is correctly encoded into %
Second run:, I get: \% with a preceding slash.
Third run, I get: 50\\%
So each time, there is added a backslash.
And after each run I saved it.

When I open the bibtex file, I see:
50\\\\%

[bernhard-kleine]

With 3.8.2. on a fresh database I loaded PMID 27151464 via the Medline fetcher, started Cleanup and got the status: doing cleanup for on entry, but it never finished and the % sign in the abstract was not escaped.

[Siedlerchr]

I recently experienced the same with the ProtectTerms formatter.
When you run it first, it protects the terms correctly. If you run it again, the already protected terms are protected again, by adding more braces around them...

[Siedlerchr]

@bernhard-kleine I found the problem, it was a problematic RegEx and fixed it.
In a couple of minutes you can try the version here http://builds.jabref.org/multicleanup/

[bernhard-kleine]

I have installed the file but it has errors: Cleanup does not finish, "save as" not work, I cannot confirm that the problem has been dealt with. Sorry.
(the testing was done on a fresh database with importing the entry PMID 27151464, with contains in the abstract a 50% to be cleaned.)

[Siedlerchr]

Ah I see the problem. Will fix that.

[Siedlerchr]

@bernhard-kleine Should be fixed now. You can try again to download the version from there

[bernhard-kleine]

the cleanup worked thank you, but, still, no way to save the bib-file in the entry, no save as in that snapshot

[Siedlerchr]

Could you please open a new issue for the saving problem and give some more details? Do you get any errors in the log? Am 05.02.2017 11:07 nachm. schrieb "Bernhard Kleine" < notifications@github.com>:

…

the cleanup worked thank you, but, still, no way to *save* the bib-file in the entry, no *save as* — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2451 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AATi5L_dukpraKKIm4-KBuQIcnC9Uhq2ks5rZkg6gaJpZM4LeCaS> .

[lenhard]

Since the original problem described here seems to be fixed (and the fix is confirmed), I will close this issue now.

For new problems in the UI, please open a new issue, thanks!