Hi All,

Following on from my recent foray into RDi plugins, where I wrote a plugin
that ( amongst other things ) allowed me to insert the beginnings of a
highlighted comment ( double slash followed by CCSID 37 x'22' {=Unicode
0082} to allow me to continue to define comments which would stand out for
the bulk of programmers where I work who still use STRSEU...

I noticed that if I was working offline in an iProject, if I insert
character I get an error when I try to save the member ( locally ) I'm
assuming that there is no translation from x'22' in CCSID37 to the default
text file encoding for the project which is 1252.

Looking at the iProject Properties I can see under Resource that the Text
File Encoding is set to "Inherited from Container Cp1252 )

Well, I'm not exactly sure what the container is in this case...
I can change the encoding here to ISO-8859-1 and that then allows me to
save the member once I have inserted the above character.

"Query Hex" shows the character as 0082 which is correct.
Hex view, with it's 3 views shows:
Unicode 0082,
Source Encoding Cp037 22
But continues to show Native Encoding 1252 3F.

I guess that view is hard-wired to 1252 and doesn't update to reflect any
changes to text file encoding.

Anyway, my question is - is there anywhere at a higher level that I can set
this up to use ISO-8859-1 which can handle the character?

If you auto-create an iProject, as happens when you select one or more
source files from RSE and say "make available offline" then the source
members will be downloaded and that particular character modified before
you have a chance to say you want the local text files in ISO-8859-1 and
not Cp1252.

Sorry I'm kinda new to iProjects.

Thanks kindly,

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

This mailing list archive is Copyright 1997-2022 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.