Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Add an option to enable word wrapping for Korean input|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Version:||OOo 1.1 RC3|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description Unknown 2003-08-14 17:24:47 UTC
This issue is about word wrapping for Korean language. I am not sure whether this issue should be in |10n or here; however, I think the issue I am filing on is more appropriate here since it is about word wrapping. I just installed 1.1 RC3. In this version, it seems word wrapping for Korean language are still occuring. Word wrapping for English, French, German and Spanish works fine as I tested it. If a word is not completed at the end of line, then it should be wrapped in the next line. But in 1.1rc3, it still treats each character as single word and does not wrap them at all. I searched help file and it only explains it as a matter of hyphenation. I also posted this problem in user mailing list and many responded that it's a hyphenation problem, too. I tried all different hyphenation options and it is still occuring. FYI, in Chinese and Japanese, word wrapping is not important, since each character could work as one single word or sentence. In contrast, Korean language works like any other Western langueges in the sense of word wrapping. Each vowel and consonant make one character and one or more charaters constitute one word. If word wrapping is based on the empty space between characters or words, then it could be resolved this problem easily, I guess. In vim, if I set format options as :set fo=twa, then I can use vim as any fine wordprocessor in the sense of word wrapping. It wraps any uncompleted word of any languages at the end of line and displays in the next new line. I want this simple and essential features in OOo for Korean language, too. Thanks. -youlgok
Comment 1 khendricks 2003-08-24 14:59:53 UTC
Hi, I am not sure how to respond since I am not sure what the problem is? If you have not installed a Korean hyphenation dictionary then hyphenating under Korean will not work. AFAIK, there is no Korean hyphenation dictionary. But I am unsure if that is the problem you are really seeing. I am changing this to issue to "writer" just in case Korean has some issues with Break Iterator that might need to be worked out. Hope someone there has a better idea of what if wrong here? Kevin
Comment 2 h.ilter 2003-08-26 16:06:40 UTC
To make it easy to reproduce, please attach a bugdoc and/or Screenshot which shows the problem, Thanks.
Comment 3 h.ilter 2003-08-29 13:20:31 UTC
HI->FME: May this issue is for Karl?
Comment 4 frank.meies 2003-08-29 13:39:20 UTC
FME->KHONG: Can you confirm this?
Comment 5 frank.meies 2003-08-29 13:39:28 UTC
FME->KHONG: Can you confirm this?
Comment 6 karl.hong 2003-09-04 01:03:10 UTC
This issue is personal preference issue. Our Korean expert, Vincent, asked to have line break through Korean word, and make alignment on page end. He showed me a Korean magazine, which has page layout like we have, break the words on the end of the line. He also mentioned two popular Korean word processing applications, MS office and Hancom office, MS may do what the submitter asked, while Hancom does what we do. So if we want to fix this problem, we need to have user perference setting for it. Falko or someone has to make decision.
Comment 7 karl.hong 2003-09-05 01:38:37 UTC
More information from Vincent. Hi Karl, I have tried this before with MS, Hancom and HunMin Xp, and I decided to go with no wrapping down feature because MS & Hancom are not wrapping down Korean words like English. Let's say if the C in a korean word ABCD reaches the end of the line, MS Word will just place D in the next line, not wrapping down a whole word ABCD to the next line. However, HunMin Xp does wrapping down whole korean words but this behavior is wrong for Korean words. Most of the publications in Korean are never wrapping down korean characters like English. May be the person filed that bug is using HunMin XP ? I am not sure... Thanks, Vincent
Comment 8 Unknown 2003-09-05 08:22:16 UTC
Thanks for all attention and interest in this thread. I did not know there is Korean expert among OOo.org staffs. I think I need to restate the wording of my previous submitting in this thread. Word wrapping in Korean language is necessary, but in many case it does not wrap since each character could stand itself and it is from the tradition of vertical direction of writing. So word-wrapping should be a choice of writer. When I need Korean language in computer, I have used Hangeul word processor (or Hancom as someone mentioned) for many years as majority of Korean people have. Hangeul word processor does wrap the word automatically. It provides it as option. I attach two screenshots: First one is from Hangeul97 with automatic word-wrapping; Second one is from OOo.org1.1rc3 with non word-wrapped sentences as default and edited word-wrapped same sentences, which is suggested way. If adding this word-wrapping feature for Korean language is not difficult task, I really want OpenOffice to have this necessary feature in coming release. Thanks. -youlgok
Comment 9 Unknown 2003-09-05 08:24:43 UTC
Created attachment 9026 [details] screenshot of word-wrapping in hwp97
Comment 10 Unknown 2003-09-05 08:26:43 UTC
Created attachment 9027 [details] screenshot of ooo1.1rc3
Comment 11 falko.tesch 2003-09-05 14:42:39 UTC
Hi, thanks for providing the screenshots. From what I learned about Hangul writing it is _not_ common to do word-wrapping and there is no hyphenation in Korean anyway. Word cannot disable word wrapping in Korean (at least I cannot find a way to disable it). Hancom is not word-wrapping by default (right?). Frankly spoken you are the first to complain about this issue and browsing through various Korean Internet sites does not show word-wrapping at all. I will have a look through some Korean books at home later to see if these use word-wrapping.
Comment 12 acli 2003-09-13 05:38:54 UTC
If this enhancement is ever implemented for Korean, it might probably make sense to consider also implementing it for Chinese (and perhaps Japanese) in some form (perhaps by having a feature where a group of chracters can be grouped as a word). If word-wrapping for Korean is rare, word-wrapping for Chinese is even rarer, but it is a legitimate typographical style and users do want to do it from time to time (though they might not be able to describe it as word-wrapping and therefore would not look for such a function in the word processor, esp. since no word processor seems to be able to do it).
Comment 13 shinjs 2003-09-20 01:37:56 UTC
> But in 1.1rc3, it still treats each character as single > word and does not wrap them at all As written by others, this is the correct standard behavior for Korean text no matter what the misinformed author of UAX #14 claimed in http://www.unicode.org/reports/tr14. (UAX #14 wrote that there are two line breaking methods *both* widely used). Some Korean texts ( less than 1%, I guess) use 'per word' wrapping that you want to be implemented by OO, but the vast majority of Korean texts in print use 'per syllable' wrapping with some prohibition rules as well outlined in UAX #14. (You can go to a nearby bookstore and pick up several books and magazines and see how lines are broken.) What HWP97 lets users do is not standard and should be given a very low priority. If ever implemented, the option has to be hidden deep inside so that only the die-hard users can find the feature and use it. > In vim, if I set format options as :set fo=twa, then I can > use vim as any fine > wordprocessor in the sense of word wrapping. It wraps any > uncompleted word of > any languages at the end of line and displays in the next > new line. I want this simple and essential features Oh, come on. This is NOT a feature of Vim BUT a bug of Vim. It's in my TOFIX list for Vim. By default, Vim should break lines at any syllable boundaries for Korean.
Comment 14 falko.tesch 2003-10-01 16:17:06 UTC
Add an option to enable word wrapping for Korean input.
Comment 15 ace_dent 2008-05-16 02:38:04 UTC
OpenOffice.org Issue Tracker - Feedback Request. The Issue you raised has the status 'New' pending further action, but has not been updated within the last 4 years. Please consider re-testing with one of the latest versions of OOo, as the problem(s) may have already been addressed. Either use the recent stable version: http://download.openoffice.org/index.html or consider trying the new OOo 3 BETA (still in testing): http://download.openoffice.org/3.0beta/ Please report back the outcome so this Issue may be Closed or Progressed as necessary - otherwise it may be Resolved as Invalid in the future. You may also wish to search for (and note) any duplicates of this Issue that may have advanced further by checking the Issue Tracker: http://www.openoffice.org/issues/query.cgi Many thanks, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 16 bettina.haberer 2010-05-21 14:51:50 UTC
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".