JabRef's current encoding list lists possible encodings.
The strings have flaws:
On the one hand, I am very well aware that a change here results in a large compatibility code where the old strings have to be mapped to the new strings. On the other hand, I would like to see JabRef having strings not causing confusion.
Related: #118, #131
JabRef's current encoding list lists possible encodings.
The strings have flaws:
UTF8andUTF-16are possible encodings. I really dislike the inconsistency between them:UTF8has no-, butUTF-16has: Both should have a dash resulting inUTF-8. (see https://de.wikipedia.org/wiki/UTF-8)Cp1251should beCP1251(see http://man7.org/linux/man-pages/man7/cp1251.7.html for example). Similar for all other code pagesISO8859_15should beISO8859-15(see https://de.wikipedia.org/wiki/ISO_8859-15). Similar for all other encodingsOn the one hand, I am very well aware that a change here results in a large compatibility code where the old strings have to be mapped to the new strings. On the other hand, I would like to see JabRef having strings not causing confusion.
Related: #118, #131