Description: Can't combine Korean Hangul Final Consonant on specific Hangul Syllable '가'in LibreOffice Impress. But, the others Hangul Syllable works in LibreOffice Impress. example) 반갑습니다 actual) 반가ㅂ습니다 expected) 반갑습니다 only mix Korean Hangul Final Consonant with specific Hangul Syllable '가'. Steps to Reproduce: Input Korean Hangul Syllable '갑' 1. ㄱ 2. ㅏ 3. ㅂ Actual Results: 가ㅂ Expected Results: 갑 Reproducible: Sometimes User Profile Reset: No Additional Info: If you add Korean Hangul Final Consonant on Korean Hangul Syllable "가" , It can't combine Hangul syllables on LibreOffice Impress Example) 각 > 가ㄱ (ㄱ + ㅏ + ㄱ) 간 > 가ㄴ (ㄱ + ㅏ + ㄴ) 갇 > 가ㄷ (ㄱ + ㅏ + ㄷ) 갈 > 가ㄹ (ㄱ + ㅏ + ㄹ) 감 > 가ㅁ (ㄱ + ㅏ + ㅁ) 갑 > 가ㅂ (ㄱ + ㅏ + ㅂ) 갓 > 가ㅅ (ㄱ + ㅏ + ㅅ) 강 > 가ㅇ (ㄱ + ㅏ + ㅇ) 갖 > 가ㅈ (ㄱ + ㅏ + ㅈ) 갗 > 가ㅊ (ㄱ + ㅏ + ㅊ) 갘 > 가ㅋ (ㄱ + ㅏ + ㅋ) 같 > 가ㅌ (ㄱ + ㅏ + ㅌ) 갚 > 가ㅍ (ㄱ + ㅏ + ㅍ) 갛 > 가ㅎ (ㄱ + ㅏ + ㅎ) But, default Impress template format is correctly done.
Created attachment 148761 [details] Can't combine Korean Hangul Final Consonant on specific Hangul Syllable '가' example odf file Implement Korean Input bug that can't combine Korean Hangul Final Consonant on specific Hangul Syllable '가' on LibreOffice Impress
Created attachment 148762 [details] Capture image that can't combine Korean Hangul Final Consonant on specific Hangul Syllable '가' on LibreOffice Impress Implement Korean Input bug that can't combine Korean Hangul Final Consonant on specific Hangul Syllable '가' on LibreOffice Impress
Created attachment 148763 [details] It correctly works and shows to Input Korean Hangul Syllable in odp file. It correctly works and shows to Input Korean Hangul Syllable in odp file. It can combine Korean Hangul Final Consonant on specific Hangul Syllable '가' on LibreOffice Impress. example) 반갑습니다 각 (ㄱ + ㅏ + ㄱ) 간 (ㄱ + ㅏ + ㄴ) 갇 (ㄱ + ㅏ + ㄷ) 갈 (ㄱ + ㅏ + ㄹ) 감 (ㄱ + ㅏ + ㅁ) 갑 (ㄱ + ㅏ + ㅂ) 갓 (ㄱ + ㅏ + ㅅ) 강 (ㄱ + ㅏ + ㅇ) 갖 (ㄱ + ㅏ + ㅈ) 갗 (ㄱ + ㅏ + ㅊ) 갘 (ㄱ + ㅏ + ㅋ) 같 (ㄱ + ㅏ + ㅌ) 갚 (ㄱ + ㅏ + ㅍ) 갛 (ㄱ + ㅏ + ㅎ)
I tested it on openSUSE Tumbleweed and KDE Plasma Desktop and fcitx-hangul(IME).
Created attachment 148785 [details] I also found the bug in LibreOffice 6.1.3.2 on openSUSE Tumbleweed and GNOME 3.30.2. I also found the bug in LibreOffice 6.1.3.2 on openSUSE Tumbleweed and GNOME 3.30.2. This is capture thread.
Hi DaeHyun, Can you paste the information list in "Help / About" here? Also I wonder if 6.0 series has the same bug? Knowing the earliest version that the issue is reproducible allows bibisecting the issue. Other QA people might help but it really needs knowledge of Korean language. I have no knowledge about Korean IME, it will be good if you can explain how to enter the following symbols fcitx-hangul ( or how to use that IME, to the extent just enough for reproducing that issue ): 1. ㄱ 2. ㅏ 3. ㅂ
(In reply to Mark Hung from comment #6) > Hi DaeHyun, > > Can you paste the information list in "Help / About" here? > Also I wonder if 6.0 series has the same bug? Knowing the earliest version > that the issue is reproducible allows bibisecting the issue. Other QA people > might help but it really needs knowledge of Korean language. Version: 6.1.4.2 Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: kde4; Locale: ko-KR (ko_KR.UTF-8); Calc: group threaded https://gerrit.libreoffice.org/plugins/gitiles/core/+log/9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 also other version shows the same bug (openSUSE tumbleweed default version) 버전(Version): 6.2.0.3 빌드 번호(Build ID): 20(Build:3) CPU 스레드(CPU threads): 8; OS: Linux 4.20; UI 표현: 기본; VCL: gtk3_kde5; 지역 설정(Locale): ko-KR (ko_KR.UTF-8); UI-Language: ko-KR Calc: threaded > > I have no knowledge about Korean IME, it will be good if you can explain how > to enter the following symbols fcitx-hangul ( or how to use that IME, to the > extent just enough for reproducing that issue ): > 1. ㄱ > 2. ㅏ > 3. ㅂ If you want to input the Korean Syllable '갑'(code point: U+AC11) step1. Input the Hangul Consonant 'ㄱ'(code point: U+1100) step2. Input the Hangul Vowel 'ㅏ'(code point: U+1161) step3. then, Input the Hangul Consonant 'ㅂ'(code point: U+1107) step1 & step2 is normal working. but, In Korean IME, step3 check step2, If step2 is vowel or consonant. If step2 is vowel then step3's consonant change the code point (Final Consonant code point: 'ᆸ' U+11B8) But, In step2 is not vowel, then step3's consonant not change it and shows Consonant 'ㅂ'(code point: U+1107) -> That's LibreOffice's situation I think, LibreOffice interferes with checking the process of confirming whether consonants are initial consonants or final consonants in Korean IME . ------ fcitx-hangul is based on libhangul library. libhangul repository: https://github.com/libhangul/libhangul Below is libhangul example link. (GNOME Korea git repository) https://gitorious.org/gnome-korea/gnome-tech-talks/trees/master/2012.03/hwanjin?p=gnome-korea:gnome-tech-talks.git;a=commit;h=9f6fd6efb890f395d5061bbeb4a0f4e697f7bc16 https://gitorious.org/gnome-korea/gnome-tech-talks/trees/master/2012.03/hwanjin?p=gnome-korea:gnome-tech-talks.git;a=blob;f=2012.03/hwanjin/gnome-tech-talk-libhangul.pdf;h=0d34be256f3592b546d6894d586b1b840eb74980;hb=9f6fd6efb890f395d5061bbeb4a0f4e697f7bc16 That link is last year's GNOME Korea meetup slide. (Summary of Korean Hangul Input processing) https://www.slideshare.net/gnomekr/20180519-hangul-processing Many of Korean IME is based on libhangul library. If I have a time, I'll summarize and write the Korean IME working English version document.
appendix Korean input overview in the linux desktop (GNOME Korea) https://www.slideshare.net/gnomekr/korean-input-overview-in-the-linux-desktop
Created attachment 148811 [details] No problem on LibreOffice 5 and Kubuntu No problem on LibreOffice 5 and Kubuntu screen capture It works to font rendering correctly in LibreOffice 5. Libreoffice version Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial3 CPU Threads: 1; OS Version: Linux 4.13; UI Render: default; Locale: ko-KR (ko_KR.UTF-8); Calc: group
(In reply to DaeHyun Sung from comment #5) > Created attachment 148785 [details] > I also found the bug in LibreOffice 6.1.3.2 on openSUSE Tumbleweed and GNOME > 3.30.2. > > I also found the bug in LibreOffice 6.1.3.2 on openSUSE Tumbleweed and GNOME > 3.30.2. > This is capture thread. the bug in LibreOffice 6.1.3.2 on openSUSE Tumbleweed and GNOME 3.30.2. Information Version: 6.1.3.2 Build ID: 10(Build:2) CPU threads: 1; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (ko_KR.UTF-8); Calc: group threaded
Hello DaeHyun Sung, Does it work if you launch LibreOffice from commandline with SAL_USE_VCLPLUGIN=gtk soffice ?
Dear DaeHyun Sung, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear DaeHyun Sung, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp