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

'APOSTROPHE' (U+0027) not well displayed in the main table #2516

Closed
Doc73 opened this issue Feb 3, 2017 · 8 comments
Closed

'APOSTROPHE' (U+0027) not well displayed in the main table #2516

Doc73 opened this issue Feb 3, 2017 · 8 comments

Comments

@Doc73
Copy link
Contributor

Doc73 commented Feb 3, 2017

JabRef version 3.8.1 on Debian 8 Jessie AMD64

Steps to reproduce:

  1. Insert this code in the bib file:
@Incollection{Mengaldo2007,
  author       = {Mengaldo, Pier Vincenzo},
  booktitle    = {L'età contemporanea},
  title        = {«L'opera in versi» di Eugenio Montale},
  date         = {2007},
  volume       = {15},
  keywords     = {italian},
  booksubtitle = {Le opere (1921-1938)},
}
  1. Give a look to the title field in the main table
  2. You should see this:
    mengaldo

Many thanks,
Domenico

@AEgit
Copy link

AEgit commented Feb 3, 2017

Might be a duplicate of this:

#2498

But to be honest I can't replicate this behaviour on JabRef 3.8.2. Have you changed your entry preview preferences for the field "title" from HTMLChars to LatexToUnicode or viceversa (see also here: http://discourse.jabref.org/t/change-of-default-of-entry-preview/446)?

@Doc73
Copy link
Contributor Author

Doc73 commented Feb 3, 2017

I modified my preferences accordingly, but the issue still persists. :-(

However, my issue is not in the preview, but in the main table, as in above screenshot.

@Doc73
Copy link
Contributor Author

Doc73 commented Feb 3, 2017

Another screenshot:

mengaldo

@AEgit
Copy link

AEgit commented Feb 3, 2017

Ooohhh, sorry - my bad. Indeed, in the main table I get the same behaviour. Yes, this has nothing to do with the preview settings. I guess this might be solved, once the latex2unicode lib is implemented (see here: #2465).
@lenhard: Any thoughts on this?

@Doc73
Copy link
Contributor Author

Doc73 commented Feb 4, 2017

Ah! It seems that the bug was already fixed. Please, see: #2500 and #2507.

If so, you could close this bug report.

@AEgit
Copy link

AEgit commented Feb 4, 2017

You could test the current master build to see whether the bug has actually been fixed for you:
https://builds.jabref.org/master/
(you might want to make a backup of your bibtex-database first, before trying the new build)

If the the new build does not contain the bug you can either keep the current master or go back to the old (bugged) version and wait for the release version.

You can then close the bug report (I'm afraid I cannot do that, as I'm not part of the JabRef development team).

@Doc73
Copy link
Contributor Author

Doc73 commented Feb 4, 2017

Yes, it works!
I close this issue.

@Doc73 Doc73 closed this as completed Feb 4, 2017
@AEgit
Copy link

AEgit commented Feb 4, 2017

Good to hear!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants