Re: [Kdiff3-user] Symbols Are Stipped Out During Merge

[Matus L. <mat...@ko...>]

Thanks for the reply, Joachim. I will use 0.9.96 until you fix these=20
defaults; I don't want any less experienced developers (or anyone else by=20
mistake) to use an incorrect encoding during merge and have all the=20
characters stripped again from the code.

Why would it strip any of these characters anyway? Regardless of the=20
encoding, it should keep any special characters as is if it doesn't=20
recognize them, no?

Cheers,

Matus





Joachim Eibl <joa...@gm...>

14/10/2005 00:37
14/10/2005 09:37 ZE2
Please respond to joachim.eibl
=20
        To:     kdi...@li...
        cc:     Matus Lipka <mat...@ko...>
        Subject:        Re: [Kdiff3-user] Symbols Are Stipped Out During=20
Merge


Am Mittwoch, 12. Oktober 2005 20:54 schrieb Matus Lipka:
> I have found that 0.9.88 strips out characters such as =B5 or =B0 during
> merge. Also, you cannot even see them when you do a simple diff. 0.9.86
> doesn't have this problem.
>
> Thanks,
>
> Matus

Hi Matus,

Version 0.9.88 supports several encodings and the preselected choice is=20
UTF-8.
Please enter the KDiff3-options dialog and select the regional-settings=20
tab=20
and change the encoding.
The local encoding is shown at the top as a hint. Probably it's best for=20
you=20
to select that.
(If you still sometimes use an older version <=3D0.9.86 then you might have=
=20
to=20
reselect this every time when switching back to a newer version.)

The next version of KDiff3 will preselect the local encoding for new=20
KDiff3=20
users.

Cheers,
Joachim