QA:Testcase ibus compose

Description

This test case is to type compose characters in f29 or later

How to test

Install your IBus engines

• For GNOME3

1. Run gnome-control-center keyboard and add an input method sources besides XKB sources to enable IBus for XKB sources.
2. Run gnome-control-center keyboard and go to "Compose key" and setup your compose key.
3. Focus on gnome-terminal and after enable an XKB source with Super-Space key, type a compose key, "^" and "a".

• For others

1. Make sure ibus is enabled.
2. Configure compose key in your desktop. XFCE4 does not have the setting and you might like to save your compose keys in $HOME/.Xkbmap file.
3. Run setxkbmap -query command,
4. Focus on gnome-terminal and after enable an XKB source with Super-Space key, type a compose key, "^" and "a".

• Test Case 2 (after above test)

1. Run mkdir $HOME/.config/myapp
2. Create $HOME/.config/myapp/ibus-compose.emoji to copy https://raw.githubusercontent.com/ibus/ibus/master/src/tests/ibus-compose.emoji
3. Add the following lines in $HOME/.XCompose : include "%H/.config/myapp/ibus-compose.emoji"
4. Run ibus restart
5. Run gedit
6. Type compose sequences described in E.g. Multi_key, Multi_key, I, n, t

• Test Case 3 (Java application)

1. Download OmegaT_@VERSION@_Linux_64.tar.bz2 from "Linux with 64-bit JRE" in https://omegat.org/download
2. Run tar xfvj OmegaT_@VERSION@_Linux_64.tar.bz2 and extract the OmegaT archive file.
3. Run java -jar OmegaT_@VERSION@_Linux_64/OmegaT.jar
4. Open "Project" -> "New" and create a new project with a test Source language and translated language
5. Click "Add Files" in the "Source Files" dialog, add a translatable file and close the dialog. E.g. IBus POT file
6. Enable the source file pane and execute the compose tests

• (In case Java applications do not show the font correctly in test case 3)

1. Check the current font with fc-match ":lang=ja"
2. Check the current Java version with /usr/bin/java -version
3. Check the JAVA_HOME with rpm -ql $(rpm -qf /usr/bin/java)
4. Make a font fallback directory with sudo mkdir -p $JAVA_HOME/lib/fonts/fallback
5. Make a symlink of the current font file to the Java font fallback drectory

Expected Results

• For GNOME3

1. N/A
2. N/A
3. IBus pre-edit shows "·" (U+00B7), "^" and output "â".

• For others

1. N/A
2. N/A
3. Show "options" line
4. IBus pre-edit shows "·" (U+00B7), "^" and output "â".

• Test Case 2

1. N/A
2. N/A
3. N/A
4. N/A
5. N/A
6. You can type the compose keys in the ibus-compose.emoji.

• Test Case 3

1. Download OmegaT_6.0.0_Linux_64.tar.bz2 for E.g.
2. Find OmegaT.jar in OmegaT_6.0.0_Linux_64
3. OmegaT GUI is launched
4. Open a new test project
5. Add ibus/po/ibus10.pot file
6. Succeed the compose tests

• (In case Java applications do not show the font correctly in test case 3)

1. NotoSansCJK-VF.ttc: "Noto Sans CJK JP" "Regular" for E.g.
2. OpenJDK 64-Bit Server VM (Red_Hat-17.0.8.0.7-1.fc39) (build 17.0.8+7, mixed mode, sharing) for E.g.
3. Found /usr/lib/jvm/java-17-openjdk-17.0.8.0.7-1.fc39.x86_64/lib for E.g.
4. Make /usr/lib/jvm/java-17-openjdk-17.0.8.0.7-1.fc39.x86_64/lib/fonts/fallback directory
5. cd /usr/lib/jvm/java-17-openjdk-17.0.8.0.7-1.fc39.x86_64/lib/fonts/fallback && sudo ln -s /usr/share/fonts/google-noto-sans-cjk-vf-fonts/NotoSansCJK-VF.ttc . for E.g.