- This topic has 133 replies, 9 voices, and was last updated Sep 20-10:51 am by marcelocripe.
-
Posts
-
Senpai
Hi:
Is Droopy working for you guys? I’m trying to run it to see how it works, but the console opens for a second and then closes… on an updated antiX-Full installation, without removing anything… in theory, it says it’s compatible with Roxterm…
Best regardsP.S
Okay, I see that the name has been mistranslated into Spanish: they translated “droppy” instead of “droopy.” I’ll take a look at it… and fix it…
There was a mistake in “antixcc”—I’ve already fixed it—but it still doesn’t work… I also get an error when running it from the console…- This reply was modified 5 months ago by Senpai.
- This reply was modified 5 months ago by Senpai.
- This reply was modified 5 months ago by Senpai.
A question… In the “boot-params” resource, on the line (kbopt=<options> Keyboard options. These give special meaning to certain keys or key combinations. For example kbopt=ctrlnocaps: turns the Caps Lock key into an extra Control key.). the command’s highlighting “kbopt=ctrlnocaps:”, Is that right?, or would it be like that “kbopt=ctrlnocaps:“,
Best regards
Attachments:
Hi @robin “or whoever it may concern ;-):
In the recourse “antiX 26 FAQ – Fluxbox” the last 3 links “Fluxbox wiki”, “How I Did It” and “antiX Tips page” They don’t work. Can anyone suggest some alternatives that do work? And please update the links in the FAQ.Best regards
- This reply was modified 4 months, 3 weeks ago by Senpai.
Robin
Can anyone suggest some alternatives that do work?
Have you searched the waybackmachine ( archive.org ) already ? There might exist mementos of the sites.
If there are, you can use the wayback links instead in translation. Please let us know here, then I can add these in the en_GB “translation” as well so they get available to translators of other languages as well.This is how I have mitigated already a few other links which were gone somewhere in this set of resources.
Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
Hello.
Entry 95 of the resource “antix-26-faq-rox” informs that:
“Yes it is. The startup scripts in IceWM and Fluxbox open a customized pinboard (called antiX) while Menu -→ Desktop -→ Desktop -→ ROX-Pinboard on/off (in Fluxbox) and Menu -→ Desktop -→ Settings -→ ROX-Pinboard on/off (in IceWM)opens the default one (called just Pinboard) only slightly customized (background image). Their configuration files are in ~/.config/rox.sourceforge.net/ROX-filer/ under the names pb_antiX and pb_Pinboard respectively. If you open the default one from the menu and make whatever changes you would like, they will be saved to pb_Pinboard and will come back every time you open it again. If you want to create yet another pinboard setup, open Menu -→ Run and type:/p> rox -p=mypinboard”
As can be seen in the images (“The command doesn’t work (1).png” and “The command doesn’t work (3).png”), the gExec program does not allow the use of the greater than sign.
The subsequent entries continue the explanation that it will only work if the previous command is successfully applied, which was not possible.
I don’t know how to correct the errors in the “en” language texts in the “pt_BR” translation.
I ask for help from anyone who knows how to correct the “en” language texts, because the volunteer translators who are doing 1-to-1 translations will be translating information that doesn’t work in antiX 26.
The English texts do not include JWM, which also allows activation of the ROX panel. In other words, there are several inconsistencies in the texts.
In other words, if the antiX help contains instructions that don’t work in antiX 26, the help will not serve its purpose.
/p>
Hi Marcelo, please simply remove the above quoted sequence, which clearly is part of a mangled html code tag and shouldn’t exist. It shows up in the rendered result, see screenshot.
Instead you can apply e.g. something like:
<em>rox -p=mypinboard</em>
or
<i>rox -p=mypinboard</i>
in your translation. I’ll apply this fix in en_GB translation (and de for sure) as well. Or you can omit this incomplete closing tag completely, if I’m not mistaken.Attachments:
Windows is like a submarine. Open a window and serious problems will start.
marcelocripe
Hi Marcelo, please simply remove the above quoted sequence, which clearly is part of a mangled html code tag and shouldn’t exist. It shows up in the rendered result, see screenshot.
Thank you very much, Robin.
Hi @robin:
In the Internet resource (net.html), the link to “Connman” is missing, and the “Wicd” link doesn’t lead to any explanation. Could you please fix this so we can finish the translation?Best regards
Attachments:
Senpai wrote:
Can anyone suggest some alternatives that do work?
Have you searched the waybackmachine ( archive.org ) already ?
Hi @robin:
I’ve never searched on archive.org before; I found an archived wiki, but it’s in Spanish… All About FLUXBOX,
Also in Spanish… Fluxbox on doc-ubuntu.es, this could work for my Spanish translation, but not for the others…In English, I found the Fluxbox website; in its help section, it could serve as a reference for one of the links, whichever you think is appropriate… Fluxbox Help Site
And there’s this documentation on archive.org about Fluxbox, although it’s in PDF… Fluxbox DocumentationI hope this helps. If you’d like me to provide the links in Spanish for my translation, just let me know and I’ll add them; if you prefer to keep the English versions, that’s fine too.
Best regards
kempelen
I’ve never searched on archive.org before; I found an archived wiki, but it’s in Spanish…
@Senpai To search an article on Archive.org you can copy the old full link that you know, into the “Wayback machine” part of archive.org that should yield old copies of the website if available. You may need to go backwards in time to find a “blue dot” which means real copy (green is redirect, red is error, on the calendar days) (example attached)
For “Fluxbox Wiki” there is a copy from 2014:
https://web.archive.org/web/20140421213545/http://fluxbox-wiki.org/index.php/Fluxbox-wikiFor “How I did it” link they don’t have a copy. ( http://forum.archives.mepiscommunity.org/viewtopic.php?f=40&t=8954 )
For “antiX tips page” there is newest copy is form 2017:
https://web.archive.org/web/20171209063251/http://antix.mepis.org/index.php?title=Fluxbox_Tips_and_Tricks_Edit_Fluxbox_MenuBut I agree with you that the link should be updated to actual Fluxbox help site.
Beyond that, Fluxbox users may want to preserve some of these info if still useful, while it’s still available. Then we could link to preserved copy.
Attachments:
if not, please bark up here
Mentioning native English speakers, @Robin please use a better verb instead of this if possible. I don’t know this verb, but never seen in any other context than “bark up the wrong tree”, and I assume it’s dog’s speak. 😉 You can e.g. say “Please let us know” or “Please tell us”, “Please alert us”. To me this sounds more friendly – not native English speaker here, but I consume almost everything in English and work for foreign company since 25+ years.
I think most FAQ fixes do not need native English speakers, if these are just wrong menu path references and similar things. Some steps are not easy to follow, like that icon placement on desktop (that’s called “icon” not “symbol”), and sometimes outdated, but by careful examining and tying it should be possible. (And may need update, of course.)
@marcelocripe You can also ask AI it may be able to help. E.g. for testing that “Rox” “pinboard” I would do the following:
1. log in with Rox – otherwise you are not testing what you are trying to understand
2. Copy paste that FAQ question and answer into Brave Leo AI and ask it to explain in your language what this question is about and how to do it.(Attached how long cool explanation I got. I cut it after 2 screens but it’s very long and clear and Hungarian.) (I have Brave from their APT source and I use it only for the Leo AI. (I have a Pro Claude Code subscription but I use that exclusively for programming stuff, not for fixing our vacuum cleaner… I want to keep the memory focused, so for all else I use Leo.) (But honestly, my Pro Claude is more accurate, so often in tech questions like this, I need to go there instead of these free, small-knowledge models. I was discussing this FAQ translation project with Leo in past hour, but I’ll switch to Claude, because I’m getting answers conflicting previous answers and so on. The “gigabytes” in the AI model’s “brain” do matter a lot. So do not expect wonders from free options.)
Attachments:
@marcelocripe Oh, one more small thing. I think when you see some text that is translated to pt_BR from English a bit “arrogant” or “rude”, I think that might be because English is very heavy on “nice words”, like repeated use of “Please” and explicitly indicating the person like “I”, “you”. But the English text is totally understandable without the extra “nice words”, yet, machine translation can go wrong without them. E.g. if I write “Sorry, I made a mistake!” but I leave out “I”, you will probably get a translation “YOU MADE A MISTAKE!”. While in original English it’s most likely obvious from the context who made the mistake. Without the “I” word too, despite the “correct grammar” absolutely requires it. Let’s try it.
Sorry, made a mistake! Forgot the file totally!
For “Fluxbox Wiki” there is a copy from 2014:
https://web.archive.org/web/20140421213545/http://fluxbox-wiki.org/index.php/Fluxbox-wikiFor “How I did it” link they don’t have a copy. ( http://forum.archives.mepiscommunity.org/viewtopic.php?f=40&t=8954 )
For “antiX tips page” there is newest copy is form 2017:
https://web.archive.org/web/20171209063251/http://antix.mepis.org/index.php?title=Fluxbox_Tips_and_Tricks_Edit_Fluxbox_MenuBut I agree with you that the link should be updated to actual Fluxbox help site.
Thanks for the help, I couldn’t find it…
I think that version of the Wiki might be usable, but I don’t have permission to edit the links, so it must be @robin, I think…Using your links, I found a more modern wiki (which is now a website). The last changes were made 3 years ago, but I don’t see how to view it online as a webpage. I think you have to do something with it, but I’m not familiar with that… I’m passing along the link in case it’s useful… https://github.com/fluxbox-wiki/fluxbox-wiki.github.io
Best regards
@Senpai That’s interesting finding, thank you. I made a clone of that, just in case. The GitHub project’s right side has a “Deployments” link and that points here: https://fluxbox-wiki.github.io/ (From this the actual pages are readable from the Languages -> English menu)
@Robin I think it’s not worth to add translator comments to those files if that makes it impossible to further edit the original HTML files and push updates to Transifex. Especially not a 3 lines comment to every 33 menu items, in 33 files, creating 1089 basically identical comments. A better aim would be: original English HTML files are the master, they can be updated, and translators can follow up with changes (just like any other files on Transifex, except where you wrote such comments already).
In general regarding “translator comments”:
I work on some projects where developers answer Transifex and CrowdIn questions in reasonable time, all my comments, often with very nice explanation of complex terms specific to that program’s in-depth workings. We are a 20-25 persons translation project – I assume -, maybe we should aim ANSWERING QUESTIONS rather than trying to help when not asked. I would participate in answering questions on Transifex (added as “issues” or “comments”). Such answers then are available to all further translators directly where needed.
A reply to my own comment:
I was discussing this FAQ translation project with Leo in past hour, but I’ll switch to Claude, because I’m getting answers conflicting previous answers and so on.
Indeed Brave Leo makes immediate answers, while Claude usually thinks 2-3 minutes on very similar questions about this FAQ project. I’m experimenting with “po4a”, which is a documentation translation system (like FAQ HTML). Last question took 20 minutes for Claude (however that resulted in a tested workflow with all necessary scripts and necessary config files). I’ll get back on this if any results.
@Robin The files are unnecessarily full of & # 13; entities, which are probably remaining trash from an aged DOS-to-Unix file format conversion or similar step.
I think they cause the weird double enter on Transifex GUI. (Attached a picture with such double enter.)
In HTML terms they play no role, especially at line end, they are a Carriage Return character from the usual \ r \ n new line sequence, so being on line end, which ALREADY behaves as a space on rendered HTML they just do nothing. They just cause difficulties for translators and also caused some hours of extra work for me now in trying to process the files. Claude recommends to remove them. But of course I understand you cannot update the English files currently, so this is not something you can do currently, but maybe a note for later. Here is final analysis from Claude Code, but it was so much stuck on errors caused by “something” (either these or not) that I needed to keep pushing it: this cannot be the cause. Finally agreed. (Partial conversation from a whole day sequence…)
Q: And do you find it reasonable that a HTML parser would not descend into the table for cells in a structure like <div
id=”main-menu”><table id=”menu-table”><tr><td>… (with no text content in between div and table) (unless there is
other structural errors)?● No, I don’t — and your skepticism is well-founded. I need to correct my earlier explanation, because I got the
causation wrong.Looking back at the actual test sequence:
– po4a-updatepo -f xhtml without -o untranslated=pre → 54 entries (this was run on stripped files)
– po4a-updatepo -f xhtml -o untranslated=pre → 4 entriesThe stripped files without the option gave 54 correct entries. That means removal was harmless all along. The
single cause of the low extraction count was always and only -o untranslated=pre — the conflict with po4a’s internal
_default_translated registration for PRE tags. The stripping was coincidental noise that happened at the same time,
and I incorrectly blamed it.So: you can safely strip from the source files if you want cleaner PO strings, and the note in pullall.sh about
keeping them is wrong. The cleaner approach would actually be to re-enable the stripping in pullall.sh and get rid of
msgids like “ 5500 which is used to listen…”.Want me to re-enable the stripping in pullall.sh, re-download the files, and regenerate the POT? It would clean up a
fair number of noise strings in hu.po.✻ Cogitated for 1m 10s
—
Now, that is a very hard decision for me here, right before starting to translate. Because if I remove the Carriage Return entities LATER, then many-many-many strings will become “fuzzy”.
So I think I’ll do the following in this pilot project for FAQ-HU: I do remove them, do the translation, and see if HTML pages look OK and see if Transifex accepts the files back. If Transifex does not accept them, but HTML works perfect, I will probably need to submit outside Transifex, and later on if they are removed from base files, … that would cause “fuzzy” for everyone who already translated so maybe we will NEVER remove them…..
- This reply was modified 4 months, 1 week ago by kempelen.
- This reply was modified 4 months, 1 week ago by kempelen.
Attachments:
- You must be logged in to reply to this topic.