So disappointed in UFO Stretch
![[Deleted User]](https://secure.gravatar.com/avatar/4a64fb71566d0b4e56fb2a244524664c/?default=https%3A%2F%2Fvanillicon.com%2F83f6992ca487b67bd3dd7df96e236fc1_200.png&rating=g&size=200) 
            
                
                    [Deleted User]                
                
                    Posts: 0                
            
                        
            
                    The user and all related content has been deleted.                
                0          
            Comments
- 
            I haven't used it for a while, but I don't remember having a problem with italics.
 Maybe drop @typemytype a line?
 Cheers,
 Artur0
- 
            I've mostly used in on uprights, but did use it on an italic project a few months ago. The results were a bit less good than the roman, but I was only using UFOstretch to rough in proportions for a display version. That's how I mostly have used the tool, as a way to get a reasonably clean scaled and interpolated rough with independent X and Y control (the latter being the big benefit over RMX Scaler).
 The problem I regularly have with UFOstretch is that the UI seems to have a problem with fonts with a >1000 unit em.0
- 
            The user and all related content has been deleted.0
- 
            
 I wouldn't know what causes that. I think if it worked with your ufo's containing romans, it should not be any different with ufo's containing italics.James Montalbano said:MY problem is that it will not even recognize Italic Font data. Nothing populates the interface when selecting Italic data.0
- 
            The user and all related content has been deleted.0
- 
            Do your italics lack points at the x-extrema? Anything else other than having an italic angle entry that might differentiate the italic, at a technical level?
 (Just wondering what might trigger the problem.)0
- 
            I remember having a problem a while back with UFO's exported by Glyphs showing up 'empty' in Superpolator. Adding a custom property entry in the master fixed this. (can't remember what the entry was though.)
 Is there any difference between how you created the ufo's for roman and italic?0
- 
            The user and all related content has been deleted.0
- 
            Might it be better to submit a bug report and try figure out what exactly makes this fail rather than publicly sharing your contempt for the app altogether?
 0
- 
            I've never had a problem with italic data working any differently than roman. The biggest problem with UFO Stretch is the lag it can really slow to a crawl depending on what you're doing.1
- 
            Did you confirm that the italic data out of FL VI is properly conformed? Seems unlikely, but possible, that something about what was written by FL got translated idiosyncratically.0
- 
            Best results with FL5 + UFOcentral. I never had a problem with italics.
 0
- 
            This might be related - maybe not.
 (Because maybe UFOStretch uses similar Python Libraries or pens etc.):
 I had problems when using Italic shapes (of serif font) with Mutator Scale.
 https://github.com/loicsander/MutatorScale
 MutatorScale uses/needs reference Glyphs for measuring stroke weights.
 (also glyph "H" for example)
 So in my case it helped to remove the overlaps of glyph H.
 (when constructed out of 3 shapes for examples: a horizontal Stroke and two vertical strokes)
 Maybe this helps with UFOStretch as well.
 1
- 
            The user and all related content has been deleted.0
- 
            Could you try creating a new italic file that is stripped down to just a particular amount of glyphs and data? I suggest that because back in the day I'd occassionally have problems in FontLab, so I'd start a new file and systematically transfer the glyphs and data to the new file until I reached a point in which the problem was reproduced, and I could then identify or address it, or at times I believe it went away entirely. On further thought, I faintly recall having corruption-like issues in with files due to random (near invisible) floating points, that I'm usually very careful to avoid.
 Lately I have the feeling that some of these software issues are idiosyncratic amongst us. For example, with Robofont whenever I edit Font Info it leads to the app crashing and it is a consistent and reproducible problem (imagine the joy of editing Font Info across a 20 style font family!). I submitted a bug and then replied to a request to submit a log file and never received an answer. I can only imagine if this was a consistent problem among other users it either would've been resolved by now or no one would use the application.0
- 
            The user and all related content has been deleted.0
- 
            What's you other solution? Always interested to know about other ways of doing things.0
- 
            It works fine for me.0
- 
            Since I use FontForge on Windows (and not directly with UFO data), I coded up my own version of this functionality, which *does* account for the italic data. It can be run via command line or as part of a library, but I haven’t gotten around to creating a GUI for it.1
- 
            Artur Schmal said:Maybe drop @typemytype a line?
 So was @typemytype able to help you, @James%20Montalbano?
 0
- 
            The user and all related content has been deleted.0
- 
            RMX tools don't enable independent x and y interpolation, right?0
Categories
- All Categories
- 46 Introductions
- 3.9K Typeface Design
- 485 Type Design Critiques
- 560 Type Design Software
- 1.1K Type Design Technique & Theory
- 654 Type Business
- 853 Font Technology
- 29 Punchcutting
- 519 Typography
- 119 Type Education
- 323 Type History
- 77 Type Resources
- 112 Lettering and Calligraphy
- 33 Lettering Critiques
- 79 Lettering Technique & Theory
- 550 Announcements
- 91 Events
- 114 Job Postings
- 170 Type Releases
- 174 Miscellaneous News
- 276 About TypeDrawers
- 54 TypeDrawers Announcements
- 120 Suggestions and Bug Reports










