opt: unify dictionaryid

[xiaoyifang]

benefit :
you can move your dictionary files into other folders and have no need to reindex the dictionary again.

drawback:
If you have two versions of the same dictionary , only the first one got indexed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[GD-fix]

drawback:
If you have two versions of the same dictionary , only the first one got indexed.

What "two versions" means here: the same content and name dictionary files on two different locations, only the same name dictionary files on two different locations, only the same content dictionary files regardless of their locations, or the same name dictionaries regardless of their content, files names and files locations?

[xiaoyifang]

What "two versions" means here: the same content and name dictionary files on two different locations, only the same name dictionary files on two different locations, only the same content dictionary files regardless of their locations, or the same name dictionaries regardless of their content, files names and files locations?

the dictionaryid only cares about the filenames ,so the answer should be " or the same name dictionaries regardless of their content"

[GD-fix]

If "the dictionaryid only cares about the filenames" than the answer about "two versions of the same dictionary" must be "only the same name dictionary files on two different locations". Am I right?

[GD-fix]

Is it possible to append to Preferences the option of "moving dictionary files into other folders and have no need to reindex", of course with ATTENTION! about mentioned drawback and full reindex of all dictionaries (and this one option with appropriate ATTENTION! too)?

[xiaoyifang]

"moving dictionary files into other folders and have no need to reindex", of course with ATTENTION!

I do not think we have time for this. The above function will only be used one time in life.

[GD-fix]

If You have such time pressure, then lay out 2 release variants please...

[shenlebantongying]

Massively breaking existing installations and creating confusion is not a reasonable action.

I don't think we will do this until we find a better solution or put significant effort writing on a config migrator and clarify that we stop keeping compatibility with the original GD.

Even the change in this PR is questionable.

For example, why do we still use md5 if we're ever going to change it? If we use something that can be decoded back to the original content, it will make debugging much easier.

Also, if the meaning of config changed, then it should be put somewhere else, instead of modifying in place.

[xiaoyifang]

For example, why do we still use md5 if we're ever going to change it? If we use something that can be decoded back to the original content, it will make debugging much easier.

md5 is signature alogrithm., while the other is encryption.
Decode is not needed at such place.over-designed.

But it is ok to close this PR.

[GD-fix]

Simply a portable binary (with statically linked libraries) version with this dictionary id variant and own config file and index folder...