kempelen
@manyroads Thank you. I downloaded that study, sounds funny from The Register’s introduction, especially if there are actual failure case studies in it. But I’m paying attention to personal data, thanks for heads up. I have Claude Code subscription, but all it knows about me is what programming languages I use, what software I develop in it, and what problems I ran into in these, etc. It helped a lot in upgrading from antiX 23 to antiX 26 (e.g. examined which of my Docker machines have data in /var and would be lost with formatting “/” root). (I didn’t give it access to /var, but I put ls -lR /var in a folder!) Maybe scroll back here to my post with two screenshots, that gives example of cool uses.
So hopefully I’m taking more than giving more up. (Claude Code just helped me to make a DEB package from RoxTerm 3, I plan to try to submit that to antiX, but first I need to figure out if the DEB builds and runs without problems – Never I made a DEB package before yesterday, and yesterday I made it in something like 2 hours. This includes creating from current git snapshot for personal use, or release tarball for actual releases, and I even submitted two patches to RoxTerm regarding their “debian” folder and other errors.) (Based on a tool that Claude Code recommended to run on the ready DEB package, to make sure maintainers won’t need to make cleanups after me.)
Then, being there deep in RoxTerm source code, I asked Claude to translate the MAN page to Hungarian. That one really needed a lot of extra work from me to make it right! I’m sure @alkaid ‘s project would have done a way better job on that.
@alkaid Is there a way to load dictionaries in your software? I’m using basically tree type of dictionaries for every translation work:
– we have a Hungarian free software community dictionary (and translation guide)
– I create dictionary for every project for terms that are specific to the project
– The program itself is also a dictionary, e.g. if I translate a “Settings” menu a certain way, references to the menu name (“Open the Settings menu”) must match original translation, this especially applies to help texts.
(I ran into these type of errors today with RoxTerm 3.x help on Claude Cude, by simply getting it translated from EN and PT_BR to HU. I didn’t ask it to use pt_BR but it did, because these are the only languages currently translated. 🙂 )
(ref: https://github.com/realh/roxterm/pull/283 )
@Robin Thanks for that pointers on missing translations. Yes, I’m on it, getting back to work on antiX translations. 🙂 The new release re-activated me! 🙂
antixscreenshot2 HU percentages are misleading due to the large help text. But thanks in advance if you will add it. I don’t see why it would create you extra work if the package was directly in antiX – the program works very well since many years, it would be really cool to add it if possible.
I know you don’t want to change the help text, because it’s already translated, but just a note for future, I found a cool way in RoxTerm source code to make man pages. It uses an XML document, and then “docbook-xsl” package to make it MAN. One single command from XML to MAN. (Maybe the previously mentioned po4a can even convert that XML to PO for Transifex use.) This is the corresponding XML file, and top comment section contains the command to convert it to MAN page:
https://github.com/realh/roxterm/blob/master/man/roxterm.1.xml.in