{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang3081\deflangfe3081{\fonttbl{\f0\froman\fprq2\fcharset0 Times New Roman;}{\f1\froman\fprq2\fcharset238 Times New Roman;}{\f2\fmodern\fprq1\fcharset0 Courier New;}{\f3\fswiss\fprq2\fcharset0 Arial;}{\f4\fnil\fcharset2 Symbol;}}
{\colortbl ;\red0\green0\blue255;}
{\*\generator Riched20 10.0.17134}{\*\mmathPr\mdispDef1\mwrapIndent1440 }\viewkind4\uc1
\pard\nowidctlpar\sb100\sa100\b\f0\fs24 INFRALUTION GLOBALIZER RELEASE NOTES\b0 \par
\b Version 4.0.1\par
\b0 Fixed issue where Translation Consistency Validation Rule would incorrectly flag errors where there are two or more translations where the invariant differs only in case (ie upper or lower case).\par
Changed Property File targets so that a Byte Order Mark (BOM) is not written when using UTF8 encoding to ensure compatibility with Java which does not handle the BOM correctly. \par
Changed licensing code so that RDP is only blocked by default when Globalizer is run on server operating systems. This enables Globalizer to be used from a VM via RDP for non-server operating systems.\par
Fixed potential issue where pinned and scrollable translation columns become out of sync when using Find.\par
Fixed issue with using\f1\lang1045 Alt\f0\lang3081 -A to enter the special character\f1\lang1045 \f0\lang3081 "\f1\lang1045\'b9\f0\lang3081 " with Polish keyboard\b\par
Version 4.0.0\b0\par
Added \i Translation Statistics\i0 . These can be calculated for selected translations, an individual target or the whole workspace. The statistics are include the number of changes (inserts and deletes) since the last translation by language as well as calculating the percentage complete.\par
Added \i Validate on Edit\i0 option. This allows applies validation rules as you edit and shows you and your translator any possible issues immediately to improve the quality of translations.\par
Added translation \i Attributes Window\i0 to allow you to specify the size available for a translation. The size can be either a fixed number of characters or a size (in Pixels, Points or Ems) calculated using a specified font. \par
Added support for scanning translation attributes (sizes and fonts) for Windows Forms/Controls and Property Files targets.\par
Added \i Absolute Length Validation Rule\i0 which allows you to validate that translations fit in the space specified for them in the \i Attributes Window\i0 .\par
Added \i Translation Consistency Validation Rule\i0 which checks for translation items which have the same invariant text but differing translations.\par
Added new \i Culture File Naming \i0 options to enable the use of an underscore as the Language/Region separator. \par
Added ability to filter translations by comments.\par
Added ability to filter translations to show only those with validation errors.\par
Changed order when writing translations to workspace (gxl) files to be alphabetical. This makes it easier to locate differences when using a version control system to save workspace files.\par
Fixed Form/Control preview to handle scaling of translated sizes and locations when the display scaling is different to that when the control was designed.\par
Improved Globalizer user interface when running on high DPI displays with scaling greater than 100%\par
The \i Default Font \i0 setting has been moved from \i .NET Forms \i0 and \i WPF Settings \i0 to \i General Settings\i0 and now supports setting different default fonts for different cultures.\b\par
Version 3.9.7\b0\par
Changed Microsoft Auto Translation to use new Azure API. Note that existing Translator API keys obtained through the Microsoft DataMarket will no longer work with this version. For more information and to obtain a new key see: {\f2\fs20{\field{\*\fldinst{HYPERLINK https://translatorbusiness.uservoice.com/knowledgebase/articles/1078534-microsoft-translator-has-moved-to-azure }}{\fldrslt{https://translatorbusiness.uservoice.com/knowledgebase/articles/1078534-microsoft-translator-has-moved-to-azure\ul0\cf0}}}}\f0\fs24\par
Fixed possible accidental cell edit when using \i Control-S \i0 to save workspace if the Control key does not remain held down while the "S" key is released. \par
Added ability to select \i Context\i0 , \i Target \i0 and \i Type \i0 columns and copy data from them. The whole translation row can still be selected by using the Row header.\par
Fixed issue with \i Control-A \i0 not selecting text in Edit window.\par
\b Version 3.9.6\b0\par
Fixed the Custom Event $(FilePath) parameter when building deployed satellite binaries. This was previously incorrectly set to the file name not the file path. \par
\b Version 3.9.5\b0\par
Fixed issues with localizing Universal Windows Platform (UWP) libraries.\par
Fixed E001 "Parent Target must implement GetCulturePath" Error when building ASP.NET Web Site Targets\par
\b Version 3.9.4\b0\par
Fixed issue with using non-ASCII characters in Custom Event commands\par
Fixed handling of markup and placeholders eg \{0\} when using pseudo translations\b\par
Version 3.9.3\b0\par
Fixed possible error while opening Workspace files due to fonts not being read correctly in some locales. \b\par
Version 3.9.2\b0\par
Improved \i Undo/Redo \i0 so that selection is changed as you undo and redo to show the changes being made\par
Changed \i Lookup Window \i0 to allow copy and paste from Invariant text. \par
Changed \i Lookup Window \i0 to clear previous result before starting a new search\par
Fixed possible hang when editing translations using the \i Edit Window \i0 with a \i Translation Filter \i0 applied and making edits which cause the translation to exit the filtered translation set. \par
\b Version 3.9.1\b0\par
Changed Workspace Invariant culture to enable a neutral culture (eg en instead of en-US) to be used if desired. This can be useful for Windows App localization where the Workspace Invariant culture must match the project Default language.\par
Fixed issue in Version 3.9.0 which causes an error when undoing edits.\par
Fixed issue with building HTML Help Projects that contain sub-directories\par
Fixed previewing and building of HTML Projects where the target culture uses a different code page to the current system locale. Globalizer can now optionally use the SbAppLocale utility to run the HTML Help compiler with the required code page.\par
Fixed issue with \i Delete and rebuild non-invariant Resx Files\i0 incorrectly rebuilding resw files for the default language in Windows App projects, causing comments in the invariant resw files to be lost.\par
\b Version 3.9.0\b0\par
Added automatic tracking of changes to the invariant text. When the invariant for an item changes then translations for the item have their status set to \i Needs Review\i0 . If there was an existing translation then the previous invariant text is now automatically saved and displayed to allows the translator to see exactly what has changed since the item was last translated. Previously you could use \i Compare Changes \i0 functionality to do something similar - however this only allowed a single previous value for the Invariant to be displayed for all cultures. The new functionality allows for the possibility that the previous invariant may be different for different cultures if the cultures are translated at different times.\par
Added \i Default Preview Font \i0 property to \i Form Settings \i0 and \i WPF Settings\i0 . This allows you to control the default font that is used when previewing controls and forms that do not have the font explicitly set.\par
Added \i BindingTargetNullKey \i0 property to \i Resx Extension\i0 to support localization of the NullValue for WPF bindings.\par
Changed build to exclude building targets for cultures which have been selected in the \i Excluded Cultures\i0 settings. Previously these settings only affected export.\par
Added support for importing of XLIFF files where the XLIFF target culture is for a specific culture and the workspace contains the parent culture.\par
Fixed Error 301 (XmlException) when importing XLIFF files exported by tools which are badly formatted. \par
Fixed error message when scanning Windows App resw files that are not in the \ldblquote Strings\rdblquote sub directory\par
\b Version 3.8.2\b0\par
Added Selected Items count to the status bar.\par
Fixed issue with 64 bit Globalizer user interface not changing when a non-English language is selected using the \i Tools > Globalizer Language \i0 menu. \par
Fixed issue with 64 bit Globalizer displaying a Virtual Tree license evaluation warning.\par
Fixed issue with \i Load License \i0 button not saving the Globalizer license file if the license cannot be reauthenticated by contacting the authentication server.\par
\b Version 3.8.1\b0\par
Changed naming of \ldblquote Metro\rdblquote projects and settings to \ldblquote Windows App\rdblquote to align with latest Microsoft terminology.\par
Fixed issue with localized resw files for Windows App projects being built in the wrong directory if the source file is in sub-directory.\par
Fixed issue with Windows App target scanning changing the Uid for existing elements\par
Fixed issue with DependentUpon attribute added by Globalizer to Windows App projects causing a warning in VS2015 \par
Fixed issue with Globalizer settings for Windows App, WPF and Silverlight targets not changing culture dynamically at runtime when the Globalizer culture is changed.\par
Fixed error when spellchecking with x64 version of Globalizer.\par
Fixed issue when adding \i Files\i0 targets where clicking the \i Files\i0 browse (\'85) button caused the \i File Type\i0 and \i Culture File Naming\i0 properties to revert to their default values.\par
\b Version 3.8.0\b0\par
Added separate 64 bit version of Globalizer. This can be used for previewing and building satellite assemblies for x64 specific .NET executables and components. It can also be used for AnyCPU assemblies. \par
Added \i Excluded Cultures\i0 settings for Targets. This allows you to select specific cultures for which a target will not be exported and translated. \par
Modified \i Export\i0 to only export targets for which translations are exported. When using the \i Export only items that are untranslated or need review\i0 option this removes targets which are not required because there are no matching translations.\par
Fixed generation of satellite assemblies to include the unmanaged resource properties (Version, Product Name etc - displayed by Windows Explorer in the Details tab) from the base assembly.\par
Fixed issue with using extended keyboard selection (using the Shift key) to select multiple translations.\par
\b Version 3.7.0\b0\par
Added support for exporting and importing from XLIFF files to support interoperability with other translation tools.\par
Updated the licensing parameters to enable use of latest licensing features. Existing customers will need download and install this version of Globalizer in order to authenticate their existing license keys on new machines. \par
\b Version 3.6.4\b0\par
Fixed issue with \i Inherit Parent Scan Filters\i0 checkbox not working.\par
Fixed Auto Translation of Norwegian Bokm\'e5l culture using Bing to handle issue with Bing using the incorrect culture code. \par
\b Version 3.6.3\b0\par
Fixed issues which caused the Globalizer workspace file to change and grow each time it was saved.\par
Fixed issues with cancellation of operations not working.\par
\b Version 3.6.2\b0\par
Fixed error when doing a deployed build of a target (in .NET 4) which has a space in the name.\par
Fixed issue with changing culture at design time for WPF controls/windows (using ResxExtension) not working in VS2012 and 2013\par
Added menu to the ResxExtension Notify Tray icon to allow the VS2012/2013 designer process (XDesProc) to be exited (and restarted) to update the display after resources have changed and been rebuilt. \par
\b Version 3.6.1\b0\par
Fixed bug introduced in 3.6.0 which caused an error when changing the .NET Framework option if not running as Administrator.\par
Fixed error message when attempting to load a workspace if a given culture (eg \ldblquote zh\rdblquote ) is not supported by the current .NET Framework version. \par
\b Version 3.6.0\b0\par
Added \i /allcultures\i0 command line option to support scanning non-invariant cultures from the command line.\par
Changed Globalizer to be DPI aware, to support high DPI displays with text scaling set to 125% or more. Previously Globalizer only supported scaling via DPI Virtualization. This means that text is now much clearer when using text scaling and Globalizer behaves correctly even when the Windows \i XP Style Scaling\i0 option is selected. \par
Added Visual Studio 2013 sample project links.\par
Changed workspace to save the current build options in the workspace. This lessens the likelihood of accidently performing a source build when using Globalizer to build the deployed binaries.\par
Fixed issue where preview fails with a \i NotSupportedException\i0 after a Deploy build is done with .NET 4 framework. Deploy builds are now done in a separate spawned process for .NET 4. \par
Fixed possible crash when previewing some .NET 4 Forms applications.\par
Fixed possible \i ArgumentNullException\i0 when auto translating duplicate entries if the Display Filter is set to \i untranslated items\i0 . \par
Fixed issue in \i Infralution.Localization.Wpf\i0 where exceptions would be thrown (and caught) when attempting to load resources from dynamically generated assemblies. While this did not actually cause an error it did make debugging more difficult. \par
Fixed error (E005) while building if the Globalizer workspace is saved in a sub-directory beneath the target project. \par
Fixed navigation failed error when attempting to preview ASP.NET windows/forms the first time. \par
\b Version 3.5.4\b0\par
Added tooltip to the \i Lookup Window\i0 to show the source of translations.\par
Changed \i Target > Start Application \i0 to set the working directory of the new process to the directory containing the application executable.\par
Changed \i MarkupExtensionManager.UpdateAllTargets \i0 (in WPF localization library) to avoid possible enumeration error if the registered targets change during the update.\par
\b Version 3.5.3\b0\par
Fixed bug when converting XAML properties to use the \i ResxExtension\i0 with the \i Set Default\i0 option selected. \par
Fixed issue with previewed forms, windows and control not being explicitly closed or disposed. This could potentially cause a memory leak when previewing multiple targets.\par
Fixed issue with incorrect resource names being generated for C# embedded resources contained in sub-folders which include hyphens (eg \ldblquote sub-folder\\MyResource.resx\rdblquote ) \par
\b Version 3.5.2\b0\par
Fixed issue in \i Infralution.Localization.Wpf ResourceEnumConverter\i0 which caused an exception when used inside a \i ResxExtension\i0 multibinding under .NET 4. \par
Fixed issue in \i Infralution.Localization CultureManager \i0 causing layout problems when dynamically changing culture if the screen DPI scaling is not set to the default (100%)\par
\b Version 3.5.1\b0\par
Fixed issue with loading Translation Memory (TMX) files where the \i \i0 appears inline within the \i \i0 tag. Previously no error was reported but the translation was not loaded.\par
\b Version 3.5.0\b0\par
Added ability to use external \i Translation Memories\i0 . Matching results from loaded Translation Memories can now be displayed automatically in the lookup window.\par
Added \i Fuzzy Match\i0 option to Lookup window. When selected the Lookup Window uses an intelligent algorithm to find approximate matching text.\par
Added \i Auto Update\i0 option to Lookup window. When selected the Lookup Window automatically searches (in background) the Workspace and loaded Translation Memories for strings matching the selected translation. \par
Added support for localizing Windows 8 Metro XAML applications.\par
Separated \i XAML Settings\i0 into three separate tabs within the \i Target Settings\i0 window for different XAML project types (WPF, Silverlight and Metro XAML).\par
Added \i Lookup \i0 context menu item to translation text edit boxes and improved \i Edit Window \i0 lookup behaviour.\par
Fixed issue when converting XAML to use the \i ResxExtension\i0 where the \i DefaultResxName\i0 attached property was added to \i ResourceDictionaries\i0 even though they don\rquote t support attached properties.\par
Fixed issues with auto spell checking sometimes using the incorrect dictionary after the default dictionary for a culture or the workspace invariant culture is changed.\par
Fixed issue with \i Validation Rule\i0 names not being saved when changed. \par
Changed licensing to allow users to transfer licenses between machines a limited number of times by uninstalling the license themselves.\b\par
Version 3.4.0\b0\par
Changed Microsoft Bing auto translation to use the new Microsoft Azure Translation API. Microsoft has discontinued support for the old Version 1 Bing API. The new Translation API requires users to create a Microsoft Azure account to use it - but remains free for translation volumes of less than 2 million characters per month. \par
Added Custom Event macros for file name and path without the file extension. Changed the naming convention for macros to be more consistent (old macros will continue to work).\par
Added \i Export each culture in a separate Workspace \i0 option. This enables you to quickly export separate workspaces when you have a different translator per culture.\par
Added Copy and Paste support for copying entire translation rows (including context and comments) to the clipboard as multi-column data. The data can then be pasted into applications such as Excel. The multi-column data can also be pasted back into Globalizer. The context column is used to locate the corresponding translation rows and update them with the pasted data.\par
Fixed possible error when removing a target culture if the preview window is currently previewing that culture.\par
Fixed issue with importing TMX files which contain empty tags.\par
\b Version 3.3.2\b0\par
Fixed exception when changing languages in WPF applications using \i ResxExtension \i0 (in \i Infralution.Localization.Wpf\i0 ) if the the \i ResxExtension \i0 is used in a Control Template.\par
Fixed display of culture names at design time when using \i ResxExtension \i0 in .NET 4 projects (previously the culture code was displayed rather than the friendly name).\par
Added overridable \i GetResourceName \i0 method to \i ResourceEnumConverter\i0 (in \i Infralution.Localization.Wpf\i0 ) to allow derived classes to change the resource naming.\b\par
Version 3.3.1\b0\par
Added links for Visual Studio 11 samples to Start page.\b\par
Version 3.3.0\b0\par
Added support for .NET Encryptor. Forms, Controls and Windows defined in assemblies encrypted using .NET Encryptor can now be previewed by setting the Bootstrap Assembly property on the Project Target.\par
Changed XAML localization attached property from \i ResxExtension.ResxName \i0 to \i ResxExtension.DefaultResxName\i0 . This fixes a runtime markup parsing exception in .NET 4 if the \i ResxName \i0 parameter is explicitly set for an extension.\par
\b Version 3.2.0\b0\par
Added following features to \i Infralution.Localization.Wpf \i0 assembly:\par
\pard{\pntext\f4\'B7\tab}{\*\pn\pnlvlblt\pnf4\pnindent0{\pntxtb\'B7}}\nowidctlpar\fi-360\li720\sb100\sa100 Added \f2\fs20 ResxExtension.ResxName\f0\fs24 attached property to allow setting the default \f2\fs20 ResxName\f0\fs24 for a window/control \par
{\pntext\f4\'B7\tab}Added binding properties to \f2\fs20 ResxExtension\f0\fs24 to allow you to format bound data using a resource string \par
{\pntext\f4\'B7\tab}Added support for binding to multiple data sources (similar to \f2\fs20 MultiBinding\f0\fs24 ) by nesting \f2\fs20 ResxExtension\f0\fs24 elements \par
{\pntext\f4\'B7\tab}Changed \f2\fs20 ResourceEnumConverter\f0\fs24 to implement \f2\fs20 IValueConverter\f0\fs24 to allow derived classes to be used in XAML as binding converters\par
{\pntext\f4\'B7\tab}Added check for dynamic assemblies to \f2\fs20 ResxExtension.HasEmbeddedResx \f0\fs24 method to avoid exceptions being thrown internally\par
\pard\nowidctlpar\sb100\sa100 Added \i Set default ResxName \i0 option to XAML Settings. If set the \i ResxExtension.ResxName \i0 property is set on the the top level element when converting XAML and the \i ResxName \i0 parameter is ommitted by default from \i Resx \i0 elements. \par
Added \i Set ResxName \i0 option for XAML properties. This allows you to force the \i ResxName \i0 parameter to be set explicitly for specific XAML properties when the \i Set default ResxName \i0 is set.\par
Fixed issues with resizing the Globalizer window when some Settings pages are displayed causing visual artefacts.\par
Changed XAML Resource Wrapper localization to add structured XML comments to the generated code wrappers. This eliminates compiler warnings when projects generate XML documentation.\par
Added support for translating Java Properties files.\par
Added support for alternative \i Culture File Naming \i0 schemes including those used for WIX, Android and Java Property files. The displayed \i Culture File Naming \i0 values now indicate the format of culture specific file names.\par
Added\f2\fs20 /scan \f0\fs24 command line option. This allows you to scan and save the workspace from the command line.\par
Added Windows Phone 7 Sample Project\par
Fixed issue with \i Undo/Redo \i0 potential causing an error if target rows have subsequently been removed.\par
Added warning when building \i INI File \i0 targets if translations contain new line characters. The new line characters are now automatically stripped when building.\par
Fixed \i Regex Pattern \i0 for the default \i Printf \i0 validation rule\par
\b Version 3.1.1\par
\b0 Fixed issues with adding Custom Cultures to a workspace.\par
Fixed scanning of HTML \i

\i0 elements to preserve formatting.\par
\b Version 3.1.0\par
\b0 Added support for Googles new paid translation service\par
Fixed issue with scanning of HTML incorrectly removing spaces around inline elements.\par
Fixed \i Filter Displayed Translations \i0 dialog to remove duplicate entry from the list of \i Translation Statuses\b\i0\par
Version 3.0.6\par
\b0 Fixed crash on XP if Service Pack 2 for .NET 2.0 is not installed\par
Fixed Bing auto translation of Chinese if no region is specified\par
Fixed issue with Start Page links not working correctly under Vista\b\par
Version 3.0.5\par
\b0 Fixed \i Infralution.Localization.Wpf.MarkupExtensionManager.UpdateAllTargets \i0 method to avoid possibility of "Collection was modified" exception when changing UI Culture for WPF applications.\par
Fixed possible \ldblquote Navigation to webpage was cancelled\rdblquote error when previewing ASP.NET targets.\par
Fixed possible hang issues with open/save file dialogs on some systems.\par
\b Version 3.0.4\par
\b0 Fixed issue with reading Version 2 Workspaces that defined XML Namespaces.\par
Fixed issue with \i Before Modifying File \i0 event not firing before files are changed when building XML and HTML targets.\par
\b Version 3.0.3\par
\b0 Fixed \i Resource Wrapper\i0 XAML localization method to generate the correct code when there are multiple Windows defined in an assembly.\par
Fixed issue with \i Resource Wrapper\i0 XAML localization when the \i Window.Resources\i0 element already contains a \i ResourceDictionary\i0 . The \i ResourceWrapper\i0 definition is now placed inside the \i ResourceDictionary\i0 in this case.\par
Fixed XAML localization so that \i App.xaml\i0 is now also scanned for localizable resources.\par
Fixed XAML localization to strip excess whitespace from content when converting to resx resources.\par
Fixed issues with XAML localization of VB Projects (generated code would not compile due to missing root namespace)\par
Fixed XAML localization so that XAML items corresponding to translations that are excluded for a target also excluded from XAML conversion.\par
Fixed issue with source localization builds when \i Flatten Folders\i0 option is not checked, where the culture specific resx files were not added to the project for resources under sub-folders.\par
Fixed possible exception when removing a culture from a workspace with \i Delete associated culture target files\i0 option checked (if a project target contains sub-folders and was scanned with the \i Flatten Folders\i0 options unchecked).\par
Added support for VS2010 C++ projects.\par
Fixed C++ Windows Forms Project targets so that the \i Resource Name\i0 and \i Resx Type\i0 properties are set correctly by default for \i Forms\i0 and \i Controls\i0 . Previously these had to be manually fixed after scanning the project.\par
\b Version 3.0.2\par
\b0 Fixed incorrect display of warning E123 in some circumstances.\par
Fixed incorrect version being displayed during non-English versions of setup.\par
\b Version 3.0.1\par
\b0 Added \i Before Deleting File\i0 and \i After Deleting File\i0 event types to allow custom events to be generated when Globalizer deletes culture files that are no longer required.\par
Fixed some cases where an incorrect custom event type (\i Modifying\i0 instead of \i Creating\i0 ) is used when new files are created.\par
Fixed exception when adding inline tags and scan attributes in HTML Settings.\par
Fixed link to help in German startup page so that it opens German help. \par
\b Version 3.0.0\par
\b0 Renamed product from "Globlizer.NET" to just "Globalizer". This is somewhat simpler and reflects the fact that Globalizer can be used for localizing more than just .NET applications. \par
Restructured XML, HTML and WPF properties related to scanning and moved them to \i Settings \i0 tab\i . \i0 These properties can now be set for any target within the Workspace. This enables you to set the scan properties for XML, HTML or XAML targets at the workspace level, but still override them for a specific Project or File targets.\par
Added \i Compare Changes \i0 functionality. This allows you to easily compare changes made when scanning or importing changes from a translator. If the option is enabled then an extra \i Compare Status \i0 column is displayed next to translations to enable you to quickly locate translations that have been changed. The \i Edit \i0 window now has tabs to display both the new and old (baseline) text for the translation as well as a \i Changes \i0 tab that highlights the differences. You can also compare changes to a workspace from another baseline version of the workspace. \par
Added \i Validate \i0 function (and \i Validation \i0 settings) for targets. This allows the user to define a set of validation rules for a target to check things like menu shortcuts/accerators, format strings and the length of translations. The user can also define their own custom pattern matching rules to check that specified strings in the invariant translation are included in the translated text.\par
Changed \i Validated \i0 Translation Status to \i Confirmed \i0 to avoid confusion with new \i Validate \i0 function.\par
Added \i Errors \i0 window. This displays errors and warnings from the latest scan, build or validation. It allows you to double click on the error to display the target and translation that the error was associated with. Errors can also be ignored so that they are not displayed (by default) next time you scan, build or validate.\par
Added \i Custom Events\i0 settings for targets (under \i Settings \i0 tab). These are similar to Visual Studio build events and allow you to specify a command line to run at specified events - such as before (or after) creating or modifying a file. This mechanism can be used to integrate Globalizer with source control systems (SCS) by specifying command to automatically add or checkout files to/from the SCS. \par
Added support for localizing Silverlight projects (and WPF projects) using the Resource Wrapper localization method.\par
Changed XAML conversion to automatically move the content for selected elements to the associated control content property before converting the property using the selected localization method. This means that elements such as \i TextBlock, \i0 which don't support content other than plain text, can now be automatically converted without having to first manually move the content into a property. \par
Added XML formatting options for XAML localization to allow more control over the XML generated when converting XAML to use resources.\par
Added \i Use compliant resource names \i0 option to XAML settings. This allows you to specify that the XAML Resx Extension localization should use resource names that are compatible with code generation (ie use an underscore "_" rather than a dot "." in resource names). For new workspaces this option defaults to true, for existing workspaces the option defaults to false for backward compatibility. \par
Merged \i Target->Add \i0 menus for XML, HTML and INI Files into a single \i Target->Add->Files \i0 menu. The \i Add Files Target \i0 dialog now allows you explicitly set the Target Type (ie XML, HTML or INI) of files selected for a File Group or to automatically detect the target type based on the file name. The rules for auto target type detection can be set via the \i Files/Folder \i0 options under the \i Settings \i0 tab. This allows you to create a single Files target that can include child Targets of different types.\par
Added \i Include sub-folders\i0 option to File Group targets. This allows you to easily scan all files within a directory hierarchy.\par
Added the ability to copy and paste settings between targets (and workspaces). \par
Added automatic detection of targets (such as Forms, Controls and File targets) that are no longer used in a Workspace when scanning. Unused targets are displayed with a question mark in the Workspace Explorer and can be removed using the new \i Target->Remove Unused \i0 menu option.\par
Added \i Flatten Folders \i0 option in \i Settings\i0 . This option is checked by default which gives similar behaviour to Globalizer Version 2 where folders in \i Projects \i0 and \i File Group \i0 targets are ignored and scanned child targets (eg Form and Control targets) are created directly under the parent \i Project \i0 or \i File Group \i0 target. Unchecking this option means that Globalizer will create targets (displayed in the \i Workspace Explorer \i0 window) that reflect the folder structure in the Project or File Group. This option can be set at the Workspace level or for individual targets. \par
Moved display of \i Excluded Child Targets \i0 to the \i Settings \i0 tab. This enables you to quickly select targets in the workspace and see whether they have excluded child targets without having to continually open and close a dialog as you did in Version 2.\par
Added \i Run/Edit using Culture \i0 option to \i Language Properties \i0 dialog. This allows you to control the specific culture that used for editing and starting applications when using neutral cultures. Previously Globalizer would just use the first specific culture for the neutral culture. \par
Added \i Switch windows culture on Start Application \i0 option to Workspace and Project properties. This allows you to control whether Globalizer will automatically switch the windows users culture to the selected culture before starting the localized application.\par
Added \i Set Translation Status on Edit \i0 option to enable you turn off automatic setting of translation status when you edit translations. This is useful when you are sorting or filtering by translations status and you don't want to change the status of translations until you have completed working on them.\par
Added \i Application Arguments \i0 to Project properties. This allows you to specify arguments to pass to the application when it is started. Application arguments for Projects and Workspaces can now contain a \{0\} placeholder for the culture name. This allows your application to implement switching the culture based on an argument. For instance setting the \i Application Arguments \i0 to "/culture:\{0\}" would call the application with the argument "/culture:de-de" when the selected culture is German(Germany).\par
Changed use of "Language" and "Culture" terminology in the Globalizer user interface and help to make it more consistent. The user interface and help now use the term "Culture" in cases where the user can specify a language/region.\par
Added new Start Page which provides quick access to sample projects and other Globalizer resources\par
\b Version 2.3.13\b0\par
Fixed issue with possible crashes when previewing WPF windows and controls. An exception thrown in an event handler or method of a WPF window being previewed could cause Globalizer to crash. Globalizer now catches the exception and displays an error message to allow the issue to be dealt with.\par
\b Version 2.3.12\b0\par
Fixed error when using \i Replace All \i0 when there are no matches.\par
Fixed issue with WPF \i ResxExtensions \i0 used in templates being prematurely cleaned up and not working in some circumstances.\par
Fixed WPF samples. Added \i OnClosed \i0 override to detach from \i UICultureChanged \i0 event so that the window is garbage collected.\par
\b Version 2.3.11\b0\par
Fixed issue with scanning resx entries with empty translations. These were incorrectly being scanned as null (or untranslated). \par
Fixed issue with scanning XML files that use namespaces resulting in warning (E004) for each item. \b\par
Version 2.3.10\b0\par
Fixed issue with reading TMX files that include empty elements. Previously these would cause the rest of the file to be skipped. \par
Changed TMX export so that it does not export translations which have a null invariant.\par
Fixed Copy/Paste to allow pasting of untranslated (null) values. This makes it easier to copy all translations from one language to another by allowing you to select the entire column (via Control-A) even if the column contains untranslated items. \b\par
Version 2.3.9\b0\par
Fixed issue with importing TMX files which contain inline markup elements (eg ). This previously caused an error. Inline markup elements are now stripped out when importing TMX data.\par
Changed TMX import error messages to include the XML line number.\par
Fixed issue with \i Translation Status \i0 not being saved for untranslated items. Previously if you manually set the \i Translation Status \i0 for an untranslated item to \i Needs Review \i0 then this status would be lost next time the workspace was opened. To fix this issue an additional \i IsNull \i0 attribute has been added when saving untranslated items to allow untranslated items to be distinguished from empty translations. Because earlier versions of Globalizer do not recognise this attribute, exporting untranslated items (which have had their \i Translation Status \i0 changed manually) from this version of Globalizer and importing them into an earlier version may result in the translations incorrectly appearing as empty (rather than untranslated). If you are using this feature you should ensure that your translators also upgrade to this version of Globalizer.\par
\b Version 2.3.8\b0\par
Fixed issue with Lookup Window not displaying translations correctly when an invariant cell is selected and you select a word or phrase in the Edit Window and use the Lookup shortcut (Ctrl-L)\par
Fixed issue with WPF conversion to ResxExtension (during scanning) incorrectly inserting Language attribute in ResourceDictionaries. The Language attribute is now only added to top level Window and Page elements.\b\par
Version 2.3.7\par
\b0 Fixed \i InvalidDataException \i0 error when installing new Open Office Dictionaries\b .\b0\par
Increased the minimum row height in Translation Window so that spelling mistake underlines are always visible when using in-place editing.\par
Fixed filter expression added when you exclude translations so that it matches the item exactly. Previously the expression generated could potential match other translation items with contexts that included the expression as part of the context.\par
Fixed issue with editing items with the \i Find and Replace \i0 dialog open. Previously if you clicked the \i Find Next \i0 button without committing any changes made in the \i Translation Window \i0 then the changes would potentially be lost.\par
Fixed possible exception when previewing forms and controls if you switch cultures while a non-previewable target is selected\par
Fixed possible exception when closing Globalizer if you have inplace editing a translation in the Translation Window and have pending changes.\par
\b Version 2.3.6\par
\b0 Fixed issue with Resx build copying all invariant resources if there are no translations defined for a given culture.\par
Fixed issue with Resx build not removing unnecessary metadata elements when creating culture specific resx files\par
Changed Resx build so that the type is not specified explicitly for string elements and the \i xml:space \i0 attribute is added. This produces resx files that more closely resemble those produced by Visual Studio and so reduces superficial changes to resx files when using both Visual Studio and Globalizer to edit resx files.\par
Fixed issue with Translator Edition defaulting to use .NET 4 Framework when only Client Profile is installed.\par
Fixed issue with Translator Edition running as Developer Edition under Windows Server 2003. \b\par
\b0 Fixed issue with previewing WPF controls that have width or height set to \i Auto\i0 . For controls with width or height set to \i Auto \i0 the preview will now use the \i MinWidth \i0 or \i MinHeight \i0 if set, or if no \i MinWidth/MinHeight \i0 is set will display the control with a fixed width/height of 300.\par
Fixed scanning/converting of WPF content elements to Resx Extension to trim leading and trailing whitespace\par
\b Version 2.3.5\par
\b0 Fixed exception (due to bug introduced in 2.3.4) when selecting \i Wpf Options \i0 in Scan Dialog\b\par
Version 2.3.4\par
\b0 Fixed preview of WPF Controls \par
Fixed build of new localized resx files so that it does not fail if the invariant resx file is Readonly\par
Fixed issue with scanning resx files that contain entries that use CDATA sections (as produced by Resharper).\par
\b Version 2.3.3\par
\b0 Fixed possible exception if \i Auto Translate \i0 context menu was clicked with no items selected\par
Fixed issue with keystroke duplication when creating new folders from with the \i New Workspace \i0 dialog.\par
Fixed possible hang when initiating an inplace edit in the Translation Window using keyboard. \par
Improved error message if using \i Google Auto Translate \i0 without .NET 3.5 installed.\par
\b Version 2.3.2\par
\b0 Fixed issue with Unauthorized Process Error occurring incorrectly in some circumstances\par
Changed splash screen.\par
\b Version 2.3.1\par
\b0 Fixed exception when selecting Chinese (Simplified) or Chinese (Traditional) text after changing .NET Frameworks (if \i Auto Select Input Language \i0 is enabled). \par
Fixed issue with \i FileNotFoundException \i0 (System.Web) when loading a workspace if .NET 4 Framework Client Profile is installed instead of full version.\par
Stopped user settings error message from being displayed when switching from .NET 4 Framework back to .NET 2 Framework\par
Fixed exceptions when running Globalizer with Microsoft Accessibility features turned on.\par
Changed install of Globalizer.exe.config file to be permanent so that installing future releases of Globalizer will not change the .NET Framework selected\par
\b Version 2.3.0\par
\b0 Fixed issues with copying and pasting cells containing multiple lines to and from Excel. \par
Added \i GlobalizerCmd \i0 command line console application. When adding build events to Visual Studio that call Globalizer if you use GlobalizerCmd.exe (instead of Globalizer.exe) the output from Globalizer will be directed to the Visual Studio Output window - making it easier to diagnose any issues with the build. \b\par
Version 2.2.3\par
\b0 Fixed issue with Globalizer not starting on systems using Sophos virus checker\par
\b Version 2.2.2\par
\b0 Fixed unhandled exception message when selecting and editing Chinese (Taiwan) text due to bug introduced in Version 2.2.0.\par
Fixed issue with \i Auto Select Input Language \i0 option not working (ie input language does not change) in some circumstances.\par
\b Version 2.2.1\par
\b0 Fixed German and Italian translations.\par
Minor corrections to help\par
\b Version 2.2.0\par
\b0 Added Spell Checking using Open Office compatible dictionaries.\par
Added option to Workspace properties to set the encoding (UTF-8 or UTF-16) used when saving Workspace files. UTF-8 is the default for new Workspaces. This reduces the size of uncompressed workspaces by about a factor of two.\par
Added \i /strongnamefile:file \i0 command line option. This allows you to set (or override) the strongname used to sign satellite assemblies created during a deploy build. The file can either be a ".snk" or ".pfx" file. For ".pfx" file you must also specify the password used to open the strong name file using the \i /strongnamepassword:password\i0 option.\par
Added \i /excludetargets \i0 command line option. This makes it easier to build the entire workspace while excluding some targets (for example the application setup msi target) from the build.\par
Added \i Language Properties \i0 dialog to allow you to set the properties (at this stage just the \i Editor Font\i0 ) for a selected culture from the \i Target Languages \i0 dialog\par
Moved selection of the \i Invariant Culture \i0 from the Workspace properties page to the \i Target Languages \i0 dialog. This allows you to set the properties for the Invariant language in the same way as for other languages. \par
Changed Deploy build so that the user is prompted to run Globalizer with elevated privileges if the Deploy Directory requires admin permissions to write to it (eg is under the Program Files directory). \par
Changed Deploy build so that it defines unmanaged version resources when building satellite assemblies. These are now displayed in the \i Version \i0 tab if you right click on an assembly and select \i Properties \i0 in Windows Explorer. \par
Added an error message if the strong name specified for signing a satellite assembly does not match strong name that was used to sign the base assembly.\par
Added option to set the .NET Framework Version that Globalizer uses when previewing and building satellite assemblies. This should be set to match the .NET Framework of the application being localized. If this is not set to the correct framework version then an error message is displayed when you preview a form/control or perform a deployed build. The default selection is .NET Framework 4 if it is installed.\par
Fixed \i Find and Replace \i0 to ensure that the column being searched is active and scrolled into view.\par
Fixed HTML preview so that clicking on the preview selects the corresponding translation in the Translation view. \par
Fixed bug when adding new HTML, XML and Ini File targets to a Workspace where the Deploy Directory was not saved. \par
Fixed issue with cancelling from the Add HTML, XML and Ini File target dialogs if the Target Name was not set and the text box had focus.\par
Fixed issue with User Locale not being set when running deployed applications from Globalizer under Windows 7.\par
Fixed \i Add Visual Studio Solution Target \i0 function to handle solution files which include projects in subfolders and fixed issues with parsing web site project solution files properly\b\par
Version 2.1.1\par
\b0 Changed "Source Localization" build to make culture specific embedded resource and content resx files dependent files of the invariant resource file. This reduces the clutter in the main project when supporting large numbers of languages. You can expand invariant resx file in the Visual Studio Solution Explorer to see the culture specific files.\par
Fixed issue with \i DeployDir \i0 command line parameter not working correctly if a path including a drive letter is used.\par
Fixed issue with scanning and converting WPF pages that are contained in sub folders.\par
Fixed issue with specifying WPF Control Types with namespaces in the WPF Conversion Options dialog. Previously if you specified a Control Type with a namespace then you would get an error when scanning.\par
Fixed issue with using \i ResxExtension \i0 with Prism\par
Fixed crash when previewing of ASP.NET pages on a network drive. The preview window now reports a configuration error in this case instead of crashing.\b\par
Version 2.1.0\par
\b0 Added preview of ASP.NET Pages. When you scan an ASP.NET project resources associated with a localized ASP.NET page are now automatically detected and the Resx Type is set to \i ASP.NET Page\i0 . Clicking on the \i Preview \i0 tab will display a preview of the ASP.NET page. To preview ASP.NET targets in existing Globalizer workspaces you need to manually change the Resx Type for the associated resource target.\par
Added support for localizing ASP.NET web sites which don't have an associated Visual Studio Web Application Project. Previously Globalizer could only localize the newer style ASP.NET Web Application projects.\par
Added \i Delete and rebuild non-invariant Resx Files \i0 option to build dialog. This allows you to reset the resources associated with forms and controls removing any culture specific resources that have been set outside of Globalizer (for example by using the Visual Studio designer to change the layout forms).\par
Added \i Target->Excluded Child Targets \i0 menu and dialog. This allows you to see the excluded child targets for a parent target and clear or remove items.\par
Added \i Auto Refresh \i0 check button to Preview Window. This allows you to turn off automatic update of the preview when entering translations. This can be useful if updating the preview is processor intensive or distracting.\par
Added \i Enable shadow copying of Preview Assemblies \i0 option. If enabled this option allows forms and controls to be previewed without locking the assemblies (and preventing them being rebuilt from Visual Studio). The default value is true. \par
Added \i Save and Reopen \i0 menu item. This allows you to save the current workspace and reopen it - which is useful if you have rebuilt your project in Visual Studio and wish to see the changes to forms and controls in the preview window. \par
Added \i Delete associated language target files \i0 option when removing languages from workspace. If checked this option will delete the language specific target files and remove them from Visual Studio Projects.\par
Added \i Save As \i0 menu to make it easier to move Workspace files to a different location. \i Save As \i0 adjusts the paths to Targets and the Workspace Deploy Directory relative to the new Workspace file location.\par
Changed preview window to automatically update when target properties are changed. The preview window will now update automatically if the target Resx Type or Resource Name is changed (you still need to use the Refresh button when changing the Resource Name). Previously the only way to force the preview to update was to select another target then reselect the changed target.\par
Fixed issue with error (\i E119: The control/form is not set to be localizable\i0 )\i \i0 being incorrectly reported when scanning with \i Scan All Cultures \i0 option checked.\par
Fixed issue in \i Infralution.Localization.Wpf \i0 assembly causing problems with localizing Xceed DataGrid. \i ManagedMarkupExtension.UpdateTarget \i0 now handles targets which don\rquote t inherit from \i FrameworkElement.\i0\par
Fixed issue with converting WPF controls to use the \i ResxExtension \i0 that meant the automatically generated resx key (for unnamed controls) may not be unique if new controls of the same type are added to a page after it has been scanned and converted initially. \par
Fixed the WPF \i ResxExtension \i0 converter to recognise and use either \i Name \i0 or \i x:Name \i0 properties when generating the resx key names. Previously it only recognised the \i Name \i0 property and if the \i x:Name \i0 property had been set instead it was not used in generate the resx key name\par
Fixed issue with previewing and building HTML pages that use non-latin character sets. The HTML meta charset attribute is now scanned by default (for new workspaces) and if translated enables previewing and building of HTML pages with non-latin character sets. If you have an existing workspace and you wish to translate into a non-latin charset then you should add \i //meta[@http-equiv='content-type']/@content \i0 to the \i Scan HTML Attribute \i0 list. \par
\b Version 2.0.4\par
\b0 Fixed issue with Evaluation Version of Globalizer reporting that the evaluation had expired when re-opening sample projects after making changes.\par
Enabled selection of multiple files in File Open Dialog for HTML, XML and INI file group targets. Fixed the initial directory for the File Open Dialog.\par
Changed \i Lookup Window \i0 so that double clicking on the invariant column for a row selects the corresponding item in the \i Translation \i0 and \i Edit \i0 windows.\par
Fixed \i Auto Translate \i0 and \i Pseudo Translate \i0 functions to exclude format specifiers eg "\{0:f\}" from translation. \par
Changed \i Auto Translate \i0 to exclude HTML tags from text before it is sent to the translation service. Previously the handling of HTML tags was dependent on the translator (Bing or Google) and, while usually excluded from translation, could produce different results depending on the context.\par
Changed handling for C# Forms and Controls to set the initial Resource Name by scanning the associated C# code file for the namespace. Previously if you changed the namespace of a control or form from the default then you had to also fix the Resource Name in Globalizer.\par
Fixed issue with translation text containing ampersands sometimes being displayed incorrectly.\par
\b Version 2.0.3\par
\b0 Fixed possible unhandled exception when hovering the mouse over the Scan Status column of expanded compound translation items (eg Size)\par
Fixed error when using \i Pseudo Translate \i0 or \i Auto Translate \i0 when the selected translations include items with no invariant. \par
Fixed issue with Resx Content files not being built in the correct deployed directory for deployed builds.\par
Fixed issue with the Deployed Assembly Directory not being saved in workspace.\par
Fixed the default Deploy Directory for Web Application Project targets (it should be null)\par
Fixed Deploy Build of Projects so that if a satellite assembly contains no resources it is not built.\par
Fixed output of empty inline HTML elements (for HTML Targets) so that they include the closing tag to conform with HTML 4.0.1\par
\b Version 2.0.2\par
\b0 Fixed issue with Scan Status column being (incorrectly) displayed in Translator Edition the first time a workspace is opened.\par
Fixed German translation in Options Dialog\par
Fixed display of preview error messages so that they are displayed in the current language. \par
Added \i SetThreadUICulture \i0 method to \i Infralution.Localization.CultureManager \i0 class\par
\b Version 2.0.1\par
\b0 Fixed \i Auto Translate \i0 so that it will work when used behind a web proxy that requires authentication.\par
Fixed conversion of WPF properties to use Resx Extension so that it does not convert data binding code.\par
Fixed issue with MSI dialog previews where clicking multiple times quickly on the \i Show Preview \i0 button could cause an exception.\par
\b Version 2.0.0\par
\b0 Added support for translating and previewing HTML files.\par
Added support for translating HTML Help Projects.\par
Added support for translating Windows INI files\par
Added dockable \i Preview \i0 Window. Previews for Windows Forms and Controls, WPF Windows and Controls and HTML pages are now displayed automatically in the \i Preview \i0 Window when the target is selected (instead of displaying previews in a separate dialog). The preview is updated automatically when translations are changed.\par
Added independent \i Translation Status \i0 for each culture. This makes it much easier to coordinate and manage large projects with many languages. \i Scan Status \i0 is now only used to track the status of translations in the last scan and is not visible to the translator. The \i Translation Status \i0 is automatically imported from the translators workspace.\par
Added \i Pseudo Translate \i0 menu option. This allows you to simulate translation of the selected items and verify that your localization mechanisms are working correctly before embarking on actual translation.\par
Added \i Auto Translate \i0 menu option. This provides automatic machine translation of the selected items using either Google or Microsoft's Bing translation services.\par
Added Previews of XML documents\par
Added separate \i Remove and Exclude \i0 option for targets. This enables you to determine whether a target you are removing should be excluded when the parent target is rescanned.\par
Added "Export only items that are untranslated or require review" option to Export Wizard. This allows you to minimize the size of the export file when just a few translations have changed.\par
Added ability to close \i Edit\i0 , \i Lookup\i0 , \i Preview \i0 and \i Output \i0 windows. Added \i View \i0 menu to allow closed windows to be reopened.\par
Added separate \i Options Dialog \i0 (replacing various options in the options menu).\par
Changed \i Translation Window \i0 to maintain the current selection where possible when the selected target is changed\par
\pard\nowidctlpar\b NOTE: \b0 This is a paid upgrade from previous versions and requires installation of a new license key. See {{\field{\*\fldinst{HYPERLINK www.infralution.com/globalizerpurchase.html }}{\fldrslt{www.infralution.com/globalizerpurchase.html\ul0\cf0}}}}\f0\fs24 for information on upgrade pricing.\par
\pard\nowidctlpar\sb100\sa100\b Version 1.8.3\par
\b0 Added ability to paste data from multiple Microsoft Excel rows into Globalizer as separate translations.\par
Fixed issue with authenticating Globalizer license keys via the internet with certain proxy servers. This meant that, in these cases, the license key had to be authenticated via email.\par
\b Version 1.8.2\par
\b0 Fixed issue where duplicate form/control nodes may be created in the Globalizer workspace when scanning project files in some circumstances.\par
Fixed bug in \i Infralution.Localization.Wpf.ResxExtension \i0 handling of conversion of strings to other types.\par
Changed \i Translation \i0 and \i Lookup \i0 windows to use GDI Text Rendering for complex script languages (Arabic, Hebrew etc). This improves layout of complex script languages.\b\par
Version 1.8.1\par
\b0 Changed \i Infralution.Localization.Wpf.ResxExtension \i0 to allow it to be used in WPF templates and for non-dependancy properties.\par
Fixed general error message displayed in some circumstances when previewing to be more specific\b\par
Version 1.8.0\par
\b0 Added support for localizing and previewing WPF controls and windows using \i ResxExtension\i0 markup extension (defined in Infralution.Localization.Wpf) to retreive resources from embedded resx files.\par
Created separate Developer and Translator Edition setup packages. This means you no longer have to select the installation type during setup and also allows side-by-side installation of both Developer and Translator Editions (useful for testing your translation packages). This also reduces the size of the setup that translators need to download and install.\par
Added support for undoable copy, paste and delete of comments. When a comment is selected Delete now deletes the comment not the translation row.\par
Add support for passing arguments to the Workspace start application\par
Added \i Translate Duplicates \i0 functionality when whole row is selected. This translates duplicates for each culture in the selected rows.\par
Fixed issues with finding and loading referenced assemblies and unmanaged DLLs when previewing forms and controls\par
Fixed error when scanning Resx files that have an assembly alias defined multiple times\par
Fixed issue with importing TMX files that use a DTD that cannot be resolved.\par
\b Version 1.7.1\par
\b0 Changed Comments column to word wrap if the length of the comments exceeds the column width.\par
Enabled use of the Edit Window for editing comments. Now when you select a comment in the Translation Window it is displayed in the Edit Window and can be edited.\par
Enabled use of Undo/Redo for changes to comments\par
Added support for loading strong names from password protected PFX key files.\par
Changed \i Target->Remove \i0 to exclude child targets so that they are not automatically readded when the parent target is rescanned. Added option to Scan Dialog to allow targets that have been removed to be rescanned and readded.\par
Changed project scanning to add controls/forms that aren't set to localizable as child targets. This allows you to remove these targets from the workspace if required eliminating the warning each time the project is scanned.\par
Changed TMX Import to enable using "Match On Invariant" option.\par
Fixed issue with Translator edition not saving license information in the workspace file. This could mean that once a translator had saved a workspace they would get a license warning if they opened the file again (although the workspace could still be opened without issues in the Developer edition).\par
Fixed issue with Edit Window allowing editing of Invariant even if \i Allow Invariant Edit\i0 is set to false for workspace. Also fixed Paste and Replace functions to respect this setting.\par
Fixed issue with preview and start language sub-menus not changing when the Globalizer interface language is changed.\par
Fixed display of non-string values for \i RightToLeft \i0 languages. Non-string values are now displayed with the same \i RightToLeft \i0 setting as the invariant.\par
Fixed potential error when Undoing/Redoing editing of translations for language after the language is removed from the workspace.\par
\b Version 1.7.0\b0\par
Added new Lookup Window. This allows you to quickly locate similar translations by selecting text in the Translation or Edit windows and using the Lookup Menu (or Ctrl-L shortcut) to display translations that contain the selected text.\par
Added split window to EditWindow to display both the invariant text and the translated text.\par
Added checking for duplicate menu accelerators and shortcuts to Preview. If you preview a form that uses MenuStrips, Globalizer will now warn you if the menus contain duplicate accelerators or shortcuts in the language being previewed. \par
Added ability to scan projects containing multiple forms or controls with the same name declared in different namespaces. Once scanned the Resource Name must to be changed to match the fully qualified type name of the associated form or control.\par
Added checks for valid control/form resource names when building deployed satellite assemblies. This warns if the Resource Name does not match the fully qualified type name for the control/form.\par
Added scanning of resx file comments. Scanning now imports comments from resx files.\par
Changed Workspace Open to allow opening of corrupted or incomplete workspace files. Globalizer will now open workspace files that are incomplete or have been corrupted but will report an error. \par
Fixed issue with saving/restoring window docking settings. \par
Fixed issue with exporting/saving to filenames with multiple dot extensions eg "Export.fr.gxz". Previously if you omitted the file extension "gxz" (ie entered only "Export.fr") then the extension was not added automatically and a zero length file was created.\par
Fixed issue with preview forms containing DevExpress controls that use multiple part resource names. Previously these resources were not shown translated in the preview (although they were correctly handled when building satellite assemblies)\par
Fixed issue with scanning forms defined in sub-folders. Previously the Resx Type and Resource Name were not detected correctly for Form defined in sub-folders of a project and needed to be adjusted after scanning the project.\par
Fixed exception when changing Globalizer user interface language after loading multiple workspaces.\par
Improved performance when adding or removing large numbers of languages to a Workspace.\par
Changed licensing of Globalizer to require authentication. This means existing customers will need to re-install the license keys they received when they purchased Globalizer.\b\par
Version 1.6.1\par
\b0 Fixed issue with Virtual Tree license dialog being displayed in Developer Edition when opening a workspace (introduced in 1.6.0)\par
\b Version 1.6.0\par
\b0 Added Italian translation for Globalizer user interface and documentation\par
Fixed issue with \i Auto Select Input Language \i0 not working correctly for inplace editing\par
Fixed Export and Import dialogs to maintain last language(s) exported/imported correctly\par
Fixed issue with Globalizer not setting the correct locale when starting the translated application when the selected language is Traditional or Simplified Chinese.\par
Fixed issues with licensing of Translators Edition. The workspace now include a translators license that enables editing the same number of translations as the Developer Edition that created the workspace. This means that version 1.6 (and later) of the Translator Edition cannot be used to edit workspace files produced by an earlier version of the Developer Edition. To overcome this limitation you can open the file in the latest version of the Developer Edition and resave it.\b\par
Version 1.5.1\par
\b0 Fixed possible exception when deleting translations.\par
Fixed \i Undo/Redo \i0 menu text displayed for \i Find and Replace \i0 operations\par
Fixed issues with \i Find and Replace \i0 dialog interaction with \i Auto Select Input Langauge \i0 option. If this option was enabled then the user would have to click the \i Replace \i0 button twice to perform the operation.\par
Fixed possible exception when using \i Replace All \i0 if nothing is replaced.\par
\b Version 1.5.0\par
\b0 Added German translation for Globalizer user interface and documentation\par
Fixed Recent Files menu so that it doesn't become disabled when changing Globalizer interface language\par
Fixed Undo/Redo menus so that they display the correct text when changing Globalizer interface language\par
Fixed possible delay (under some circumstances) while validating the Globalizer license\par
\b Version 1.4.3\par
\b0 Added support for using positional notation for XML Context (using # character). This is useful in cases where XML nodes cannot be uniquely identified using any other relational context.\par
Fixed issue with scanning XML nodes that contain child nodes. Previously this would scan the combined content of the child elements - and cause issues when building the translated XML document. Now only the text actually directly associated with the element (if any) is scanned.\par
Fixed issue with tooltips for very large translation items causing screen flashing.\par
Fixed issue when using Find/Replace where the found translation was selected correctly but may not always be scrolled into view.\par
Changed the default location of columns when adding a new language to a workspace so that the new language column is placed immediately following the existing language columns.\b\par
Version 1.4.2\par
\b0 Add \i Options->Globalizer Langauge \i0 menu to allow the Globalizer user interface language to be changed dynamically (previously you had to change the windows locale and restart the application)\b\par
Version 1.4.1\par
\b0 Added \i Translate Duplicates \i0 context menu.\par
Added handling of special characters in \i Display Filter \i0 dialog using escape sequence. \par
\pard{\pntext\f4\'B7\tab}{\*\pn\pnlvlblt\pnf4\pnindent0{\pntxtb\'B7}}\nowidctlpar\fi-720\li720\sb100\sa100\\*\tab - searches for literal * \par
{\pntext\f4\'B7\tab}\\%\tab - searchs for literal %\par
{\pntext\f4\'B7\tab}\\t \tab - searches for tab\par
{\pntext\f4\'B7\tab}\\n\tab - searches for newline\par
{\pntext\f4\'B7\tab}\\r \tab - searches for carriage return\par
{\pntext\f4\'B7\tab}\\\\\tab - searches for literal \\ \par
\pard\nowidctlpar\sb100\sa100 Fixed French translations of some error messages.\par
Changed \i Undo/Redo \i0 menus to display information about the operation to be done/undone\par
Fixed sorting to use culture specific string comparison\par
Added support for Visual Studio 2008 solutions and projects\par
\b Version 1.4.0\par
\b0 Added support for Import/Export of Translation Memory eXchange (TMX) files.\par
Fixed \i Display Filter \i0 dialog so that it can handle expressions where wild card (* or %) appears in the middle of text. Previously an exception would occur if a wildcard was used anywhere other then at the beginning or end of a filter expression. \par
Changed \i Display Filter \i0 dialog to set the default filter culture based on the currently selected language in the Translation Window.\par
Fixed \i Display Filter \i0 and \i Find & Replace \i0 dialogs to set the Input Language based on the selected culture when \i Auto Select Input Language \i0 is enabled.\par
Fixed errors when scanning forms containing typed DataSet components. These errors did not impact the scanning process - but were annoying.\par
Changed default Scan Filters "Scan Type Properties" option to unchecked. This results in faster scans and is probably the appropriate option for most projects.\par
Fixed error message when saving to readonly files.\par
Improved error messages when starting the deployed application.\par
\b Version 1.3.0\b0\par
Added support for localizing Windows Installer Files (MSI)\par
Changed preview mechanism to automatically close preview dialogs when the user clicks in the main window. This also allows dialogs that do not have a close button (or that throw exceptions in their OnClosed methods) to be closed.\par
Added option to allow automatic select of the Windows Input Language to match the language being edited.\par
Reorganised menus (added Options menu and removed Workspace menu)\par
Fixed incorrect output of form localizable warning (E119) when forms/controls are located under project sub-directories.\par
Fixed issue with editing Right To Left languages.\par
Added warning when importing by context if the target no longer exists in the workspace.\par
Added warning when adding/loading languages which aren't supported by the operating system.\par
Embedded Globalizer.msi in self extracting setup executable to avoid issues with launching MSI from mapped drives.\b\par
Version 1.2.1\b0\par
Fixed problem with Source Localization builds for XML files when the files are in sub-directories.\b\par
Version 1.2.0\b0\par
Added Find and Replace mechanism\par
Added functionality to Display Filter dialog to allow filtering of translations which are the same in two cultures.\par
Fixed cancel mechanism when scanning and building to make it more responsive.\par
Changed Scan and Build dialogs to remember the options from the last scan/build of the current session\par
Changed Xml File Target build so that new XML files are only created for a culture if they will be different from the Invariant (ie there are translations for the target)\par
Fixed issues with deployed directory locations for XML file targets.\par
Fixed minor issues with properties window save behaviour\par
\b Version 1.1.4\b0\par
Fixed exception when importing translations from exported workspaces\par
Fixed potential exception when closing workspaces that were created using beta versions of Globalizer\par
Fixed issue with filtering and translating duplicates for country specific cultures\par
Fixed slight flicker when completing edits\par
Fixed undo of edits to untranslated values so that the value is set back to untranslated (rather then empty)\par
\b Version 1.1.3\b0\par
Added Print/Print Preview functionality\par
Added Next/Previous Translation buttons to Edit Window and shortcut keys (Ctrl+Up, Ctrl+Down) for moving to the next/previous translation when editing.\par
Fixed exception when undoing a deletion of a selection of translation values that includes untranslated values.\b\par
Version 1.1.2\b0\par
Changed build process so that files are only written if changes have been made.\par
Added support for localizing ASP.NET projects\par
Added \i Scan Type Properties \i0 option to \i Scan Filters \i0 tab. Allows scanning of form/control localizable types to be optionally turned off.\par
\b Version 1.1.1\b0\par
Fixed issues with building XML targets in some circumstances.\par
Changed Resx Target build so that new Resx files are only created for a culture if they will be non-empty\par
Added ability to select languages to build.\par
Added ability to explicitly set status of translations.\par
Rationalized context menus for Translation Window\b\par
Version 1.1.0\b0\par
Beta Release\par
\b Version 1.0.0\b0\par
Alpha Release\par
\f3\fs20\lang1033\par
\b\f0\fs24\lang3081\par
}