|Mailing List email@example.com Archived Message #6||back to list|
I suggest we consider moving this to the list, now that its confirmed that
we're all on it.
On 08/27/20 06:21 am, Alfredo Fernández Díaz wrote:
On 20/08/26 21:18, Lewis wrote:
Clearly, this isn't a major issue, currently.
Depends on your definition. As far as lSwitch is concerned it's not an issue
even for me, but...
Well, I say "currently" as the Russian translation is woefully out of date at
this point. Still, an argument could be made that it is sufficient for basic use.
Russian just made it into the build tree, so I've been going cross-eyed
looking at Cyrillic recently, and worse, CP866 strings under CP850 (which is
headache-inducing). If the time comes that we have users with a need to switch
from a CP850 language to CP852 (Czech) or CP866 (Russian), this may become
more of an issue. Right now, it's trivial, at best, but does fail the fit and
I have mentioned it in the past, but it was a side comment kind of thing, so
I didn't expect you to remember yet even more trivia about me. I need to
keep around both an 850/1004 to exchange system and an 850/866 one to
exchange stuff with Windows systems and work with Russian files easily
(currently that means running a VirtualPC ArcaOS inside my main OS/2 system).
I did not recall that. Thanks for reminding me.
I had thought of writing something called CPLaunch in the past, that would
start processes in any code page supported by the system regardless of
config.sys CODEPAGE=, but it seemed too much to study and a lot of work to
build something only I would use once in a while.
An interesting idea.
I'm not sure how one could accomplish this, given the
primary/secondary handing of codepages in OS/2, but we do a lot of stuff right
now that five years ago nobody thought possible (like booting ArcaOS on UEFI,
and soon, being able to create and install to GPT disks).
Mail to ListMaster