Type issues (Small Caps, OsF...)

https://www.dropbox.com/s/lehai5gx1bb6kom/IllustratorBUG.mp4
You can see in this video what I mean. It is almoste the same in Illustrator, InDesign... Photoshop seems to work a bit better. I already deleted the font lists, but this did not help.
I wanna earn money with good design, but without functional typographic tools I am disabled... Please gimme a hint what to do...

Can you give us a screencap with an example?

Similar Messages

Small Caps Problem

I use Helvetica Neue, and have for the last 4 years. Recently, whenever I change lower case type to small caps, funky looking characters show up. If I export to a PDF, the small caps are fine. What's happening?

Can you give us a screencap with an example?

Photoshop CS3 can't do lowercase type-only large and small caps

Photoshop CS3, G5 PowerMac Dual 2GHz w/ 7GB RAM
A weird Photoshop problem: using the type tool, I can only produce type in large-and-small-caps, as opposed to upper and lower case. I can't generate any lowercase text. I've tried all the usual diagnostic tools: trashing the prefs seemed to work at first, but it's destructive of other stuff I don't want to lose, and anyway the problem came back after a while. I tried the Phantom User, and learned that the problem is tied to my User Identity, i.e., the problem doesn't exist in other User identities, but how do I make use of that information? I considered migrating to a new user identity, but I would have to go through every single appliciation, blah blah blah. So: does anybody have a quick, elegant solution to this, or is this a problem that has suddenly cropped up elsewhere? I'm not crippled by it, thanks to Illustrator CS3, but it's a convenience that I miss. And how do I trash the PS prefs without losing my brush tool presets?

Birck, >trashing the prefs seemed to work at first, but it's destructive of other stuff I don't want to lose, What "destruction" are you talking about? >and anyway the problem came back after a while. I assume this happens with fonts other than those (such as Trajan Std) that were designed with just caps and small caps. It sounds like it may be a duplicate or corrupted font issue. Did you use a good font manager to check for duplicate or corrupted fonts? Did you clear font caches (with Cocktail)? > tried the Phantom User, I see a black mask, cape and scary organ music here. <g> If logging in as a new user clears the problem, you may have a corrupted user identity and should stop using it. Neil

Small Caps ePub Issue

I am working on putting text into the ePub format and keep running into the same issue.
I want the title of the chapter to utilize Small Caps. Within InDesign I've got it look exactly the way I wish for it to - "Chapter One" appearing with small caps.
I've Highlighted the phrase "Chapter One" and applied a paragraph style that has the following features:
[no paragraph style] + next [same style] + Times New Roman + size: 24 pt + small point
When I export to ePub to view the document in Adobe Digital Editions these changes are not present. I've tried just about everything from applying character styles and nested styles, but nothing is working. I'd like these Small Cap appearances to work in the ePub versions as well.
Any thoughts on why this is not working?
Any help is much appreciated. Scouring the internet for a while has not turned up any advice.
Thanks in advance.

Hi- I have a problem with small caps and epub export too, in InD 5.0.
I defined a style with a nested stye that applies small caps for the first four words. I see this definition in the CSS output by InD:
span.no-style-override-2 {
font-variant: small-caps;
I do not see this style applied in any of the content. If I manually code it in:
Eric and Kate, young ....
it is correctly displayed. I'd like to get InDesign to export it correctly. I notice the same behavior in 5.5.
What can I do to have my nested style properly marked up in the epub export?
Thanks.

Office 2013 RTM: STILL no true small caps: WHY? WHY? WHY?

I have just un-installed the Office 2013 Preview, and installed the Office 2013 RTM 60-day trial.
I had hoped that between the two versions, the issue of missing true small caps in Word had been addressed. But no. Whilst Word 2013 supports OpenType ligatures and OpenType stylistic sets and OpenType old-style numbers and and and, it STILL DOES NOT SUPPORT
TRUE SMALL CAPS. Yes, it has a small caps function, but this just reduces the size of the font, instead of using the dedicated small caps letters included in a lot of OpenType fonts. What's the difference? The difference is that with true small caps, the stroke
width of upper case, lower case and small caps letters match, whereas in the cheapy, flimsy, yucky version that Office only offers, the small caps letters are thinner than the normal letters of that font - obviously so, as they are merely shrunken.
Try it for yourself. Type something like "AaMmXx" in an OpenType font with small caps, say, Calibri or Gabriola, at, say, 24pt, in Word 2013 and in Publisher 2013, and apply small caps in each, and print them. Compare the stroke widths. See what I mean?
Publisher does true small caps. Word doesn't.
So, why, Microsoft, why, oh why, oh why, when other typographical features (ligatures, stylistic sets, etc. etc. & so 4th) are supported in Word 2013, are small caps not? I just don't understand it. Why? Are small caps held to be something that only
professional typesetters should be allowed to use with typesetting programs like Publisher, whereas ordinary folk with Word shouldn't? Or is it trick to boost sales of Puiblisher? Or did no-one think about it? What is it? Because it's very annoying!

Well, in the second place, inserting characters via Insert Symbol is a pain in the posterior, and, of course, the spell checker doesn't recognise them. But in the first place, that only works if the font author has been thoughtful enough to give the small
caps glyphs Unicode code points, say, in the Private Use Area (like in Calluna). Normally, however, they don't - the small caps glyphs are only accessible via a small caps function, as lacking in Word. Excel is worse - apparently, Microsoft think that OpenType
advanced features ought not to be used in spreadsheets.
So having found fonts with small caps, the only way to use them is to use a font program either to assign the small caps glyphs to PUA code points, or to put them in a separate font (which at least means that other applications and spell checkers can use
them).

Simulated helvetica small caps not displayed acceptably in PDF

It's a never ending battle, this trying to get some sense out of computers. In a post earlier this year (http://forums.adobe.com/message/1287805#12878) I asked how to overcome the lack of proper small caps in Helvetica. Sandee came back with a suggestion, which I followed up, and it seemed to give reasonable results. And within InDesign, and when printed, it works.
However, when I export to PDF the small caps are not shown correctly on the screen. (The PDF file can be downloaded from http://www.mediafire.com/download.php?nmjlhmiwt3i). They look a mess unless you zoom in about 500%. They print okay, but I'm not having a messy looking PDF sent to the printer. It's nothing but offputting.
If that was the only difficulty I could probably accept it, but I intend making my two books freely available for download in PDF form and I certainly don't want rubbish-looking fonts on display.
It looks like my mock small caps may have to be replaced with caps.
QUES 1
Is it possible to make my mock small caps display acceptably on the screen within a PDF? I have tried exporting to PDF at various resolutions, and with optimize for web turned on and off, but that makes no difference.
QUES 2
Another option is to get hold of a Helvetica font (or similar) that does have small caps. Where could I get hold of one of those?
The original InDesign file from which the PDF was obtained, can be downloaded from http://www.mediafire.com/?zddtj5m5d3q in case anyone wants to play around.

Thanks for the responses. I'm surprised the PDF looked okay, so I've emailed it to half a dozen people to see how it looks on their system. Maybe it's my screen or my Adobe Reader that's at fault.
I have attached two screen captures of what it look like on my screen. One at 100%, the other at 200%.
I'd like to continue using Helvetica because it's the one I've used in about 200 sidebars. If I change fonts, I imagine I could be days cleaning up the text oversets or undersets. I did think of changing fonts, and looked at all the sans serifs on my system, including the Open Type ones, but none had small caps. And buying an expert set: I could spend the next two days trying to sort out where to buy one of those and whether it actually contain small caps. Plus, I can't justify a price in excess of $100 for the sake of 400 words.

Pages 4.2 no Small Caps can be activated

I use a lot Pages for texts, flyers and posters. There seems to be a serious bug within Pages 4.2. if you open the typo panel and activate the Small Caps feature or Opentype fonts they though they can be clicked Pages does not transform the marked text into Small Caps. So the this opentype feature doesn't finction under Pages any more. I experienced also kerning problems within Pages 4.2 using the word "Test". There is no kerning between T and e using the Fakt font from Ourtype. The same problems don't occur in TextEdit and the same problems never occured under Leopard or Lion, so it seems to be a sole Pages 4.2. problem under Mountain Lion. I reported it to the Apple Bug Reporter (no reply so far) but would be interested what you guys think of it and if you experience the same problems?

Sorry for the spelling and grammar errors, here again the topic:
There seems to be a serious bug within Pages 4.2. If you open the typography panel and activate the small caps feature of opentype fonts though you can click the check-box Pages does not transform the marked text into small caps. So this opentype feature (small caps) doesn't function under Pages any more.
I experienced also kerning problems within Pages 4.2 using the word "Test". There is no kerning between T and e using the Fakt font from Ourtype. (There was never every any issue with this under Leopard or Lion!)
The same problems don't occur in TextEdit under Mountain Lion, so it seems to be a sole Pages 4.2. problem under Mountain Lion.
I reported it to the Apple Bug Reporter (no reply so far) but would be interested what you guys think about this and if you experience the same problems?

Small caps not displaying correctly in the ePub file

Hello All,
I am using cs5.5 to generate ePub file, and I found that small caps contents not displaying correctly in the generated ePub file even the CSS looks correct. Please check and confirm, if anyone faced this issue? Also other formatting components are looks fine in the ePub file.
Thanks,
Praveen

@Jongware/Bob, thanks for your responses, I checked the ePub output using 'Adobe Digital Editions', and getting the same issue in 'Calibre', but in 'Sigil', it looks fine.
In CSS it has been declared like below:
span.SmallCaps {
font-variant : small-caps;
Here 'SmallCaps' is the character style applied for the 'small caps' contents.
Thanks,
Praveen

Small caps in running heads - mixed case problem

My running head is set to be small caps, and it picks up mixed-case text from the document. I want the head to be all 'lower case' small caps (or 'upper case', unless that really means ordinary caps) but can see no way to achieve this. Instead I get 'mixed case' small caps, if that makes any sense. If I select the head on the master page and then Type | Change Case, this has no effect on the appearance either on the master or the generated heads. How do I achieve uniform small caps where the source text for the running head is mixed-case? If small .indd attachments were allowed I would have attached one, but it got rejected despite not being llisted as a forbidden type.

A few ways to do this:
a script: http://jsid.blogspot.com/2005/09/script-of-day-changing-case-again.html
or in your paragraph styles use OT small caps (assuming you're using an OT font)
I also set up a keyboard shortcut, to Type > Change Case > lowercase
you could probably do it with GREP too...

Problem with Small Caps

I have a problem with small caps when using Times New Roman and Helvetica, but not when using Adobe Garamond Pro, and would like to find out why.
I generate the small caps within InDesign by the "TT" box in the Control Window. Adobe Garamond comes up with beautiful small caps that blend in with the surrounding text. When I do the same with Helvetica, the small caps, especially if they have normal caps amongst them, are quite inelegant looking because of different letter widths.
So I did some experiments with half a dozen other serif and sans-serif fonts and none of them were as elegant as Adobe Garamond Pro. For a sample of what I mean, download:
http://www.mediafire.com/?z5fm0zndmzm
which compares three fonts: Adobe Garmond, Heletica, and Times New Roman.
Unfortunately, I did not pick up this problem until I received my first proof from the printers, and now I will have to change all the Helvetica small caps to normal caps, as I can see no other way of overcoming this inelegancy.
I checked in New Scientist magazine (it uses a serif and sans-serif font throughout, and what I thought I remembered as small caps to begin their stories) to see what they do, but they actually use caps instead of small-caps at the beginning of stories.
Three questions:
Q1: Is the way I generate small caps the correct way?
Q2: Is there something wrong with my Helvetica and Times New Roman fonts?
Q3: Could it be that only Adobe Garamond has an internal, properly designed small caps?
I have checked the attributes of the fonts: Garamond is Open Type Postscript, Helvetica is PostScript Type 1 , and Times New Roman is TrueType.
Any comments most appreciated.

Thanks for the hints. I tried Scott's method and it works with a bit of extra adjustment. The settings I obtained for 12 point Helvetica were:
Horizontal and vertical scaling: 70.5%;
Stroke: 0.1 pt
Tracking: +25 em
Baseline shift: +0.1 pt
The steps to obtain small-caps 12 pt Helvetica are:
Step 1: Type text as normal.
Step 2: Select only the lower-case text you want to convert to small caps. i.e if what is to become small caps already has a capital (such as a place name) do not apply the settings to the capitals, unless that's the effect you want.
Step 3: Apply the above settings manually or via or Character Style.
Problem 1: How do I rid my Character Style of the font size so that only the scaling factors remain? As it is, if I want to apply small-caps to a different font size than the one I have set up, I have to manually change the font size after applying the style.
Problem 2: The scaling factors do not appear to work for changes in font size. When I used 24 pt and applied the above settings, the small-caps were too thin. The method only really works for a particular size, which in reality is all you would normally require.

Small Cap Fonts

I am trying to figure out how to use a small cap font when creating a PDF document manually... for example:
7 0 obj
<<
/Type/Font
/Name /T5
/BaseFont/Helvetica,SmallCap
/Subtype/Type1
/Encoding /WinAnsiEncoding
>>
endobj
I've tried many different variations around this basic structure, and I have tried including a fontDescriptor
7 0 obj
<<
/Type/FontDescriptor
/Flags 131104 %NonSymbolic & Small Caps
endobj
Can anyone point me in the right direction?
Thanks!
Corey

> What I am not fully clear is how to use styled variations.
These are either separate fonts or typesetting effects.
>
> What I am trying to figure out is how to use Helvetica in small cap style.
>It seems that you are telling me that I would need to embed a Helvetica small caps font - but I don't know where to get it or how to embed it.
It's not clear whether such a thing even exists. Certainly, no such
font is commonly found, nor an Arial small caps.
If you had the font, the PDF Reference tells you how to embed it,
though this is a major project (people often find the scope of the PDF
generation project multiplies by 10 at this point).
>
>I have adobe
Big company, Adobe. What of their software do you have?
> I can print a Word document with small cap text to a pdf, and it works fine, but looking the file, I can't tell where it has gotten the font information.
Since you almost certainly don't have the font, this leaves us with
typographic effect. Just use capital letters in the regular font, but
use them smaller. This wouldn't satisfy a typographer, but if you are
happy with what Word does, go for it.
Use font metrics to determine the ascent of nondescending lower case
and upper case letters in your target font, and scale accordingly (so
your upper case is the same height as a lower case character).
> when I select to use small caps on a font in MS Word, do I have a specific small cap font installed, or is word doing its magic with the base font and different sizes?
Word is doing some simple magic. Even if you purchased and installed a
small caps font, Word would have no way to use it unless you selected
the font: Windows has no style linking beyond bold and italics.
Windows will in fact fake missing bold and italic, which is considered
in typographical terms truly evil.
Aandi Inston

IWorks: no small caps can be activated

Hi there, I wonder why so far no body has picked up or discussed a serious bug in iWorks that is: that no true small caps from opentype fonts can be activated via the typography panel within Mountain Lion. The problem exists with Pages 4.2., Numbers 2.2., and Keynote 5.2. Its also impossible to install the former version of Pages, 4.1., under Mountain Lion, where this function still worked. There are also problem with the kerning. Opentype fonts who have kerning like Fakt from Ourtype have no kerning in iWork products but they have it in TextEdit. Within TextEdit those problem don't exist.
I reported these problems to https://bugreport.apple.com/ but no response so far.

Sorry for the spelling and grammar errors, here again the topic:
There seems to be a serious bug within Pages 4.2. If you open the typography panel and activate the small caps feature of opentype fonts though you can click the check-box Pages does not transform the marked text into small caps. So this opentype feature (small caps) doesn't function under Pages any more.
I experienced also kerning problems within Pages 4.2 using the word "Test". There is no kerning between T and e using the Fakt font from Ourtype. (There was never every any issue with this under Leopard or Lion!)
The same problems don't occur in TextEdit under Mountain Lion, so it seems to be a sole Pages 4.2. problem under Mountain Lion.
I reported it to the Apple Bug Reporter (no reply so far) but would be interested what you guys think about this and if you experience the same problems?

Small Caps CS6 printing incorrect characters

Windows 7, CS6, Universal Type Client (extensis)
Working files for over a year all ok. Now when printing files, random characters which are using 'small caps' in character style are being mapped to different characters. Workaround is to close file, shutdown system & restart. Reprint same file & characters are ok. Has anyone seen this happen?

Sounds like a font clash.
Are you using any font management systems?
Have got a version installed in your System Fonts and in your Adobe Fonts folder?
Try and trace the original font that's used and archive the other fonts you can find in folders.

Change Small Caps Cap Height?

Is there a way to change the small caps cap height, both when there are no dedicated small caps and when there are?

No.
Edit > Preferences > Advanced Type > Small Cap adjusts the *size* (width as well as height) of generated small caps. True small caps are presented the way the font designer intended, not at the size you put in Preferences.
There's nothing to stop you from making your own small caps character style with the vertical scale (or vertical and horizontal scale) adjusted however you like. PITA, though, applying this to only lower case letters.
BTW, and you probably know this but I'll mention it anyway: true small caps are drawn for their size. IOW, the letterforms are thicker, proportionately, than their full-caps counterparts. The reason people think true small caps look better than generated small caps is because generated small caps are 70% (or whatever) smaller everywhere. Generated small caps look thin, and the smaller they get the thinner they look. True small caps look appropriately thick. Sizing them differently from the font designer's intent subverts this perfection.
Ken

Script to replace small caps that are typed as capital letters with non-capital letters (A = a, B = b, etc...)

I'm looking for a way to replace small caps that are typed as capitals by their normal equivalent.
I've got a text that contains a lot of names which should all be set in small caps.
In fact they are, but because capital letters are used for first letters they don't scale.
Short: I would like to be able to look for A, B, C... (in small caps) and replace them with (a, b, c...) in small caps in one go.
(compare two arrays?? -> is this possible in indesign scripting)

Hi,
Actually, it works only with OpenType fonts and - in this case - can be managed by UI find...change feature.
With other type of font we need a real change of contents (another keyboard hit).
It could be done with this code (activeDocument is a target):
-- works for Open Type as well --
// For Latin Basic (ASCII from 65 to 90)
// changes a "cap" letter to a "small" letter
// if Capitalization.SMALL_CAPS is applied to
app.findGrepPreferences = app.findGrepPreferences = null;
app.findGrepPreferences.findWhat = "\\u";
app.findGrepPreferences.capitalization = Capitalization.SMALL_CAPS;
var
mSTART = 65, // ASCII number for "A"
Mstart = 97, // ASCII number for "a"
mDiff = 0,
mTarget = app.activeDocument,
mFound = mTarget.findGrep(),
len = mFound.length, cString;
while (len-->0) {
cString = mFound[len].contents;
mDiff = cString.charCodeAt(0) - mSTART;
if (mDiff > -1 && mDiff < 26)
mFound[len].contents = String.fromCharCode( Mstart + mDiff );
app.findGrepPreferences = app.findGrepPreferences = null;
Jarek

Type issues (Small Caps, OsF...)

Similar Messages

Maybe you are looking for