Files.co PDF Suite 1.5.1: fourteen languages, on Mac and on Windows

Version 1.5.1 of Files.co PDF Suite is approved on both stores: Apple published it on 28 August, the same day we submitted it, and Microsoft finished certification the day after. It is a maintenance release with no new tools, which is exactly why it is worth writing about — what it fixes is the kind of thing that never makes it into a feature list.

The headline is that the Mac app now speaks the same fourteen languages as the Windows one. Polish, Turkish, Russian, Japanese, Korean, Chinese and Arabic join the seven it already had. Same tools on both platforms, and from now on the same languages.

It was not a copy and paste

The plan was to take the Windows catalogue and carry it over. Then we opened it and found that seven of its languages were missing 219 keys between them, nearly all of them belonging to the tools that arrived with 1.5.0. The app had been showing those strings in English to anyone using it in Polish or Turkish, and nobody had told us.

So the job turned into 3,633 strings translated from scratch and then reviewed one by one. The review found around 350 mistakes, and the interesting part is what kind:

• .NET placeholders in strings meant for Swift. A {0} that the Windows app substitutes and the Mac app prints verbatim, so a file name would have shown up as a literal {0} in the middle of a sentence.
• Keys paired with a string that says something else. The translation was fine; it was simply attached to the wrong message.
• Text naming the wrong platform. Our favourite: a string that told Mac users, in seven languages, about a certificate installed on Windows.

None of those break the build. They just quietly make the app look like it was assembled by someone who does not speak your language, which it was, until it got reviewed.

Arabic reads right to left, and now so does the window

Arabic was the one that needed real work. Switching language while the app is running changed the words but not the layout, so Arabic came out written correctly inside a mirror-image window: text flowing one way, toolbars and panels the other.

Mirroring the interface is not the same as translating it. The Unicode Bidirectional Algorithm handles the text itself, but the window around it — where the sidebar sits, which way a progress bar fills, which corner the buttons live in — is the application’s job, and it has to happen the moment you pick the language, not on the next launch. It does now.

Two settings that were saved and then ignored

This one had been there since before 1.5.0, on both platforms. In Settings you can choose an output folder and ask the app to open the result when it finishes. Both were saved correctly, and then every tool ignored them and asked “Save as…” as though the setting did not exist.

Each app now has a single point of exit that every tool goes through, including the ones that produce several files at once. “Save as…” still asks every single time, because that is the one place where you did ask to choose.

And because the bug got in by being copied from one tool to the next, each platform now has a build guard that fails the build if a new tool opens its own save dialog. The next tool cloned from an old one cannot inherit this in silence.

What changed on each platform

	macOS	Windows
Approved	28 August 2026	29 August 2026
Interface languages	7 → 14	14, unchanged
Arabic with right-to-left layout	New	New
Output folder and “open when finished”	Fixed	Fixed
Build guard against per-tool save dialogs	New	New

Everything else is where you left it

The tools are the same ones, all free, and they still run entirely on your machine: no uploads, no account, no telemetry on your documents. Pro is still a one-time purchase, and anyone who bought it already has this update without paying again.

Get it on the Mac App Store or the Microsoft Store, read the technical detail in the release history, or take a look at the app overview. If you would rather not install anything, the browser tools are still there, with nothing uploaded.