Hi Frank, On Wed, Oct 19, 2005 at 12:42:47 +0200, Frank Schönheit wrote:
> > 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 ;-) For Vim it is the combination of the 'encoding' and the 'fileencoding' setting, in rare cases also 'termencoding' may be involved. 'encoding' specifies how your terminal is setup, 'fileencoding' specifies how the file is written, respectively read if the setting is changed and the file reloaded. If they differ, conversion occurs. Normally, 'encoding' is set according to the environment encountered, so setting that to en_US.UTF-8 or alike already does it. If you don't have an utf-8 environment and are working in a latin1 environment, you may have to use the ``:e ++enc=utf-8 filename'' command to load the file if you want to be able to display the decoded characters, otherwise you may of course also just look at the encoded characters. Writing files in encoding=latin1 is also no problem if you can live without decoded display. I'm not sure how detection works under Windows, the GUI version should work flawlessly, the terminal version might be a pain.. you may have to specify encoding=ucs-2le (for little endian). For details see the extensive :h utf-8 help page in Vim. 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 ;-) Eike -- OOo/SO Calc core developer. Number formatter bedevilled i18n transpositionizer. GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
