On Wed, 2 Sep 2020 13:24:10 -0400 Lewis wrote:
>
>Replying in no particular order...
>
>On 08/29/20 06:46 am, 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 :(
>>
>
>Well, for lSwitcher, it's not like we have a whole translation team. So,
>the few of us polyglots (of one sort or another) here have to just look
>at several things. I see more of the non-EN ArcaOS builds because, well,
>they install that way. I generally don't install a package in English
>and then go switching (although I used to for ANPM, but that was before
>we - again - had a real team in place). I just have to remember what's
>what in the different projects, that's all.
Yes we missed that you can't load CZ in the recent betas. Don't ask as I have a work around but know idea why it happens.
I now have the various languages appearing correctly in the Language selection box (yes including the Cyrillic). I mostly have all the languages rendering properly in the settings dialog (one string of Russia still doesn't work). Note this is on an 850 English system. It still has menu problems and you probably won't like the font.
>
>>>>>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
>>
>>You know, that could even be a good idea ;p
>>I'll mull a bit over it.
>>
>
>Think of how we handle the timezone names list for each language. We
>don't list Kenya in Swahili.
>
>>>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'.
>>
>
>I unmangled it. ;-)
Both CP 1207 and 1208 seem to work pretty well (one bad Russian string but that is probably my fault since all the others work fine).
>
>>>>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?
>>
>
>The thought is that if it were a Russian system, it would install by
>default in Russian, and thus, all of the language names would start in
>Russian (and not default to English).
>
>Even if the install itself was an EN install, chances are that a native
>speaker would set LANG appropriately, so that as much as possible was in
>Russian. Isn't that the reasoning behind you setting your LANG variable
>to es_ES, even on ArcaOS EN?
Well I have found a way to load readable Russian on a default installed English system. This is really how all this should work but it is non trivial to get it working and it doesn't work in VIO/command windows.