Audex 27.04 - Upcoming major update and early translation availability

[Marco]

Hi,


> Any particular reason for it to not be translated?

No, it was just a design decision.

The CLI is primarly intended for scripting, automation and diagnostic rather 
than normal users. I thought keeping the output in english - independent from 
the environment - would make logs and messages more consistent. But that is 
not set in stone.

On the other side I see a human-readable CLI output can benefit from 
translations as well. I'm open to reconsidering this if there's a good reason 
to follow a different approach. Maybe there are any established KDE conventions 
to also translate the CLI.


Regards,

Marco



On Samstag, 7. November 2026 12:32:38 Mitteleuropäische Normalzeit Albert 
Astals Cid wrote:
> El dissabte, 7 de novembre del 2026, a les 10:08:52 (Hora estàndard d’Europa
> central), Marco va escriure:
> > > That does not work at the moment since your Messages.sh is not
> > > extracting
> > > any of the tr() strings
> > 
> > Oh, I see, thank you for the catch...
> > 
> > So, I do need to extract:
> > 
> > 1. tr() strings
> > 2. QCoreApplication::translate() incl. Qt disambiguation contexts
> > 
> > and fix the Messages.sh accordingly.
> 
> Yes, we already have a way to do that, please see the documentation or ask
> if you need help.
> 
> > Furthermore I'll create a regression
> > test to verify that the strings actually appear in the generated POT file.
> > 
> > One more word to the new CLI of Audex: The CLI is intentionally
> > english-only. It does not load translation catalogs and always uses the
> > original english messages provided by the engine.
> > To make that sure, I think something line "! -path './cli/*'`" should be
> > part of the message extraction in Message.sh.
> 
> Any particular reason for it to not be translated?
> 
> Cheers,
>   Albert
> 
> > Reagrds,
> > 
> > Marco