I set some text with different opacity settings on each letter in Quark, fully expecting InDesign to use the first letter’s opacity (InDesign can’t set opacity on a letter-by-letter basis), but I would have expected the frame and fill opacity to be honored, as CS3 now supports it. Perhaps the greatest omission was with items with different Frame, Fill, and Text opacity in Quark, which translated to a single CS2-type opacity setting.
Q2id for cs3 plus#
For example, nonprinting layers in Quark (Suppress Output) converted to CS2-type hidden layers, not nonprinting CS3 layers plus the Keep Runaround layer setting in Quark was lost in InDesign. Other areas of conversion didn’t seem to take advantage of the CS3 features.
Most specialty characters translated correctly except for Quark’s discretionary paragraph return, which didn’t translate to the new CS3 discretionary line break, but instead to a space.
Q2id for cs3 update#
Still, in the end, it was easy to update the type styles and remove all the overrides. Also, Quark’s keep-with-next paragraph settings didn’t translate to InDesign’s keep-with-next “X†lines - I realize the plug-in would have to make a line quantity decision, but I feel a default “1†would have been better than ignoring the setting. When I removed the overrides, some of the based-on style settings didn’t carry through, including first-line indent. My text came in visually correct but I noticed style overrides on both the paragraph and character styles. One should expect text to rewrap because of the difference with how the programs work however, I noticed some glitches with the type-style formats that, in my opinion, shouldn’t have happened. There are, however, some areas that need improvement. In addition, if a file has multiple layouts, you get to choose which layout is translated (you can’t select all of them at one time).
0 kommentar(er)
