OpenType Ligatures broken in CS6

I have an OpenType Font of "cursive" handwriting. I used it for years in CS4 (InDesign and Illustrator). I just upgraded to to CS6 and some of the ligatures don't work, namely, initial capitals don't connect unless they are the first word on a line or after a comma or period. This worked great in CS4 and works fine in Word. I checked it on my Windows machine and with a friend's Mac. The problem is the same on all. Does anyone know how to fix this? Thanks!

Mylenium, you are awesome! May your day be merry and bright. Here's the trick: Paragraph>Adobe World Ready Paragraph Composer. The default is Adobe Paragraph Composer, but that won't let these complex OpenType Ligatures work properly. Thank you!

Similar Messages

Idml from cc cannot be opened or rather is broken in cs6

Hi there,
i saved an idml from an indesign cc document and tried to open it in indesign cs6. First cs6 crashes down, than after trying again, it opens indeed, but the textboxes are broken..they are displaced and to small for their content. (don't know, if there was any other problem..just saw that one for the moment)
Please help me! I'm really desperate, becaus i need this document for my client..:(
Thanks a lot!
Hanna_999

I'm notr sure I understand the question, or maybe you didn't understand me. I'm sugesting you not use the existing files, which seem to be damaged. You can probably recover the text from those files using InDesign Tagged Text, story by story, but that's all you will be using from what you have now. You need to make new files the same size, import the tagged text, then re-import any placed art.
The easy method for cleaning a damaged file is to export to .idml, but you've already found that isn't working.

After Effects CS4 files alignment broken in CS6

Hi all. I have just been loading some of my older projects (CS4) into my shiny new copy of CS6 and a lot of the files are broken. The issue is that the layers seem to have shifted horizontaly...their pivot points are still correct, however the layer's position has shifted left or right horizontally...no problems vertically. It seems to be happenng with assets generated in CS4 Illustrator and it is almost like their bounding box has changed. This will mean spending ages lining stuff up again, and I'd love to know if anyone else has seen this happening...and has found a way to fix it.
Thank you for your time
Shane

Thanks for the heads up. Embarrassingly I thought I had
I've posted over there too.
thanks again
Shane

Fit Content Proportionally Broken in CS6?

I have been having a lot of issue with Fit Content Proportionally since upgrading to CS6.
In many of my documents (some new, some pulled in from earlier versions and saved over as CS6), I find that both via the menu and via the keyboard shortcut, the commonly-used and absolutely essential "Fit Content Proportionally" command just simply does not work.
I can create a bunch of square frames, and then fill them all with various-sized and shaped images, and then when I would usually Fit Content Proportionally to make them all scale down inside the boxes, what I get instead is no response at all. The only way to "fix" the problem is to go to the toolbar with the content selected and change either the vertical or horizontal percentage to any number at all. As long as the proportion lock is in place, then that changes both % numbers to the same number, and thus fixing the problem. This is what makes me think it is a bug.
Is there some new fitting setting in CS6 that I need to change?
I have tried saving as IDML and importing back into CS6, but the behavior persists. Interestingly, if I change the fitting via the toolbar % "fix" and then select Fit Content to Frame (not proportionally), then Fit Content Proportionally is broken again, and does nothing at all.
On most of my documents, Fit Content Proportionally works exactly as expected, and exactly as it always has. Of course my biggest "problem" documents contain large numbers of images.
High Res Image:
http://i.imgur.com/kl9jS.jpg

This is a bug or a big enough change in behavior that it should come with a warning alert the first time you use it. I've replicated it across different 8.0.1 installs and (Mac) OSs.
To replicate:
Place graphic. I haven't seen a difference among placed graphic types.
Resize the graphic frame non-proportionally.
Object=>Fitting=>Fit Content to Frame, so that the content is scaled non-proportionally. (Or select the content and scale it non-proportionally.)
Object=>Fitting=>Fit Content Proportionally. Nothing happens. (Or, if you scaled the content without fitting it in the previous step, the content may be centered, and it may be scaled, but the proportions won't be changed.)
I suppose you could make an argument that this is more correct than the old behavior—the command now means "Fit without changing the proportions"—but it's a big change, and I doubt anybody wants it to work this way.
Here's a short script that should more or less give the old behavior:
function fit(item) {
var i, l, graphic;
if (item instanceof Group) {
    for (i = 0, l = item.pageItems.length; i < l; i++) {
      fit(item.pageItems[i].getElements()[0]);
else if (item.hasOwnProperty("imageTypeName")) {
    item.horizontalScale = item.horizontalScale < 0 ? -100 : 100;
    item.verticalScale = item.verticalScale < 0 ? -100 : 100;
    item.fit(FitOptions.PROPORTIONALLY);
else if (item.hasOwnProperty("graphics")) {
    for (i = 0, l = item.graphics.length; i < l; i++) {
      graphic = item.graphics[i];
      graphic.horizontalScale = graphic.horizontalScale < 0 ? -100 : 100;
      graphic.verticalScale = graphic.verticalScale < 0 ? -100 : 100;
      graphic.fit(FitOptions.PROPORTIONALLY);
function main() {
var i, l;
if (!app.documents.length) {
    return;
for (i = 0, l = app.selection.length; i < l; i++) {
    fit(app.selection[i]);
app.doScript(main, ScriptLanguage.JAVASCRIPT, undefined, UndoModes.ENTIRE_SCRIPT, "Really Fit Content Proportionally");
There are certainly some corner cases I've left out. Let me know if you try to use it and it doesn't work right.
Jeff

Does Framemaker 10 support opentype ligatures like InDesign?

Could not find an answer to this doing a search. Does FM 10 offer full Opentype support for ligatures etc?
Thanks.

Naphtali,
As Van said, FrameMaker does not support any OpenType »features«, it has the same plain old text composer. There are some new fonts around that non longer contain traditional kerning pairs but only OpenType kerning and FrameMaker has a problem with them (unless you switch off kerning).
Basically this is a pity, because there very cool fonts around which take advantage of OpenType features, one example was mentioned today by Thomas Phinney, a font you can use to build charts by switching on ligatures:
http://tktype.com/chartwell.php
Cool, isn't it?
- Michael

Playback is entirely broken in CS6 and Elements

I have a frustratingly persistent problem: When I hit space or "play" to play my timeline, nothing at all happens.
This happens regardless of what files I put in the timeline (it even happens if the timeline has just an audio file or a photo). The program lets me put clips into the timeline, render them, and scrub through them manually by dragging the slider. It just won't play the timeline.
The problem only began after I'd already used the program normally for about an hour. And bafflingly, every now and then—twice so far in my few dozen attempts to use the program—this problem disappears and the timeline plays just fine.
An Adobe Support employee used screenshare to try fixing the problem by creating a root user account for me, but using it changed nothing.
Technical details:
New iMac 27" with a clean install of OS X Mountain Lion 10.8.2
Adobe Premiere Pro CS6 and Adobe Premiere Elements 11 (problem occurs with both)
Fixes I've tried:
Logging in as root
Replacing com.apple.audio.AggregateDevices.plist by deleting/renaming it (I don't have the file)
Replacing com.apple.audio.AggregateDevices.plist by creating an aggregate device with Audio MIDI Setup (does not create file)
Repairing disk permissions, repairing disk, then trying all the above
Installing new NVIDEA driver
Uninstalling and re-installing Premiere
My problem seems very similar to another user's unresolved reported issue: http://forums.adobe.com/message/4822956 I've messaged that user asking if they found a solution, but received no reply.

Just to get this out of the way early, as a test, make sure that the Timeline Panel has focus, and try the Spacebar again. While the Timeline will play, with many other Panels having focus, I have encountered times, where, say focus on the Project Panel, will not allow the Timeline to play.
In PrPro, there is an orange border around any Panel with focus, but PrE is not so easy to spot, unless you are looking at the Timeline Panel's border, when you click on it, and notice a very subtle (I mean VERY subtle) change.
Good luck,
Hunt

Pages panel: Option-drag to duplicate broken in CS6

For some reason, the ability to quickly duplicate a page or spread in the Page panel via an Option-drag doesn't work in CS6. If I try to, say, Option-drag page 3 to insert a duplicate of it between pages 8 and 9, all it does is move page 3 there. To get the desired result, I have to first duplicate the page (which inserts it at the end of my document), then drag it to the proper place.
Option-drag to duplicate/insert worked fine in previous versions, and it's expected behavior on the Mac. Am I missing something here?

Thanks, Bob!
I've also noticed that sometimes Option-drag does nothing at all. I get a spinning beachball for a second, then... nothing.
I'm hesitant to believe that trashing my preferences will fix this, as I've seen this happen on two separate Macs.

Scene Detection Broken in CS6?

I'm having awful difficulty capturing video in CS6. Specifically, every 60 seconds or so CS6 keeps prompting me to save the scene it thinks it's captured, even though scene detection is *not* checked (it is off) and abort on dropped frames is also off.
I'd be happy to just have it capture the tape as a single scene, but it refuses to cooperate.
I am unable to disable scene detect, it seems.
The only other reports I was able to find relate to CS5 and the suggestions there do not seem to make any difference.
Re: Possible Work Around for Capture and Scene Detect
Anyone else seen this problem?
Setup:
Mac OS X 10.10.2
Canon GL2 (mini DV; firewire)
Premiere Pro CS6

I ended up enabling scene detect and babysitting this particular tape. That was extremely painful and not what I expected from a professional product like Premiere.
As a side note, it seems like scene detect works and that this is perhaps a problem with a separate mechanism that tries to detect the end of tape or something.

Is Dynamic Link Encore Burning a Bluray.....Broken in CS6?

I started a new thread for this as it is an important question. The background for my question is in another current thread about 1080 60P clips being in a sequence time line with the project settings at 1080i 29.97. Using the Dynamic Link > Encore > bluray burned works fine for me in CS5.5 Premiere, still active in my Mac. From a self contained 1080i movie I imported that I was able to export from the time line or sequence in CS6 which I am just starting to use. The project settings are 1080i 29.97 in both CS5.5 and 6.0. I just updated to the latest 6.0.2 software and still no luck. The whole process seems to work and for the test 4 minutes in the sequences the burns take the time to do them. Just under 1GB burned onto the 25GB -R discs.
But the 5.5 works fine whereas the now updated 6.0.2 Premiere version yields discs that will not read in a bluray player, and with the Disc Utility looking at them, it is saying the burns are "unsupported".
Is this a known issue they are working on? I don't think I'm a unique situation as I was searching with google today and came across somewhere else someone saying the same thing about the Dynamic Link process > burns with CS6.
Thanks
Ron

Have you tried creating a disc image first and then burning that to disc in Disk Utility? You may also want to try burning at lower speeds than the maximum your drive offers.

Export to layers broken in CS6

When I use it, I get:
The object "current document" is not currently available.
Win7Pro x64

By any chance are you editing in floating windows. There is a bug in CS6 that can cause Scripts and action to fail when Script and actions switch betweem documents. Like your script or action is processing a document opens an other document sizes it to fit into the the document you working on then select all and copies the resized image to the clipboard. When the script or action then closes the second document no save the does a select to past the clipboard into the select or any other command that requires a current document may fail. What seems to be happening is the command is being executed befor the close no save complets the switch back to the first document. Thus "current document" is not currently. This happen on my Windows XP laptop 32bit system and on my Windows 7 system when I run Photoshop CS6 32Bit exe. The Windows 7 Photoshol CS6 64bit dydtrm does not fail. If I edit itn tabs this problem does not happen but other bugs in the action Player and Pfotoshopp scripting still cause some actions and scripts to fail.
http://feedback.photoshop.com/photoshop_family/topics/actions_do_not_work_properly_while_o pen_documents_as_tabs_are_not_selected

Use Previews not working in CS6 Mac

It was working in 5.5, but appears to be broken for CS6.
I just rendered a spot using MB Looks on an adjustment layer. Took 6 minutes. I then immediately exported the sequence, and it took 6 minutes. My past experience is that the export should have taken about 18 seconds.
Anybody else seeing this? If so, I'll file a bug report.
MacPro3,1 - 10.7.4 - 32G RAM, Quadro 4000 w/stock OS driver; CUDA 4.2.10 - Pr CS 601

Be that as it may, Jim, this isn't advertised behavior. The Help documents specifically claim that using Previews will speed up exports when the output format matches the Sequence settings.
To wit:
Work with preview files
When you render previews, Premiere Pro creates files on your hard disk. These preview files contain the results of any effects that Premiere Pro processed during a preview. If you preview the same work area more than once without making any changes, Premiere Pro instantly plays back the preview files instead of processing the sequence again. Premiere Pro stores the preview files in a folder you can specify. Similarly, preview files can save time when you export the final video program by using the processed effects already stored.
web page:
http://help.adobe.com/en_US/premierepro/cs/using/WS1c9bc5c2e465a58a91cf0b1038518aef7-7cd7a .html
I don't want an inferior workaround, I want the software to work as advertised.

Weird Symbols in my Text! Help! (Unicode?)

So, InDesign has decided to change certain character combos into weird characters. When I copy them out, they show up right in every other program - but they print and export wrong (otherwise I wouldn't care too much).
il = S with a v mark on top (I don't even know how to make it with the keyboard, or what it's called.)
io = Ú
There may be more that I haven't come across yet.
It's done this before, but I don't remember how I fixed it. It had something to do with changing to or from some kind of Unicode, I think.
Working in Snow Leopard, CS6 with Cloud.
Thanks! -T
EDIT: It doesn't do it in certain boxes, but I have no idea why some and not others.
EDIT 2: FIXED! Yay for corrupt fonts! (/sarcasm) Deactivating and then reactivating the trouble fonts fixed the problem.
It's still an InDesign bug though, since it DOESN'T affect any of my other programs. Omg. That was not cool to happen on deadline.

Glad you could get it to work again! Nothing like a good deadline to encounter such problems.
Here is a bit of background information:
A font consists of 'regular' characters (which you can type in from a keyboard; those are indeed Unicode characters), 'special' characters (ligatures, Real Small Caps, Oldstyle numbering, etc., which typically are not valid Unicode characters), and a list of commands which say "if these two character go in, replace them by this single other one instead". That list of commands specifies OpenType ligatures -- and it doesn't really work on characters, but on glyphs instead. A 'character' has a Unicode value, but a 'glyph' may not have one -- it's just an index in the list of all individual drawings in the font, specifying the nth glyph in there.
When all's well, this is not something you'd ordinarily notice. InDesign keeps a list of all fonts, and of all characters and glyphs in all of these fonts, and its OpenType Glyph relations (which, as you may deduce, are only valid for the font they appear in -- some fonts have more "glyphs" than others, and the Glyph Order varies wildly from one font to another, as you can see in the Glyphs Panel when sorted on "GID" (= "Glyph ID")).
What happened with your system is that presumably InDesign got the list of 'glyphs' from one file, but OpenType features from another file, with the exact same font name! So the perfectly normal operation "if you see glyph number 15 followed by glyph number 31, replace it with glyph number 65", meaning for that one font "replace "f" followed by "i" with the glyph "ﬁ"", got confused and instead came to mean "replace "i" followed by "l" with "Š"" (its proper name is "S Caron", with the Caron being this V accent).
So possibly you had more than one version of the same full font name installed (not the file name, but the internal full font name; "Times New Roman Italic", for example). One of the tricks to check this is to select this weirded-up text and disable Automatic Ligatures. If you see it revert to readable text, then this was the issue.
It's also possible something inside your system got confused -- InDesign, written by Adobe, accessed loads and loads of Extra Tricks in fonts that your typical other software doesn't care, or even know, about. That's why mishaps of this kind are typically picked up first by InDesign.
The Find Font dialog is your friend in tackling this issue. You can inspect the file paths of the troublesome fonts, and see if there is anything out of order; for example, you might suddenly see an unexpected file path. A tell-tale sign of Double Font Syndrome is when you physically remove that font file out of InDesign's view, and you can still see it works in InDesign -- but now with another file path in the Find Font dialog. At that point you only have to decide which one of the two was the "correct" font file ...

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

FRAME FITTING BUG? Indesign CC

I think this has been covered before for Indesign CS 6. (Re: Indesign CS6 Frame Fitting Options bug?)
I have this same bug in CC. We have recently moved from 5.5 to CC and it's causing a major issue. I do comic strip and multiple place comic strip pages into full page frames that have been set via frame fitting to being centred. Except it won't centre the images. See the CS 6 discussion above for more specifics.
Is there a work around yet for CC or is is still broken since CS6?! It's costing me money as i cannot go back to cs 5.5.

Hi, Pickory!
(Or Richard – whatever you prefer)
That was easy. You left your traces in the copyright statement of the script at Kerntiff ;-)
//DESCRIPTION: After place, V1.0.1.
//(c) 2013 Richard Bines kerntiff.co.uk
And posted about the function ourAfterPlace(e){} here:
Re: Indesign CS6 Frame Fitting Options bug?
After tracing all app.eventListeners with a for in loop, I could tell the jsxbin part of the script was using that function:
//RESULTS:
name
label
eventType    afterPlace
handler
function ourAfterPlace() {
    [compiled code]
id    6
isValid    true
parent    [object Application]
index    1
properties    [object Object]
isValid    true
Uwe

No recognized audio in .M2TS files

I've seen a couple of different threads about this issue that have said the same thing but all have referenced AVCHD from various Sony Cameras. In my case my footage is from HDPVR. Why the capture device would matter doesn't make any sense to me but regardless Premiere Pro CS6 doesn't just not import the audio... it doesn't recognize it at all. There is no mention of audio at all when looking at the properties.
My footage is recorded with AC3 (2 channel source)
As everyone else has said... there was no issue with 5.5 which is what I'm still using to edit since this is obviously broken in CS6.
I've yet to see a concrete solution anywhere. I was hopeful that a bug fix would be included in the update today but no such luck.
So what's the solution Adobe? Is there a bugfix coming? In the mean time I should just leave CS6 installed in hopes of an update to fix the issue?
Slightly Annoyed with this.

OK OK OK ! Everyone is rigth . Here we´re wrong. Hitachi corporation is wrong, makiing the hayabusa´s camera that produces a MPEG2 file that CS6 "hate" ! The 40K dollars Sony camera we have , make a .MPEG file that CS6 "hate" , and yet these two companies decided to use non-standard file on purpose, so that users had problems many problems, to cause, delays, losses, hassles and all sorts of trouble with clients, losses contracts . miss schedules and so on. A jerky and flaw Encore to do not generate the DVDs, many PGC problems, and so on. OK.
OK. ADOBE is that it must be right, and the whole world wrong. Thank you. I know well what we here suffer with this CS6, and user Hayabusa knows what he is passing trough his CS6 do not recognises audio. The CS6 he have installed in his machine maybe other tha "hates" his audio files.Tje software "hates" us is the only explanations.
We do not try to use CS6 anymore. We knew what we being trough. many monts of sadness, frustrations, many many many redo jobs...
Maybe in the future a new version CS7 will solve problems and return with MPEG2 fully supported, as occurs today in CS5.5.
An editor who works here, once said, that seems to be "The curse of the even number"! Explaining : The CS3 version was very good. The CS4 came full of problems and unstable, as occurs today with CS6. The CS5.5 came and solved the problems of CS4.
Thus, the CS7 will come OK, no problems and everything is working to solve the problems of CS6 !

OpenType Ligatures broken in CS6

Similar Messages

Maybe you are looking for