>> Again, this is correct behaviour: Running the CJK package directly
>> on a Thai file doesn't work. It must be preprocessed with
>> cjk-enc.el which inserts proper font switching commands, including
>> the encoding. LaTeX's font fallback mechanism finds a different
>> font family for a given encoding, but it can't guess the text's
>> encoding.
>
> Would/should mandating \usepackage[encoding]{inputenc} do?
Maybe, I don't know. I suggest that you contact Theppitak
Karoonboonyanan <[email protected]>, the maintainer of thailatex,
for further assistance.
>> Apparently, you've missed the comment in the beginning of
>> thai.tex:
>>
>> % This file should be processed with cjk-enc.el to get
>> %
>> % . proper word breaks
>> % . font switching between Thai and non-Thai
>> % . intercharacter glue
>
> Argh, I thought "should" is optional - what you are saying is that
> it 'must' be processed with cjk-enc.el .
Right. Bad wording.
> Are you saying that it must be processed by cjk-enc.el or it does
> not work? So It is more equivalent to what bg5latex/bg5pdflatex
> does?
Yes.
> That puts a rather big limitation to CJK thai: ties it to emacs.
No. A look into `thaifont.txt' would tell you the following:
[...] The just sketched outline works without cjk-enc also (but no
word breaks are inserted automatically); you must then insert
\addto\extrasthaicjk{\fontencoding{C90}\selectfont}
in the preamble of your document to make Babel switch to Thai font
encoding on entering the `thaicjk' language environment.
I've tried to improve the thai.tex's comment prologue in the git
repository.
> It sounds like most of my problems are due to not reading the
> documentation carefully enough (or alternatively, important issues
> aren't emphasized enough in the documentation...).
:-) Any documentation patches are highly welcomed.
Werner
_______________________________________________
Cjk maillist - [email protected]
https://lists.ffii.org/mailman/listinfo/cjk
