Download it now!
Bug 107718 - Some of old Hangul not rendering faithfully in vertical layout
Summary: Some of old Hangul not rendering faithfully in vertical layout
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) rc
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on: HarfBuzz
Blocks: Vertical-Text
  Show dependency treegraph
Reported: 2017-05-09 09:27 UTC by Volga
Modified: 2020-05-14 03:48 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Test File (11.05 KB, application/vnd.oasis.opendocument.text)
2017-05-09 09:28 UTC, Volga
Screenshot (104.05 KB, image/png)
2017-05-09 09:29 UTC, Volga

Note You need to log in before you can comment on or make changes to this bug.
Description Volga 2017-05-09 09:27:42 UTC
Several Hangul Jamos can conjoining together in horizontal layout, but when I switch into vertical layout, they are failed.

Steps to Reproduce:
1. Open LO Writer
2. Insert -> Frame -> Frame Interactively
3. Copy texts from
4. Select the whole text and using Source Han Sans
5. Set the text vertically in frame

Actual Results:  
Several Hangul Jamos not joined into syllable as my attached image

Expected Results:
All Hangul Jamos should joining into syllable in vertical layout, they should works as the following image:

Reproducible: Always

User Profile Reset: No

Additional Info:

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Comment 1 Volga 2017-05-09 09:28:50 UTC
Created attachment 133182 [details]
Test File
Comment 2 Volga 2017-05-09 09:29:31 UTC
Created attachment 133183 [details]
Comment 3 Buovjaga 2017-05-13 16:18:22 UTC

Font is here:

Arch Linux 64-bit, KDE Plasma 5
Build ID: c0968aa4673a8ac9a8a09a0e291b58b94bdbb35e
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on May 13th 2016
Comment 4 QA Administrators 2018-05-14 02:29:11 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2020-05-14 03:48:57 UTC
Dear Volga,

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 with the latest version of LibreOffice from

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from

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