|
You want a Norwegian keyboard? Then no X or Z for you! You'll have to use the menu for Cut and Undo. And no Q either! If you're lucky, you might get a C and W! 
|
|
|
|
|
Strangely enough, I've got a Norwegian keyboard with both X, Z, Q, C and W. And ÆØÅ as well!
Surely, I am getting your joke, though. X, Z, Q, C and W are used so rarely in Norwegian words that those keys are not likely to be worn out before the others.
Side comment:
A coworker of mine showed me a "hierarchical" presentation of the morse alphabet as a binary tree, sort of like the one at Morse Decoder[^] (my Boy Scout handbook had a slightly different gaphical presentation, but the idea was the same). When I nodded, "Sure, that clearly reflects the frequency of characters - E is the most frequent, so it has a single dot, T is the second most frequent, having a single dash, and so on, to make the messages as short as possible", he looked at me in astnoishment: It had never occurred to him that that sort of optimization lay behind the design of the Morse alphabet! But it did.
The letter frequency of course depends on the language. The Morse alphabet is not optimal for every language, not even for all Western ones, but it is close enough.
In modern times, we keep this up: As long as you need to represent only characters in the English language, UTF8 lets you do it using a single byte per character. When you move to the languages of Western Europe, with nasty characters such as ÆØÅ, you must be prepared to spend twice as much space. If you move further away, outside Western cultures, you might even have to spend three times as much space per character!
Both memory and disk space is cheap nowadays; I doubt that this can be considered any major threat to non-Western cultures. Yet is does reflect a Western-centric view. The UTF16 format has been well defined for many, many years, putting practically all the written languages of the world on an equal footing. We choose not to use it, because we can save a little space for our Western culture languages. Sure: Disk and memory are cheap, yet we are not willing to spend money on UTF16 when we can spend a few cents on going for the UTF8-oriented Western solution... (Both are equally general; you can do the same in both, so the only difference between them is the space saving when handling Western languages!)
I actually don't know what Linux people are doing internally - they were hard to get out of the 7-bit track, accepting 8-bit alphabets. Today, I know that a lot of applications accept UTF8, and I know a lot that don't. Can you rely on all system functions accepting >8 bit character codes? Since the dawn of 32 bit Windows, Windows supported the basic UTF plane of 64ki character codes. I wouldn't trust applications to go beyond that, but for most practical purposes it is enough (... just like 7 bit US-ASCII was enough in the 1970s ...).
Yet... I am a Westerner, and when someone on the Internet provides a link (or printed reference) with Chinese characters, I gladly admit that I sure wish they would have provided it in some readable format. But my intellect says that the Chinese, or any culture using a non-Latin alphabet, has an equal right to present, and link to, their information in they style/language of their own culture. They have no obligation to other cultures to present stuff according to any, to them, foreign culture. So although Chinese, Korean, Japanese, Cyrillic or Greek links are all Greek to me, I admit that they have their place in an international world.
|
|
|
|
|
WEll I have closed my eyes and I am typing this . So far so good. It is significantly slower though. I guess we all cheat a little but I think I am donig OK
Now to open my eyes and hit send...
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Having had a visually impaired daughter, I have seen lots of software vendors demonstrating how great their software is for visually impaired users. But none of them have been willing to turn the screen away from the user/demonstrator, towards the audience, during the show. Noone has even been willing to give the demonstration using glasses smeared with vaseline, or glasses covered except for a small spot in the center (or off center). Or having the screen's color contrast reduced to an almost B/W picture, so that color information is worthless (for users with various kinds of color blindness).
For other physical disabilities you might of course ask the demonstrator e.g. to wear thick mittens. Or place the keyboard on a shelf that is irregularly shaking from one side to the other.
Generally speaking: I am not at all proud of UI designers, Web designers in particular, as see from a "Universal Access" point of view.
|
|
|
|
|
I type with my two forefingers, and that's it. And I'm always looking at the keyboard when I type.
People are always stunned by the fact that although I'm one of the slowest typists in existence, I'm also one of the fastest writers.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I still remember how impressed I was when we in 8th grade were in "Work practice week": I was "working" in a newspaper's local editorial office and couldn't believe the speed of one of the other journalists hammering away on a Teletype 33 with two fingers only. This was after I had had my 8th grade touch typing class, but that guy could easily beat me with his two fingers on the TTY 33 against me on an IBM Selectric!
Today, I am a fast typist, but not necessarily a fast writer. I use the screen as a way to try out sentences, phrasing and wordings. I read what I have written, reconsider it, rephrase it, reword it ... or delete it. My rough guesstimate is that I type between three and five times the number of characters ever saved. If you look at what has survived revisions and editions (of my own, forget about what others cross out!), at most five percent of what is saved survives its first year. Maybe it is down to 2-3%; I never checked, but I wouldn't be surprised.
A few of my coworkers keep gigantic mental structures in their head, needing only a structure of labels/identifiers on their PCs to keep their thoughts organized. I am the other way around: I like to offload those complex structures from my brain, using the labels/identifiers to recall them when necessary.
So when I offload something to the keyboard/PC it is essential to me to get it right. Therefore, although I am a fast typist in the sense of keypresses per minute, quite a large fraction of those are deletes and rewrites. So, to some degree I am a fast typist, but a slow writer.
|
|
|
|
|
Member 7989122 wrote: although I am a fast typist in the sense of keypresses per minute, quite a large fraction of those are deletes and rewrites. So, to some degree I am a fast typist, but a slow writer
That's the thing. Typing speed has precious little to do with either coding or writing.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I type with about six of my fingers (and my left thumb for the space bar) ...and I look at the keyboard regularly but the screen more so. I have never learned, or attempted to learn, touch typing and I can type faster, and more accurately, than most people in my office. There is one guy who can beat me for speed and he only uses about four fingers (and I can always hear him hammering at his keys). Touch typing is overrated especially when coding where you need to use {[( +-*/ and @#$!=, etc. on a regular basis. When I am working on my books I perhaps get up to higher speeds than when working on code, but not much.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I'm a fast (and relatively precise) touch-typist, but what still gets me to this day is the fact that split/so-called ergonomic keyboards (where you have a gap between the keys for each hand) aren't doing it right. In typing class, you're taught to type 4 and 5 with the left index finger, and 6 and 7 with the right one...but a lot of ergonomic keyboards have 4/5/6 on the left side, and only 7 on the right. So that always trips me up when I'm trying to type in a 6 or ^ (Shift-6).
Then there's the function keys. They used to be grouped in sets of 4 (F1-F4, F5-F8, F9-F12). But no, my current keyboard splits them along with the rest of the keys - F1 through F5, then F6 through F12 (so shouldn't F6 be on the left, right above the 6, if they're going to pretend 6 shouldn't be on the right?)
Then there's the additional buttons that are unique to each keyboard, the Ins/Del/Home/End/PgUp/PgDown layout that can be inconsistent, the location of things like quotes that depend on the keyboard and language used by the OS...it's all slowing me down tremendously, especially when I switch keyboards. I took a touch-typing class over 30 years ago, but I still have to look at a keyboard for all of these. Gimme plain text though and I can bang out a full page in no time at all.
I play GTA Online, on a system with a different keyboard than the one I'm used to. Based on the results (especially as I'm trying to do other things in the game), you'd swear I can't type at all.
|
|
|
|
|
I can't touch type either - at least not properly. I chicken peck at 100 wpm.
It's not pretty.
cheers
Chris Maunder
|
|
|
|
|
|
Awesome song, he was a truly great human being!
Young enough to know I can.
Old enough to know I shouldn't.
Stupid enough to do it anyway!
JaxCoder.com
|
|
|
|
|
Yes Sir and btw I enjoy reading your JaxCoder 
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
hanks for the kind words, I don't get many visitors...except my photos they seem to get quite a few hits.
Young enough to know I can.
Old enough to know I shouldn't.
Stupid enough to do it anyway!
JaxCoder.com
|
|
|
|
|
For me it was the part in "contact me" and then especially the "2 tours ..." which attracted my attention. After this I started reading the other stuff 
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Young enough to know I can.
Old enough to know I shouldn't.
Stupid enough to do it anyway!
JaxCoder.com
|
|
|
|
|
Mike Hankey wrote: hanks for the kind words,
Freudian narcissism?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Arthritic paraphrasing
Young enough to know I can.
Old enough to know I shouldn't.
Stupid enough to do it anyway!
JaxCoder.com
|
|
|
|
|
Questionable elucidation.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
One of the revelations that has come about as a result of covid-19 is that data is not the new oil. So many people working from have realised that bandwidth is the new oil. Data is just the vehicle.
|
|
|
|
|
Which made me immediately associate to all those software developers grabbing every new language feature (or whatever feature) searching frenetically for some place to use it. The important thing is not solving a given problem more easily thanks to the new thing. What is important is to find some - no matter which one - code piece where they can display their mastery of this new feature. Who cares about solving problems? Having a long list of tools and techniques that you master is far more impressing on your CV that a varied list of actual real world problems you have solved during your programming career.
|
|
|
|
|
I just realised that I'm doing that right now. I have just started using extension methods and I'm trigger happy when it comes to using them.
|
|
|
|
|
codejet wrote: Data is just the vehicle.
Not sure I agree with that. I'd say that bandwidth is the pipeline. The bigger the pipeline the more oil/data you can transfer.
Soon, underprivileged will be defined by the amount of buffering one must endure for those precious cat videos or episodes of the masked singer. 
Covid-19 is like a bad software project...not enough testing to properly debug. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
I like you analogy. Kindly complete it for me.
Pipeline - Bandwidth
Oil - Data
Vehicles - ?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
