Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backslashes are repeatedly escaped on save in Content-Selectors #2426

Closed
universal opened this issue Dec 22, 2016 · 2 comments · Fixed by #2445
Closed

Backslashes are repeatedly escaped on save in Content-Selectors #2426

universal opened this issue Dec 22, 2016 · 2 comments · Fixed by #2445
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs status: waiting-for-feedback The submitter or other users need to provide more information about the issue

Comments

@universal
Copy link

Hello,

JabRef version: JabRef 3.8; linux 4.4.0-57-generic amd64; Java 1.8.0_111 on Ubuntu 16.04
Steps to reproduce:

  1. Create a new, empty database (bibtex mode)
  2. Add a keyword under manage content selectors for journal: Test {"U}mlaut
  3. Hit Save
  4. Check comment in editor: ... Test {\"U}mlaut ...
  5. Restart Jabref
  6. Hit Save
  7. Check comment in editor: ...Test {\\"U}mlaut

So with every save each Backslash is escaped again and again.

1. Save

% Encoding: ISO-8859-1

@Comment{jabref-meta: databaseType:bibtex;}

@Comment{jabref-meta: selector_journal:Test {\\"U}mlaut;}

2. Save

% Encoding: ISO-8859-1

@Comment{jabref-meta: databaseType:bibtex;}

@Comment{jabref-meta: selector_journal:Test {\\\\"U}mlaut;}

I hope this provides all necassary and relevant information. I hope I haven't missed something. :-)

@koppor koppor added the bug Confirmed bugs or reports that are very likely to be bugs label Dec 22, 2016
@lenhard
Copy link
Member

lenhard commented Dec 27, 2016

Thanks for your report! This sounds like something that is hopefully not too hard to fix. I will have a look at it after new year.

@lenhard
Copy link
Member

lenhard commented Jan 5, 2017

@universal In a few minutes, a dev version of JabRef that fixes this issue should be available here: http://builds.jabref.org/contentselector-escaping/ Can you please try it out?

Please note that meta data information in JabRef has to be escaped. Thus, if you enter a new selector keyword {\"U}mlaut in the UI, it should be written into the bibfile on save as {\\"U}mlaut, but upon parsing {\"U}mlaut should be displayed in the UI and written into an entry if you select it.

@lenhard lenhard added the status: waiting-for-feedback The submitter or other users need to provide more information about the issue label Jan 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs status: waiting-for-feedback The submitter or other users need to provide more information about the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants