Sally v1.0.24

Fixes

Icon overlays now appear (#90)

TortoiseSVN, TortoiseGit and any other provider that supplies its overlay icon as a .ico
file were being discarded at startup, so their overlays never showed in the panel.

Sally asked Windows for two icons in a single call with both sizes packed into one
argument. That form asks for two consecutive icon resources rather than one icon at two
sizes — and a standalone .ico holds exactly one, so the second size came back empty. An
overlay is only used when every size loads, so the handler was thrown away.

A note if you compare against Explorer: Windows stops loading overlay handlers once
roughly fifteen are registered. On a machine with several cloud-storage clients installed,
Explorer may show no Tortoise overlays in the very folder where Sally now does. That is a
Windows limit, not a difference in the repository state.

Context menus on non-ASCII filenames (#79)

Right-clicking a file whose name contains characters outside your system's ANSI code page
produced no menu at all — and no error explaining why.

Menu entries are now built from the full Unicode filename, the containing folder is
resolved without narrowing its path, and a name that cannot be resolved is skipped instead
of discarding the whole selection. If nothing in the selection can be resolved, you now get
an explanation rather than silence.

Scope: this covers non-ASCII filenames. Files inside a folder whose own path
contains such characters are a separate, known limitation — see Known issues below.

Opening files inside folders with non-ASCII paths

Pressing Enter did nothing for files inside a folder whose path contains characters outside
the ANSI code page — including files with perfectly ordinary ASCII names, because the code
path was chosen from the filename alone.

Diagnostics

Help → Report a Bug

Writes a report describing configuration and shell integration state: what happened to each
registered icon overlay handler, and the outcome of recent context menu commands.

The existing Help → Task List → Break route needed two running instances and terminated the
process. This one needs neither. The report is written to
%LOCALAPPDATA%\Open Salamander\ and its location is shown when it completes.

If you hit a shell integration problem, this report is far more useful than a description —
it records what Sally handed Windows and what came back.

Localization

All ten shipped languages are now complete. Strings introduced by earlier releases were
still displayed in English in every locale:

• the Light / Dark / System theme names
• the Find results save and load commands
• the Paste Shortcut failure message
• the Windows Terminal and default shell integration

Other

• Development builds report the correct version again. It had been pinned by cached build
  configuration, so binaries carried the previous release's number.
• AUTHORS now credits the people who report problems, test pre-release builds and confirm
  fixes.

Known issues

Actions on files inside folders whose path contains characters outside the system ANSI
code page remain unreliable — Properties, Copy Full Name, Paste, packing and others. The
folder browses and displays correctly; only the actions fail. This is tracked separately
and is being worked through.

Filenames outside the ANSI code page are fine as long as the containing path is
representable.