Skip to content

3.16 - New AI Rule Studio tool and One Project mode

Latest

Choose a tag to compare

@rmlockwood rmlockwood released this 25 Aug 12:43
· 50 commits to master since this release
bd8381e

What's Changed

  • New AI Rule Studio tool — describe a transfer rule in your own words and let an AI provider write it
    • Creates a new rule or modifies an existing one, and works on macros as well as rules
    • Explain mode describes what an existing rule or macro does, in plain prose
    • Grounded in your own project: the real categories, features and affixes come from FLEx, and sample rules from your transfer file are sent along
    • Every generated rule is validated and shown to you in a preview before it's written to the rules file
    • Sample data can be included to help the AI create good rules.
    • Your description and the AI's explanation can be in any language, not just the interface language
    • Choose your provider and model in the Settings tool — Gemini, Anthropic or OpenAI supported initially
    • Nothing is sent anywhere until you consent. Your API key is kept in the Windows credential store, and you can choose whether project names are included in the prompt
    • A history of the modifications the AI made is kept
  • The Rule Assistant has been rewritten in Python and replaces the old Java version
    • A splitter between the rule information and the test data lets you give each pane the room it needs
    • It's now a normal FLExTrans window: it opens directly, shows the FLExTrans icon, and remembers its size and its splitter positions between sessions
    • The Help button jumps straight to the Rule Assistant section of the documentation
    • Many fixes to the feature editor, the disjoint feature split, the affix context menu, category editing and new-rule defaults
    • Support for a "many" noun class in Bantu noun class processing
    • The Rule Assistant no longer has to be installed via its own sub-installer
  • One project mode — you can now run FLExTrans with a single FieldWorks project that holds both languages in two writing systems, instead of separate source and target projects
    • Set the source and target writing systems in the Settings tool
    • Works through the drafting modules, including HermitCrab synthesis
    • Modules that don't apply in this mode are prevented from running
  • Text In and Text Out rules
    • New case modifiers in search and replace: \l and \u change the case of the next character, \L...\E and \U...\E change a whole stretch
    • Clearer messages when a rule fails, and shorter paths in the reports
  • You can define your own lowercase/uppercase pairs for special letters, so capitalization works for all kinds of non-ASCII characters
  • The Apertium tools now include the official fix for a lowercasing problem
  • Text Out rules are applied automatically in the End Testbed module if a setting is on
  • Live Rule Tester improvements
    • Splitter controls, with the sizes remembered
    • Refreshing the source lexicon fixed
    • Comments you write on a test are saved in the testbed file and shown in the log viewer
  • Localization
    • All French and about half of Spanish translations reviewed and approved
    • Adding a new interface language is now driven from one authoritative language list
  • The id line is now imported and exported in Import Text From Paratext and Export modules
  • Documentation updates, including the Rule Assistant documentation now folded into the FLExTrans user documentation
  • Bug fixes

Full Changelog: v3.15...v3.16