L10NSharp.CheckOrFixXliff
8.0.0-beta0004
See the version list below for details.
dotnet add package L10NSharp.CheckOrFixXliff --version 8.0.0-beta0004
NuGet\Install-Package L10NSharp.CheckOrFixXliff -Version 8.0.0-beta0004
<PackageReference Include="L10NSharp.CheckOrFixXliff" Version="8.0.0-beta0004" />
paket add L10NSharp.CheckOrFixXliff --version 8.0.0-beta0004
#r "nuget: L10NSharp.CheckOrFixXliff, 8.0.0-beta0004"
// Install L10NSharp.CheckOrFixXliff as a Cake Addin #addin nuget:?package=L10NSharp.CheckOrFixXliff&version=8.0.0-beta0004&prerelease // Install L10NSharp.CheckOrFixXliff as a Cake Tool #tool nuget:?package=L10NSharp.CheckOrFixXliff&version=8.0.0-beta0004&prerelease
Validate and fix XLIFF files.
Learn more about Target Frameworks and .NET Standard.
-
.NETFramework 4.6.1
- L10NSharp (>= 8.0.0-beta0004)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
8.0.0-beta0005 | 95 | 6/4/2024 |
8.0.0-beta0004 | 94 | 5/10/2024 |
8.0.0-beta0003 | 95 | 4/19/2024 |
7.0.1-beta0001 | 137 | 4/15/2024 |
7.0.0 | 333 | 11/6/2023 |
7.0.0-beta0013 | 168 | 11/3/2023 |
7.0.0-beta0011 | 187 | 3/17/2023 |
7.0.0-beta0010 | 166 | 3/13/2023 |
6.1.0-beta0009 | 117 | 3/13/2023 |
6.1.0-beta0008 | 173 | 12/9/2022 |
6.1.0-beta0007 | 163 | 12/9/2022 |
6.0.1-beta0002 | 165 | 11/23/2022 |
6.0.0 | 305 | 11/23/2022 |
6.0.0-beta0018 | 217 | 11/21/2022 |
6.0.0-beta0017 | 198 | 10/7/2022 |
6.0.0-beta0015 | 248 | 8/24/2022 |
6.0.0-beta0013 | 225 | 8/24/2022 |
6.0.0-beta0003 | 248 | 7/12/2022 |
5.0.0 | 431 | 7/8/2022 |
5.0.0-beta0098 | 213 | 7/8/2022 |
5.0.0-beta0097 | 239 | 7/8/2022 |
5.0.0-beta0094 | 250 | 6/2/2022 |
5.0.0-beta0092 | 247 | 5/31/2022 |
5.0.0-beta0090 | 218 | 5/19/2022 |
5.0.0-beta0088 | 240 | 5/17/2022 |
5.0.0-beta0086 | 218 | 4/12/2022 |
5.0.0-beta0082 | 240 | 4/11/2022 |
5.0.0-beta0080 | 246 | 3/9/2022 |
5.0.0-beta0059 | 259 | 2/4/2022 |
5.0.0-beta.77 | 119 | 2/21/2022 |
5.0.0-beta.75 | 130 | 2/4/2022 |
4.2.0-beta0006 | 219 | 8/20/2021 |
4.2.0-beta0004 | 188 | 5/14/2021 |
4.1.1-beta0002 | 223 | 4/14/2021 |
4.1.0 | 420 | 3/4/2021 |
4.1.0-beta0051 | 271 | 3/4/2021 |
4.1.0-beta0050 | 245 | 1/28/2021 |
4.1.0-beta0049 | 245 | 1/26/2021 |
4.1.0-beta0047 | 317 | 7/6/2020 |
4.1.0-beta0045 | 359 | 6/8/2020 |
4.1.0-beta0043 | 361 | 6/8/2020 |
4.1.0-beta0039 | 345 | 6/5/2020 |
4.1.0-beta0036 | 341 | 5/28/2020 |
4.1.0-beta0032 | 371 | 5/27/2020 |
4.1.0-beta0027 | 387 | 4/7/2020 |
4.1.0-beta0026 | 371 | 4/2/2020 |
Changes since version 7.0.0
Changed:
- BREAKING CHANGE: If no `LocalizationManager`s have been created, but the client asks for a string to be localized, an `InvalidOperationException` is thrown. This is to prevent an invalid state where language IDs get mapped incorrectly at the beginning and then never get updated which can cause us to fail to return properly localized strings when requested (see BL-13245). This is a breaking change because it may cause existing code to throw an exception. The fix is to ensure that a LocalizationManager is created before calling any localization methods. Or, to maintain existing behavior, set `LocalizationManager.StrictInitializationMode` to false.
See full changelog at https://github.com/sillsdev/l10nsharp/blob/master/CHANGELOG.md