[XeTeX] XeTeX documentation? (from "Checking if a font exists")

Gareth Hughes garzohugo at gmail.com
Tue Aug 31 16:24:44 CEST 2010

Peter Baker wrote:
>  On 8/31/10 6:51 AM, Vafa Khalighi wrote:
>> I believe that in any case the original developer should write the
>> main documentation not anyone else simply because the original
>> developer implemented the software and he knows absolutely every
>> single detail about his software and what he has implemented.
> But developers are not always good writers. Our Will Robertson has
> produced a great manual for fontspec, but some TeX developers who have
> written manuals would have done better to recruit someone else to do it
> for them. A developer's duty is to write well commented code, and to be
> willing to work with writers of documentation to help them get it right.

There has always been the RTFM response to questions about some code or
other. Yes, there are people who find it easier to post to a discussion
group than read the manual. One problem with TeX is that one might be
reading the wrong manual, because one is blaming the wrong package.
However, if there is a steady stream of questions from users who have
read the right manual but still implement the package wrongly, then the
manual is either not clear enough or has holes in its coverage. However,
rather than taking over the manual, I think it would be far better if
developers felt able to ask for input from others on how best to improve
the manual. After all, I'm sure the developer doesn't have to read their
own manual, but the rest of us do.


More information about the XeTeX mailing list