Robin
Oh, sorry! For sure, this asks for a fix. Shit happens. 🙂 Many thanks for catching and reporting the issue @PPC ! And not to forget: great to read you again.
There is a test package version already available you can check out your translation result against Just make sure to have antiX 26RC1 updated from apt with at least:
$ sudo apt-get update
$ sudo apt-get install desktop-menu-antix antiX26-desktop-filesThen install the control-centre package from the link above,
and finally fetch the pt_PT translation .po file “for use” from transifex, run msgfmt on it and put the resulting .mo file renamed to antixcc.mo into /usr/share/locale/pt/LC_MESSAGES.
If its GUI won’t come up in translation, but when running with LANG=C, there must be some forbidden character in your translation. Check the console output for the line number, and then call the script again, this time using the -d (not d) command line option to check what the decried line reads, so you can easily look it up at transifex then, using their powerful filter search, and fix it. Also don’t forget to check the translation result of the -h command line option. You may adjust the columns for the latter by adding or removing blanks to or from the strings 318 to 331.
Currently I’m reworking still some details in the integrated installer routine, and also streamlining and improving the use of its controlling lockfiles. The whole mechanism is way to overengineered, because it still stems from the handling of running the installer within parallel windows. All this is no longer needed now, and moreover it turned out on really slow machines it might conjure false error message windows pop open out of thin air now while still in the process of installing. I guess there will be a next version up at my git by this evening already, if everything works out like expected. Most important: Translatable strings won’t change from this, its just rummaging in the underlying machinery.
Windows is like a submarine. Open a window and serious problems will start.