How many chords can be listed for a language?

[crimson arch]

If I wanted to add a whole chord list for another language, how many chords can I list into the device's memory?

[wintry lake]

All of them

@hollow fossil should have the actual number somewhere

[mossy wren]

Not if one of them is Chinese.

[wintry lake]

Ok sure

[crimson arch]

I am planning to add korean chords when I have a device.

And can it switch chords list I use without reprogramming?

[rustic ibex]

This is from the wiki.

[lean sandal]

I believe this is going to be changing in the Universal Update.

[mossy wren]

I’m not sure that anyone has actually run the numbers. It would be challenging to get an accurate number because of how things can get stored in several different ways.

@crimson arch If you will help me with some of the factors, I’ll try to find/figure out what you might reasonably plan on fitting in.

The list is internal to the CharaChorder, so having different languages would require that the host be able to map characters from different languages, but ultimately, the CharaChorder sends key codes, rather than actual characters, so there isn’t any real reason that multiple languages couldn’t be added to the table. The limitation would really be the reasonable number of possible chord combinations that can be keyed. If you swap the code table when you swap languages, you would basically be starting with a blank CharaChorder for each language.

My personal point of view is that you would really be pushing the outside of useful words at about 600 for most languages, and after about 500, each persons word list would begin to diverge pretty widely. You would also have to memorize the chord tables for the separate languages. I would think that the idea would start to lose out to diminishing returns at maybe 350 words per language, but I would be happy to be proved wrong on any of these estimates.

[crimson arch]

@mossy wren Thank you so much. My questions are all answered.

korean keycodes are the same with standard qwerty but it matched into korean compositing characters.

the exisiting speed type product for korean uses about 3000 chords. I think I can make my own version of korean chords.
while keycodes are same, the way of making chords will look like a random to english speakers (the reduced chances of duplication) for example 사랑 means love but we do type tkfkd with the standard query. so tkfd can be a good chord for the word.

[rustic ibex]

Keep us posted if you make a Korean chord library. That would be so cool!

[crimson arch]

I want to do it asap when I have the product.

[bold quartz]

GG @crimson arch, you just advanced to level 1!

[mossy wren]

You clearly understand the relevant concepts. The only reason that we use the letters in an English word for the English chord is because it's easier for us to mentally construct the memory of what the chord should be like. It's a memory tool for what could as easily be arbitrary chords based on the word frequencies. We could use the 10 easiest chords for the 10 most frequently used words. This is especially possible for the CharaChorder One where we have no preconceived expectations for the layout.