L10NSharp.CheckOrFixXliff 11.0.0

Learn more about Target Frameworks and .NET Standard.

• .NETFramework 4.6.2

  • L10NSharp (>= 11.0.0)

• .NETFramework 4.8

  • L10NSharp (>= 11.0.0)

• net8.0

  • L10NSharp (>= 11.0.0)

Changes since version 10.0.0

Added:
- [L10NSharp] Added pseudolocalization support: lookups for the standard `qps-ploc` pseudo-locale (`LocalizationManager.PseudoLocalizationLanguageId`) return the English text pseudolocalized at runtime (e.g. `[Tîitlée Mîissîing]`), so testers can spot non-internationalized strings and layout problems. Set `LocalizationManager.OfferPseudoLocalization = true` to include it in the offered UI languages; `LocalizationManager.PseudoLocalize(string)` exposes the transform directly. The SampleApp turns this on, so you can see it in action. See `src/L10NSharp/Pseudo/README.md`.
- [L10NSharp] Added two new public on-the-fly translators, `MicrosoftTranslator` and `MyMemoryTranslator`, subclassing the now-public `TranslatorBase`. They were introduced as the fail-safe translators behind `LanguageChoosingDialog` (see "Fixed", below), but are general-purpose and usable directly for similar ad hoc localization needs: `MyMemoryTranslator` needs no configuration (free, keyless, ~5,000 characters/day/IP quota); `MicrosoftTranslator` is an opt-in wrapper around the Azure AI Translator v3 REST API, configured via `MicrosoftTranslator.SubscriptionKey`/`.Region` or the `L10NSHARP_TRANSLATOR_KEY`/`L10NSHARP_TRANSLATOR_REGION` environment variables.

Changed:
- BREAKING CHANGE: [L10NSharp] [L10NSharp.Windows.Forms] [SampleApp] [CheckOrFixXliff] [ExtractXliff] Replaced the `net461` target framework with `net462`. The `System.Resources.Extensions` version raised transitively by the `SIL.ReleaseTasks` upgrade (above) no longer ships a `net461`-specific assembly, so `net461` is no longer a supported or tested target. Projects that still need to target `net461` should continue using the last release built for it, or upgrade to at least `net462`.

Fixed:
- [L10NSharp.Windows.Forms] Fixed `LanguageChoosingDialog`'s fail-safe, on-the-fly translation of its title/message/OK button, which had been silently broken since the Bing/Microsoft Translator v1 SOAP API it used was retired. It now uses the free, keyless MyMemory Translation API by default; host apps that want more robust translation can opt in to the new public `MicrosoftTranslator` class (Azure AI Translator v3) by setting a subscription key (see "Added", above). See [#163](https://github.com/sillsdev/l10nsharp/issues/163). The SampleApp has a "Show Language Chooser" button so you can see it in action without needing to fake a missing-locale scenario.

Removed:
- [L10NSharp.Windows.Forms] Removed the internal `BingTranslator` class and its generated WCF service reference, along with the `System.ServiceModel`/`System.Security.Cryptography.Xml` dependencies they required, since the API they called has been retired. See "Fixed", above.

Security:
- [L10NSharp] [L10NSharp.Windows.Forms] [CheckOrFixXliff] [ExtractXliff] Upgraded `SIL.ReleaseTasks` from 2.5.0 to 3.3.0. This also raises the resolved version of `System.Resources.Extensions` (a transitive dependency of `SIL.ReleaseTasks`) from 6.0.0 to 10.0.11. Note: `SIL.ReleaseTasks` 3.3.0 has a known, build-time-only dependency on a vulnerable `Newtonsoft.Json` (via a temporary revert of its own `SIL.Core` dependency, pending an upstream `Mono.Unix` packaging issue) — per the upstream maintainers this is not an exploitable runtime risk, since the package is build-tool-only and never ships in L10nSharp's own output, and no L10nSharp or SIL.ReleaseTasks build step feeds it untrusted JSON. See [sillsdev/SIL.BuildTasks#88](https://github.com/sillsdev/SIL.BuildTasks/pull/88) for details.

See full changelog at https://github.com/sillsdev/l10nsharp/blob/master/CHANGELOG.md