Microsoft has released a service pack for Microsoft Expression Design. This article describes the issues that are fixed in Expression Design by Microsoft Expression Design Service Pack 1 (SP1).
Expression Design SP1 provides the latest updates to Expression Design. This article contains a list of the issues that are fixed by Expression Design SP1.
For more information about Expression Design Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
Description of Expression Design Service Pack 1
Issues that the service pack fixes
Issues that cause Expression Design to crash
Localization and globalization issues
- The candidate list may not appear for certain locales
After you set certain text properties, the candidate list does not appear when you enter text. This issue occurs if the following conditions are true:
In this scenario, the IME candidate window does not appear until you click the artboard.
- You use one of the following locales:
- KO (This issue affects the Hanja candidate list for the KO locale.)
- You use a dialog box such as the Font Gallery, the Swatch Gallery, or the Stroke Gallery while you edit text by using an Input Method Editor (IME).
- You cannot turn on or turn off the Traditional Chinese IME by using the CTRL+SPACEBAR keyboard combination
The CTRL+SPACEBAR keyboard combination is used to turn on or to turn off the Traditional Chinese (CHT) IME. Sometimes, you cannot turn on or turn off the CHT IME when you are editing text on the artboard.
- The CTRL+BACKSPACE keyboard combination does not work correctly in the Japanese IME
In the Japanese IME, the CTRL+BACKSPACE keyboard combination reverts character strings that have been "determined." However, this keyboard combination does not work correctly in the release version of Expression Design.
- The Hanja key does not work correctly in the Korean IME
After you click outside the artboard, the Hanja key no longer works correctly.
- The Hanja conversion window does not appear when you use a Type 3 keyboard
In the Korean IME, the Hanja conversion window appears when you press CTRL+SPACEBAR.
However, the Hanja conversion window does not appear when you press CTRL+SPACEBAR if the following conditions are true:
- You use a Type 3 keyboard.
- You edit text on the artboard.
- An unexpected character appears when you enter a character that is represented by a Unicode surrogate pair
When you enter a character that is represented by a Unicode surrogate pair, you may experience one of the following symptoms:
- The character that you enter appears two times on the artboard.
- An incorrect or unexpected character appears.
- The BACKSPACE key and the arrow keys do not work correctly in the Japanese IME
When you enter text by using the Japanese IME, the BACKSPACE key and the arrow keys may not work correctly. You experience this issue if the following conditions are true:
- You use the Japanese IME on a computer that is running Windows XP.
- The IME Input Style option is set to Natural Input.
- Text attributes do not persist when you enter text by using the Traditional Chinese IME or the Simplified Chinese IME
When you enter text by using the Traditional Chinese (CHT) IME or by using the Simplified Chinese (CHS) IME, text attributes that you set do not persist. You experience this issue if the following conditions are true:
- You enter some text by using the IME.
- You set a text attribute such as a font attribute.
- You enter more text.
- Unrecognizable text appears when you enter characters between Unicode surrogate pairs
You enter three Unicode surrogate pairs in succession and then insert characters between the pairs. When you do this, unrecognizable text appears.
This issue occurs because of an issue in the Windows Presentation Framework. This issue is fixed in the Microsoft .NET Framework version 3.5 (code name "Orcas"). To work around this issue, finish the composition before you insert characters between Unicode surrogate pairs.
- Surrogate characters may not be exported to XAML
Surrogate characters are not exported to XAML if the following conditions are true:
- You create text that contains surrogate pair characters.
- You export the text to XAML.
- Invalid XAML is generated when you paste an element that contains an image
This issue occurs when you use a locale that does not use a period (.) as the decimal point.
- Unicode characters that you copy from Adobe Illustrator may not appear in Expression Design
When you copy Unicode characters from Adobe Illustrator to Expression Design, the characters may not appear in Expression Design. This issue occurs if the following conditions are true:
In this scenario, the Unicode characters are lost when the text objects are translated for the insertion into Expression Design.
- You have Unicode characters in multiple text objects.
- You copy the multiple text objects from Adobe Illustrator and then paste them into Expression Design.
- A gradient midpoint is ignored when you export XAML
When you create a gradient in Expression Design, you can change the gradient midpoint. However, this value is not saved to XAML that you export. Therefore, an object that has a gradient may appear differently in Microsoft Expression Blend than it does in Expression Design.
- Image fills write out invalid XAML for Microsoft Silverlight
When you create an object in Expression Design that uses an image fill, the object writes the Viewport property. Silverlight does not support the Viewport property. Therefore, an exception error occurs when you run a project that uses XAML in Silverlight.
- LiveFX effects that are applied to images are not exported when you export the images to XAML
Imported images that have LiveFX effects applied are not exported to XAML correctly. Only the image is exported to XAML. The effect that was applied to the image is not exported.
- Expression Design writes an incorrect slash mark character in XAML files for use with Silverlight
In the release version of Expression Design, the direction of the slash mark character for use with Silverlight was changed. Expression Design writes a backslash character (\) in XAML files. However, Silverlight expects a forward slash mark character (/).
After you install Expression Design SP1, all exported XAML contains forward slash mark characters.
- You cannot create an image stroke that uses a grayscale alpha channel
When you create an image stroke, you can select one of the following options for the alpha channel:
However, all resulting strokes are the same, regardless of the option that you select. Therefore, you cannot create an image stroke that uses a grayscale alpha channel.
- No alpha
- Use original alpha value
After you install Expression Design SP1, you can create an image stroke that uses the fill and the stroke color that is specified in the color picker when you select the Grayscale alpha channel option. The grayscale is used to determine the transparency.
- A stroke color may unexpectedly change to a basic stroke
You change the stroke color on two selected objects that have different strokes
applied. When you do this, the stroke color may unexpectedly change to a basic stroke.
- Expression Design appears to stop responding when you import an Adobe Illustrator file
When you import an Adobe Illustrator file that contains a mesh gradient, Expression Design may appear to stop responding (hang).
- The name of an object is unexpectedly changed when you use the attribute dropper tool
When you use the attribute dropper tool to copy attributes from one object to another object, the name of the destination object may unexpectedly change to the name of the source object.
- An unwanted aliasing effect occurs when you export an image
The rasterizing algorithm for exporting images may create an unwanted aliasing effect when you export an image.
- You cannot perform antialiasing on an image whose size is 1600x1200 pixels
In the release version of Expression Design, you export an image whose size is 1600x1200 pixels. When you do this, the anti-alias check box in the Export image dialog box is unavailable.
After you install Expression Design SP1, the anti-alias check box in the Export image dialog box is available for all image sizes.
- Expression Design does not use modified document unit settings
After you modify a document unit, Expression Design does not use the modified unit setting when you next open the document. For example, you follow these steps:
In this example, the document does not use pixels when you reopen it.
- On the Edit menu, click Options, and then click Units and Grids.
- Change the Document Units value to pixels, and then click OK.
- Save the document, close the document, and then reopen the document.
- Many display updates occur when you modify a multilayer design
When you modify a multilayer design, every tool gesture causes Expression Design to update the display.
Note Tool gestures include moving or resizing a shape.
These many updates may cause an unwanted flickering effect.
- Image opacity is not exported to XAML
When you export an image to XAML, the opacity for the image is not preserved.
- A "keyPreviewImage" text string appears under a preview thumbnail image
When you first start Expression Design and then click Open on the File menu, the following text string may appear under a preview thumbnail image:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.