Re: A "slash o" ?? Cannot get it...
ehud.kap...@gmail.com wrote: > When I type Bro{\o}sted I get the right character. The {..} is ERT, of > course. To see what I mean when I say the braces affect the kerning, compare 1. V\AA V 2. V\AA{}V 3. V{\AA}V You will see that the kerning is only good in the first case. In the second case, the Å and the second V are badly kerned, in the third case, all three characters are badly kerned. Jürgen
Re: A "slash o" ?? Cannot get it...
When I type Bro{\o}sted I get the right character. The {..} is ERT, of course. On 02/03/2011 03:12 AM, Jürgen Spitzmüller wrote: Also sprach Kenward Vaughan: The space worked fine. Should that always be done with ERT? To terminate a command, if no other termination is done. In your case, LaTeX thought you meant the command \onsted (which could very well be meant), and failed, because no such command existed. If another command follows (Br\o\ss), not termination is needed. You can also terminate by braces (Br{\o}nsted or Br\o{}nsted), but this affects the kerning, so the space is suggested. Jürgen -- Ehud Kaplan, Ph.D. Jules and Doris Stein /Research to Prevent Blindness /Professor *Director*, Center of Excellence for /Computational & System neuroscience,/ The Friedman Brain Institute, MSSM *Director*, The laboratory of /Visual & Computational Neuroscience/ Depts. of Neuroscience, Ophthalmology, Chemical & Structural Biology The Mount Sinai School of Medicine One Gustave Levy Place New York, NY, 10029
Re: A "slash o" ?? Cannot get it...
Julien Rioux wrote: > I'm curious... how does {} affect the kerning? Because TeX does not treat the two characters as a pair for proper kerning. > Is one of {\o} or \o{} preferable? No. > The space is problematic when processed by bibtex: > "J. N. Br\o nsted" will become "nsted, J. N. B." Try {Br\o nsted} Jürgen
Re: A "slash o" ?? Cannot get it...
On 03/02/2011 3:12 AM, Jürgen Spitzmüller wrote: Also sprach Kenward Vaughan: The space worked fine. Should that always be done with ERT? To terminate a command, if no other termination is done. In your case, LaTeX thought you meant the command \onsted (which could very well be meant), and failed, because no such command existed. If another command follows (Br\o\ss), not termination is needed. You can also terminate by braces (Br{\o}nsted or Br\o{}nsted), but this affects the kerning, so the space is suggested. Jürgen I'm curious... how does {} affect the kerning? Is one of {\o} or \o{} preferable? The space is problematic when processed by bibtex: "J. N. Br\o nsted" will become "nsted, J. N. B." -- Julien
Re: A "slash o" ?? Cannot get it...
Also sprach Kenward Vaughan: > The space worked fine. Should that always be done with ERT? To terminate a command, if no other termination is done. In your case, LaTeX thought you meant the command \onsted (which could very well be meant), and failed, because no such command existed. If another command follows (Br\o\ss), not termination is needed. You can also terminate by braces (Br{\o}nsted or Br\o{}nsted), but this affects the kerning, so the space is suggested. Jürgen
Re: A "slash o" ?? Cannot get it...
Kenward Vaughan wrote: > Being a perfectionist, I'd love to get the name Bronsted properly > spelled, with a slash through the o. Using LyX, I've inserted "\o" in > ERT, but get an undefined control sequence error: > > > ...Define a \inputencoding{latin1}{Br\onsted > }\inputencoding{latin9}-L > owry You need to terminate the macro by a space, i.e.: Br\o nsted. Or insert the real character via Insert > Special Characters > Symbols. Jürgen
A "slash o" ?? Cannot get it...
Being a perfectionist, I'd love to get the name Bronsted properly spelled, with a slash through the o. Using LyX, I've inserted "\o" in ERT, but get an undefined control sequence error: ...Define a \inputencoding{latin1}{Br\onsted }\inputencoding{latin9}-Lowry The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. I can make umlauts, etc., but this one evades me. Does anyone know what my mistake is? Using LyX 2.0b3 in Debian (Sid). It happens with 1.6.7 as well. :( Thanks! Kenward -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein