On Sun, Dec 4, 2011 at 3:55 PM, Hin-Tak Leung <hintak_le...@yahoo.co.uk> wrote:
> --- On Sun, 4/12/11, Werner LEMBERG <w...@gnu.org> wrote: > swath isn't advertised on the front of thailatex's web site. Oh, I thought I had done this but actually had not. I'll add it soon. (In fact, it's currently hidden in some linked documents.) >> > That's ironic: Texlive 2011 ships thailatex fonts >> ready for CJK's >> > use, but not for thailatex's own use. >> >> Thailatex is a rather recent addition to CTAN inspite of >> its age. >> IIRC, it wasn't present three years ago. Karl Berry >> has added the >> font part of thailatex to TeXLive in 2009, but it seems to >> be a >> non-trivial issue to do the rest: Currently, the LaTeX >> files of >> thailatex are in `$TEXMF/source' only. >> >> I suspect the main problem is the dependency on a new >> binary, namely a >> Thai word separator program (not part of thailatex itself) >> which must >> be available on all platforms TeXLive supports. >> However, looking into >> the thailatex SVN repository, I see that Theppitak is doing >> a lot of >> work recently, so maybe things are moving. What I've done recently was splitting the fonts back to their source. Previously, the generated fonts were copied over to thailatex on every update in their source and thailatex was then triggered for re-release with pure font changes. Now they're shipped directly from the source instead. This decoupling also allows alternative Thai LaTeX font packages, e.g. fonts-arundina, and yet more to come. My next plan, then, is to clean up the Thai language definition and submit it for inclusion in upstream babel, and thailatex won't be needed any more, only the fonts left for users to install. (Could someone suggest me who to contact?) > Actually my main grief with thailatex is its odd circular division/dependency > with the thaifonts. Without a ready-made set of font files (tfm's, etc), it > is difficult to "try" thailatex as an add-on to an existing TexLive > installation, but to build the font files (the tfm's etc), some of the bits > of thailatex needed to be found by TexLive/MikTeX to build. I'm not sure if I understand what you said. Of course, you can't try it without a font. So, speaking in terms of Debian packaging, all you need is apt-get the font package, and thailatex will be pulled-in as dependency. Also, thailatex is a build-dependency of the font package, never in the other way round. To install it manually, one just installs thailatex before building the fonts, and it's done. > In fact the inter-dependency can be broken quite easily - copying two files > (the *.enc files) from thailatex to the thaifont directories allow the > tfm/map files to build. After doing that, it is just populating those > combination of files from thailatex and thaifonts-* into a few user > directories and setting 6 enviroment variables to 6 groups of files to have > an entirely out-of-tree installation of thailatex from TexLive 2011. (or if > one so wishes, putting the 6 groups of files directly into an existing > Texlive installation). The *.enc files are to be shared by font packages. In the end, when thailatex is finally disbanded, lthuni.enc is meant to be shipped with babel, and the other stuffs, thailigs.enc and thai-dummy.afm, may be copied to the fonts, if not get included upstream. But for the time being, shipping it with thailatex is more convenient for sharing and updating. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ _______________________________________________ Cjk maillist - Cjk@ffii.org https://lists.ffii.org/mailman/listinfo/cjk
