OS/2, eCS & ArcaOS - Technical > Applications

LarsenCommander - new test version

<< < (5/5)

Andi B.:

--- Quote from: Alfredo Fernández Díaz on December 05, 2023, 03:32:36 pm ---I'm glad to to see LC actively developed once again. Thank you, Andi - will be giving it a spin : )
Quick question - is NLS functional?

--- End quote ---
It should be all included in the package. I remember I've worked on adding all necessary components for NLS to the distribution script long time ago. But I didn't test it. So feedback is appreciated.

Remember at https://sourceforge.net/p/lcmd-git/tickets/ there's a ticket system. Although I try to read all infos here, chances that something get remembered in future is much higher when there's a ticket ;-). No clue if you need an account for that. For me sourceforge works pretty good with our ancient SM (and so FF I think). In contrary to other sites username/password authentication still works.

Alfredo Fernández Díaz:
Hi again, Andi, thank you...

--- Quote from: Andi B. on December 08, 2023, 10:58:16 am ---It should be all included in the package.
--- End quote ---

I asked whether it is functional because I saw a bunch of old RC translated files under the 'locale' subdir with no obvious way to switch languages from within the application (and still can't find it).


--- Quote ---I remember I've worked on adding all necessary components for NLS to the distribution script long time ago. But I didn't test it. So feedback is appreciated.
--- End quote ---

OK, fiddling about a bit, under locale there is an old email called 'reply.txt' that you can get rid of. Its slightly more updated cousin 'readme_translation.txt' (which you could refactor) reads "start Larsen Commander version 1.5.1 or 1.5.2 with this command: LCMD.EXE -rcFileLocale lcmd_it.rc" . I cloned the English file onto a Spanish one in the LC folder and changed a few strings -- LC picks it up with the proper parameters in place in the program object. Functional, but a bit cumbersome to keep switching languages while translation is in progress.


--- Quote ---Remember at https://sourceforge.net/p/lcmd-git/tickets/ there's a ticket system. Although I try to read all infos here, chances that something get remembered in future is much higher when there's a ticket ;-). No clue if you need an account for that. For me sourceforge works pretty good with our ancient SM (and so FF I think). In contrary to other sites username/password authentication still works.
--- End quote ---

OK, but let me see first if I can figure out the locale format ("text" and "hint" are obvious, but what are "alt1", 2, and 3?), how everything is put together (menus seem to be scattered), and whether the autogenerated mnemonics and such do not make translation much of a PITA.

Andi B.:

--- Quote from: Rich Walsh on June 10, 2023, 05:45:41 am ---The solution to this particular problem is to get rid of the DLL -- there's no reaon for it to exist. The original author claimed that VACPP 4.0 couldn't handle a 16-bit call so he created a separately-compiled file. But rather than simply linking it into the exe with all the other .obj files, he created a dll. Why?
...
--- End quote ---

It seems it was that easy - add '      source "gl16os2.obj"' to lcmd.icc and don't delete gl16os2.obj during the build. As far as I can see the only 16 bit function which is used by lcmd is Dos16MemAvail. But no clue when it is called. Have to test a while to be sure there's no sideeffect.

Navigation

[0] Message Index

[*] Previous page

Go to full version