Hi Frank,

Frank Schönheit - Sun Microsystems Germany wrote:
Hi Eike,


conflicts during cws resync caused by this change. In this case convert
your new / changed strings to UTF8.

Dumb question: how do I do this?

Dull answer: use an editor ;-)
...


Well, what I like about the concept of an "Integrated Development
Environment (IDE)" is the word "integrated" ....

(and no, neither my IDE's editor nor my fallback editor (TextPad)
currently seem to recognize UTF-8 :( )


I don't know what IDE you use. My msdev opens resources files well.

Let me rephrase this: When such a change was first discussed, there was
the idea to use files which somehow indicate they're UTF-8, IIRC with
some signature bytes at the beginning, something like this. It was said
that this would enable more editors to properly handle those files. What
became of this idea?

Every editors writes those "Byte order marker" while saving the document in UTF8. Or lets say nearly all ;)



I'm not really objecting the change as such, I suppose it solves a lot
of problems for people L10N'ing OOo. However, to me it seems to create
new problems for other people (well, developers). This is okay in
general, provided that the sum of hassles decreased (it's bad luck then
that now some of us developers have the hassle to do additional
conversion steps or change to another editor). However, it would have
been nice to address those new problems before doing the change, IMO.

As 95% of all editors are able to read/write UTF8 I didn't saw any reason to do so.


Anyway. If German is removed from the files, the problems would vanish.
However, I'm still waiting for the answer how this interacts with our
current feature implementation process, which requires us developers to
specify and implement the German strings from the beginning.


For other editors, if they're not able to cope with utf-8, you may
always type and save your text in latin1 respectively cp1252 and use the
``recode'' utility to convert, e.g. ``recode latin1..utf-8 filename''
respectively ``recode cp1252..utf-8 filename''. However, I'd suggest
switching editor in this case ;-)


"recode" is not known in my development environment ...
(yeah, I can probably obtain it somewhere. Again: Would have been nice
to address those issues *beforehand*.)

Ciao
Frank


Cheers,
Ivo

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to