Description of problem: Question mark cannot be inputted because it has been changed to wildcard character for version 1.8.2-1. Version-Release number of selected component (if applicable): ibus-table-chinese-wubi-jidian-1.8.2-1.fc20.noarch How reproducible: Everytime Steps to Reproduce: 1. Active wubi-jidian input method 2. Press question mark key but question mark will not be outputted. 3. Question mark act as a wildcard character. Actual results: Question mark act as a wildcard character, and I cannot get question mark outputted. Expected results: Wildcard character should be "z" not question mark in wubi.
See also: https://code.google.com/p/ibus/issues/detail?id=1720
A workaround, if you want to type a ? using wubi: Type “?”, then commit with Return or Enter. Unless the option AUTO_SELECT is TRUE (it is FALSE by default for all Chinese tables!), Return or Enter commits the *unconverted* input string. I.e. if you type “ygkg” using wubi-jidian86, one of the candidates will be 语 and you can commit the Chinese using SPACE. But when committing with RETURN, the direct input, i.e. “ygkg” will be committed. This can be used to commit a ? directly.
According to https://en.wikipedia.org/wiki/Wubi_method#Implementation_specific_details wikipedia> [...] In such an implementation, the z key breaks the paradigm wikipedia> and as such is not found in much generalized software wikipedia> (although the Wubi input method commonly found in Chinese wikipedia> Windows implements the feature). [...] I.e. not all wubi implementations use z as the wildcard, some use ? and *.
Currently, the wildcard charactes to be used can be chosen in the source of the table by adding options like this: ### If true then a multi wildcard will be automatically appended ### at the end of input string. AUTO_WILDCARD = TRUE ### Single wildcard char SINGLE_WILDCARD_CHAR = ? ### Multi wildcard char. MULTI_WILDCARD_CHAR = * These options are are currently *not* in wubi-jidian86.txt as you can see here: https://raw.githubusercontent.com/definite/ibus-table-chinese/master/tables/wubi-jidian/wubi-jidian86.txt (They are in other tables like stroke5.txt). If these options are missing in the table source, the defaults are as shown above, i.e. AUTO_WILDCARD=TRUE, SINGLE_WILDCARD_CHAR=?, MULTI_WILDCARD_CHAR=*. An easy way to use z as the wildcard instead of for wubi-jidian86 would be to add ### If true then a multi wildcard will be automatically appended ### at the end of input string. AUTO_WILDCARD = TRUE ### Single wildcard char SINGLE_WILDCARD_CHAR = z ### Multi wildcard char. MULTI_WILDCARD_CHAR = * to wubi-jidian86.txt. Or, if one does not want a multi wildcard character, maybe: AUTO_WILDCARD = FALSE SINGLE_WILDCARD_CHAR = z MULTI_WILDCARD_CHAR = 不 <- any character here which cannot be typed with the keyboard directly But maybe other users want “?” and “*”? I should probably make this easy for the user to change in the setup tool so that it is not necessary to change the table source in ibus-table-chinese and rebuild the table.
Mike, Thank you very much for your rapid reply. 1. ? + ENTER in wubi-jidian can only input a half-width question mark. I think most of wubi users would want to input a full-width question mark. * will be the same. 2. Actually, wildcard character "z" was not implemented in previous version of wubi-jidian. 3. Being one of the wubi users, I would like to have one or more wildcard characters, but the input method should provide alternatives to input full-width wildcard characters. Thank you.
(In reply to Daniel from comment #5) > Mike, > > Thank you very much for your rapid reply. > > 1. ? + ENTER in wubi-jidian can only input a half-width question mark. I > think most of wubi users would want to input a full-width question mark. * > will be the same. Ah, yes, you are right of course! > 2. Actually, wildcard character "z" was not implemented in previous version > of wubi-jidian. ibus-table had no wildcard support at all, I implemented it recently. > 3. Being one of the wubi users, I would like to have one or more wildcard > characters, but the input method should provide alternatives to input > full-width wildcard characters. Yes, I am thinking about a way to do that. I will try not only to make the wildcard characters configurable but also make it possible to input the wildcard characters themselves easily.
Mike, > Yes, I am thinking about a way to do that. > > I will try not only to make the wildcard characters configurable > but also make it possible to input the wildcard characters themselves > easily. Thank you very much for your reply. I am looking forward to the new version.
Created attachment 911631 [details] 0001-Insert-a-special-candidate-for-the-wildcard-characte.patch Patch to make it possible to input fullwidth wildcard characters like fullwidth question marks. If only a wildcard character has been typed, insert a special candidate at the first position for the wildcard character itself. For example, if “?” is used as a wildcard character and this is the only character typed, add a candidate ('?', '?', 0, 1000000000) in halfwidth mode or a candidate ('?', '?', 0, 1000000000) in fullwidth mode. This is needed to make it possible to input the wildcard characters themselves, if “?” acted only as a wildcard it would be impossible to input a fullwidth question mark. I am working on making the wildcard characters configurable now.
ibus-table-1.8.3-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ibus-table-1.8.3-1.fc19
ibus-table-1.8.3-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ibus-table-1.8.3-1.fc20
The above update should solve the problem. There is a minor quirk I found while testing which I will fix soon: If one uses the setup tool to setup '?' as the single wildcard character and then changes it to 'z' with the setup tool, '?' is still remembered in the list of valid input characters (Because a the moment, I add the wildcard characters to the list of valid input characters). So after changing the wildcard that way, one has a problem typing the fullwidth ? again until one restarts ibus. The problem disappears when restarting ibus after changing the wildcard characters in the setup tool.
Package ibus-table-1.8.3-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ibus-table-1.8.3-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7756/ibus-table-1.8.3-1.fc19 then log in and leave karma (feedback).
ibus-table-1.8.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
ibus-table-1.8.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.