On Sat, 29 Aug 2020 12:46:31 +0200 Alfredo Fernández Díaz wrote:

.... and getting ahead again... ;p

On 20/08/27 18:24, Lewis wrote:

Still running to catch up...

On 08/27/20 05:53 am, Alfredo Fernández Díaz wrote:

<snip>

The screenshot is from January, 2019. I guess some subconscious part
of my
brain was hoping somebody else would notice too ;(

And I have a few like that for AOS too ;(((

If everyone used English (as he should, some would no doubt argue), we
would
not be having this discussion. :-D

Indeed, I am guilty as charged for not reviewing the other languages
(at all,
in this case). :'(

Well, it's part of what we're supposed to do. I'm sorry sometimes
somebody "has to" report something because I didn't clear my to-do list
fast enough, though. So many wasted hours :(

I didn't check because the change that caused this was to the build system not any of the resources. In retrospect I should have realized what could happen.

I wish there were something we could do about the non-CP850 language
names,
such as to localize the dropdown content itself. We can discuss for a
future
release, I guess.

The names /are/ localized,

Quite right. I meant to say, localized for the currently-selected
language. Thus:

English
Spanish
French
German
Russian
Czech

I can do this if that is what everyone want or I can translate Spanish and German but leave Russian and Czech in English. Let me know.

You know, that could even be a good idea ;p
I'll mull a bit over it.

vs

English
Español
Français
Deutsch
⌂⌂⌂⌂⌂⌂⌂ ⌂⌂⌂⌂
⌂e⌂tina

(Russian and Czech come from Wikipedia; I take no responsibility for
lack of
capitalization or spelling!) These all work well in Unicode, of course,
which
is why I can do this in SeaMonkey without any problem.

Which helped me stay in os2land a couple of times.

just broken as Gregg said in another message. Unless standard PM can
really
CP1028 characters (unlike Mozilla or OOo, which use some trickery of
their

That should have been 'can really show CP1208 characters'.

own) and convert everything, I don't think there's much more that can
be
done (so you will see ÓÒß߬¿® instead of proper Cyrillic, etc.).

If I were a native Russian speaker, with little English skills, would I
be
able to determine that that was my language? Well, perhaps, if when the
system
was switched to CP866 before PMSHELL started the string would show
properly
(luckily, 866 includes most 850 characters, so those wouldn't be
rendered
illegible).

I'm not sure I see what you mean there. I don't think anyone without
a very particular background would be able to tell "ÓÒß߬¿®" means
"Russian" (and for a PM program, where would it be displayed in CP866
before PMShell starts?). I also wonder how well a Russian with little
English skills and somehow being able to recognize the word "Russian"
(in English) go together. Why would the former be using an English
system?

Probably better than figuring out what the odd string at the bottom is. Also if you install on a Russian system it will automatically come up in Russian (mostly). Thanks