<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> Just a follow up to people interested in the localization.<div>After a nice oversea skype conversation with Axel we arrived to a final agreement.</div><div>The LOCALIZE keyword has been restructured in order to avoid too many</div><div>nested sections. That's how the final template looks like:</div><div><br class="webkit-block-placeholder"></div><div>DFT%PRINT%LOCALIZATION%LOCALIZE has been moved into DFT%LOCALIZE</div><div>DFT%PRINT%LOCALIZATION%LOCALIZE%PRINT%WANNIER* moved into DFT%PRINT%LOCALIZATION</div><div><br class="webkit-block-placeholder"></div><div>LOCALIZATION is therefore now just a container for print_key based on localization. </div><div>the LOCALIZE%PRINT does not exist anymore.</div><div>For XAS and LINRES the corresponding LOCALIZE%PRINT%WANNIER* have been moved into XAS%PRINT and LINRES%PRINT.</div><div>This should be the best compromise in order to have some logic grouping of common keywords and</div><div>avoid, at the same time, too many nested section to print basic quantities.</div><div><br class="webkit-block-placeholder"></div><div>All changes are already in the CVS.</div><div><br class="webkit-block-placeholder"></div><div>Cheers</div><div>Teo</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><div><div>On 20 Oct 2008, at 20:45, Axel wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">anyways, i think we should move this to a private discussion (skype?)</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">in the hope to converge to a result that satisfies both of us faster.</font></p> </blockquote></div><br></div></body></html>