[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA: Overbars
- To: geda-dev@xxxxxxxx
- Subject: Re: gEDA: Overbars
- From: Ales Hvezda <ahvezda@xxxxxxxx>
- Date: Thu, 02 Mar 2006 19:59:03 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: geda-dev-outgoing@seul.org
- Delivered-to: geda-dev@seul.org
- Delivery-date: Thu, 02 Mar 2006 19:59:05 -0500
- In-reply-to: Your message of "Mon, 27 Feb 2006 19:21:40 +0100." <1141064501.4350.26.camel@otilio> ------
- Reply-to: geda-dev@xxxxxxxx
- Sender: owner-geda-dev@xxxxxxxx
Hi Carlos,
>I have just commited the changes into CVS. I used "\_" as the overbar
>delimiter. Images are always better than words, so I attach a
>screenshot.
Very nice.
Yes, thanks for implementing the overbar mechanism. I've
played with it (myself and with the people at the freedog meeting) and
we were all impressed. The overbar mechanism is a frequently asked
for feature, and I'm glad we have them now.
With regard to the delimiter, let's leave it at \_ for now.
\ is meant for quoting so it make some sense (to me) to use \ followed
by the underbar.
>PNG output works ok, but the Postscript output doesn't. I hope someone
>could take a look at it. If I'm not wrong, the changes are needed in the
>o_text_print function, in libgeda/noweb/o_text_basic.nw.
When we get around to fixing the PS output, it is important
to use the PS string measuring functions to determine how long a certain
overbar should be depending on the string. This will guarantee that
the overbar are drawn in the right place and length.
-Ales