Issue 82170

Summary: Autocomplete display double character for this word [CTL / Thai]
Product: Writer Reporter: samphan
Component: editingAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P4 CC: arthit, hdu, hin.stone, issues, jjc, markpeak, pocha, samphan, sirapat, suparoek
Version: OOo 2.2   
Target Milestone: ---   
Hardware: All   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 41707, 92549    
Description Flags
Text after autocomplete should look like this.
Incorrect real result, before and after pressing ENTER none

Description samphan 2007-10-02 10:11:05 UTC
1.Open a blank Writer document.
2.Switch keyboard to Thai.
3.Type text “มิถุ” by press “,b5”.
4.The function autocomplete will display the full word.

Expect result:
This function should display the text as “มิถุนายน”.

Real result:
It displays the text with the second character doubled and overlapped.
(See the pictures)
Comment 1 samphan 2007-10-02 10:13:46 UTC
Created attachment 48645 [details]
Text after autocomplete should look like this.
Comment 2 samphan 2007-10-02 10:16:12 UTC
Created attachment 48647 [details]
Incorrect real result, before and after pressing ENTER
Comment 3 samphan 2007-10-02 10:19:35 UTC
Please note that, AFAIK, this only happen for this particular word 'มิถุนายน'.
Comment 4 eric.savary 2007-10-02 14:22:14 UTC
Reassigned to SBA
Comment 5 stefan.baltzer 2007-11-07 18:23:13 UTC
SBA: If this happens only to this particular word, then this issue should be
Prio 4. -> Changed.
Reassigned to HDU.
Comment 6 2008-09-16 15:18:00 UTC
@fme: I suggest to autocomplete only at cell boundaries. Splitting cells into different portions is not 
Comment 7 tantai 2008-09-29 11:55:22 UTC
I find more test cases for this bug

A) switching font style inside a cluster
Step to reproduce :-
1.Open Writer
2.Switch keyboard to Thai
3.Type the character “ก” (by pressing “d”)
4.Then change font style, e.g. Bold or Italic
5.Type the character “ ิ” (by pressing “b”)

B) add a non-base character in record change mode
Step to reproduce :-
1.Open Writer
2.Type some word in Thai
3.Choose Edit > Changes > Record
4.Type the character “ ่” (by pressing “j”)
Comment 8 tantai 2010-12-07 04:04:31 UTC
This problem occurs when some text is splitted into 2 runs. if a non-spacing
vowel mark (e.g. ุ) is placed at the first character of the second run, the text
will be displayed overlap. But the problem will occur in the first (regarding
position in the document) autocompleted word in a document. I've pasted 2
snipplets of content.xml to show examples:-

A: Western autocomplete case:
<text:p text:style-name="Standard">January</text:p><text:p

B1: Thai autocomplete case with overlapped text:
<text:p text:style-name="Standard">มิถ<text:span text:style-name="T1">
ุนายน</text:span></text:p><text:p text:style-name="Standard"><text:span

B2: Thai autocomplete case without problem:
<text:p text:style-name="Standard">กรก<text:span text:style-name="T1">
ฎาคม</text:span></text:p><text:p text:style-name="Standard"><text:span

You will see that, in case B1 and B2, the first autocompleted word (e.g.
"มิถุนายน") is splitted before the vowel mark (ุ). But in the second autocompleted
word (e.g. "มิถุนายน"), the entire autocompleted word is placed in the text:span
element. OOo seems not to be able to display non-spacing mark at the begining of
a text run so that's why the text is displayed overlapped.

Note that the splitted autocompleted word always happend if you insert the word
before any other autocompleted word. That is, it happend only for the first
occurance of such autocompleted words.

My questions are:
1) the text:style-name="T1" is used in Thai (or every CTL?) autocomplete case
but not in Western case. What's it for?
2) I guess the <text:span text:style-name="T1"> element should actually span the
whole autocompleted word like this <text:span text:style-name="T1">
มิถุนายน</text:span>, right?
Comment 9 tantai 2010-12-13 05:37:40 UTC
I move the case in the comment #8 to a new issue