eclipse-uml2 / uml2

An EMF-based implementation of the UML 2.x metamodel for the Eclipse platform.
Eclipse Public License 2.0
5 stars 4 forks source link

BiDi3.2: node naming problem when the name starts with a digit. #18

Open eclipse-uml2-bot opened 7 hours ago

eclipse-uml2-bot commented 7 hours ago

| --- | --- | | Bugzilla Link | 133152 | | Status | NEW | | Importance | P3 normal | | Reported | Mar 24, 2006 09:20 EDT | | Modified | Oct 05, 2010 16:16 EDT | | Version | 2.0.0 | | Depends on | 160682 | | Reporter | Ahmed Farrag |

Description

Steps to recreate the problem:

  1. Set your locale to Arabic Egypt.
  2. Open a UML2 model from Example EMF Model creation wizard.
  3. In the properties view, name the "Profile" node with an name that starts \ with a digit.
  4. Observe the resulted name in both, the properties view and the Resource set \ view.\ Problem:\ The digits are not displayed using national numerals.\ The digits are not placed next to the profile name (due to the contexual behaviour). Please see attached image for further describtion.\ expected behaviour:\ digits should be displayed using national numerals.\ the digits are supposed to appear to the left of the node name.
eclipse-uml2-bot commented 7 hours ago

By Ahmed Farrag on Mar 24, 2006 09:22

Created attachment 36885 screen capture

uml2.JPG

uml2.JPG

eclipse-uml2-bot commented 7 hours ago

By Ahmed Farrag on Mar 26, 2006 10:07

Similar behaviour is found under GMF.\ Steps to recreate this problem under GMF:\ 1- Go to file->new->Other .. ->Example EMF Model Creation wizard -> EXTLibrary Model and hit next\ 2- Click next, select any existing project, and select Library as a root element, and UTF-8 for the encoding.\ 3- Click finish to close the wizard.\ 4- create some child nodes and try naming them in a similar way.

eclipse-uml2-bot commented 7 hours ago

By Kenn Hussey on Mar 27, 2006 18:07

Given that this problem occurs in different projects, it's likely that it is a platform (jface?) issue.

eclipse-uml2-bot commented 7 hours ago

By Eric Moffatt on Mar 28, 2006 15:05

Karice, not sure if this is yours but could you please check it out?

eclipse-uml2-bot commented 7 hours ago

By Karice McIntyre on Apr 04, 2006 20:04

This is not a UI/JFace issue. Basically, you need to call org.eclipse.osgi.util.TextProcessor.process(label, "<>") \ to get the indicated string to render correctly. The problem is there is mixed RTL and LTR text and the neutral characters are not rendered properly on windows platforms.

eclipse-uml2-bot commented 7 hours ago

By Matitiahu Allouche on Apr 09, 2006 10:50

In response to comment #1, it seems that the sample profile name contains digits at both ends. Unfortunately, these are the same digits (123) so that it is not possible to see which digits are displayed on which side. The example would be more instructive if different digits were appended on each side.

Also, it would be nice to have not only a screen capture of the wrong display but also of the required display (generated by whatever hacks are appropriate).

eclipse-uml2-bot commented 7 hours ago

By Matitiahu Allouche on Apr 09, 2006 10:54

The required presentation could be achieved by adding an RLM (Right-to-Left Mark, U+200F) before the profile name when the profile name contains letters from a Right-to-Left script.

eclipse-uml2-bot commented 7 hours ago

By Kenn Hussey on May 24, 2006 13:48

This bug has been marked as a duplicate of 132461

eclipse-uml2-bot commented 7 hours ago

By Ahmed Farrag on May 25, 2006 08:45

This defect was opened in a Windows environment against:

1)Contexual behavior, which is not maintained in our case. 2)Disordering of the node name when it starts with digits. As a solution for this problem, you may consider the use of Unicode control characters to make the node names ordred properly.

For the reasons mentioned above, this bug can't be set as a duplicate of 132461.

eclipse-uml2-bot commented 7 hours ago

By Kenn Hussey on May 25, 2006 09:23

OK, keeping as separate bug, but I believe all of these BiDi issues will be resolved once support for text "processing" (see bug 135674) is provided by EMF.