Community
Participate
Working Groups
I see a lot of \ in my localized Dutch Eclipse. When translating through the webinterface, I notice strings like the following: '=\' operator I am pretty confident this cannot be correct. I suppose it should be \'=\'. An easy workaround for this would be to enter the 21st century and use proper curled unicode quotes instead, so no more need for escaping: ‘=’
More cases: in the Breakpoint view in the debugging perspective: AutomatonTester\ [ingang] - evaluation() Note the \. I suppose the relevant string looks like this: ‘\ [ingang]’. I suppose the English one is ‘ [entry]’. The backslashes seem to be added by the web interface when showing the original string. Translators then are inclined to take them over, since they do not know what they are for. I also see them in the ‘Type proposals’ popup which comes up in the Java Editor, even quoting totally innocent characters: ‘ListIterator\ -\java.util’
Is this related to bug 227366?
(In reply to comment #2) > Is this related to bug 227366? Looks like it, although I don’t understand enough to be sure. An example is the string searchCategories.updates.desc in org.eclipse.update.ui/plugin.properties. It seems like this is not only due to linebreaks, although it could be. Also, I notice that if I remove the backslashes in the translation, the result is formatted nicely in the preview in the middle, whereas if they are there, it is rendered as-is.
Hendrik, We think this is related to bug 222660. Can you start launch a fresh copy of Eclipse and install the Dutch language pack from this update site, and see if the problem is solved: For Eclipse 3.4 : http://build.eclipse.org/technology/babel/test-updates/ganymede/ Thanks
(In reply to comment #4) > Hendrik, > > We think this is related to bug 222660. > > Can you start launch a fresh copy of Eclipse and install the Dutch language > pack from this update site, and see if the problem is solved: > > For Eclipse 3.4 : > http://build.eclipse.org/technology/babel/test-updates/ganymede/ I’ve been testing with two 3.3 releases from this site and it looks fine on both.
