Re: Removing of Hex Characters in Source members

Hi Jim,

When downloading members in RSE, UTF-8 encoding is used. There is no way to
change this.  The hex characters should make the round-trip
(download-edit-save-upload) without getting corrupted.
When in LPEX, you will not see the effects of these hex values - they do
not impact the parser tokenizing (although we do have a requirement for
this).
These hex values sometimes have a character representation, and so you may
see a period '.'  or a question mark '?' or some other character where
these hex values are encountered (it also varies depnding on the font
selected in Remote Systems LPEX Editor).

iSeries projects do not always use UTF-8, and allows you to select the
encoding you want for the project.  This is so you can launch tools like
CODE Editor or CODE Designer, which do not support UTF-8 encoding for PC
files.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab


wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/27/2006 03:48:17 PM:

I know this was discussed  back in May for iSeries Projects, but is there

any other place the Text File Encoding can be changed?

We are not using the iSeries Project perspective, just the Remote System
Explore perspective (plus I've gone into the
Windowq>Preferences>Workbench>Editors  panel and change the "Text file
encoding" to be UTF-8" like what was discussed in the archives) and this
didn't help.

Maybe I should be asking if the RSE perspective and LPEX editor use this
value or is there some thing like this that can be set for them?

What I found stranger is that even if I do not save the source back to

the

file the Hex Codes are stripped out an dreplaced with "?".  Not trying to

beat a dead horse but we have several people that  use highlighting and
Hex Codes that "need" this to be there for the moment, or they are likely

not to switch till PDM is pried from their cold dead hands.

Thanks,

Jim Lowary
System Analyst, Salton Inc.
(573) 447-5500