Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 379074

Summary:

[GTK] DBCS4.2: A semi-voiced sound mark disappears in button controls

Product:

[Eclipse Project] Platform

Reporter:

Masaihko Maedera <maedera>

Component:

SWT

Assignee:

Platform-SWT-Inbox <platform-swt-inbox>

Status:

CLOSED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

arunkumar.thondapu, camle, ericwill, harendra, kennoji, maedera

Version:

4.2

Keywords:

triaged

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Java Project	none
bug379074.zip	none

Description Masaihko Maedera

2012-05-10 01:06:36 EDT

Build Identifier: I20120503-1800

I will update this report after the system assigns a bug number.

Reproducible: Always

Comment 1 Masaihko Maedera

2012-05-10 01:14:22 EDT

Created attachment 215375 [details]
Java Project

Description:When a combining character, semi-voiced sound mark locates at the last of string, this character is truncated in SWT controls.
OS: RedHat Linux 6
JDK: 1.7.0 IBM
Locale:Japanese

Steps to recreate problem:

1. import bug379074.zip
2. run src/Bug379074.java
3. compare the button with images/expected.png or images/unexpected.png
4. In my RedHat 6, the last semi-voiced sound mark disappears
   at the third character like as unexpeced.png.
5. This may not be a SWP bug. but I hope you investigate the reason. 
   This also happens on other controls.
6. I created the button control as follows

Button button = new Button(shell, SWT.PUSH);
button.setText("\u304b\u309a\u304b\u309a\u304b\u309a");

Comment 2 Masaihko Maedera

2012-05-10 01:15:29 EDT

Created attachment 215376 [details]
bug379074.zip

Comment 3 Eric Williams

2018-11-30 11:29:23 EST

Still reproducible with SWT from master as of today, Fedora 29, and GTK3.24.

Comment 4 Eric Williams

2018-11-30 14:53:55 EST

(In reply to Eric Williams from comment #3)
> Still reproducible with SWT from master as of today, Fedora 29, and GTK3.24.

Oops, I posted this on the wrong ticket. I cannot actually reproduce this bug, on the environment above.