v0.126.0

Added

• new-object --periodicity creates a periodic constants set. It takes Day, Month,
  Quarter or Year, in either language. Such a set has a list beside its record, so
  --presentation writes the list caption and --record-presentation the record one, and the
  new set passes naming/presentation. MCP meta_new_object and the language server call it
  periodicity. (#166)

Changed

• naming/presentation expects (not used) from an English project. A deprecated element
  starts its presentation and captions with that mark, and the rule does not count the mark of
  the other language. translate adds (not used) itself when a dictionary entry leaves it out. (#169)
• The localization tools know every language of the platform. localization-info and
  add-localization, with their MCP and language server twins, take the languages from the data
  together with the compatibility mode each one needs, so Chinese, Vietnamese and Tajik join
  Russian and English. A value of LocalizationLanguages the data does not know is named in the
  notes. (#169)
• yaml/duplicate-subtree no longer compares the translations of one localized-strings
  dictionary. Two languages of one dictionary repeat each other key for key. (#169)
• translate swaps the base only with the translation into the target language. Its folder
  is found in any letter case, and a translation into another language keeps its place on purpose. (#169)
• naming/presentation now asks a processing for its caption. A processing keeps it in
  Interface.Presentation: the form and the command that opens it are named by it, and without it
  both carry the element name. The standard lists processings among the elements whose
  presentation is mandatory, and new-object --presentation writes the caption right there. (#167)
• data-diff no longer says "no changes" where the data changed. It now compares the whole
  stdlib catalog, module handlers and signatures included, as well as uiterms.json,
  terms_full.json and the text of the help pages. The text report keeps to a count and the first
  names; --limit 0 lists them all. (#168)

Fixed

• xbsl extract reads the languages of a project. The data gains the language table and the
  English names of the newer languages, so translate --strict no longer reports a platform gap
  on a descriptor that lists one of them. (#169)
• The cards of the help no longer run together. The links of a card grid used to merge into one
  line, and an example lost the icon that told a right one from a wrong one. The help now lists link
  cards, labels right and wrong examples, and keeps the code fragment of a card as code. (#165)
• Servers no longer answer from data replaced under them. An MCP worker that read the term pairs
  just before a reinstall rewrote them kept answering from the old ones. Now it refuses with reason
  data and a new worker answers the call; the language server asks for a restart. (#168)
• xbsl extract no longer writes into the package. The grammar step used to cache the grammar
  files next to the package code whatever --data-dir said; now it reads them from the
  distribution in memory, and an installed package stays as it was. (#168)
• The help of --element-version names the real default. It said "the latest in the
  bundle", while the version comes from XBSL_ELEMENT_VERSION or, without it, from the default
  of index.json in the data root. (#168)
• The translator spells the standard attributes of an exchange plan in ComputePermissionsBy.
  The number of the sent message and this node stayed Russian in the list, so the English exchange
  plan named fields its object does not have. Now the kind spells them: SentNumber, ThisNode. (#168)
• xbsl extract no longer pairs a name of an element model with its neighbour. Such a class
  writes the Russian name first, and this node of an exchange plan read as ReceivedNumber; a dozen
  words of the compiler dictionary were wrong as well, and the name of a Java constant passed for
  the English of the word it holds. Run xbsl extract --dist ... --only terms. (#168)
• A second translation of the same file no longer leaves the schedule kind Russian. The
  translator wrote the English kind back into the parsed file kept with the source, so the next
  pass in the same process found nothing to change. It now leaves the parsed file as it was. (#168)
• The translator names a declared standard attribute the way its kind does. An exchange
  plan that declared the number of the sent message kept it Russian and asked the project for
  an entry, while its own list already said SentNumber. An entry of the project still wins. (#168)

What's Changed

• Batch 44: (not used) for English projects, languages of the project, disputed property by @keyfire in #169

Full Changelog: v0.125.0...v0.126.0