octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #31468] multi-line text objects


From: Vanya Sergeev
Subject: [Octave-bug-tracker] [bug #31468] multi-line text objects
Date: Wed, 28 Sep 2011 19:33:29 +0000
User-agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1

Follow-up Comment #58, bug #31468 (project octave):

Hi Rik,

I got an email reply for this thread, so I figured I'd chime in:

* mangled TrueType rendering for Mac OS X in txt-eng-ft.cc. I believe Ben's
image captures it in file #23826, versus file #23823.
I can't add much to this since I don't have OS X environment to test with, but
maybe checking some of the return values for the FreeType calls in
txt-eng-ft.cc would be a good place to start.

* lack of multi-line support in print/gl2ps plots because gl2psTextOpt() does
not parse newlines.
I was working on an experimental patch that used the TrueType rendered pixels
in txt-eng-ft.cc instead of gl2psTextOpt(), since they already took into
account the alignment (left, center, right). The patch for this is file
#23814, a sample output image is #23815, and the test code in the second half
of comment #49. The output looked good, except for a position offset that I
haven't had time to track down. If that offset is taken care of, print/gl2ps
plots would have the same multi-line rendering as the FLTK/OpenGL frontend
(same pixels). The resolution could be better, though.

Thanks,
~vsergeev

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31468>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]