L10NSharp.Windows.Forms 10.0.0-beta0009

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher. .NET Framework 4.6.1 This package targets .NET Framework 4.6.1. The package is compatible with this framework or higher.
This is a prerelease version of L10NSharp.Windows.Forms.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package L10NSharp.Windows.Forms --version 10.0.0-beta0009
                    


                    

                
NuGet\Install-Package L10NSharp.Windows.Forms -Version 10.0.0-beta0009
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="L10NSharp.Windows.Forms" Version="10.0.0-beta0009" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="L10NSharp.Windows.Forms" Version="10.0.0-beta0009" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="L10NSharp.Windows.Forms" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add L10NSharp.Windows.Forms --version 10.0.0-beta0009
                    


                    

                
#r "nuget: L10NSharp.Windows.Forms, 10.0.0-beta0009"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package L10NSharp.Windows.Forms@10.0.0-beta0009
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=L10NSharp.Windows.Forms&version=10.0.0-beta0009&prerelease
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=L10NSharp.Windows.Forms&version=10.0.0-beta0009&prerelease
                    


                            Install as a Cake Tool

L10NSharp.Windows.Forms is a .NET localization library for Windows Forms applications. It collects strings which need localization when your application first runs and saves them in a XLIFF file. It can also dynamically collect strings at runtime.

Product Compatible and additional computed target framework versions.
.NET net8.0-windows7.0 is compatible.  net9.0-windows was computed.  net10.0-windows was computed. 
.NET Framework net461 is compatible.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 is compatible.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (5)

Showing the top 5 NuGet packages that depend on L10NSharp.Windows.Forms:

Package Downloads
SIL.Windows.Forms.Keyboarding

The SIL.Windows.Forms.Keyboarding library provides cross-platform functionality for keyboard selection and switching in Windows Forms applications. Currently, this library supports system and Keyman keyboards on Windows, and X keyboard extension (XKB) and Intelligent Input Bus (IBus) keyboards on Linux.
SIL.Windows.Forms

SIL.Windows.Forms contains Windows Forms classes for UI elements (controls and dialogs) that are commonly used across various SIL applications. SIL.Windows.Forms is similar to SIL.Core in that it does not contain classes that are specific to any domain.
SIL.Chorus.FLExBridge

Library that allows multiple FieldWorks users to collaborate remotely (i.e., not necessarily connected by a local network).
SIL.Chorus.LibChorus

End-user collaboration library via 3-way xml merging and hg dvcs under the hood.
SIL.ChorusPlugin.LibFLExBridge

Library that allows multiple FieldWorks users to collaborate remotely (i.e., not necessarily connected by a local network).

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.0.0-beta0013 57 6/29/2026
10.0.0-beta0012 251 6/26/2026
10.0.0-beta0011 54 6/26/2026
10.0.0-beta0010 310 6/17/2026
10.0.0-beta0009 92 6/15/2026
10.0.0-beta0008 92 6/15/2026
10.0.0-beta0007 90 6/15/2026
10.0.0-beta0006 91 6/15/2026
10.0.0-beta0005 89 6/5/2026
10.0.0-beta0004 1,996 5/4/2026
10.0.0-beta0003 101 5/4/2026
10.0.0-beta0002 270 4/28/2026
10.0.0-beta0001 831 2/9/2026
9.0.0 3,204 2/3/2026
9.0.0-beta0002 112 2/3/2026
9.0.0-beta0001 6,731 9/18/2025

Changes since version 9.0.0

Added:
- [L10NSharp] Added `net8.0` as a target framework, enabling use on non-Windows platforms, and added cross-platform CI/CD coverage for `net8.0`.
- [L10NSharp] Added UiLanguageChanged event to ILocalizationManager. This provides a way for clients to deal with changes now that (in Windows) LocalizeItemDlg<XLiffDocument>.StringsLocalized no longer exists.

Changed:
- [L10NSharp] Removed CanCustomizeLocalizations and PrepareToCustomizeLocalizations from ILocalizationManager since L10nSharp no longer provides a mechanism by which users may customize localizations.
- [L10NSharp] Removed the following members from ILocalizationManager since they are really only needed internally and serve no purpose in the public API:
   - AppVersion
   - NamespaceBeginnings (no longer used even internally)
   - FilenamesToAddToCache
- [L10NSharp] Removed emailForSubmissions parameter from LocalizationManager.Create. Since the localization dialog was jettisoned, it no longer makes sense to store this information on the localization manager.
- [L10NSharp.Windows.Forms] Removed emailForSubmissions parameter (8th parameter) from LocalizationManagerWinforms.Create. Since the localization dialog was jettisoned, it no longer makes sense to store this information on the localization manager.
- [L10NSharp] Replaced the .NET 8.0 target with .NET Standard 2.0 for broader compatibility.


Fixed:
- [L10NSharp.Windows.Forms] Restored project-local Resources support for `FallbackLanguagesDlgBase` button images (`Move`, `Move_up`, and `Move_down`).
- [L10NSharp.Windows.Forms] Corrected resource manager base name to `L10NSharp.Windows.Forms.Properties.Resources`.
- [L10NSharp.Windows.Forms.Tests] Corrected resource manager base name to `L10NSharp.Windows.Forms.Tests.Properties.Resources`.
- [L10NSharp] Fixed race condition in `XLiffBody.AddTransUnitRaw` where two concurrent threads with the same translation-unit ID could both bypass the duplicate check and silently overwrite each other's entry. (#150)
- [L10NSharp] Eliminated unnecessary cross-instance lock contention in `XLiffBody` by making `_transUnitIdLock` instance-level instead of static. (#150)
- [L10NSharp] Fixed `FilenamesToAddToCache` yielding both the custom and installed XLIFF for the same language when `UseLanguageCodeFolders` is `true`, causing custom translations to be silently overwritten by installed ones. (#140)
- [L10NSharp] Fixed `ExtractXliff` accumulating duplicate "Not found in static scan" notes on successive runs; the note is now replaced rather than appended, and removed when the string is subsequently found. (#113)
- [L10NSharp] Fixed `LocalizationManager.GetString` silently falling back to English when called with a one-shot `IEnumerable<string>` for `preferredLanguageIds`; the sequence is now materialized before use. (#139)

Removed:
- [L10NSharp] Removed EnableClickingOnControlToBringUpLocalizationDialog. Since the localization dialog was jettisoned, this is meaningless (and wouldn't belong in the Winforms agnostic namespace anyway).
- [L10NSharp] Removed EmailForSubmissions. Since the localization dialog was jettisoned, it no longer makes sense to store this information on the localization manager.
- [L10NSharp.Windows.Forms] Removed LmGrid, LmButtonColumn, LmButtonCell, TipDialog.
- [L10NSharp.Windows.Forms] Removed the version of LocalizationManagerWinforms.Create that did not take an icon. The mere absence of a usable icon does not preclude the possibility of displaying the dialog for the user to choose a fallback language. Callers that do not wish to provide an icon can safely pass null for that parameter.
- [L10NSharp] Removed ITranslator, TranslatorBase, GoogleTranslator, and BingTranslator

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