Interpreter.app 1.0.1 #3
abra-code
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Requires macOS 14.6 or later, Apple Silicon. All translation still runs entirely on this Mac.
Fixed
Translated documents are named after their language. Document mode used to write every result to
<name>-translated.txt, so translating one document into a second language silently overwrote the first. The output is now named for the language it is in -report.txtbecomesreport-pl.txt,report-es.txt- derived from the To picker and re-derived whenever it changes. Translating one document into several languages now leaves several files you can tell apart.Re-translating replaces its own output instead of piling up copies. Each window remembers the file it uses for a given language, so switching To away and back returns to the same destination: a second run into Polish overwrites
report-pl.txtrather than creatingreport-pl-1.txt. A first translation into a language still steps around any file you already had, so nothing of yours is clobbered. A destination picked through Save As is remembered the same way, under the language it was picked for.The translation preview shows the new translation. The right-hand QuickLook pane could keep displaying the previous result after a re-translation, because the preview ignores a file path it already holds - and an overwritten file has the same path. The pane is now cleared before the new path is set, which makes the reload actually happen.
Changing the target language mid-translation no longer moves the file being written. The destination is settled and captured when Translate is pressed, so a To change made while a translation is in flight sets the default name for the next run without retargeting the write already under way. The preview is deliberately left alone at dispatch, so the translation being replaced stays on screen while its replacement is made instead of blinking out, and Reveal is disabled only after the destination settles - if settling fails, Reveal still points at the previous, still-valid output. On completion, the Output field and the preview report the file that was actually written.
The preview and Reveal follow the destination. Switching To to a language you have already translated into brings that file back into the preview and re-enables Reveal; switching to a fresh language clears the pane instead of leaving the previous language's translation on screen. This also applies when a model change forces the language list to fall back to a different To language.
This discussion was created from the release Interpreter.app 1.0.1.
All reactions