Anonymous
For the persistence+remaster scripts, the gitlab repository contains only .mo files (no .po files). I found no .pot file, so cannot easily check whether the same string is given for “setup” and for “configure”.
http://gitlab.com/antiX-Linux/remaster/-/tree/master/locale/es/LC_MESSAGES
In the context of the program(s), these 2 terms are vague even in English.
setup:
create; establish;
user decides, and and specifies, several parameters
(home-only persist vs home+root)
(dynamic vs static)
(size of persistence savefile)
(operation “mode”: manual vs semi-automatic vs automatic save)
configure:
user may elect to change various previously-speficied parameter values.
For instance, increase the size of the savefile container
or choose a different “operation mode”
___________________________
Even “mode”, in this context, is vague in the English usage.
Mode is the term I have been using, across years, but within the program no formal term (“mode” or otherwise) is given.
$(gt "Configure root persistence saves to run either:")
1) $_Automatic_[/] ($(gt "at shutdown/reboot, no asking"))
2) $_Semi_Automatic_[/] ($(gt "ask at shutdown/reboot"))
3) $_Manual_[/] ($(gt "you snooze, you lose"))"Configure-Persistence-french-ellipse.jpg
No, I do not see the same as shown in that screenshot.
Instead, I find this:
I can’t guess how, or why, multiple//redundant menu entries are displayed.
instead of guessing, tracked down the likely cause of the redundant menu entry labels
~~ cited in my followup ppost
Did the reporter browse or grep /usr/share/applications/ (and /usr/share/applications/antix/) to determine whether or not multiple .desktop files containing identical icons (and text string on Name= line) are present?
.
If multiples are present, the following will enlighten us as to which packages provided (installed) the files:
dpkg -L /usr/share/applications/TWIN_1.desktop
dpkg -L /usr/share/applications/TWIN_2.desktop
^— If no matching package is found for a file, that would indicate:
1) either the file was pre-installed (was injected during the pre-release “build-iso” process)
2) you, or your cat, or your grandma… someone using your local machine accidentally created the file
re “browse or grep”:
? Did the reporter also ruleout presence of user-created .desktop files, pathed under ~/.local/
Perhaps, on the reporter’s affected machine, the “Add Menu Item” hickeydoodle was used and TWIN_1.desktop was edited, filename (but not icon and text string on Name= line) was changed, and was savedAs TWIN_2.desktop
^——- This is a potential cause of the reporter’s redundant menu entries
I didn’t reread today all the posts here. Possibly the reporter’s machine was originally antiX 17… and was upgraded to 19… and, along the way, a different name was applied to a .desktop file in the “packageX” (which, in antiX19 release, may also have changed)(the packagename of the package associated with installing one of the twin sibling .desktop files)?
chasingmytailchasingmytailchasing