<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Christian,<div><span class="Apple-tab-span" style="white-space:pre"> </span>Chimera is <i>supposed</i> to honor the element column and apparently it is not. I'll open a ticket in the Chimera Trac database for this bug and will put you on the CC list for it. It will definitely be fixed by the next release. Sorry it didn't work!</div><div><br></div><div>--Eric</div><div><br><div><div>On Mar 19, 2009, at 6:49 AM, Christian Schudoma wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Thanks Elaine and Eric, for your quick replies and clarification.<br>Nevertheless, the "element column override" (s. below) doesn't work for me, regardless of where in the element record I place a single-character element symbol (neither placing it in column 77 nor in 78).<br><br>Best regards,<br>Christian<br><br><br>Eric Pettersen wrote:<br><blockquote type="cite">To supplement what Elaine said, without the column-positioning of the atom name it would be impossible to distinguish a carbon alpha (CA) from a calcium (CA). Though if you provide the element symbol in columns 77-78 then the atom name will be ignored for determining the element.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">--Eric<br></blockquote><blockquote type="cite"><br></blockquote><br></div></blockquote></div><br></div></body></html>