German Umlaut Encoding isn't always working in 2018-09 with ADT 3.0.2

[jamesmorrison]

Hi everyone.

My colleagues and I found a problem with character encoding with ADT 3.0.2 tested in Eclipse Photon, 2018-09 and also 2018-12.

Version 2.102.5 of ADT doesn't have that problem.

Setting the Encoding from default (CP1252) to UTF-8 and reopening the file fixes the problem. Even switching back to CP1252 fixes the problem too.

The error reappears with a complete new workspace.

While the workaround works, we are afraid that at some point a developer forgets to apply it.

And then edits a file with encoding problems and persists them on the SAP server for real.
If the problem occurs in string literals, which I cannot confirm at this point, but is very likely this could potentially inflict faulty run-time behavior.

Is this something the SAP-ADT-Team can fix please?

Cheers, André

Detailed Version information:

[pokrakam]

I am also experiencing this. Actually you don't need to switch codepage, just close and reopen the class/report/whatever.

Just for fun, try UTF-16. Instead of just garbled Umlauts, you sometimes get the whole shebang, like: 䙕乃呉低⁃䡁乇䕟偏䥎呅剓彃剅䅔䕟䱏乇ഊ†䥍偏剔䥎䜍ਠ†⁖䅌啅⡃䡁乇䕟䑏䍕䵅乔彈䕁䑅利

Again, just close and reopen.

It worked fine with Eclipse Oxygen on the same SAP systems. I'm conecting to different SAP versions and the issue appears everywhere, so am sure it's local. I don't know if it's Eclipse or ADT as both have been upgraded before I started noticing this.

Perhaps thomasfiedler could ping the team?

[pokrakam]

FWIW, I just noticed an even quicker way to get rid of the garbled encoding is to just reload by pressing F5.

It's still a nasty little bug, because once someone opens that 2000 line legacy report riddled with German comments and saves, the garbage becomes pernament.

[jamesmorrison]

Thanks for the pointer with pressing F5 Mike.

[jamesmorrison]

I have created a SAP support incident.

.

[marcus_hoepfner]

Hi,

thanks for reporting this issue.

Also thanks for the incident.

We will track the issue in the incident then.

Kind regards, Marcus

[pokrakam]

Unfortunately the latest update to ADT 3.0.5 still doesn't resolve it.

[jamesmorrison]

Reads promissing.

[pokrakam]

Bit of a version jump in today's update to 3.2.3. Sadly it's still broken.

[pokrakam]

...aaaand followed closely by a swift update to 3.2.4. Still broken.

[jamesmorrison]

Very unfortunately confirmed. 😞

I wrote back to SAP via the incident ticket.

[pokrakam]

Let me guess, your ADT debugger no longer works either?

[jamesmorrison]

Nope, works fine for me, but I am on Eclipse 2018-09 and ADT 3.2.4.
You are on 2018-12, I read.

[jamesmorrison]

Just tested 3.2.5 and it fixes the problem.
Thanks SAP and Mike for sticking with me on that one.

[pokrakam]

Hurraah! Yes indeed it does, thanks SAP! I'm going to go and have a drink now... OK, maybe later.

Seriously, this bug had me so on edge lest I accidentally save a corrupted version. Well, I wouldn't be surprised if I did, but then again texts belong in text elements and comments should be in English anyway...