Stickies on "TrueEdit Docs"


This comment page will be removed from the final version!


Do you have the correct wording for legal waffle on "contents" page.

Is "Oink!" in Pig Latin a good example of a rearrangement effect?

Is "Oink!" registered in the Feature Registry? ;-)

How does one register a feature? (Do you have the guidlines for contacting FONTREGISTRY?)

Is there a font which demonstrates "Titling Capitals" or "Display Text" ?

I am assuming that "full Cursive Connection" uses kashida glyphs between letters during justification, whereas "partial Cursive Connection" just puts inter-glyph space between letters - is this the correct definition?

I can't do these diagrams

(...and have them make sense and/or not be mortally offensive ;-) ),
can you supply me with them?

a. Chinese simplified characters
b. Chinese traditional characters
the same meaning for both, if possible

c. Arabic text with and without diacritic marks.

d. Text with linguistic rearrangement.

e. Cursive Arabic text (justified and unjustified to show extension of kashida glyphs)
- I have done this one (I stole the text off the GX typography pages) but if you have the Arabic text in vector format I'll take it - the bitmap version looks a bit ropey.


Does GX allow both left- and right-hand collision avoidance in the one font?

If the fraction-bar isn't shift-opt-1 on most keyboards, where is it?

Is this diagram correct or not?

A question:

How does GX deal with capitalisation of something like:

"Diese Maschine ist außer Betrieb"

...?

The correct capitalisation of "außer" is "AUSSER" - I realise that TrueEdit's capitalisation editor can't deal with this, but can GX do the conversion from ß to SS, even if the "ß" was directly entered?

The same applies to directly-entered fi and fl ligatures, I suppose.


You do know that this editor has a horrible redraw bug, don't you?
The Upper and Lower areas aren't redrawn when scrolling down through the list.

I assumed that you meant Small capital text with each word given a large capital (and not what you wrote...)

Is this where things like "ß" get sorted out?

Rebus pictures? Is there really a font for this? (the mind boggles...) If you have a font, please could you send it.

TrueEdit bug:


start-of-line words are not capitalised (I faked the example!).

eg. I wandered
lonely as
a cloud that
floats...

becomes:

I Wandered
lonely As
a Cloud That
floats...

rather than:
I Wandered
Lonely As
A Cloud That
Floats...


"···[[(Dave: The EZ-Reader numbers have got to go.) there's a bug on them: Radar 1121604]]"

-- it's still there!

You have got to be kidding!

Sorry, I can't supply any information for this section - you'll have to get someone who knows to do it.


Has the TR12 table been removed from TrueEdit?


Has the TR12 table been changed? Should it be documented? (I won't be able to do it!)


There's no indication that this dialog is available, or even exists!


Bug 1114308 "There is no way to set the caret slope offset in the hhea table. But you can do it using the fmtx table and the magic glyph."


Ligature carets, caret slope, other things.

  1. Caret Slope selected was 5:1. This was determined visually, in the absence of any specific known value.
  2. The Caret Slope Angle is currently adjusted digitally in the hhea table, then visually confirmed by closing/reopening the lcar window. The CSA ought to be manually adjustable in the lcar window.
  3. It would be much more efficient for the CSA indicator line to appear (<Command-a>) at the current position of the cursor, rather than at the 0,0 intercept. This would enable the designer to do much less cursor movement and repetitive dragging, by allowing a rough initial positioning.
  4. TrueEdit should avoid refreshing the entire lcar list window after each change to a glyph. Only one entry need be updated, not the entire list.
  5. Dragging of the CSA is sluggish, and should be sped up. Currently, extra work must be done when the designer moves to fast and has the CSA overshoot the desired position.
  6. ···too specific?This operation is very easy. Even with the above problems, and saving every 3-4 operations, I was able to process all ligatures in Hoefler Italic in approximately 10 minutes. (43 ligatures, 9 double ligatures)

···Bug 1126004 says TrueEdit uses the wrong marker vaalue (for end of table)


"We need standardized test fonts with appropriate baselines to refer to."


I can't get this to work at all: TrueEdit just hangs when I drag a glyph into the Contextual Kerning window.


Are these things: << , >> called << Guillemots >>, or is my memory playing tricks on me?


What is the "lower decomposition threshold" for?

Surely ligatures are smaller than their components, so what is the advantage of decomposing them when shrinking a line?


(What if different sequences of components form the same ligature? What do they decompose into?)


Logos? Wasn't the only example of this effect ("apple" -> Apple Logo) to be removed from Apple GX fonts?


"TrueEdit forces all tracks to have the same point-sizes"

-- Is this required by Layout?

** WHAT ARE THE UNITS FOR TRACKING VALUES!! Points, ems, Miles??

** What are the numbers of the default tracks? -2=v.tight, -1=tight, 0=normal, +1=loose, +2=v.loose ?


 

 

 

 

 

 

[Sticky!]