Download it now!
Bug 97702 - Specific Korean combination appears incorrectly
Summary: Specific Korean combination appears incorrectly
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: CJK
  Show dependency treegraph
Reported: 2016-02-10 07:48 UTC by jasonmallet
Modified: 2017-05-22 23:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description jasonmallet 2016-02-10 07:48:31 UTC
When trying to type "간" into LibreOffice Writer, it always appears as "가ㄴ".  Even when copy/pasting from an external source this happens.  When copy/pasting it from LibreOffice to an external text field, it appears normal ("간").  I have only seen this so far with this specific combination of Korean letters.
Comment 1 Buovjaga 2016-02-12 09:24:56 UTC
Copied from your desc. Not reproduced.

Ubuntu 15.10 64-bit 
Build ID: 1:5.0.4~rc2-0ubuntu1~wily1
Locale: en-US (en_US.UTF-8)

Win 7 Pro 64-bit Version:
Build ID: a6f876d45bd4e41a7143594a6cb11b6893a0f620
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-02-11_00:07:38
Locale: fi-FI (fi_FI)
Comment 2 Hiunn-hué 2016-03-25 21:51:09 UTC
I can reproduce this with "Droid Sans Fallback".

OS: elementary OS 0.3.2 Freya (based on Ubuntu 14.04)
Version: (1:5.1.1~rc2-0ubuntu1~trusty0)
Comment 3 Buovjaga 2016-03-25 21:55:57 UTC
NEW per comment 2.
Comment 4 QA Administrators 2017-05-22 13:20:19 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice 
(5.2.7 or 5.3.3

If the bug is present, please leave a comment that includes the version of LibreOffice and 
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team