Interlinked •Find and •TRANSLITERATION functionalities in prep. (Concordance Viewer #Sword -based app.)//I don't like GitHub so much, need I additional „shadow” copy repo caused IT issues?!]

Simple transliteration, Levenstein distance algorithm should copy with it through-fully.

 •Instead of transliteration, I can use Linux font viewers and hexadecimal-styled standard Xorg shortcut sequence „input method”/„IME”.

•The core and «BLANKET» of Hebrew dict contents is „basic” letters, NOT the ”bushes” for vocalization forms. The „blanket” of each Strong's Real Concordance entry consist basically of „clean” letters, not the details that can change with entry pos., the Aramaic lang., or the influence of US speaker.

•„W” is „o”, does IS =„u”, and, the „v” — all Hebrew analysis should start with this piece of science. Note – „b” is not always „w”. You can read aloud bet letter as wav... but it is somewhat relative.

This is proper „data view” model on topic.

So far, Levenstein's working OK. I replaced code model to conform with std::vector of C++ standard library. Readability of code should be better then.

Not wanting to make additional HDD-backed GitHub - the factual main repo. Why to copy files LOCALLY?!

My experience w/GitHub is too small. I concentrate on code model, code base... and NOT about design patterns (so much...) . Qt lib object serialization process is somewhat „hard-coding”... all such declarations, classes hierarchies... .

     And I have experience in .NET Framework, not in multiclass-oriented load/saving of configuration.

Good soft requires minimalization of amount of classes to code-in the definitions.

Analytical program extensively uses system clipboard.

Some sci-orientation, passion on good details. Even the unimplemented yet green 4eyes-healthy mode/GUI styling.

•Linux clipboard support is not perfect, even none clipboard viewer you have in popular distros. And not meaning next Wordpad...