>> You'll have to preprocess the text into something compatible with >> one of the defined FMapType values (unless you're lucky enough to >> have a printer with something more modern than Level 2, I suppose, >> if such a thing exists). > Ok, can you suggest what kind of multi-byte encoding would work? > UTF-16?
I'm not sure; the Red Book is at home. But the simplest thing is to restrict yourself to the BMP and then encode each character as two octets, using a composite font with a suitable suite of base fonts an FMapType specifying either 9/7 or 8/8 encoding (depending on whether you have 512 7-bit base fonts or 256 8-bit base fonts - well, minus whatever ones aren't needed because you don't need those characters). > The immediate problem seems to me.. how do you refer to a specific > glyph image you want. [Let's] pick the "mu" symbol as an example. I > can find its unicode, but what would the postscript font know this > as? 00b5? Or 03bc? It depends on the fonts in use, of course, but the former would probably be encoded as two bytes 0x00 0xb5 and the latter as 0x03 0xbc (in PostScript strings, most likely \0\265 and \3\274). /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML [EMAIL PROTECTED] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
