[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

From |
"Leny Mathew" <lenymathewc@gmail.com> |

To |
statalist@hsphsun2.harvard.edu |

Subject |
Re: st: RE: RE: symbol for ">=" in graph text box |

Date |
Mon, 13 Oct 2008 14:16:38 -0400 |

Ok!. That's something I didn't think about. Thank you, Eva. Leny On Mon, Oct 13, 2008 at 1:35 PM, Eva Poen <eva.poen@gmail.com> wrote: > Leny, > > in case you are a latex user, you can use the psfrag package, which > allows you to replace arbitrary text in .eps files by latex code of > your choice, on the fly. E.g. you could have "xyz" in you graph where > you want the symbol to be, and then have \psfrag{xyz}{$\geq$} in your > latex document. > > Eva > > > 2008/10/13 Leny Mathew <lenymathewc@gmail.com>: >> True! Even hacking .ps doesn't work as if I open the .ps file as in >> notepad and change the symbol using the one from the character map, I >> still have to save it with ANSI coding. If I keep it as ANSI and force >> it to save, the ">' disappears and the "=" remains. It doesn't look >> like unicode is compatible with .ps. I'll post a listing if I figure >> out a way to this. >> >> Leny >> >> >> >> On Mon, Oct 13, 2008 at 1:16 PM, Nick Cox <n.j.cox@durham.ac.uk> wrote: >>> <> >>> >>> No, "over" does not capture the = bit. >>> >>> -----Original Message----- >>> From: owner-statalist@hsphsun2.harvard.edu >>> [mailto:owner-statalist@hsphsun2.harvard.edu] On Behalf Of Nick Cox >>> Sent: 13 October 2008 17:40 >>> To: statalist@hsphsun2.harvard.edu >>> Subject: st: RE: symbol for ">=" in graph text box >>> >>> Hitherto in such cases I have used the word "over". >>> >>> Some people have saved to .eps and hacked the PostScript. >>> >>> Otherwise I agree with your general drift that it would be very nice if >>> it were easier than it appears to be. >>> >>> Nick >>> n.j.cox@durham.ac.uk >>> >>> Leny Mathew >>> >>> I'm trying to include the 'correct' symbol >>> for ">=" in the legend text box in a graph. Looking through the >>> archives, I found Nick Cox's article on inserting awkward characters >>> in stata which recommended using the 'char' command with the ASCII >>> codes. This would have worked, but the ASCII code for ">=" comes under >>> the extended list (code- 242) and this produces a different character >>> which corresponds to 242 in the ANSI list. It looks like ">=" doesn't >>> exist in the ANSI list! >>> Another option was to use the method suggested by David Harrison in >>> http://www.stata.com/statalist/archive/2005-03/msg00483.html. I could >>> modify the font that I was using by replacing a least used character >>> by the ">=" sign from the ASCII list >>> I ran into trouble with this as I couldn't replace a character with >>> the ">=" symbol. >>> >>> Is there any easy way of doing this? I would think that the symbol for >>> ">=" would be commonly used in graphs and was under the impression >>> that this would be a simple thing to do! >>> > * > * For searches and help try: > * http://www.stata.com/help.cgi?search > * http://www.stata.com/support/statalist/faq > * http://www.ats.ucla.edu/stat/stata/ > * * For searches and help try: * http://www.stata.com/help.cgi?search * http://www.stata.com/support/statalist/faq * http://www.ats.ucla.edu/stat/stata/

**References**:**st: symbol for ">=" in graph text box***From:*"Leny Mathew" <lenymathewc@gmail.com>

**st: RE: symbol for ">=" in graph text box***From:*"Nick Cox" <n.j.cox@durham.ac.uk>

**st: RE: RE: symbol for ">=" in graph text box***From:*"Nick Cox" <n.j.cox@durham.ac.uk>

**Re: st: RE: RE: symbol for ">=" in graph text box***From:*"Leny Mathew" <lenymathewc@gmail.com>

**Re: st: RE: RE: symbol for ">=" in graph text box***From:*"Eva Poen" <eva.poen@gmail.com>

- Prev by Date:
**st: Re: graph frequency distribution (discrete)** - Next by Date:
**Re: st: re: Troubleshooting 'not sorted' and 'not regularly spaced' errors** - Previous by thread:
**Re: st: RE: RE: symbol for ">=" in graph text box** - Next by thread:
**st: transform the dataset structure** - Index(es):

© Copyright 1996–2017 StataCorp LLC | Terms of use | Privacy | Contact us | What's new | Site index |