Small Cap Bug

Apologies if this has been answered, but I tried to do a search on the forum.
I know in CS2 there was a bug with small caps. Has this been fixed in CS3?
Thanks
doc

>The typesetting houses can't tell the a Random House, Simon & Schuster, or a HarperCollins (or whoever) what to do.
Where did I ever say they could? All along, I've noted that these sort of decisions are often made by people at a level higher than those doing the typesetting and that they're not negotiable. However, you wrote that in this case "Their designers did their design", and I just posed the question why those designers would choose a typeface without small caps when they knew that the text required them. And it was actually meant as a rhetorical question - rightly or wrongly, I assumed that the reason they did was because they simply didn't care or know about the difference between true and faked small caps.
>if they want to use fake small caps I'm not going to tell some guy behind the oak desk that he's full of crap.
Where did anyone ever suggest telling the client that he or she was "full of crap"? If a client comes in and says "use typeface X for this book", I don't see what the problem is with the designer saying "you realise that this means that we're going to have to fake the small caps/artifically bolden the text/oblique the text?". There's a world of difference between that and abusing them. And I never said that the typesetting house was to do this - I said that the designer should. You do say that "We can advise", which is all I ever suggested. I don't know where you're getting this impression from that I'm saying you should abuse them and tell them what to do.
>I haven't lowered my standards.
Never said you had. You seem to be getting very worked up about what was, as I say, a simple rhetorical question.
>And personally I'd rather see fake small caps used than gaudy CAPS.
Gosh, never heard of caps being gaudy before!
>Are you in book publishing?
Yes, though it's a lot smaller market in New Zealand than the States.

Similar Messages

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?

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 disappeared

Hi,
I have InDesign-files made about one and a half monthes ago (with CS5).
When they were done they had text with small caps (font used was Arial and Trebuchet), and they worked fine. Now, when I opened those same files (which have not been edited in the mean time), all the small caps are now showing as regular text, and I can't get the small caps to appear.
This same behavior appears in both mac and windows cs5.
What has happened, and how can I fix that?
Best regards,
Johanna

Did you package the job? Check the file location for a fonts folder - then remove the fonts folder (copy it to a safe place)
It's a known bug.
http://indesignsecrets.com/document-fonts-feature-in-indesign-cs5-appears-buggy-with-small -caps.php

CS4 small caps size and tracking

Found something annoying. Maybe someone can confirm it (or explain it?)
before I file a bug report. I'm using 6.01.532 on Windows XP SP2.
Set some type in full/small caps using a font that doesn't have true
small caps. Change the small caps size to something ridiculous (like
30%) in Preferences and you should be able to see the change when you
okay Prefs. Now set some tracking on the type and try to change the
small caps size in Preferences again.
Does your type show the change, or does it ignore your setting in
Preferences?
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com

Thanks, Peter
I can't duplicate it today. I did try restarting ID yesterday (and it's
been restarted again this morning), and it was showing up yesterday only
hours after trashing prefs due to a different problem (that was fixed by
trashing prefs). Mystery.
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com

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).

In Acrobat, is there a way to have a form field use small caps in place of lower-case text?

I found java script online that will force a field to be all caps (using it in the format tab > custom format script). But I have not been able to find anything to change the lowercase text to small caps. Anyone know how to do that (or if it just can't be done in Acrobat)?

But if you use a "small CAPs" font, you need to be sure the font is fully embedded in the PDF. If not, it is likely that users will not be able to use your form.

Using TextInput boxes to change to small Caps lettering with NO ....

Using two TextInput boxes (fName and lName) which are writting at the same time over to a (fullName) Text box, BUT change the data in here automaticly to 'small Caps' lettering with NO spaces.
I'm finding all sort of things but nothing close enough.Any help would be appriciated!
Thanks in advance aktell

How about this:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
    <mx:Script>
        <![CDATA[
            protected function name_changeHandler(event:Event):void {
                var firstName:String = fName.text.toLowerCase();
                var lastName:String = lName.text.toLowerCase();
                fullName.text = firstName + lastName;
        ]]>
    </mx:Script>
    <mx:Label x="156" y="74" text="first"/>
    <mx:TextInput x="199" y="72" id="fName" change="name_changeHandler(event)"/>
    <mx:Label x="156" y="104" text="last"/>
    <mx:TextInput x="199" y="102" id="lName" change="name_changeHandler(event)"/>
    <mx:Text x="199" y="132" text="Text" id="fullName"/>
</mx:Application>
I think this does what you were asking for.
Chris

How do I change caps of an OpenType font to small caps in my InDesign cc document?

Greetings, Community. It would be great if I could discover how to change caps of an OpenType font to small caps in my InDesign cc document. That's the simple question.
To be more exact, I have an 18-page play that contains stage directions in caps in parentheses, which I would like to change to small caps. The font I'm using is an OpenType, Minion Pro, with small caps.
Another thing is, I'd ideally like to be able to do that without changing all caps in the document, and also, to not have to convert the caps to lower case in order to do it.
My source document (which I Placed in my InDesign document) is Microsoft Word 2011 for Mac.
I did go to Microsoft to find out how to do it in Word, but could only find a solution for Word for Windows.
I did try their solution anyhow (a macro) but it didn't work.
     Thanks a lot. It's great being in InDesign even though I had my good years with QuarkXpress, which eventually became impossible for me.
     Morty Sklar

Is this what you're talking about, Michael? Where do I paste it? (The whole thing?)
     Morty
// Change case interactively. Find/change options should be set in InDesign's Find/Change window.
// Peter Kahrel -- www.kahrel.plus.com
#targetengine "change_case";
create_palette().show();
function create_palette ()
    var w = Window.find ("palette", "Change case");
    if (w === null)
        return create_palette_sub ();
    return w;
function create_palette_sub ()
    var changetype;
    var w = new Window ("palette", "Change case", undefined, {resizeable: true});
        w.alignChildren = "fill";
        var options = [ChangecaseMode.lowercase, ChangecaseMode.uppercase];
        var rb = w.add ("panel");
            var upper_to_lower = rb.add ("radiobutton", undefined, "A > a");
            var lower_to_upper = rb.add ("radiobutton", undefined, "a > A");
        var smallcaps = w.add ("checkbox", undefined, " Apply SC");
        var b = w.add ("group {orientation: 'column', alignChildren: 'fill'}");
        var find = b.add ("button", undefined, "Find");
            var change = b.add ("button", undefined, "Change");
            var change_all = b.add ("button", undefined, "Change all");
            var change_find = b.add ("button", undefined, "Change/find");
        if (app.findGrepPreferences.findWhat.indexOf ("\\u") > -1)
            upper_to_lower.value = true;
            changetype = ChangecaseMode.lowercase;
        else
            lower_to_upper.value = true;
            changetype = ChangecaseMode.uppercase;
        upper_to_lower.onClick = function () {changetype = ChangecaseMode.lowercase};
        lower_to_upper.onClick = function () {changetype = ChangecaseMode.uppercase};
        var found, found_counter;
        find.onClick = function () {
            if (this.text === 'Find') {
                found = app.documents[0].findGrep();
                if (found.length > 0){
                    found_counter = 0;
                    find.text = 'Find next';
                    show_found (found[found_counter]);
                } else {
                    alert ("No (more) matches found.");
            } else {
                found_counter++;
                if (found_counter < found.length){
                    show_found (found[found_counter]);
                } else {
                    find.text = 'Find';
                    alert ("No (more) matches found.");
        change.onClick = function () {
            found[found_counter].changecase(changetype);
            if (smallcaps.value == true) {
                found[found_counter].capitalization = Capitalization.smallCaps;
        change_find.onClick = function (){
            if (found_counter < found.length){
                found[found_counter].changecase(changetype);
                if (smallcaps.value == true) {
                    found[found_counter].capitalization = Capitalization.smallCaps;
                found_counter++;
                if (found_counter < found.length){
                    show_found (found[found_counter]);
                } else {
                    alert ("No (more) matches found.");
        change_all.onClick = function () {
            for (var i = found_counter; i < found.length; i++) {
                found[i].changecase(changetype);
                if (smallcaps.value == true) {
                    found[i].capitalization = Capitalization.smallCaps;
        w.onDeactivate = w.onActivate = function () {find.text = 'Find'}
    return w;
    } // create_palette_sub
function show_found (f)
    if (f.parentTextFrames.length === 0) // If in overset text
        app.activeWindow.activePage = find_page(f.parentStory.textContainers[0].endTextFrame);
    else
        f.select();
        app.activeWindow.activePage = find_page (f.parentTextFrames[0]);
function find_page(o)
    if (o.hasOwnProperty ("parentPage")) // CS5 and later
        return o.parentPage;
    else
        return find_page_classic(o)
function find_page_classic (o)
    try
        if (o.constructor.name == "Page")
            return o;
        switch (o.parent.constructor.name)
            case "Character": return find_page_classic (o.parent);
            case "Cell": return find_page_classic (o.parent.texts[0].parentTextFrames[0]);
            case "Table" : return find_page_classic (o.parent);
            case "TextFrame" : return find_page_classic (o.parent);
            case "Group" : return find_page_classic (o.parent);
            case "Story": return find_page_classic (o.parentTextFrames[0]);
            case "Footnote": return find_page_classic (o.parent.storyOffset);
            case "Page" : return o.parent;
        catch (_) {return ""}

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.

Is there a way to format text in Small Caps?

I have just installed Photoshop Elements 11 for Windows and am wondering if there is a setting to format text in small caps?

No, PSE doesn't recognize small caps as an option. You can do all caps, but small caps only happen by accident. For some reason it's not uncommon for the text tool to decide on its own only to do small caps, but there's no way to make it happen at will, at least not without an add-on like elements+ from simple photoshop. (There may be others that include small caps, but that's the only I can think of right now.)

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...

Table and columns in small caps!

Dear All,
My database is 11gR2 and Linux is the OS.
One of my application, whose code I am unable to access, it trying to insert records in Oracle database. The problem is that application is case sensitive and try to find table name and columns in small caps, while it gets upper case from Oracle and give error or invalid identifier.
Is there any option to create table and fields with small letters.
Kindly help.
Regards,
Imran

misterimran wrote:
...The problem is that application is case sensitive and try to find table name and columns in small caps...What application could look for tables/columns in small caps ? As stated above, creating tables/columns enclosed by double quotes might help, but that'd mean the code must use double quotes everywhere...
while it gets upper case from Oracle and give error or invalid identifier. It get as is, please show the error.
Nicolas.

Small caps - is there a way to change size ratio of lower to upper case?

I am using Adobe InDesign CS4 and one problem I've had is that when I select Small Caps on the character styles panel, lower case characters are about 60% the size of upper case characters. I'd like this to be more around 80% in my document.
I don't see a way to do this, so I'm having to avoid using Small Caps and am having to select various portions of each word and set them to different sizes.
Is there a setting I am missing for Small Caps that would save me this trouble? My typeface is Minion so I may also see if there's a variant available that uses well-crafted small caps.
Tim

Dave,
>.. adjust the size of the "lowercase" characters by using a GREP style
Yes ... and no.
It doesn't have to be an extremely complicated GREP style. You mention Unicode ranges, but it's not even necessary. You could try
>[a-z]
to select all lowercase characters, but it leaves out accented ones. Now specifying ranges for these doesn't work very good (to put it mildly), because they do not appear consecutively in the Unicode set.
Fortunately, GREP has a wildcard
>\l
for "lowercase", and this matches
i every
lowercase character (even Greek and Russian ones). It's equal to the POSIX expression
>[[:lower:]]
As this seems to work just the way you want, then why the "No"? The GREP style will be applied to
i all
lowercase characters in the paragraph, not just to the words you wanted.
[Warning: Dirty trick follows. Do Not Copy Unless Forced To.]
Of course you can
i force
the GREP style pick up 'unique' words by making them unique somehow. If you insert an invisible character
i before
and
i after
the words you want to mark -- in the case at hand, the ones you want to small-capitalize --, you can include the invisible characters in the GREP style. For example, by specifying
>~-\l+~-
you can "mark" words by inserting a soft hyphen before and after certain words. (This example also presumes only lowercase characters inbetween.) You don't have to use the soft hyphen, there are a couple more markers you could (ab)use. I think I'll leave it up to your imagination to wonder where it could possibly go wrong.

Small Cap Bug

Similar Messages

Maybe you are looking for