× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

thanks for checking!

I will try to explain exactly how it looks. I have two source files. I have
tried different CCSID and it seems it has no influence
here. At the moment one file has CCSID(1141) and another has CCSID(273). In
both files there is a member with line like:

D VO C CONST('üJKLMNOPQR')

When I open it in LPEX editor it looks fine. I did a test with different
encoding setting for entire workspace and it seems it
also does not have influence on the issue. The only problem is when I try
to use compare editor. The result is like this:

D VO C CONST('�JKLMNOPQR')

ü (0xC3BC) is converted to � (0xef 0xbf 0xbd REPLACEMENT CHARACTER). What
is more, when I make some changes
in compare editor and save the member, it is saved with wrongly encoded
characters. It is not a problem when special character
is in comment section but in this case it changes program's logic as well.

The same member opened in LPEX editor after save in compare editor:

D VO C CONST(' JKLMNOPQR')

Best Regards,
Lukasz.



2017-11-16 8:34 GMT+01:00 Thomas Raddatz <thomas.raddatz@xxxxxx>:

So far I am lost with reproducing the problem, because for me using a
source file with encoding 1208 (UTF-8) does not work at all.

Here is what I tried to reproduce the problem:

1) Precondition: my workspace is set to Cp1252, which is the default
Windows encoding
2) Started the test case with creating a source physical file like this:
crtsrcpf raddatz/qsrc1208 ccsid(1208)
3) Added two fresh members.
4) Started the iSphere compare editor and got nothing but garbage.
5) Opened the members with the Lpex editor and got the same garbage.
6) Changed workspace encoding to utf-8.
7) Removed the members from the "RemoteSystemsTempFiles" folder.
8) Opened the members with the Lpex editor and got the same garbage again.

When I debug the iSphere compare editor, then the downloaded resource
files are reported as UTF-8:

System.out.println(((IFile)fLeftResource).getCharset());

But when I open the files, I cannot properly decode them with Notepad++.
All I see is garbage. Hence I am sure it is not utf-8.

iSphere uses the "QSYSEditableRemoteSourceFileMember.download(IProgressMonitor
monitor)" method for downloading the members and I expect that the Lpex
editor does it the same way. I wonder whether the problem is in
QSYSEditableRemoteSourceFileMember.

Last but not least I did my tests with RDP 8.0 and RDi 9.5.1.2 with the
same results.

Did I do or understand something wrong?

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von Zyto45
Zuzel
Gesendet: Mittwoch, 15. November 2017 11:36
An: wdsci-l@xxxxxxxxxxxx
Betreff: [WDSCI-L] iSphere compare editor encoding issue

Hi,

I am experiencing some issues while using iSphere Comprae Editor (3.1.1.r)
on sources which contain special characters encoded in UTF-8. My workspace
setup in RDi is set to UTF-8 but still when I use compare editor all
unicode characters are replaced by substitute character (SUB). It seems
like compare editor is not using UTF-8 encoding. I could not find any
configuration that would change this behavior. Do you have any idea if it
is possible to force UTF-8 encoding in compare editor?

Thanks!
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a criminal
offence. Please delete if obtained in error and email confirmation to the
sender.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.