Search Results for 'boot from iso'

[Member Xecure]

I think this is related to you using the syslinux/isolinux boot menus to select a different timezone (or selecting a language, which will automatically also change the timezone).
On my UEFI system, I select the timezone once, and then remove the timezone bootcode from my live system grub.conf file. I suspect that using the syslinux/isolinux boot menus to select a timezone/language and saving the options will lead to the live system to reset the repo each time you boot (except if using the norepo or disable=r boot parameter).

If I am mistaken, please ignore my reply.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Anonymous]

halfway down the wiki page

Figure: LiveMedium boot screen of x64 ISO

Whatever was supposed to be there (an image?) is missing.

[Member mikey777]

Thanks skidoo. The problem presents itself before ‘apt update’ and ‘apt-upgrade’ stage.

Let me explain: after booting laptop to the antixcore isofile on USB drive, I follow prompts and enter username & password as ‘root’,
then enter the text ‘cli-installer’…
1st question: what partition do you want to install ‘/’ on – answer = sda1.
2nd question: next line asks, if I remember correctly, if OK to destroy any pre-existing data on sda1 – answer = yes.
3rd question: do you want to install a separate /home partition – answer = yes, and specify sdb1.

Then get told that this location is invalid, even though it has already been listed as part of the partition structure, following booting to USB isofile.
Same response if I attempt to install /home to sda2.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member ModdIt]

HiGeoffC,
Different persons different ways,
Just make your important changes. After setup of apt sources update your system, install any software
you want, customise desktop confirm things work then do a live remaster. Select Personal unless you want to give
an image to others. That will preserve most of your changes. You can change excluded files list before remastering
if wished for.
You still have an opportunity to rollback to previous state if needed as well as fastest boot time.
Persistence can be slow if files are large.

Clone your remastered stick to a second one or create an ISO file on a non volatile medium, means DVD or an
external HDD, SDD.. If you have a backup you can be up and running in a few minutes if anything untoward happens.

As also recommended by skidoo, saving important work to a separate stick or other device is a very good idea.

[Anonymous]

After following some topics on this forum, I understood the importance of separating into different partitions, one partition for the operating system and another for storing user data and settings. At installation the system – “root” is on the sda1 partition and “home” is on the sda2 partition of the hard drive.

Well… somehow, I do not share that “understanding”.
Compared to “separate partitions”, placing $HOME on a separate physical device seems like a more effective way to mitigate risk.

What can we do in antiX when wrong shutdowns occur due to a power outage and the operating system no longer starts in graphical mode?

Is this “the wrong question” to ask?
Probably a better approach would be to ask/investigate How might we preclude future similar problems?

my recommended solution, toward avoiding “power outage and the operating system no longer starts…”
is
liveboot, dynamic root persistence, semi-automatic save
plus, if feasible (and here, my attention is toward storms/lightning)
choose the “toram” liveboot option ~~ detaching the liveUSB device until/unless a persist-save operation is warranted.

^—- plus one more detail (explicit “data=journal” ext4 mount option, but this merits a separate explanatory post)

______________________________________

(using self as an example)
-=-
According to debugfs (and my conky on this machine), here are a couple of stats/details:
1) latest remaster (rootfs was “born on”): 5 Sept 2020
2) To date, since 5 Sept 2020, a cumulative total of (only!) 463MB has been written to the rootfs.
3) trivia: the content of that roofts file presents as (only!) 16 fragments

The bulk of those writes are attributable to system updates (package upgrades)…
yet (however) I am not utilizing a separate “$HOME”.
Frequent iso snapshots, offloaded to LANserver for safekeeping, cover the task of “full system backup” and re-attaching (or reconnecting to, via LAN) external data volumes… this has enabled me to boot from whichever machine I choose and/or workaround any equipment downtime.

six vs half-dozen?
For others, using a separate $HOME may provide a fine experience.
I’m not knocking it, just explaining a “works well for me” alternative.

[Anonymous]

if it is not secure, as mentioned by skidoo

Please recheck ~~ that brief post of mine regarding briar-gtk did not mention security.

or is only the “Briar-GTK” is affected?

As I recall, the java dependency is specific to only briar-gtk.

So what exactly is the problem with that java

In this context…

>>> Do you even realize that briar-gtk necessitates installation of a Java (JRE) component?
>>> To date, nothing else pre-installed in antiX uses Java, right?

the problem my concern is identical to
how I might (did?) react to the suggestion of pre-installing LibreWolf
or how I would react to the suggestion/request to update “yad” to a later version
-=-
Both of these depend on gtkwebkit (scusa if I grabbed the wrong pkg name offhand)
and to date nothing pre-installed in antiX depends on that
and its addition would add a huge chunk to the ISO
(or, more specifically, from the POV of a “toram” liveboot user… the rootfs)

—————————

For the record, there are several Java -based programs that I admire, and recommend
(but would NOT recommend for use on antiX).

• FAR (aka “find and replace”, available from sf.net)
• java version of SearchMonkey (for windoze users, available from sf.net)
• a great RegularExpressions tester GUI app, its name escapes me at the moment
• jedit (kickass text editor, inspiration for coding “BirdsEyeView” feature into my bespoke programs)
• freeplane (cross-platform, GUI mindmapper program)

lookit:

$ sudo apt install freeplane
The following NEW packages will be installed:
ant antlr ca-certificates-java default-jre default-jre-headless freeplane groovy ivy java-common java-wrappers javahelp2
jmapviewer junit4 libantlr-java libapache-pom-java libasm-java libavalon-framework-java libbatik-java libbsf-java
libcommons-cli-java libcommons-codec-java libcommons-io-java libcommons-lang-java libcommons-logging-java
libcommons-parent-java libel-api-java libfontbox2-java libfop-java libhamcrest-java libhawtjni-runtime-java libidw-java
libjansi-java libjansi-native-java libjaxp1.3-java libjgoodies-common-java libjgoodies-forms-java libjlatexmath-java
libjline2-java libjsp-api-java libjsyntaxpane-java libknopflerfish-osgi-framework-java libmnemonicsetter-java libqdox-java
librhino-java libservlet-api-java libservlet3.1-java libsvgsalamander-java libwebsocket-api-java libxalan2-java
libxerces2-java libxml-commons-external-java libxml-commons-resolver1.1-java libxmlgraphics-commons-java libxpp3-java
libxstream-java openjdk-11-jre openjdk-11-jre-headless simplyhtml
0 upgraded, 58 newly installed, 0 to remove and 67 not upgraded.
Need to get 94.3 MB of archives.
After this operation, 269 MB of additional disk space will be used.
Do you want to continue? [Y/n]

[Member calciumsodium]

However, the live USB, created with the antiX-bullseye-a2-runit_x64-full.iso file successfuly created by the live USB maker, boots up well on an HP 6550b system with an i3 processor with 4 GB of ram.

Some initial questions/findings:
1. Under Control Centre > Drivers, there is no Windows Wireless Drivers program anymore. I actually use this in my antiX 19.X systems for some of the older wireless hardware. Any chance that this program can be included?
2. For Themes, when I change from the Clearview Blue Medium theme to the Default, I no longer see the Minimize, Maximize, Close icons on the top right of the windows. I only see blank boxes.

[Member calciumsodium]

1. Both the antiX-bullseye-a2-runit_x64-full and the antiX-bullseye-a2-runit_x64-full-legacy kernel do not boot up in my HP 6730b system with an intel core 2 duo processor (2.4 GHz) with 2 GB ram.

2. Both the antiX-bullseye-a2-runit_x64-full and the antiX-bullseye-a2-runit_x64-full-legacy kernel do not boot up in my HP 6730b system with a Centrino processor (2.4 GHz) with 4 GB ram.

For both systems, booting leads only to a blank screen freeze.

This is surprising, since both these systems work really well with antiX 19.X.
These tests were done using a live USB created with the antiX-bullseye-a2-runit_x64-full.iso file successfuly created by the live USB maker.

[Member namida12]

ModdIt wrote:

What will end up in the next version of antiX is a matter for devs, ISO size aims mean some pretty tough selection.
MX is mid weight and includes some tools some users may find more comfortable, after more than a year on antix with icewm
majority of other distros feel slow and distracting. :-).

For your current problem:
Do you have sudo apt-get install exfat-utils exfat-fuse installed.
You can then set media to automount in the controll center. Should that not work for some reason we will need to figure out
why.

Seems gparted is not working correctly for xfat, as a fallback you can use it to correctly identify your device then
format with sudo mkfs.exfat -n /dev/sdb1 Substitute sdb1 with your device !!!.
Or format in the camera, i have several non go pro devices which demand internal format.
gnome-disk-utility is reputed to work with xfat.

Moddit,

I understand the future antiX software choices is a matter for devs. I am trying to request a few things I need, and would like to see added to the forthcoming newer Antix. If I didn’t suggest then developers may not remember my software requests.

I had exfat-utils exfat-fuse installed in the previous antix 19.3 install on this hardware that does not like the 5.10 kernel in Antix. That did not work well as I have many different Micro cards, and large flash drives with exfat. The problem using (sudo mkfs.exfat -n /dev/sdb1) is the device always disappears immediately after formatting.

For the moment booting the hardware with a live media MX thumb drive is much simpler to format a flash drive or move my videos about on exfat devices than to use antix. Then I can copy them to the antix home. Then I reboot into antix 19.3. I have moved things about in my work space and set up another desktop system adjacent to this hardware, with MX installed. But I have experienced many problems trying to transfer some videos from the MX system from exfat devices, on fat32 thumb drives (size limit). This is the Reason I am using MX live media to store files on Antix.

I Have just started using the Xmas gifted GoPro on my bicycle, and posting to youtube. I haven’t really started editing yet, will use Blender, kdenlive, and DaVinci Resolve software in Antix, before uploading to Youtube in the future.

I had not done much since Xmas, when I got my GoPro because I was doing an eye procedure to fix my poor eye sight in both eyes. I can see again, and everything is amazingly bright and vivid colours. It is nice to see again, and ride my bicycle when I am away from the computer’s 34 inch screen…

• This reply was modified 2 years, 1 month ago by namida12. Reason: Gramer

[Anonymous]

FYI, I tested “personal snapshot” ( iso-snapshot-antix v0.4.3 ) ~~ it worked fine

Prior to creating snapshot, I had removed one of the preinstalled kernels.
Later, while booted from the snapshot…
IIRC the stray pair of (stranded? unused) initrd.1 and vmlinuz..1 files were still present.
The extra 5MB or so used on the boot device is no biggie, but their lingering presence invites confusion.

[Member Robin]

Many thanks, skidoo for counterchecking the findings. I’ll give feedback to your comments as soon as possible.

Let me state for clarification:
All findings described above on this system are “as delivered” by antiX 19.3 full ISO, updated and upgraded using apt update and upgrade for all upgradable packages, with one exception: xserver-xorg-core, which is pinned to version xorg version 19 from (instead of 20 which was standard in antiX 19.3.) So some findings may not be representative for other users (who are not in need to use prorietary nvidia stuff) at all. Then this is a “live persistent all” system tentatively used until replacing hdd installl of 17.4.1 by 19.3 once it has proven to function as rock stable and doesn’t slow down system, which can always happen when switching to a next generation of an operating system.
It’s not a problem for me to fix most of the findings individually on this very notebook, but this list was meant to give an impression what a new user faces when using the standard tools antix features for all the tasks.

2)…

Anonymous wrote:

you will probably need to provide a verbose, step-by-step, “what I clicked, what I typed” walkthrough.

I’ll do that as soon as possible (need to free an USB stick before, you simply won’t never have enough of them at hand 🙂 and make some additional screenshots.

3)…
I didn’t use the command line options at all, since script complained about something missing in the arguments, couldn’d figure out what, even if ‘man’ claims you can mix the two methods. Will have to look deeper into the options of this script some day. For now I just wanted to use it to get a fresh fallback copy of the stick in case the recent kernel upgrade would fail. Could have done this using dd as well. But I decided to follow the path a new antiX user would probably take also.
from man:
or you can let a series of menus guide you
which I did. I’ll provide a step by step description what exactly I did and when and where for this also.

5)…
have to append that this happens only on actually “power down”. While on “reboot” the file system on Live USB stick seems to get unmounted properly (at least for some times now, I’ll observe this and report again). So maybe a short delay, added just before actually last power down command in this tool would fix this already? Seems the stick encounters an energy shortfall before it has a chance to get everything settled?

6)…
since I’m quite familiar with mounting and unmounting any kind of whatever using simply the standard mount command in terminal, this is not the point. This tool is meant to make this everyday routine task handy and efficient. For this it has to function correctly, then it is a nice shortcut. When working on a pc (other than programming) you usually won’t want to rummaging in the engine room just for plugging off an USB stick. So this tool has its clear right to exist. But it has to safely function under any conceivable circumstances. And you probably wouldn’t expect you’d need to chase for each popup window of a tool in another place on your screen. For sure, I absolutely agree people need to learn to do things manually, but given that somebody does know this already, he can use a tool for everyday usage. Most people prefer to use a pocket calculator instead of dividing four or five digit numbers with a pencil on a sheet of paper, even if they need to know how this works manually, before they start using this handy tool.

Since “unplugdrive” tool is a bash script I’ve looked into before already, I’ll take care of this myself and present the resulting modifications here on board before trying to upload them to git repo. Maybe they will meet the needs to get merged into antiX in order to fix all this.

The mentioned double mount happens right after first boot of a fresh Live-USB install from “full” ISO, without having touched any settings. So the default settings in antiX are probably the culprit. I immediately stopped this spook, but I still state: If the tool does claim it was safe to plug off your stick, this has to be true, irrespective how or who has mounted some additional partitions of it elsewhere before. No long palaver here, I can fix this bug easily in the script, making it safe.

7)…

Anonymous wrote:

Are any of the previously pre-installed ClawsMail plugins now absent?

Nope.
For comparison:

$ grep laws /usr/share/antiX/installed-packages.txt | cut -d ' ' -f 1
claws-mail
claws-mail-i18n
claws-mail-pdf-viewer:i386
claws-mail-pgpinline:i386
claws-mail-pgpmime:i386
claws-mail-tools

Only difference to antiX 17 was the imagemagick tool was removed from the preinstalled programs in the full antiX 19.3 ISO, but clawsmail does obviously expect it to be present.

8)…

Anonymous wrote:

remove the bootline parameters “quiet” and “splasht”

well, this was exactly how I fixed this indeed. (I’ve set it to “quiet” and “splash=v”, moreover added “mount=all” before saving all this with f8 option.) Wanted just to make aware of the strange behaviour of this affectionate clingy splash screen new users will face here when expecting simply to see the boot process instead after once having decided this question by pressing the offered key.

• This reply was modified 2 years, 1 month ago by Robin.
• This reply was modified 2 years, 1 month ago by Robin.
• This reply was modified 2 years, 1 month ago by Robin.

Windows is like a submarine. Open a window and serious problems will start.

[Anonymous]

antiX boot menu is presented for about half an hour
[..]
The time constant for this delay is set way to long.
[..]
can’t simply leave the notebook power up itself unattened on a live-persistent system
[..]
in antiX 17.4.1 already, I was able to fix it by editing some configuration file.
[..]
You’d better set this to a reasonable value by default.

on antiX 17, I checked:
/live/boot-dev/boot/syslinux/syslinux.cfg
^—> timeout 3000
(syslinux docs explain that the time unit is deciseconds)
300 seconds = 5 minutes

For antiX 19 (at least for the “net” edition), the value has already been reduced, from 3000 to 600
https://gitlab.com/antiX-Linux/Build-iso/-/blob/master/Template/net/isolinux.cfg

Just now, I booted a21 alpha in virtualbox and awaited “one circle”.
my observation: one circle ~= 1 minute

>>> can’t simply leave the notebook power up itself unattened

Due to a different bug — or call it an inherent “tight loop” or race-like behavior, within the “gfxboot” component which paints the bootmenu screen — it would be a poor idea to allow a battery-powered machine to “sit idle” with the legacy boot menu displayed. Vrroooooom 100% singlecore CPU usage.

Now after having succeeded in installing proprietary nvidia 304 drivers for go6600 GPU which was dismissed by this fu*%$(!7*ing manufacturer from their recent driver packages, threatening to brick my fully functioning well-tended notebook due to lack of functioning graphics drivers (nouveau driver wouldn’t work), I was able to have a look into the recent antiX version 19.3 (full) for the first time, using a live “persistent all” setup, completely apt-upgraded.

Some minor bugs raised my attention, maybe the listing can keep antiX 21 from inheriting these potential bugs:

1.) When running antiX-cli-cc from within terminal window in ROXTerm, the upper window frame stays completely blank after the program has finnished execution, also the minimized tab and the info in the taskbar at bottom line of icewm. Only closing ROXTerm and restarting will bring the missing strings back.

2.) In live-usb-maker-gui-antix the “Weiter” button (probably “Proceed” in original) is without any function. Can’t believe anybody else has noticed this behaviour, while trying to clone from running LIVE USB system to a fresh USB stick? Checked all possible choices, none of them would obviously allow to start the process. Butten “View log” presents an error message when pressed after a couple of minutes still: “Cant find log file at: /var/log/live-usb-maker.log” No further information present when running from command line instead from menu. All the other radiobuttons, dropdown-menues and buttons work as expected, only the “Proceed” button wouldn’t do anything. Button “Close” closes window, and that was all. No USB was created. Only calling the other script “live-usb-maker” from terminal window did the job flawlessly. I did never see this happen in antiX 17.4.1

3.) “live-usb-maker” from terminal window wouldn’t copy the persistent home from the running instance to the new stick, presenting a fat “WARNING” instead. This makes it necessary to boot a second instance afterwards from a third stick, mounting the two sticks (original and clone) side by side and copying the missing file from original to the freshly cloned stick.

4.) live-unmount: on shutdown from menu the “persist-save” (save persistent root) mechanism is performed twice. Once when still GUI is running, making the system wait for about a minute and a half or two, and then again during shutdown sequence not long before unmounting all drives finally, delaying the process again for a minute and a half or two. This was not present in antiX 17.4.1

5.) Obviously the live USB stick gets never unmounted properly on shutdown: On every single boot system complains about a not properly unmounted stick and performs a filesystem check on the live stick, setting the mount counter to 1 again, keeping the system for at least a full minute or two from proceeding. I’ve checked this using different USB-sticks and fresh installs of antiX 19.3, allways with this same result. This definitively does never happen in antiX 17.4.1, even when using one and the same stick for testing.

6.) The recent antiX USB unmounter from left side of the bottom bar is a hidden object game rather than a serious tool for everyday work (see screenshots). The borderless windows hide somewhere camouflaged and moreover can pop up in any corner of the screen, mostly invisible, always in a place you never would expect. What kind of April fool is this? Moreover, when you do have more than two USB devices pluged, the third one is not displayed since the window does only have two lines. The handle at right side is without function (doesn’t move at all), so you can’t reach the devices for choosing them to be unmounted when working with a classical 3 button mouse. What the heck? And finally this tool doesn’t function reliable. Sometimes a device is mounted twice to different mountpoints for some reason when plugged in. antiX USB unplug tool tells you happily you are safe to unplug your device, even if is still mounted somewhere. There is no check in the end whether it has completed its job actually, or would have better to perform a lap of honour and unmount the remaining mountpoints of the device silently as long as everything is done. This way it raises danger of data corruption if user trusts in the final message.

7.) In antix 19.3 claws mail the function to view an image (not thumbnail) is broken:
In 17.4.1 this works still as expected: when either clicking on the thumbnail image inside a message itself or right click and chose “view image” the image is expected to get opened full size within an external viewer.
This does not happen in 19.3 anymore, instead claws mail freezes for some seconds, before the context menu vanishes without any further notice. Starting the program in console window with –debug option, following lines show up when trying to access the image:

	$ claws-mail --debug
	[...]
	file-utils.c:58:TIMING safe_fclose : 26s986ms
	utils.c:2575:execute_command_line(): executing: /usr/bin/display-im6 /home/demo/.claws-mail/mimetmp/025b.jpg
	
	** (claws-mail:4103): WARNING **: 01:17:04.025: couldn't execute command: /usr/bin/display-im6

So I conclude the expected viewer not to be present in antiX 19.3

	$ ls /usr/bin/display-im6
	ls: Zugriff auf '/usr/bin/display-im6' nicht möglich: Datei oder Verzeichnis nicht gefunden

There is no setting available within claws-mail menue to chose another image viewer instead.
“display-im6” directs to something connected to “imagemagick”, which was present in antiX 17.4.1 still.
The problem can get fixed by installing imagemagick simply, but this doesn’t help the fact that either
the dependencies for the program “claws mail” are not met, or the default settings for this program as delivered in antiX 19.3 full (32bit) ISO are wrong in this concern. By the way, do we have “gedit” installed by default? Then user should not find a reference to this program somewhere.

8.) When pressing the button combination for turning off the splash screen during boot (after antiX boot menue) in order to observe startup process, this choice is not respected for the full duration of sequence. You have to press this button combination again and again at least 3 or 4 times, missing some lines each time, since splash screen reappears again and again after some time.

9.) The antiX boot menu is presented for about half an hour before all the pretty circles are filled. The time constant for this delay is set way to long. You can’t simply leave the notebook power up itself unattened on a live-persistent system, since it will wait all the time doing nothing but filling happily some circles. Nobody, really nobody could ever need that much time to decide whether he wants to intervene in the boot process by pressing any button in front of this screen (well, I like this screen, but…) This was the same in antiX 17.4.1 already, I was able to fix it by editing some configuration file. I will have to look up the what and where in my notes, but I remember it was quite difficult to locate. You’d better set this to a reasonable value by default. By all means, this happens on a 1.7 GHz CPU.

10.) Btw, what is that a crude battery value displayed in default 19.3 Conky? Well, I’m used to customise this display to my likes and dislikes anyway, but that default way it doesn’t look to much trustworthy to new antiX users…

Please check all this behaviour in 64 bit version of 19.3 and alpha preview of antiX bullsey as well, to prevent future releases of antiX from inheriting these bugs.

kind regards
Robin

• This topic was modified 2 years, 1 month ago by Robin. Reason: added screenshots
• This topic was modified 2 years, 1 month ago by Robin.
• This topic was modified 2 years, 1 month ago by Robin.

Attachments:

1. 

   bug-clawsmail-antix19-bearbeitet.jpg
   

2. 

   bug-where-is-the-unmounter.jpg
   

3. 

   wrong-default-setting-gedit-bearbeitet.jpg
   

Windows is like a submarine. Open a window and serious problems will start.

[Member marcelocripe]

Spartak77,

I thank you for your kindness and for all your work in inserting the Deepl translations in pt-BR in the file.

The “Help” (/usr/share/antiX/FAQ/index.html), for example, from the antiX ISOs 19.2 and 19.3, are currently in several files in “HTML” format.

Translating multiple “HTML” files is a much bigger job to do than translating into a single text file, as much as for an eventual correction. The “HTML” codes have special codes to implement the accent display (uncle, low and high accents, apostrophe, caret, etc.) that from the point of view of Latin-derived languages, I have no idea of ​​the complexity and what it is I need to display special characters in languages ​​that are not derived from Latin in “HTML” files.

The “/usr/share/antiX/” folder contains, in addition to the “FAQ” folder, other important help files: “antix_help_videos.html”, “equivalents.html” (comparison between the application programs available in antiX and Windows XP), folders: “Boot_Menu”, “live-boot”, “localization” and other files.

It would be interesting if antiX administrators/developers signaled in what format they intend to include “antiX Help” in the final antiX 21 ISO. This way we could join forces to include several files in different “Help” languages ​​for antiX 21.

Outside the main subject of this important topic, but related to antiX translations, I hope you can follow the other topics: https://www.antixforum.com/forums/topic/package-installer-only-in-english/page/3/ and https://www.antixforum.com/forums/topic/list-of-antix-programs-that-are-yet-to-be-translated..

marcelocripe
(Original text in Brazilian Portuguese)

———-

Spartak77,

Eu agradeço por sua gentileza e por todo o seu trabalho em inserir as traduções do Deepl em pt-BR no arquivo.

A “Ajuda” (/usr/share/antiX/FAQ/index.html), por exemplo, das ISOs do antiX 19.2 e 19.3, atualmente estão em vários arquivos em formato “HTML”.

Traduzir vários arquivos “HTML” são um trabalho muito maior de ser feito do que traduzir em um único arquivo de texto, tanto quanto para uma eventual correção. Os códigos “HTML” possuem códigos especias para implementarem a exibição de acentuação (tio, acentos grave e agudo, apóstrofo, circunflexo e etc) isso do ponto de vista dos idiomas derivados do latim, eu não faço nem ideia da complexidade e do que é preciso para ser exibido os caracteres especiais em idiomas que não são derivados do latim nos arquivos “HTML”.

A pasta “/usr/share/antiX/” possui, além da pasta “FAQ”, outros arquivos de ajuda importantes: “antix_help_videos.html”, “equivalents.html” (comparação entre os programas aplicativos disponíveis no antiX e no Windows XP), pastas: “Boot_Menu”, “live-boot”, “localisation” e outros arquivos.

Seria interessante se os administradores/desenvolvedores do antiX sinalizassem em que formato pretendem incluir a “Ajuda do antiX” na ISO final do antiX 21. Assim poderíamos unir forças para a inclusão de vários arquivos em diversos idiomas de “Ajuda” para o antiX 21.

Fora do assunto principal deste importante tópico, mas correlato as traduções do antiX, eu espero que você possa acompanhar os outros tópicos: https://www.antixforum.com/forums/topic/package-installer-only-in-english/page/3/ e https://www.antixforum.com/forums/topic/list-of-antix-programs-that-are-yet-to-be-translated.

marcelocripe
(Texto original em idioma Português do Brasil)

[Member marcelocripe]

Hello Wallon, Anticapitalist and Robin.

What Wallon detected and explained very well, I realized on Friday (02-04-20201) in the update of 9 antiX (8 antiX 19.3 full 64 bits and 1 antiX 19.3 Legacy 32 bits – built by the NGO Xecure ). I thought it could be a temporary problem, I decided to wait, today I updated 3 other antiX (2 antiX 19.3 full 64 bits and 1 antiX 19.3 Legacy 32 bits – built by Xecure), the problem you described also occurs with the language pt-BR.

Another issue very well raised by Robin is about the transifex, because when the developers / programmers update or edit the file, we are not notified by email. When a new file is sent by the programmers, replacing an existing one, ALL translations are lost, this happened with the “icewm-toolbar-icon-managershpot” and with another file, it made me very sad, because the texts were almost the same and I had to redo it from scratch. Since then, I started to download each file that I edit the texts en-BR, I kept them all. I’m usually notified when a new file is sent, but sometimes it doesn’t. For example, who told me that there were new texts in the “antix-packageinstaller-descriptionstxt” was Wallon, so since March 29, 2021 the 545 phrases are available for use in pt-BR. The next step will be to take to the “mx-packageinstaller-descriptions” the text models that I built that were satisfactory in the opinion of antiX users who participate in the unofficial MX Linux BR Telegram group.

The percentage of differences may vary from language to language, so I had to learn there are many important differences between pt_PT and pt_BR, so a high percentage has to be translated seperately.

Yes Robin, the Portuguese language (pt-BR) suffered several influences from several languages, from the dialects of the indigenous tribes (totally extinct with colonization), to the diverse African languages ​​of HUMAN beings who were enslaved for almost 400 years, later European settlers, so words practiced in Brazil have formats similar to French, Italian, Spanish, German and so on.

I just saw, unintentionally, that a new phrase was added at https://www.transifex.com/anticapitalista/antix-development/translate/#pt_BR/bootrepair_ents/319409988?q=translated%3Ano. It is very difficult for anyone who wanted to collaborate with antiX translations to have to guess where and when phrases were added or that a new file was sent that has yet to be translated.

Anticapitalista, what do you think we have in this forum as a means of communication to notify the translators about the new files or about the editing of the files?
In this way, we will be able to circumvent the limitations of the transifex site with official reports from developers / programmers about the need for new translations.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Olá Wallon, Anticapitalista e Robin.

O que o Wallon detectou e explicou muito bem, eu percebi na sexta-feira (02-04-20201) na atualização de 9 antiX (8 antiX 19.3 full de 64 bits e 1 antiX 19.3 Legacy de 32 bits – construído pelo Xecure da ONG). Eu pensei que poderia ser um problema temporário, resolvi esperar, hoje eu atualizei outros 3 antiX (2 antiX 19.3 full de 64 bits e 1 antiX 19.3 Legacy de 32 bits – construído pelo Xecure), o problema que você descreveu ocorre também com o idioma pt-BR.

Outro assunto muito bem levantado pelo Robin é sobre o transifex, pois quando ocorre a atualização ou edição do arquivo pelos desenvolvedores/programadores, não somos notificados por e-mail. Quando é enviado um arquivo novo pelos programadores, em substituição a um já existente, TODAS as traduções são perdidas, isso aconteceu com o “icewm-toolbar-icon-managershpot” e com outro arquivo, isso me deixou muito triste, pois os textos eram quase os mesmos e eu tive que refazer do zero. Desde então, passei a baixar cada arquivo que faço a edição dos textos pt-BR, guardei todos. Normalmente eu sou notificado quando é enviado um arquivo novo, mas às vezes isso não acontece. Por exemplo, quem me avisou que haviam novos textos no “antix-packageinstaller-descriptionstxt” foi o Wallon, por isso desde o dia 29-03-2021 as 545 frases estão disponíveis para uso em pt-BR. A próxima etapa será levar para o “mx-packageinstaller-descriptions” os modelos texto que construí que ficou satisfatório na opinião dos usuários do antiX que participam do grupo de Telegram do MX Linux BR não oficial.

The percentage of differences may vary from language to language, so I had to learn there are many important differences between pt_PT and pt_BR, so a high percentage has to be translated seperately.

Sim Robin, o idioma Português (pt-BR) sofreu diversas influências de vários idiomas, desde os dialetos das tribos indígenas (totalmente extintas com a colonização), passando pelos diversos idiomas africanos dos seres HUMANOS que foram escravizados por quase 400 anos, posteriormente com os colonos europeus, sendo assim palavras praticadas no Brasil possuem formatos semelhantes a escrita francesa, italiana, espanhola, alemã e etc.

Eu acabei de ver, sem querer, que foi acrescentada um nova frase em https://www.transifex.com/anticapitalista/antix-development/translate/#pt_BR/bootrepair_ents/319409988?q=translated%3Ano. É muito difícil para qualquer pessoa que queria colaborar com as traduções do antiX ter que adivinhar onde e quando ocorreram o acréscimo de frases ou que ocorreu o envio de um novo arquivo que falta ser traduzido.

Anticapitalista, o que você acha de termos neste fórum um meio de comunicação para avisar aos tradutores sobre os novos arquivos ou sobre a edição dos arquivos?
Desta forma, poderemos contornar as limitações do site transifex com informes oficias dos desenvolvedores/programadores sobre a necessidade de novas traduções.

marcelocripe
(Texto original em idioma Português do Brasil)