Hola Noelia, Donde puedo inscribirme para aprender estenografia en español usando tu plugin? mi correo es [email protected] Muchas gracias
El viernes, 12 de marzo de 2021 a las 9:57:31 UTC-6, [email protected] escribió: > Sorry, a mistake: I wrote "what Melani > system used the Microsoft Access database", meaning "how, not what". > Thanks > > 2021-03-12 16:55 GMT+01:00, Noelia <[email protected]>: > > Hello, first of all, thanks for starring! > > About using Python dictionaries, the reason is that they allow to > > borrow lot of entries in json files. > > For example, instead of writing: > > # Json > > > > "CAsa": "casa", > > "CAse": "case", > > "CAsi": "casi", > > "CAso": "caso", > > etc, we have in the Python file "the letters that can be use to write > > these words, but they can be useful to type many many other > > expressions. We use an algorythm as follows, similar to the algorythm > > used by the original Melani system, with the difference that this is > > open source and we had to make a lot of tests to know what Melani > > system used the Microsoft Access database, in particular a field named > > semplice, used for subsets of characters that can be part of a stroke: > > > > def searchKey(dictionary, stroke): > > searchKey = stroke[:] > > searchKeyValue = "" > > lenSearched = 0 > > value = "" > > while len(searchKey) > 0: > > if dictionary.get(searchKey) is not None: > > searchKeyValue = dictionary.get(searchKey)[1] > > if searchKeyValue == "": > > searchKey = searchKey[:len(searchKey) - 1] > > else: > > value += searchKeyValue > > searchKeyValue = "" > > lenSearched += len(searchKey) > > searchKey = stroke[lenSearched:] > > if value == "": > > value = "{empty}" > > return value > > > > Hope this helps > > > > 2021-03-12 16:46 GMT+01:00, Flavio Egoavil <[email protected]>: > >> Hi, > >> > >> I just starred your repository. This is very interesting work and no > >> doubt > >> having more than one Spanish system for Plover will strenghten the Open > >> Steno project. > >> > >> I just have a quick question after taking a look: Why does a large part > >> of > >> the dictionary is hardcoded into a .py file instead of residing on a > >> separate JSON file? Is there a particular reason? Just curious. > >> > >> For example this python file has OVER 9000 definitions: > >> > https://github.com/nvdaes/plover_spanish_mqd/blob/main/plover_spanish_mqd/dictionaries/spanish_mqd_single.py > >> > >> > >> On Wednesday, March 10, 2021 at 11:29:26 PM UTC-5 [email protected] > wrote: > >> > >>> Hello: > >>> > >>> Yesterday we released version 1.0.4 of a plugin to add support for > >>> Melani > >>> > >>> system with italian keyboard in Spanish. It uses Python dictionaries, > >>> json > >>> > >>> files and another plugin required for using combinations with different > >>> translations if they are used to start or not a word. The theory is not > >>> documented, just some examples about the API. > >>> We release new versions at least when Python dictionaries are modified. > >>> https://github.com/nvdaes/plover_spanish_mqd > >>> Enviado desde mi iPhone > >>> > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Plover" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to [email protected]. > >> To view this discussion on the web visit > >> > https://groups.google.com/d/msgid/ploversteno/137c12d9-8772-4bd3-bf42-78c8dbec8a82n%40googlegroups.com > . > >> > > > -- You received this message because you are subscribed to the Google Groups "Plover" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/ploversteno/52902271-252f-4c20-9443-28887013ea9fn%40googlegroups.com.
