Photoshop: Font style size problems in CS6

  • 41
  • Problem
  • Updated 4 years ago
  • Solved
  • (Edited)
The charater style is buggy sometimes it won't change the type size. e.g. 14pt will appear has 8.64pt it's very frustrating. Something which I felt would speed my process up has slowed things down.
Photo of sam Dallyn

sam Dallyn

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 7 years ago

  • 41
Photo of MICHAEL DRINKS

MICHAEL DRINKS

  • 9 Posts
  • 0 Reply Likes
Nope, it's still there in 13.0.5. As a test, I just started a new piece of text at 40 pt, then scaled it from the corner up to about 390 pt. Then in the Character palette if I change the point size to 300, the value suddenly changes to 11640.42 and I get the error message: "A value between 0.01 point and 1296.00 Points is required. Closest value inserted." (1296 pt)
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
We will be releasing a fix for CS6 VERY soon...

Thanks,
David
Photo of Terrence Seaford

Terrence Seaford

  • 12 Posts
  • 3 Reply Likes
13.0.6? So far so good. Transformed text works, as expected. And I'll take a leap of faith and trust that the PDF issue has been solved as well.

David, you and your team rock. Many thanks.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15365 Posts
  • 2239 Reply Likes
Terrence, great to hear. Thanks.
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Actually, Terrence, it has...! 8-)
Photo of David

David, Official Rep

  • 3096 Posts
  • 481 Reply Likes
Official Response
Howdy folks,

I am happy to announce that a patch for this issue in CS6 is now available for Mac (13.0.6) and Windows (13.0.1.3).

Enjoy!
David
Photo of klipp86

klipp86

  • 4 Posts
  • 0 Reply Likes
David, I was on your list before about getting this patch. How do I actually get (and use) it? Thanks,
Photo of David

David, Official Rep

  • 3096 Posts
  • 481 Reply Likes
The builds you were given were RAW builds and are independent from this patch. You should be able to launch you CS6 install and update normally. If you have any problems, post a message in the prerelease forums and I'll make sure it gets addressed.

Thanks,
David
Photo of Paul Riggott

Paul Riggott

  • 360 Posts
  • 144 Reply Likes
The scripting bug mentioned above has still has not been addressed.
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Paul, you were on the prerelease forums. I was very clear there that that the scripting bug was NOT included in either CC or CS6's fixes. We are hoping to address the problem with a future solution.

David
Photo of Paul Riggott

Paul Riggott

  • 360 Posts
  • 144 Reply Likes
Your statement to me was very different and you know so! Why don't you let the rest of the world know!
Photo of Alexandre Souza

Alexandre Souza

  • 5 Posts
  • 0 Reply Likes
It seems the new fix is only for the retail versions of PS6, as my CC installation does not show any updates available.

Can you please confirm?
Alex
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Hi Alex,

I think you have some terminology mixed up here.

Photoshop CC has had the fixes for a couple months. Photoshop CS6 has the fixes now. Regardless of how you installed, if you click Help > Updates you'll get the latest version which is:

Windows:
CC 14.1.2
CS6 13.0.1.3

Mac:
CC 14.1.2
CS6 13.0.6

Thanks,
David
Photo of David ODonoghue

David ODonoghue

  • 7 Posts
  • 0 Reply Likes
Is there a ETA on when the scripting side will be addressed for this bug?
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
The scripting side will hopefully be addressed by an architectural change in the future. As yet, there is no ETA I can share publicly. Sorry.

David
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Also, there are some code snippets that might help you here: http://feedback.photoshop.com/photosh...
Photo of David ODonoghue

David ODonoghue

  • 7 Posts
  • 0 Reply Likes
I'm trying to use layer.textItem.contents = "newContents" and still keep the size of the text item I am updating even when it has been transformed.

Does the fix resolve this?
Photo of David ODonoghue

David ODonoghue

  • 7 Posts
  • 0 Reply Likes
I'm using CC
Photo of David ODonoghue

David ODonoghue

  • 7 Posts
  • 0 Reply Likes
Ok, I've read through and understand it's not yet fixed. I hope this gets fixed soon. I'm trying to compile my font atlases for our game and this is a big road block.
Photo of George Cuevas

George Cuevas

  • 1 Post
  • 0 Reply Likes
Was this type issue ever fixed. I am on PScc and the I keep getting text size being input automatically and locking me out totally from using the program. This is incredibly aggravating ADOBE. Your CC version is an absolute mess.
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
This bug was fixed about four months ago. If you're using PS CC, then simply update to the latest release.

Thanks,
David
Photo of anna

anna

  • 8 Posts
  • 0 Reply Likes
I just updated yesterday and it doesn't seem to me to be fixed.
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Hi Anna,

In what way are you still encountering this problem? Keep in mind, once type has been transformed, it is forever-more transformed when moving between documents. But, other than that, the problem with the widget and the problem with seemingly random font sizes should have been solved months ago. Could you share the steps you are performing? Also, I'm available for a web-hosted screenshare to get to the bottom of the trouble you're having. Just let me know and we can set that up.

Thanks,
David
Photo of Allen Roberts

Allen Roberts

  • 107 Posts
  • 1 Reply Like
Any update on the fix for the scripting version of this problem in CS6?
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Sorry, Allen, but there are no plans to update the scripting for CS6.
Photo of Allen Roberts

Allen Roberts

  • 107 Posts
  • 1 Reply Like
Wow.. that is a pretty significant bug to just leave there. What about CC, are there plans to fix the bug for that?
Photo of Thomas Nebesar

Thomas Nebesar

  • 3 Posts
  • 0 Reply Likes
Hello,

I've been having the issue of decimal points being added to type size for a while now in CS6. However the text is not being transformed at all. The type is set at a fixed size, say "26"px, and when the file is later opened the type is now set with a random decimal point like "25.42".

Photoshop CS6 is up to date, any hope of a future fix coming?

thanks.
Photo of Sorin Jurcut

Sorin Jurcut

  • 7 Posts
  • 0 Reply Likes
The issue is not fixed and is present in CC 2014 as well. I am working on a script which manipulates font sizes and I have problems retrieving the correct font size after the layer has been free-transformed
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
The problem has been fixed in the app, but NOT on a scripting level. Once a block of text has been transformed, scripting won't work.
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
This code snippet might help (from an external user):

function getFontSize(){
if(app.version.match(/^\d+/) < 13) return activeDocument.activeLayer.textItem.size;
var ref = new ActionReference();
ref.putEnumerated( charIDToTypeID('Lyr '), charIDToTypeID('Ordn'), charIDToTypeID('Trgt') );
var desc = executeActionGet(ref).getObjectValue(stringIDToTypeID('textKey'));
var textSize = desc.getList(stringIDToTypeID('textStyleRange')).getObjectValue(0).getObjectValue(stringIDToTypeID('textStyle')).getDouble (stringIDToTypeID('size'));
if (desc.hasKey(stringIDToTypeID('transform'))) {
var mFactor = desc.getObjectValue(stringIDToTypeID('transform')).getUnitDoubleValue (stringIDToTypeID('yy') );
textSize = (textSize* mFactor).toFixed(2).toString().replace(/0+$/g,'').replace(/\.$/,'');
}
return Number(textSize);
};
Photo of Sorin Jurcut

Sorin Jurcut

  • 7 Posts
  • 0 Reply Likes
The problem is that when you try to apply a size to a transformed text, the new size is also subjected to the transformation. So basically this only solves half of the problem. Also, most of these types aren't documented anywhere ("Lyr","Ordn",'Trgt') to my knowledge. I've tried to look for them in all the documentation provided by adobe and got no hit.
Photo of Allen Roberts

Allen Roberts

  • 107 Posts
  • 1 Reply Like
I sure hope that Adobe has a plan to fix this. While I have used to the code posted by David, this is very much of a band aid. Adobe, you have a great scripting language, please don't screw it up with stuff like this creeping in.
Photo of Martin Kleis Sundstrøm

Martin Kleis Sundstrøm

  • 6 Posts
  • 1 Reply Like
This issue is so dar from "solved" I can't even...

Please look at this screengrab video of me using Photoshop CC 2014 (15.2.2). It's driving me around in circles as I try to figure out .. what size is the font I'm using? What size is it ACTUALLY?

https://www.dropbox.com/s/xek9uu1iovv...
Photo of David

David, Official Rep

  • 3092 Posts
  • 481 Reply Likes
Hiya Martin,

Without looking at your settings, my first guess is that you have Snap to Pixel on.  You can turn it off under Preferences > General -- it's the bottom right of the grid of check options in the middle of the page.  This, of course, begs the point that you almost certainly transformed your text with a large scaling factor at some point.  Photoshop (normally) maintains transformations forever (yes, yes, I'm trying to get that changed...keep reading) and as a result, probably because the transformation was so large, there are floating-point rounding issue (math problems).

I get that you probably "just want it to work" and I sympathize.  I actually agree with you on that idea!

I point out how this happened, however, because TRANSFORMING TEXT is NOT the same as changing the point size.  This is true and, quite frankly an issue, because Photoshop has tried so hard to streamline and de-complicate the process to help users, as a result most people don't understand the important differences.  ANY object in Photoshop can be transformed and that process is very straightforward.  Only text, however, can get different point sizes and layering the two on top of one another is a) problematic, since most people think the two actions are the same and b) really complicated to handle, resulting in a whole suite of bugs due to older workflows and user confusions about definitions (among others).  Honestly, it's a pet-peeve of mine and I'm trying to get the architecture changed.  But, even if that does happen, if you transform text, you're likely gonna have problems.  And if you don't then, transformations would have been dumbed down way too far...  Take-Away: if you want to change the point size, use the point size control OR transform it, get an idea of the value, UNDO the transform, and enter the value.  At least for now...or keep reading...

'Course, you're probably saying, "damn it, David, just remove my transformation!"  Uh, not so easily done AND not what most users actually want.  We tried and the forums erupted in fire with the (negative) feedback.  BUT, I have a work-around...!

Using the new Libraries, you can effectively remove a PROPORTIONAL transformation from text.  How, you ask?  Open the Libraries panel.  Select your text layer and in the Libraries panel, click the T icon at the bottom left (second icon in).  You've now defined a Text Style which is based on your type layer, with the transformation calculated into the point size and then removed (*applause*).  Now, simply re-apply that Text Style back onto your selected layer and the transformation (IFF proportional) is now gone.

With this now set, you can use it as a sample to redefine your Type Styles (which have serious difficulty understanding transformations, since they're a little abstracted from them).  From there, your problems should be solved.

If not, just ping me back and I can walk you through it and/or see what troubles you're encountering.  I do screenshares with Europe all the time...

Thanks,
David