> > Or, more simply, we could just use the current inefficient Unicode support > > (via the UNICODE16 and UNICODE32 functions in the Plucker doc format), and > > hook it up with the grayscale fonts and a map specifying ranges, and just > > ensure that the parser uses it more aggressively. > > yes, that could be a first step - after all, in latin-based languages, > it would increase the text size just by a few percent.
Or even less than that, because the compression should pick up on it. Alex _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
