RDp to handle special character in RPG

Unfortunately there is no solution at this time. The EBCDIC control characters used in the green screen environment have no specified visual representation in Unicode and it is left up to each operating system to decide how to render them. RD Power uses OS font libraries, so is directly impacted when an OS changes its renderings (which Microsoft did, starting at Vista and perpetuated in Windows 7). Our team spent a few months going back and forth with Microsoft to see whether they could provide a solution but they maintain that the behaviour is working as designed.

So the exact behavior you are seeing is inherent to Windows. Behavior might be different on a Linux desktop (or Team server) but it would not be surprising if some unwanted behavior occurred.

Any work-around we might implement in RD Power would be extremely costly and would drive out work that the broader customer community has given high priority. That is why the PMR was closed as a limitation. You could open a new RFE if you would like to see RD Power strip these hex codes from their source members (or vote for an existing RFE if one is already outstanding).

As a work-around you could do a Find/Replace of the hex characters in their source members. Perhaps you could even create a Pluglet that would do this in a more comprehensive, automated way (i.e. per Project or Workspace), perhaps even based on a mapping table you define.

Unfortunately there is no solution at this time. The EBCDIC control characters used in the green screen environment have no specified visual representation in Unicode and it is left up to each operating system to decide how to render them. RD Power uses OS font libraries, so is directly impacted when an OS changes its renderings (which Microsoft did, starting at Vista and perpetuated in Windows 7). Our team spent a few months going back and forth with Microsoft to see whether they could provide a solution but they maintain that the behaviour is working as designed.

So the exact behavior you are seeing is inherent to Windows. Behavior might be different on a Linux desktop (or Team server) but it would not be surprising if some unwanted behavior occurred.

Any work-around we might implement in RD Power would be extremely costly and would drive out work that the broader customer community has given high priority. That is why the PMR was closed as a limitation. You could open a new RFE if you would like to see RD Power strip these hex codes from their source members (or vote for an existing RFE if one is already outstanding).

As a work-around you could do a Find/Replace of the hex characters in their source members. Perhaps you could even create a Pluglet that would do this in a more comprehensive, automated way (i.e. per Project or Workspace), perhaps even based on a mapping table you define.