<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Apostolos, Ulrike, All,<div><br></div><div>I agree TFMs are outdated, but for being backwards compatible the functionality</div><div>has to be in there.</div><div><br></div><div>From what I have so far understood about LuaTeX is that the font loader can handle</div><div>about all types of fonts running around, today. Even AAT-fonts. </div><div><br></div><div>In other words there is a possibility to add ATSUI-functionality. If it is not there already.</div><div><br></div><div>LuaTeX handles utf-8 natively and has support for older encodings, so no problem there</div><div>either.</div><div><br></div><div>One has to keep in mind that LuaTeX is still evolving. The developers have taken a very good</div><div>approach:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>1) get LuaTeX-proper working</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>2) add needed features</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>3) preserve backwards compatibility</div><div><br></div><div>Missing features in the handling of eg. not so commonly used OT-features, is not necessarily</div><div>an oversight on their part. Just, like the missing language support in TeX.</div><div><br></div><div>So far, I do not see why LuaTeX can not have similar functionality as XeTeX. It will have a different</div><div>syntax. just as XeTeX is different than LaTeX.</div><div><br></div><div>To get there though one has to get involved. The more involved the better the chance that packages</div><div>will be written so it is no longer needed to do the processing by hand. This is the TeX-way.</div><div><br></div><div>regards</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Keith.</div><div><br></div><div> <br><div><div>Am 07.08.2012 um 09:06 schrieb Apostolos Syropoulos <<a href="mailto:asyropoulos@yahoo.com">asyropoulos@yahoo.com</a>>:</div><div><br></div><blockquote type="cite"><span style="font-family: monospace; ">Ulrike Fischer <</span><a href="mailto:news3@nililand.de" style="font-family: monospace; ">news3@nililand.de</a><span style="font-family: monospace; ">> a écrit:</span></blockquote><blockquote type="cite"><blockquote type="cite"><br>I understand you're concerned about future font support in LuaTeX, but<br>technically the engine is little more than an extendable PDFTeX. Fonts<br>follow that philosophy: TFM (with mapping to T1) fonts are supported<br>as in PDFTeX, other formats must be loaded and processed by hand. Whether<br>it's a good idea or not in that case I don't know, but it is definitely<br>consistent. (Actually I do think it's a good idea, but I accept my<br>opinion might be marginal.)<br><br></blockquote><br>Using TFMs and related technologies seems to me quite outdated. Personally,<br>I want to be able to use any font my system includes without having to do<br>fancy transformations. This and XeTeX's capability to natively process<br>UTF-8 source files were the factors that made me abandon "good", (really)<br>old TeX. BTW, TeX itself is consistent too, but it is definitely outdated.<br><br></blockquote></div><br></div></body></html>