On Sunday, March 06, 2005, at 07:03PM, Alan W. Irwin <irwin@...> wrote:
>On 2005-03-06 15:14-0800 hbabcockos1@... wrote:
>> The AquaTerm driver now also supports unicode, or more accurately, only
>works with unicode. Mac/AquaTerm users won't notice much of a difference
>since all this does is eliminate the middleman, i.e. PLplot UCS4 text is now
>directly translated to Mac UTF8, where as before it followed the more
>complicated path of UCS4(PLplot)->ASCII text(driver)->UTF8(OS X).
>I am pleased you have been able to make this transition.
>I cannot try it out for myself because I have no access to Macs, but I would
>be interested in looking at some new screen shots. For some time now I have
>noticed some obvious 3D transformation issues for your fonts for your old
>screenshot at http://aquaterm.sourceforge.net/index.shtml?page=s4 so I hope
>your latest effort has been able to address that issue.
Unfortunately, that issue is still unresolved, but Per and I are aware of it & hope to clear it up soon.
>When looking at the latest aqt.c, I noticed a couple of font selection
>* AQT_Type1Lookup only has 5 font names rather than the 30 expected. Compare
>with Type1Lookup in plfci-type1.h or TrueTypeLookup in plfci-truetype.h.
I went with these 5 as that was all the original aqt.c driver supported, but I suspect that most if not all of the 30 expected are in fact available. I will add as many of the 30 as I can.
>* The font names in AQT_Type1Lookup are the standard adobe names for Type 1
>fonts. Type 1 fonts are a limitation we are forced to accept for ps.c for
>the time being, but if possible I advise using TrueType (which ironically is
>an Apple invention) if you can; the symbols available in any given TrueType
>font are much richer than the Type 1 case (because of the limitation of only
>255 characters in Type 1).
I guess that would explain why so many boxes are blank in examples/c/x23c... Honestly I don't really know if TrueType fonts are available, but I will try and find out & use them instead if I can.
>Do these font selection constraints reflect similar issues in the underlying
>aquaterm software that your aqt.c device driver calls?
I don't think so, but I'll defer to Per on that one.