Releases: sillsdev/FieldWorks
Releases · sillsdev/FieldWorks
FieldWorks Base Build #1398
Remove ScrChecks project and replace with streamlined parser (#764) * Delete entire Lib/src/ScrChecks/ project and tests * Remove unused interfaces: IChecksDataSource, IScriptureCheck, RecordErrorEventArgs * Remove ScrChecks from solution, build targets, installer targets * Replace with ParseCharacterSequences in TextFileDataSource using StringInfo.GetTextElementEnumerator for correct Unicode handling * Update CharContextCtrl and ValidCharactersDlg to remove reflection-based loading of ScrChecks * Remove FwDirectoryFinder ScrChecks directory helper * Add comprehensive tests for diacritics, surrogate pairs, supplementary plane chars, and minority language scripts The ScrChecks project under Lib/src was over-engineered for the limited functionality actually used by FieldWorks. Only character sequence parsing (grouping base characters with combining diacritics) was needed. Currently all the artifacts from projects under Lib\src are committed in DistFiles - leave that for future evaluation Co-Authored with Claude
FieldWorks Base Build #1392
Partially revert "LT-22446: Polish Installer Builds (#744)" build.ps1 -RunTests and test.ps1 both fail; revert to the old way of running tests for now to get builds working. This partially reverts commit cb276a1991c09f74cd8a2e5a7fc58c1ed0665714.
FieldWorks Base Build #1387
Revert change to CustomComponents.wxi and pass logging variables to installer builds
FieldWorks Base Build #1379
Better Style Import and Export (a step toward LT-20393) (#613) * Export each Style's Function (@use) (needed to match on import) * Fix style export for undefined structure: The Style import expects a missing `structure` attribute for StructureValues.Undefined. The initial fix to LT-20393 caused a regression with the same steps as LT-20895. Fix the style export update so that the legacy style import continues to work. Also: * Modernize the import * Update a message about the installation CD * Fix incorrect exception messages regarding the import * Remove some TE-specific code * Fix the comment on EnsureCompatibleFactoryStyle * Test Style Serialization * Update comments and messages; remove dead code
FieldWorks Base Build #1351
build-1351 Bump version to 9.3.5 Beta (#590)
FieldWorks Base Build #1188
Fix problem with LT-22261 fix reported by Daney (#499) * Fix problem with LT-22261 fix reported by Daney * Added unit tests requested by Jason * Clean up code to detect guesses
FieldWorks Base Build #1186
LT-22306: Fix Startup Crash on Clean Machine Prompt the user for update preferences after initializing the l10n manager. The l10n manager must be initialized before looking up strings to prevent language IDs from being mapped incorrectly (see https://issues.bloomlibrary.org/youtrack/issue/BL-13245). The prompt remains as early in startup as possible so that the user can choose before any update checks are initiated. Change-Id: Ib2284a6022c362b5dd961ed5f330a8ed63b540e1
FieldWorks Base Build #1185
LT-22306: Fix Startup Crash on Clean Machine Prompt the user for update preferences after initializing the l10n manager. The l10n manager must be initialized before looking up strings to prevent language IDs from being mapped incorrectly (see https://issues.bloomlibrary.org/youtrack/issue/BL-13245). The prompt remains as early in startup as possible so that the user can choose before any update checks are initiated. Change-Id: Ib2284a6022c362b5dd961ed5f330a8ed63b540e1
FieldWorks Base Build #1184
Fix LT-22109: Handle embeddings in flextext (#502) * Fix LT-22109: export embeddings * Add code to import items with runs
FieldWorks Base Build #1182
LT-3646: Unchecked checkboxes count as "no data" When determining field visibility, treat unchecked checkboxes as if they have "no data". Note: This change applies to all checkboxes stored as a Boolean, and one checkbox that is stored as an integer. To apply the new behavior to a checkbox stored as an integer, and avoid changing the behavior of all integer fields, we specifically identify the integer field. There is a possibility that we missed other checkbox fields that are stored as an integer.