|
Hey Adam, I've added it to the list of requirements for iSeries projects. Thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 05/25/2006 12:20:18 PM:
Good question. The encoding for a file or a container is something that
is
set at the underlying Eclipse platform level. I didn't see an option to
set
the default for the workspace on a quick tour through the preferences. Anyone else see one? If not, we'll add this to the list of enhancement
for
iSeries Projects. _______________________ David Dykstal david_dykstal@xxxxxxxxxx
AGlauser@erbgroup
.com
Sent by:
To
wdsci-l-bounces@m Websphere Development Studio
Client
idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
05/25/2006 10:57
Subject
AM Re: [WDSCI-L] Hex codes in
position
5 are being mangled
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Worked like a charm. Three cheers for Unicode! To save searching through the prefs, is there a way to set the default encoding for projects? If you don't know offhand I can go pref-diving. Thanks, Adam wdsci-l-bounces@xxxxxxxxxxxx wrote on 24/05/2006 04:47:47 PM:Try changing the project's text encoding to UTF-8. You'll find thisunderthe project's properties -> info. It will probably say something like "inherited from container (Cp1252)". My guess is that you'll have to re-download the members that use the
hex
codes, but uploading them should then work if they are stored locallyusingUTF-8. Round-tripping of the hex codes doesn't work if the local code page is Cp1252 (in fact, it looks like they are changed on download). The hexcolorcodes are problematic in general - since they are control characters(5250attributes) they fall outside of the range of most code pageconversions._______________________ David Dykstal david_dykstal@xxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.