Bug 545466 - Thai character rendered incorrectly
Summary: Thai character rendered incorrectly
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.11   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-16 06:26 EDT by Peter Nickut CLA
Modified: 2023-04-09 13:45 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nickut CLA 2019-03-16 06:26:13 EDT
In Eclipse version 4.10, 4.11 it is not anymore possible to use unicode characters in string constants.

steps to reproduce:
- copy following String constant with a thai charactar into Java text editor 
  String s1 = "มื่";
- after pressing the Enter key it is transformed to:
  String s1"มื่"

This worked fine with Eclipse Oxygen and strangely it also works fine with Version  4.10 if the workspace was created with an older version of eclipse.
Comment 1 Dani Megert CLA 2019-03-22 11:25:59 EDT
Something is strange. It's not always reproducible.
Comment 2 Eclipse Genie CLA 2021-03-12 04:07:51 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-04-09 13:45:48 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.