-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Rework used encodings #2013
Comments
One thing that we talked about earlier with regard to the I want to note that this is nothing we "broke", JabRef has always done that as far as I can recall. |
Its ignored by the parser but not by the importer:
|
I see. My knowledge seems to be confined to the deeper parts of our parsing stack ;-) |
I don't think that we currently have open issues related to the encoding. Although the used encoding is still sometimes a bit mystic, I will close this issue now. |
I think JabRef sometimes uses encodings which are a bit counter-intuitive or where a better alternative might be available. Triggered by JabRef/JabRef-Browser-Extension#33.
In this issue, I try to collect the current usage of encodings so that we get an overview. Feel free to edit this list.
--importToOpen
)Legend:
The text was updated successfully, but these errors were encountered: