I assume this won't affect sites that use GreekKeys or other encodings, which one can do right now by generating a GreekKeys font? (Now font packages can be easily (with a GUI!) be generated from ttf and type1 fonts.)
No, it should be fine because I'm not really doing anything new. The parser always includes an alternate ascii rendering for each unicode character in the plucker document. Before the default alternate rendering for each character was &#XXXX; where X=the decimal value of the character, now anything in the dictionary will get an alternate rendering that has some value to the reader.
As long as the viewer can display the unicode character, the alternate rendering will be ignored.
Hi David,
Thanks for making a patch for swapping encodings. Is there a commandline switch for switching a lookup table (similar to how we can hotswap an exclusionlist.txt for a list of exclusions)?
Best wishes, Robert
_______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
