| 
      
      
      From: Alan W. I. <ir...@be...> - 2006-08-03 15:05:46
      
     | 
| On 2006-08-03 17:42+0900 Valery Pipin wrote:
> Hello Alan,
>
> Thanks for the quick help!
>> I get a slightly different result with the CVS version of PLplot: #(2229)
>> (vertical bar)
> Yes it is also works for me. I wanted to  refer the char #(2104) for
> differential
>> works okay, but #(2053) (italic upper case C) does not.
>>
>> To solve the problem I suggest you use -drvopt text=0 which enforces
>> Hershey fonts in all cases.
> where should I place this option? Can I use plparseopts?
hmmm.  I am sure there is an internal way to specify it, but I always just
specify it on the command line.
>> For new plots I suggest you abandon -dev psc and use -dev psttfc instead.
> I found psttf drivers are problematic to use.
> pllab("TIME,
> [YR]", "[Wb#u2#d]","#(2412)#(2229)h#d#(2053)#u#(2229)#(2104)V#dCZ#u")
> gives quite ugly results for ps file. The characters itself  look very well
> but there combination does not.
The old #(nnnn) notation has some internal limitations. You have to move to
the new scheme (UTF8 strings or #[nnn] with FCI's) to get complete results
for special characters with the unicode fonts.
>
> Another problem for me with the collor ps drivers that I could not find the
> simple way to get the black color (with white background).
> For plplot5.3.1 in yplot I find that  plscol0,1,1,1,1 gives the perfectly
> black color. However its python conterpart  plscol0(1,1,1,1) gives gray
> color.
The first index in cmap0 is the special background colour index, and it must
be set before plinit in order for it to work at all.  The simple way is
to use the -bg option on the command line.  (Use the -h option on the
command line to see all the options available.)
>
>> You then are allowed to specify the labels and symbols with either UTF8
>> strings or else the #[nnn]
> However the proposed table of characters is not as complete as the Hershey
> table.
There are literally millions of unicode glyph possibilities which are now
accessible with PLplot.  (Example 23 is only a tiny subset of what is
possible with -dev psttfc.) Also, unicode is the standard so if people
actually want to use a glyph it tends to be represented in the unicode
tables of glyphs. That said, I agree that some of the more exotic Hershey
glyphs are not represented in the unicode glyphs (or we haven't found them
yet in the millions of possibilities), but I doubt those glyphs are used by
too many people if they are not already in the unicode tables.
I highly recommend trying the gucharmap GUI to see all the unicode glyph
possibilities available for the fonts installed on your system.  Those glyph
possibilities are _all_ accessible with PLplot and the #[nnn] scheme.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
 |