further enrich the documentation adding a cedilla tweak example

[ninrod]

@39aldo39, klfc is pretty important for non english speakers that must compose special characters through deadkeys. As a brazilian that uses us keyboards, this is specially important.

In OSx, this is a solved problem. In windows it is solved too. But in linux, we have a shortage of options when it comes to programs that allow the user to easily tweak his keyboard and klfc is really a god send. Even now, if you search for ways of how to achieve this in linux, you are directed to various hacks that solve the issue tangentially, while breaking other parts of the system.

That said, would you be willing to accept a PR that adds an example of how to configure a us keyboard to tweak the cedilla settings using the customDeadKeys options?

for example, It was not clear for me that I had to append the cdk:nameOfMyCustomDeadKey. Further, I don't understand yet what is the semantics of leaving out the baseChar field from the customDeadKeys entry.

[39aldo39]

Sorry for the late response, I didn't have time (vacation, etc.).

I will certainly accept such PR! Feel free to improve the documentation. Furthermore, the baseChar field doesn't have a lot of meaning in Linux or OS X. There, a dead key only produces output on full sequences, so the baseChar never gets printed. If you leave out the field, a random Unicode code character from the private use area is used, since it doesn't matter which character it is. That said, if you assign the output of a different key to the same character, that key becomes a dead key as well.

[DreymaR]

Actually, to preserve functionality the baseChar should get printed by the dead key plus Space sequence, I think? This is the way with Windows dead keys; although it isn't happening automatically it's recommended for all dead key tables.

I'm not sure, but I think that two presses of a dead key also should produce the base character? But it'd be tempting to use that for the combining accents instead...?