<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Le 18 mai 09 à 17:54, Yannis Haralambous a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I opened that font under FontLab, standard names are missing:<div><br></div><div>Family Name: UntitledTrueType</div><div>Menu Name : UntitledTrueType</div><div>FOND Name : UntitledTrueType</div><div><br></div><div>The Bengali name appears in the name table at position 1 (Font Family name) and in 4 (Full font name).</div><div><br></div><div>There is also entry 18 (Compatible Full), maybe you could try it: <span class="Apple-style-span" style="font-family: 'Lucida Grande'; font-size: 13px; ">SolaimanLipi-Regular</span></div></div></blockquote><div><br></div><div>It doesn't work either; I get:</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">This is XeTeXk, Version 3.1415926-2.2-0.999.6 (Web2C 7.5.7)</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; "> %&-line parsing enabled.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">entering extended mode</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">(./AAT-info.tex [1]</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">** ERROR ** Cannot proceed without the "native" font: SolaimanLipi-Regular (<span style="font: 10.0px রূপালী">সোলাইমান</span> <span style="font: 10.0px রূপালী">লিপি</span> Regular)...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">Output file removed.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; "> )</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">Error 256 (driver return code) generating output;</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">file AAT-info.pdf may not be valid.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Monaco; ">Transcript written on AAT-info.log.</div></div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">Otherwise I would contact the author and tell him to provide the standard font names...</span></div></div></blockquote><br></div><div>So I'll need some patience :)</div><div><br></div><div>I don't know if it's relevant, but obviously the system can use SolaimanLipi and its AAT features. For instance if I type "ki" in a text editor and I select Code2000 the "i" is misplaced (after the "k"), which is normal since Code2000 has no AAT features, but if I select SolaimanLipi the "i" is correctly placed (before the "i").</div><div><br></div><div>Yves</div><div><br></div><br></body></html>