4 ms·

Does it fix incorrect Unicode chars? I've had a huge problem with that recently when for some reason Kbibtex insisted on converting {\"O} into Ö. I believe Jabr

Does it fix incorrect Unicode chars? I've had a huge problem with that recently when for some reason Kbibtex insisted on converting {\"O} into Ö. I believe Jabref fixed it but I've made very bad experiences with Jabref in the past and would prefer not to use it.

azalemeth 5y ago
This doesn't answer the question, but I think that if you use XeLaTeX you get Unicode support universally "for free", including in bbl files (generated by bibtex, bibtex8 or biber -- which itself is great, even if it has more of a learning cliff than most!)
- skateboardCat 5y ago
  IME biber still nags you about unicode in weird ways; i ended up always escaping that characters to avoid breaking the compilation, so YMMV
shoeffner 5y ago
What do you mean? I tried placing Ö and {\"O} in the author's name of the example and tidied it: Click Tidy to clean up the entries below @Book{sweig42, Author = { Stef{\"O}{n} SwÖig }, title = { The impossible book }, publisher = { Dead Poet Society}, year = 1942, month = mar } This is the output: Click Tidy to clean up the entries below @book{sweig42, title = {The impossible book}, author = {Stef{\"O}{n} SwÖig}, year = 1942, month = mar, publisher = {Dead Poet Society} } And \"O should be Ö, so I guess I do not really understand what is "incorrect" in your use case. I know that the Zoteroplugin BetterBibTeX converts Ö to {\"O} when exporting as BibTeX, but keeps it as Ö when exporting as BibLaTeX – maybe Kbibtex has similar options? edit: It actually "fixes" Ö to {\"O} if you tick "Escape special characters" or supply the command line argument `--escape`, which should be the default according to GitHub.
- jonathanstrange 5y ago
  I meant leaving the Ö as is or even introducing it, which is always wrong with Bibtex. I'm not using Zotero but Jabref also fixes it. There was an Ö in an author name and when I manually changed it to {\"O} Kbibtex reverted it back to an Ö! It's easy to fix by switching to XeTeX but some editorial systems don't use it and will make your manuscript fail. I was just hoping that the tool fixes this problem, too. Maybe in a future version.

azalemeth 5y ago

This doesn't answer the question, but I think that if you use XeLaTeX you get Unicode support universally "for free", including in bbl files (generated by bibtex, bibtex8 or biber -- which itself is great, even if it has more of a learning cliff than most!)

skateboardCat 5y ago
IME biber still nags you about unicode in weird ways; i ended up always escaping that characters to avoid breaking the compilation, so YMMV

shoeffner 5y ago

What do you mean? I tried placing Ö and {\"O} in the author's name of the example and tidied it: Click Tidy to clean up the entries below @Book{sweig42, Author = { Stef{\"O}{n} SwÖig }, title = { The impossible book }, publisher = { Dead Poet Society}, year = 1942, month = mar } This is the output: Click Tidy to clean up the entries below @book{sweig42, title = {The impossible book}, author = {Stef{\"O}{n} SwÖig}, year = 1942, month = mar, publisher = {Dead Poet Society} } And \"O should be Ö, so I guess I do not really understand what is "incorrect" in your use case. I know that the Zoteroplugin BetterBibTeX converts Ö to {\"O} when exporting as BibTeX, but keeps it as Ö when exporting as BibLaTeX – maybe Kbibtex has similar options? edit: It actually "fixes" Ö to {\"O} if you tick "Escape special characters" or supply the command line argument `--escape`, which should be the default according to GitHub.

jonathanstrange 5y ago
I meant leaving the Ö as is or even introducing it, which is always wrong with Bibtex. I'm not using Zotero but Jabref also fixes it. There was an Ö in an author name and when I manually changed it to {\"O} Kbibtex reverted it back to an Ö! It's easy to fix by switching to XeTeX but some editorial systems don't use it and will make your manuscript fail. I was just hoping that the tool fixes this problem, too. Maybe in a future version.