Unfortunately I have several bibliography entries with umlauts but I need to have them parsed in the Latex way. E.g. "{\"{o}}" instead of "ö" etc. Selecting ISO8859-1 has the effect that I can not save the bibtex file anymore because of invalid characters. I would have expected that JabRef is converting non-ISO8859-1 characters automatically. Is there any way to do so because replacing every umlaut manually is not very efficient. If not, I would be very appreciated to include such feature in one of the next versions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right. The example you gave does not work. However, there is a workaround.
author = \{\\\x22O\}quist works with regular expressions enabled for {\"O}quist
so \" does not work as a escape for ", but \x22 (character hexadecimal 22 in ASCII table) does.
author = Bolh{\`a}r works with regular expressions disabled, and
author = Bolh\{\\`a\}r works with regular expressions enabled.
So it seems to be a problem on how " is handled on input... but you can use the \x22 escape sequence to work around this limitation.
I hope this helps,
Pedro.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-04-15
I am thinking about the same issue. But I think a conversion will produce a new problem. Have you tried to search a titel like "Kritik der politischen {\"O}konomie."? both, searches with Ö or {\"O} don't find the entry. Is it the same for you?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have not tried it in practice, but searching for {\"O} should work if regular expression search is not enabled. If you use regular expressions you should escape the characters with special meaning by putting a backslash before them. \\ for \, \{ for {, and \} for }. Please, give it a try and let us know whether it works.
I hope this helps.
Pedro.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-04-15
It does not work for me. Perhaps I'm using jabref not the right way....perhaps it's abug?!
I tried the search with an without regular expression
Benjamin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately I have several bibliography entries with umlauts but I need to have them parsed in the Latex way. E.g. "{\"{o}}" instead of "ö" etc. Selecting ISO8859-1 has the effect that I can not save the bibtex file anymore because of invalid characters. I would have expected that JabRef is converting non-ISO8859-1 characters automatically. Is there any way to do so because replacing every umlaut manually is not very efficient. If not, I would be very appreciated to include such feature in one of the next versions.
You are right. The example you gave does not work. However, there is a workaround.
author = \{\\\x22O\}quist works with regular expressions enabled for {\"O}quist
so \" does not work as a escape for ", but \x22 (character hexadecimal 22 in ASCII table) does.
author = Bolh{\`a}r works with regular expressions disabled, and
author = Bolh\{\\`a\}r works with regular expressions enabled.
So it seems to be a problem on how " is handled on input... but you can use the \x22 escape sequence to work around this limitation.
I hope this helps,
Pedro.
I am thinking about the same issue. But I think a conversion will produce a new problem. Have you tried to search a titel like "Kritik der politischen {\"O}konomie."? both, searches with Ö or {\"O} don't find the entry. Is it the same for you?
I have not tried it in practice, but searching for {\"O} should work if regular expression search is not enabled. If you use regular expressions you should escape the characters with special meaning by putting a backslash before them. \\ for \, \{ for {, and \} for }. Please, give it a try and let us know whether it works.
I hope this helps.
Pedro.
It does not work for me. Perhaps I'm using jabref not the right way....perhaps it's abug?!
I tried the search with an without regular expression
Benjamin