- This topic has 320 replies, 28 voices, and was last updated May 11-8:42 pm by Wallon.
-
Posts
-
PPC
@Wallon – my guess would be that the excessive creativity of the fr translators, that decided to include strange characters in the text and the buttons, messed up antiX-Updater in French – I’ve said, in private, lots of time, to a fellow translator: “Stick as close as possible to the original version, do not add to much…”
On the Trash icon on the desktop – I did not see that, but you can add it easily yourself- there’s a .desktop file for it…
P.
RJP
When installing NetworkManager, the installer does not make startup file to /etc/rc.local or other place, so it must make by hand.
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # NetworkManager start exit 0Also nm-applet must launch as root for editing connection.
gksu nm-appletRobin
excessive creativity of the fr translators, that decided to include strange characters in the text and the buttons
Dear PPC, what would you suggest for languages completely comprising of such „strange characters” ? Should these „modernise” their language to the constricted plain English character set to make programmers happy? I recon it should be done the other way around. The programs and scripts have to deal with this properly.
A good example how this can be hosed completely is barrier I mentioned in another thread these days. This nice tool resets the keyboard layout for all foreign languages on the Client PC to US-English and ties it to this as long as mouse is on client screen. So you won’t even be able to log in, if you don’t accidentally happen to know the position of characters needed on US-English layout by heart.
Windows is like a submarine. Open a window and serious problems will start.
Wallon
Brian Masinick
Just because a character is not in the ASCII character set does not make it a strange character, far from it!
What would we do with any of the Chinese character set, which is arguably the most expansive of all?
Even the “Simplified Chinese” character set is much larger than any European character set.
Being able to build for any of these character sets would be wonderful, even if it is a significant challenge.--
Brian MasinickBrian Masinick
We may need to take a closer look; I found a scenario, after a long pause of not actively using the system, then returning to the system that led to some WiFi instability.
I’ve not repeated the behavior after reboot, but since you are also seeing a problem I think we need a deeper look to see what’s going on.
I won’t have time to do proper log examination and verification today, but I will attempt to follow up in that area soon too.Meanwhile, @calciumsodium, if you can find something helpful, I’ll check similar things when I have more time to “dig in”. Thanks!
I do not see this as an antiX issue; saw it again briefly during the day, but it’s better in the evening, suggesting that the issue is a result of some work taking place in our area, nothing more. Positive feedback today; checked out several things in the package installer, was also able to remove some apps I didn’t care to include on my instance of the full test and the removals worked fine as part of today’s testing.
--
Brian Masinick
marcelocripe
The English original does not need to be changed, only the french localization. Localization is perfect in pt and pt-br. Do not blame the original script for a bad localization…
I just saw the antiX updater in the ISO “antiX-23-beta1-runit_x64-full.iso”. Unfortunately, the text without line breaks made the window look huge and doesn’t look good on a 1024×768 screen. I added a lot of line breaks, but the latest “yad-update” file in “pt_BR” is still unused.
As I’ve already written on the forum several times, every new resource uploaded on Transifex that doesn’t have comments instructing the translators causes this kind of aesthetic problem or even translating what shouldn’t be translated.
I hope the most recent file from “yad-update” in “pt_BR” is used.
– – – – –
The English original does not need to be changed, only the french localization. Localization is perfect in pt and pt-br. Do not blame the original script for a bad localization…
Eu acabei de ver o atualizador do antiX na ISO “antiX-23-beta1-runit_x64-full.iso”. Infelizmente, o texto sem as quebras de linha fez a janela ficar enorme e não fica bem apresentada em uma tela com a resolução 1024×768. Eu adicionei várias as quebras de linha, mas o arquivo mais recente do “yad-update” em “pt_BR” ainda não foi utilizado.
Como eu já escrevi no fórum várias vezes, todo novo recurso enviado no Transifex que não possui os comentários instruindo os tradutores, causam este tipo de problema estético ou ainda de traduzir o que não deveria ser traduzido.
Eu espero que seja utilizado o arquivo mais recente do “yad-update” em “pt_BR”.
anticapitalista
@all
This is a beta.
It will be full of bugs.
It will not include all ‘perfect’ translations (as I mentioned in the opening post).
So, please don’t assume that if something is not working for ‘you’ is intentional.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Brian Masinick
@all
This is a beta.
It will be full of bugs.
It will not include all ‘perfect’ translations (as I mentioned in the opening post).
So, please don’t assume that if something is not working for ‘you’ is intentional.Even though we completed Alpha 1 and we are early in Beta 1, I am pleased and impressed with the general quality of this work, and my expectation is that we are here to help out; things like translations, quite frankly dear friends, should be among the final things to complete.
When I worked on a commercial UNIX system we did a little bit of language work, but mostly in the (I18N) internationalization (coding side) during development. Most of the (L10N) localization work took place in the final beta just prior to the code freeze.
We’re doing great and the quality EXCEEDS that of many commercial efforts during Alpha and early BETA tests. While we can mention potential coding changes, translation work is among the final touches, so let’s concentrate on making sure code function proceeds and help in that area.
--
Brian Masinickcalciumsodium
Testing beta1 on a 2009 computer with G33 graphics.
Enjoy watching youtube video using mpv (360p resolution).
I see good performance with this 6.1.18 antiX kernel and this rtl8188fu wifi driver.
Solid and robust.
I am using the theme Clearview Blue Medium with a dark wallpaper and a black color background in roxterm. The main window is clearly blue on top to distinguish it from the background windows which have the off-white top. There was a discussion about what themes people like. I like the Clearview Blue.
Attachments:
I also tested beta1 on a 2010 computer (G41 graphics) that I have put together from various scrap parts.
I also see good and robust performance with this 6.1.18 antiX kernel and this rtl8188fu wifi driver.
Attachments:
vance
Downloaded 23 beta1 & tried it from the jump drive. I am impressed. Right after starting up the OS using all the defaults, on the desktop it reports under 200M RAM being used on Conky. 21/22 reports about the same maybe a little less on the same machine. My question is the disparity between using the command “free -h” in a terminal window & comparing the used value reported between the 2 OSs. In 21/22 it’s about the same as what Conky reports but in 23 beta1 “free -h” reports over 400M being used. Based upon using other memory tools I think it’s a bug in the “free -h” command. Any thoughts?
sasa_
The old hardware works fine. Memory usage 660 MB.
inxi -b System: Host: antix1 Kernel: 6.1.18-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM v: 3.3.2 Distro: antiX-23-beta1-runit_x64-full Grup Yorum 21 March 2023 Machine: Type: Desktop System: wortmann product: P5K v: N/A serial: <superuser required> Mobo: ASUSTeK model: P5K v: Rev 1.xx serial: <superuser required> BIOS: American Megatrends v: 1201 date: 10/14/2008 CPU: Info: dual core Intel Core2 Duo E8500 [MCP] speed (MHz): avg: 2004 min/max: 1998/3163 Graphics: Device-1: NVIDIA GT218 [GeForce 8400 GS Rev. 3] driver: nouveau v: kernel Display: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau resolution: 1366x768~60Hz API: OpenGL v: 3.3 Mesa 22.3.3 renderer: NVA8 Network: Device-1: Qualcomm Atheros Attansic L1 Gigabit Ethernet driver: atl1 Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc Drives: Local Storage: total: 465.76 GiB used: 6.11 GiB (1.3%) Info: Processes: 122 Uptime: 7m Memory: 3.83 GiB used: 482.5 MiB (12.3%) Shell: Bash inxi: 3.3.25Attachments:
Dear all:
I’m glad I did not post last night, because that would be a Skidoo level of snarky reply that could eventually get me banned:
Please compare the screenshots of antiX-Updater running in french and in english that Wallon posted. Try to see what’s different on the buttons, besides the language. It’s an easy “spot the difference” game, that will probably let anyone with a little experience in yad scripting know what probably is causing the script to fail, when localized in French…
Dear PPC, what would you suggest for languages completely comprising of such „strange characters” ? Should these „modernise” their language to the constricted plain English character set to make programmers happy?
Short version: No.
Long version: Simply not randomly replacing a single quote with a double quote, inside a variable would do. I only know a little of bash and yad – I will not learn a programming language just to please a translator that thinks it’s a good idea to replace the special characters used on the text.
Anyone that follows my posts about my scripts knows the efforts that I go trough, just to make them easily localizable. I had scripts localized to other alphabets, like Russian Cyrillic, and no one every complained those scripts were broken by the localization- this was the very first time. Why? Once again, thanks to the fr localization, it now has double quotes inside a yad text. Yad seems not to like that. Nothing I can do about that, except suggesting, once again: stick as much as possible to the original text, when localizing. Use special characters (and I do not meant accented characters or non latin alphabet, or pictugrams, hell, even cunniform writing!!!), like quotes or double quotes, etc, only when they are on the original text!
Want to make me “happy”? – just localize the text. Do not try to inovate.@PPC
Your words are shocking.
I thought everyone could use antiX.Read what I wrote above. Anyone can use antiX. I work a lot (and like every one else here, for free), to make user’s life easier – adding as many useful GUI’s as anticapitalista lets me, and trying to make my scripts as easy to localize as possible – why? Because I want anyone, speaking any language, to be able to use antiX, even without any technical skills.
For that to happen translators can’t randomly insert special characters (read above what I mean by that) on their localizations, because, as you can see, they can break the script. If the “programmer” uses a single quotation mark, when localizing, respect that. It’s probably there for a reason. Off course you can use any character you own language has – if you don’t know, I’m Portuguese myself. We have lots of “special characters”, with accents, etc. Using them never broke any script. What can break scripts? Inserting double quotation marks where there’s a single quotation mark.As I’ve already written on the forum several times, every new resource uploaded on Transifex that doesn’t have comments instructing the translators causes this kind of aesthetic problem or even translating what shouldn’t be translated.
True, if possible, comments on Transifex help the translation team. I don’t put stuff on Transifex myself, so I never inserted any comment. When in doubt, translators should do what some users do: ask here in the forum for what some localization string means… a lot of work, I know, but we all work in this system for free.
…But it’s also true that thinking it’s a good idea to stick three times que words that are on the original text is almost always sure to cause “aesthetic problems”. Try to just localize, not innovate (unless you really know what you are doing – sometimes my pt localizations are slightly different from the original text, on the scripts what I write, because I know exactly what the “programmer” wanted to say and how to adapt it to my “culture”. When localizing something I did not write myself? I try to stick as close to possible to the original meaning and the original word count).Edit: I appreciate everyone that puts work in our OS – specially the localization team- by no means I want to sound that I’m complaining about the FR localization team- they are well meaning and just made a tiny localization “mistake”, by changing something they should not. It happens to us all, bugs happen. That’s what beta versions are for!
- This reply was modified 1 month, 2 weeks ago by PPC.
ile
Hello anticapitalista
PPC , zzzfm View;yes., now i see the wingrid keys.
sasa_ , Thanks for showing Task Mananger.
Grup Yorum. maybe the next name can be simply
cool beans.
antiXbeta1GY3 running live [not.persist]
was asked to use live usb maker to make
a clone of itself. complete success.
The first usb made with mx live usb maker Full-featured mode.
Can the live usb maker have text beneath the “dd Image” mode
with wording that ddImage means “Useful for installing antiX” (?)
The clone usb is live [not.persist] demo started here in:adventure. small keyboard. touchbroken-screen touch not operable.
jwm Theme red; icewm Theme Dust; fluxbox Style Numix
jwm is very nice.System: Host: antix1 Kernel: 6.1.18-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: IceWM v: 3.3.2 wm: JWM v: 2.4.4 dm: slimski v: 1.5.0 Distro: antiX-23-beta1-runit_x64-full Grup Yorum 21 March 2023 base: Debian GNU/Linux bookworm/sid Machine: Type: Laptop System: LENOVO product: 20428 v: Lenovo Yoga 2 11 serial: <superuser required> Chassis: type: 10 v: Lenovo Yoga 2 11 serial: <superuser required> Mobo: LENOVO model: VIUU4 v: 31900058WIN serial: <superuser required> UEFI: LENOVO v: AACN21WW date: 01/30/2015 Battery: ID-1: BAT0 charge: 29.7 Wh (100.0%) condition: 29.7/34.0 Wh (87.3%) volts: 8.2 min: 7.4 model: Lenovo IdeaPad type: Unknown serial: BAT20101001 status: full CPU: Info: dual core Intel Core i3-4012Y [MT MCP] arch: Haswell speed (MHz): avg: 599 min/max: 600/1500 Graphics: Device-1: Intel vendor: Lenovo driver: i915 v: kernel arch: Gen-7.5 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0a1e class-ID: 0300 Device-2: Sunplus Innovation Lenovo EasyCamera type: USB driver: uvcvideo bus-ID: 2-1:2 chip-ID: 1bcf:2c66 class-ID: 0e02 Display: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1366x768~60Hz API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel HD Graphics 4200 (HSW GT2) direct-render: Yes Network: Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Lenovo driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:0036 class-ID: 0280 Drives: Local Storage: total: 494.88 GiB used: 1.57 GiB (0.3%) Weather: Report: temperature: 10.78 C (51 F) conditions: scattered clouds wind: from SSW at 3.6 m/s (13 km/h, 8 mph). Gusting to 3.6 m/s (13 km/h, 8 mph) cloud cover: 40% humidity: 81% pressure: 1016 mb (34 in) Locale: Washington, US, 20500 current time: Thu 23 Mar 2023 03:03:38 AM MST observation time: N/A Source: OpenWeatherMap.org Info: Processes: 142 Uptime: 5h 0m wakeups: 2 Memory: 3.72 GiB used: 1.27 GiB (34.1%) Init: runit v: N/A runlevel: 2 Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg pkgs: 1617 Shell: Bash v: 5.2.15 running-in: roxterm inxi: 3.3.25Attachments:
- You must be logged in to reply to this topic.
