Fixing some rules; conflicts and misc

[Tibowl]

• Fixes some conflicts
• Adds closing parentheses where missing
• Changes " to ' in comments to fix when trying to do multikey + =~ results in

≅" U245 # APROXIMATELY EQUAL TO (It actualy means "congruent

instead of ≅

[samhocevar]

Thanks for the patches. As of now, I do not wish to modify Xorg.txt or Xcompose.txt because they come from external projects, namely Xorg and .XCompose. I very much would like that incompatibilities be fixed by these projects instead. I will leave this pull request open for reference, but I’m afraid I do not wish to fix these issues in that way.

Alternatively I would like a mechanism that lets users solve incompatibilities or set priorities using the GUI, but I haven’t started any work on this yet.

In 910d681 I fixed the parsing bug that you discovered, though; thanks a lot for spotting this! The fix will be in the next release.

[zommuter]

Since one can additionally use a .XCompose{,.txt} file, does anything defined in there have overriding priority?

[joaopizani]

Hi, I have my own XCompose file defined during years of development. And now I have placed it in %USERPROFILE%, but now WinCompose uses BOTH the internal mapping plus the extra ones in my own XCompose file. Is there any way to make my own mappings the ONLY ONES in the system, i.e, delete all mappings that come with WinCompose by default? Would 💗 that.

[samhocevar]

You can manually remove the files in c:\Program Files\WinCompose\res\ until #24 is fixed. I’m afraid you’ll have to do it after each upgrade.

[joaopizani]

One way which I think wouldn't be so complex to implement would be if the loading of the "standard" mappings was made optional. It would be enabled by default, but with an "advance" panel in the options screen the user could choose whether or not to load them.

[joaopizani]

I already renamed the files in %APPDIR%/res BTW, I read the code and found out where it was loaded, but thx for the tip anyways :)

[rillig]

Another way to prevent the default sequences would be to have a special command Dont_use_standard_sequences. The following code could be added at the beginning of Settings.LoadSequenceString:

if (line.Equals("Dont_use_standard_sequences"))
{
    m_sequences = new SequenceTree();
    m_sequence_count = 0;
}