gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] gzz/doc/pegboard/1008 PEG_1008.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] gzz/doc/pegboard/1008 PEG_1008.rst
Date: Mon, 07 Oct 2002 01:05:09 -0400

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/10/07 01:05:09

Modified files:
        doc/pegboard/1008: PEG_1008.rst 

Log message:
        I guess we need this, then

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/1008/PEG_1008.rst.diff?tr1=1.13&tr2=1.14&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/1008/PEG_1008.rst
diff -c gzz/doc/pegboard/1008/PEG_1008.rst:1.13 
gzz/doc/pegboard/1008/PEG_1008.rst:1.14
*** gzz/doc/pegboard/1008/PEG_1008.rst:1.13     Mon Oct  7 00:33:07 2002
--- gzz/doc/pegboard/1008/PEG_1008.rst  Mon Oct  7 01:05:09 2002
***************
*** 4,11 ****
  =============================================================
  
  :Authors:  Tuomas Lukka, Benja Fallenstein
! :Date:     $Date: 2002/10/07 04:33:07 $
! :Revision: $Revision: 1.13 $
  :Status:   Incomplete
  
  
--- 4,11 ----
  =============================================================
  
  :Authors:  Tuomas Lukka, Benja Fallenstein
! :Date:     $Date: 2002/10/07 05:05:09 $
! :Revision: $Revision: 1.14 $
  :Status:   Incomplete
  
  
***************
*** 28,49 ****
  (very desirable). Also, the origin of the text, and the direction.
  
  The solution is to pass nothing about what should be done to the width
! of the string, but simply the unit square of the font. I.e.: the
! font will render itself with baseline somewhere between y=1 and y=0, and 
! the line height such that the similar line rendered above would have its 
! y=1 coordinate at this vob's y=0.
! 
!     (Benja:) I object to this peg on the grounds that without a clear
!     definition where the baseline will be, it is impossible to do
!     text layout. I also object because even though I asked for it,
!     there is no explanation of the considerations above, just a
!     (fuzzy) rule how it should work (``:-(``). With the rule given,
!     the baseline could be at y=0 or y=1, if the rendering is only
!     consistent in this choice, but text layout based on that is
!     absolutely impossible!
! 
! The font will have its normal aspect ratio if the unit vectors 
! are equal, i.e. if the distances (0,1)..(0,0) and (0,1)..(1,1) are the same.
  
  A table-driven lookup needs to be done to find the correct point size
  for a given height in the AWT rendering code.
--- 28,49 ----
  (very desirable). Also, the origin of the text, and the direction.
  
  The solution is to pass nothing about what should be done to the width
! of the string, but simply the unit square of the font.  The font will 
! have its normal aspect ratio if the unit vectors are equal, i.e. 
! if the distances (0,1)..(0,0) and (0,1)..(1,1) are the same.
! 
! TextVob will take a flag ``baselined``, indicating whether the baseline
! should be at y=1 or not. That is, ``baselined`` affects the layout
! in the following way:
! 
! true
!     The baseline will be at y=1. This allows different fonts to be
!     rendered on the same line by matching their baselines
! false
!     The baseline will be between y=1 and y=0, so that as much of the
!     text as possible will fit. This allows easy placement of a single
!     line (or several lines) of text of the same font into a box.
!     In Java terms, baseline y coord = 1-descent.
  
  A table-driven lookup needs to be done to find the correct point size
  for a given height in the AWT rendering code.




reply via email to

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