FW: Problem with Lout & zcaron in Latin2

[Matěj Cepl]

Dobry den,

pokousim se zprovoznit lout a mam problemy s~cestinou. Po kratsi
emailove konverzaci s~nejvetsim zijicim odbornikem (dobre, druhym
nejvetsim) na lout, Valeriem Usakovem jsme dospeli k~zaveru v~prilozenem
dopise.

Pro jistotu, moje sestava:

lout 3.12, Win NT 4.0CZ, GhostScript 4.03,
ISO Latin 2 Type1 fonty od Petera Soose (OSB Madarsko)
z~ftp://ftp.osb.hu/pub/misc/fonts/local/latin-2

Pokud CSTEX neni nejlepsim mistem pro diskuse o~PostScriptu, prosim,
odkazte me na spravne misto.

A v~zadnem pripade mi neradte, ze si mam poridit TeX. Vim alespon
minimalne co delam (to neni nic proti TeXu, don't flame me please!).

		Diky
				Matej

> -----Původní zpráva-----
> Od:	Valeriy E. Ushakov [SMTP:uwe at ptc.spbu.ru]
> Odesláno:	14. října 1998 3:17
> Komu:	Matěj Cepl
> Kopie:	Jeff Kingston
> Předmět:	Problem with zcaron in Latin2.
> 
> Hi, Matěj.
> 
> So I have figured out what the problem is.
> 
> The Latin2 fonts you've got are broken.  They use Latin1 glyph names
> for Latin2 glyphs.  So glyph for zcaron (190) is not named `zcaron'
> but `threequarters' (which is 190 in Latin1).  Since lout ignores `C'
> codes from AFM file and use LCM file instead, the entry for 190 is
> never filled in lout internal tables and so contains some random junk
> which gives you huge object sizes.
> 
> So the solution to your problems is twofold.
> 
> Attached is the patch to z37.c to use calloc (which will memset
> alloced memory to zero) will prevent lout from reading random junk
> from unitialized memory.
> 
> On your side you have to edit your fonts to be real Latin2.
> 
> . make an auxilary table that maps Latin1 glyph names to Latin2 glyph
>   names, e.g.
> 
>     Code	Latin1 Glyph		Latin2 Glyph
>     ...		...			...
>     190		threequarters		zcaron
>     ...		...			...
> 
> . get t1 utils (for win32 you can get them precompiled from CTAN, I
>   belive)
> 
> . disassemble font (t1disasm, probably after t1ascii if fonts are pfb)
> 
> . change glyph names according to the table
> 
> . assemble font back (t1asmand then maybe t1binary to get
>   pfb from pfa)
> 
> . change glyph names according to the table in the AFM file
> 
> . you have proper Latin2 font
> 
> 
> Hope that helps.
> 
> PS: Jeff, ain't it be safer to use calloc for all internal tables?
> 
> SY, Uwe
> -- 
> uwe at ptc.spbu.ru                         |       Zu Grunde kommen
> http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: calloc.txt
URL: <http://lists.felk.cvut.cz/pipermail/cstex/attachments/19981014/6740fdd6/attachment-0001.txt>