Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 20061 invoked by uid 500); 10 May 2003 14:49:32 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 20049 invoked from network); 10 May 2003 14:49:31 -0000 From: =?ISO-8859-1?Q?Andr=E9?= Malo Subject: Re: stuck with PDF creation MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Organization: TIMTOWTDI References: <20030510000758.1bec1571.jacek.prucia@acn.waw.pl> Date: Sat, 10 May 2003 16:41:52 +0200 To: docs@httpd.apache.org Message-ID: User-Agent: Yes! X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N * Jacek Prucia wrote: >> Although I don't think it was me who originally suggested this, I do hav= e >> considerable experience with latex. It produces great-looking results, >> but is a little bit of a bear to configure and use correctly. (Packages >> like MikTeX make this a little easier.) >=20 > Which reminds me, there are different TeX/LaTeX distributions out there. = We > schould make a doc about what set of packages we require for successful b= uild. > Or as an option we could stick to some distro (like TeX Live or something= ). I think, it will be similar to the CHM creation. The source files will be autogenerated. The "compiler" must be installed. To achieve the same result= s on different systems, we probably should put the fonts and other special files (hyph-patterns?) into CVS (build-tools). >> The other thing that would >> concern me is the multi-lingual issue. I have no experience in using >> latex with languages other than english. I know it handles latin-based >> languages well, but I have no idea about others. >=20 > Basically it boils down to 2 things: >=20 > 1. You make sure TeX/Latex understands your encoding, typically with: >=20 > \usepackage[X]{inputenc} >=20 > where X is a proper option (e.g I use option 'LATIN2' for inputenc). You = might > want to use: >=20 > \usepackage[X]{fontenc} >=20 > with some magic option, if LaTeX/TeX won't complain about character encod= ings, > but PDF output seems to be scrambled. I'm sure we can solve that problem. (Effectively, CHM creation and even PDF via fop suffers from similar problems). > 2. You make sure that hyphenation for your language is selected. You do > this by hand (HYPHEN -> pdftex in texconfig), or by using special package= that > does this for you at runtime. For example polish package for LaTeX does t= his, > not sure about other languages >=20 > Side Note: >=20 > Unless there's a TeX/LaTeX guru among us (I believe such a man is called > TeXpert), we schould find one (local TUG might be a good source), and ask= for > help. For most people some things work out of the box, and because of tha= t > they don't mess much with software internals. We just might have to... That is not the worst idea. Although I think, we should look first in our circles here :) We would need at first someone, who can dissect the DTDs (or sample xml files) and make an outline, how this can be written in (La)Tex. Once we hav= e this, xslt for autogeneration is easily written and we get a base to work o= n and develop further (fonts, encodings etc.). Though I'm not able to create such samples (currently ;-), I can imagine that it's not so difficult (look= s like latex provides similar semantics). nd --=20 my @japh =3D (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~}); my $japh =3D q[sub japh { }]; print join ######################### [ $japh =3D~ /{(.)}/] -> [0] =3D> map $_ -> () # Andr=E9 Malo # =3D> @japh; # http://www.perlig.de/ # --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org