Korean Language Mishaps

Bug #1543571 reported by sameum on 2016-02-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently on OpenLP 2.2, if you use Korean, the program seems to recognize each character/letter as individual words and will wrap incorrectly when the word length exceeds the screen width.

For example:
태초에 하나님이 천지를 창조하시니라!

Will become:
태초에 하나님이 천지를 창조하시

Notice how the last word was cut in an odd spot.

It should be like this:
태초에 하나님이 천지를
창조하시니라 !

To Korean view
ers this is ha
rd to read and
 makes the bib
le function im
possible to us
e :)

Keep up the awesome work!

sameum (sameum) wrote :
tags: added: language
description: updated
Phill (phill-ridout) on 2017-10-09
Changed in openlp:
importance: Undecided → Low
importance: Low → Medium
Phill (phill-ridout) wrote :

Hi Sameum,

To a non Korean speaker this issue is a little difficult to understand. I've done some research, and it seems in certain situations like the text should only be broken on white space, while in other cases its permissible to break in word (between syllables)

https://www.w3.org/TR/css-text-3/#line-breaking has this to say:
"As another example, Korean has two styles of line-breaking: between any two Korean syllables (word-break: normal) or, like English, mainly at spaces (word-break: keep-all)."

http://nojeokhill.koreanconsulting.com/2013/05/korean-translation-tip-cardinal-rules-of-korean-language-layout.html Suggests that its all to do with alignment, and if the text is 'professional' or 'friendly' (see comment)

So there are a few options to fix this:
1. Always break on the white spaces. (Maybe with an option to turn this off or on)
2. Set in the theme
    A. Based on the alignment
    B. As an option independent of the alignment?

The following link is detailed and maybe of use (I have not read all through it yet!) http://www.unicode.org/reports/tr14/tr14-37.html

Raoul Snyman (raoul-snyman) wrote :

I just tested out Phill's CSS in WebEngine, and without the "keep-all" it breaks the Korean incorrectly, but with it everything works. I tested it with English too, and the English is fine, so I reckon we should put this into our CSS.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers