[Riyad Kalla]

Darren,
After restart MyEclipse does it still die every time you ever try and do *anything* with the file, or is it just that first time?

Also we fixed a huge number of internationalization issues in 5.0.2 (internal release for our partner in Japanese market) that will be in 5.0.3 plus a whole slew of other bug fixes, so my gut tells me this issue will magically disappear but if we *can* pin it down, I’m all for it.

[tenjin]

Hi,

Yes, whenever I try to open the XML file the problem occurs.

I don’t think this is an internationalisation problem per se as this is still an english character (trademark symbol – tm), it’s just not in the default codepage. That shouldn’t be an issue I guess, as the file opens find in Windows notepad, and the character is displayed correctly.

Is this a UTF-8 problem maybe? The file is saved as UTF-8, so double byte and BOM need to be respected? Just a thought.

Regards

Darren.

[tenjin]

Hi,

Also, just wanted to add that I have not yet successfully opened the file in Eclipse (with MyEclipseIDE installed), although it opened fine Eclipse running on Ubuntu and without MyEclipseIDE installed.

Regards

Darren.

[Riyad Kalla]

Darren,
I’m assuming the difference with the last comment being that without MyEclipse it was opening in the plain text editor right?

[tenjin]

Hi,

Yes, but that was Eclipse on Ubuntu (same versions though).

On the Ubuntu version I also have the Eclipse WTP 1.0 (and associated components) and the Orangevolt EclipseXSLT plugins.

I haven’t tried uninstalling MyEclipse from my windows machine to test it that way.

Regards

Darren.

[Riyad Kalla]

Ok no need, hang in there, I have a feeling 5.0.3 will fix this.

[Author]

Posts