my comments below marked with ****
On Aug 4, 6:44 pm, pks kolkata <
pksharmakolk...@gmail.com> wrote:
> > Towards the end of gkosw.cpp there is a large amount of tables with
> > words that are default values for the shortcuts.
>
> i think the start is :
>
> // ==========================================================
> // Selecting Shortcut Strings
> // and creating the tables
> // ==========================================================
> //
> // =================FIRST CHARACTER is Special===============
> void gSendSC_Period()
> { sc1 = 0;
> switch (ChordonByte[2])
>
> and the end is :
>
> default: gSendRest(); break;
> }}
>
> // 781 chordon shortcuts total !!!
>
> hmmm....
**** right as far as I remember
>
> > They can however be
> > modified without editing the code itself by just renaming data file
> > gkos-shortcuts.dat (created when gkosw.exe is run for the first time)
> > to gkos-shortcuts.usr and editing the content of that which consists
> > of the shortcut words.
>
> when the gkosw_066.zip file is unzipped it created a gkos-shortcuts.usr file
>
> do i have to edit the .dat file and then copy/rename that to a .usr file ?
*** you can just edit the words in gkos-shortcuts.usr if the file was
zipped in already. the chordons at the beginning of each line are only
references for the human reader and have no impact on operation itself
>
>
>
> > If you want to edit the Chordons that trigger the shortcut words, you
> > will have to edit C++ code and re-compile it. The Chordons are defined
> > in C++ function gSendShortcut() and some other places near that
> > routine.
>
> hmm .. this is a C++ code .. these steps should not be difficult .. altering
> the key sequences to other key combos and maybe even more keys (10 ?)
> could be done .. but that would need detailed work, coding, collaborating
> with you and a good C++ programmer at my end
>
> which C++ was used ? since that would be the best to compile the code too
**** I used Dev-C++ version 4.9.9.2 which is still available at
http://www.bloodshed.net/
**** in case you try some other compiler, you are sure to get error
reports during compilation of my code!
>
> i am strongly inclined to NOT get into deep coding-debugging-recoding
> particularly after my doctor's strict advice to not 'strain' while working
> on computer .. meaning totally avoiding looooong hours at single stretches
>
> so i will try to explore the special key combos to get hindi characters
> in groups .. by altering the .usr file
*** editing the words only, not the 2-character shortcuts, will have
an impact on output