--- On Mon, 5/12/11, Theppitak Karoonboonyanan <t...@linux.thai.net> 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.) Yes, that needs to be fixed. I did find some very obscure reference to it to an interior part of thailatex's ftp site. But it would be good to list it and make it official-looking. > 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 I don't find that necessary - the thai.ldf file only needs to be found somewhere under TEXMF (or equivalently, a user's TEXINPUTS) to be used by babel, and there is no need to modify babel at all, despite some of the instrucions on the web says. The enc files and sty files are needed so you might as well ship a package of your own. > I'm not sure if I understand what you said. What I mean is, it is not easy to have an outside-$TEXMF user installation of thailatex (i.e. one entirely in the user's $HOME), because of the strange build dependency. > 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. I don't use Debian. Used to work daily with one of the ex-Debian project leaders (and a few Debian fanatics) for a few years, and that puts me off Debian completely. (Use slackware for years and still for server installs, and fedora for desktop/laptops). > To install it manually, one just installs thailatex before > building > the fonts, and it's done. That's the part I found wrongly designed - one does not want to install a non-functional piece of software just to build another piece of software, with the hope that the resulting combination would become functional. > 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. Not really. The *.enc files needs to be found by dvips/pdftex's font backends, so they are logically part of the font bundles rather than the preprocessor bundles. I think a better way of looking at it, is at what stage files are needed, if you stick to the latex->dvi->ps/pdf regime. (instead of the one-step pdflatex/XeTeX). The enc files aren't needed in the first stage I think, whereas the sty files aren't used in the 2nd stage. (although, I surely understand the need of separating parts which are still-in-progress and need further updates and fast-changing, from parts which don't - so the gyphs themselves - the sfd files, would be ideally separated from the enc files for ease of maintainance.) _______________________________________________ Cjk maillist - Cjk@ffii.org https://lists.ffii.org/mailman/listinfo/cjk
