"A*UN SMIT"
would be "onSubmit". You could also fall back to forcing an attached, uppercase word. So: "ON KPA* SMIT" Why You Should Use Private Search Engines?
Here's the entirety of that section: The truth is, people know that search engines are
tracking them. Most websites have privacy policies
which clearly state that they use cookies and other
means of tracking users. Any in many cases, when we
are asked to give apps, websites, or products
permission to track us, we blindly agree. This may
seem acceptable at first, but it’s problematic if that
same tracker is following you two years later, when
you’ve forgotten about it.
Your search engine should be optimized for searching
the internet, not tracking you once you’ve left. Your
Google information can be used against you in legal
cases, even in civil cases like divorces.
So if I understand correctly:
However, not all of them are "computer" or "realtime" compatible, which roughly means that you wouldn't be able to distinguish in your writing between homophones like "their" and "there" and "they're."
Here's a list of some of the languages that have been developed or ported to Plover: https://github.com/openstenoproject/plover/wiki/Chorded-Syst...
There is a Plover plugin to switch on-the-fly between different steno systems.
There is also a plugin to switch between enabled dictionaries on-the-fly.
Finally, there is the idea of bilingual dictionaries, but I haven't seen it implemented well yet.
There's also the problem of some languages having drastically different layouts.
So far, the most multilingual and successful stenographer I've seen is Stanley Sakai. Here's him writing in a Spanish theory that he developed: https://www.youtube.com/watch?v=eGZ43TID9jU&t=90s
I also know that there are bilingual stenographers in Canada who write both English and French, but I haven't seen it in action yet.
In summary, I think that multilingual stenography is critical for the adoption of steno, but it's currently not easily accessible or widely used.