schmidt@cadlab.cadlab.de (Michael Schmidt) (08/08/89)
We would like to use GNU Emacs' texinfo system as an internal
documentation carrier. But, most of the time we are speaking
german to each other. And so should our documentation. Is there
any possibility (despite of @iftex and @ifinfo, that is not
acceptable) to get e.g. an Umlaut a in the printed manual and a
"ae" in the info file or an \ss{} in the printed manual and a
"ss" in the info file?
--
Michael Schmidt, CADLAB / FB 17, Uni-GH Paderborn, Bahnhofstr. 32,
D-4790 Paderborn, West Germany
Mail: schmidt@cadlab.UUCP or schmidt@cadlab.dejcgs@wundt.harlqn.uucp (John Sturdy) (08/09/89)
In <557@cadlab.cadlab.de>, schmidt@cadlab.cadlab.de (Michael Schmidt) writes: > We would like to use GNU Emacs' texinfo system as an internal > documentation carrier. But, most of the time we are speaking > german to each other. And so should our documentation. Is there > any possibility (despite of @iftex and @ifinfo, that is not > acceptable) to get e.g. an Umlaut a in the printed manual and a > "ae" in the info file or an \ss{} in the printed manual and a > "ss" in the info file? I think this can be done at the TeX end, by defining ae as a "ligature". I don't have a TeXbook handy, and I'm not sure of the details offhand, but I'm pretty sure it can be done. You may have local installation notes with your TeX concerning non-English customizations (depending on where you got your TeX distribution from). I've added comp.text to the newsgroups field, as that is probably the most helpful place for this one. -- __John When asked to attend a court case, Father Moses took with him a leaking jug of water. Asked about it, he said: "You ask me to judge the faults of another, while mine run out like water behind me." jcgs@uk.co.harlqn (UK notation) jcgs@harlqn.co.uk (most places) ...!mcvax!ukc!harlqn!jcgs (uucp - really has more stages, but ukc knows us) John Sturdy Telephone +44-223-872522 Harlequin Ltd, Barrington Hall, Barrington, Cambridge, UK