|
From: Joachim E. <joa...@gm...> - 2006-05-03 06:28:34
|
Hi John,
Since it seems to work for me, could you please check which encoding you us=
e.
("Regional Settings", "File Encoding for A" etc.)
Since you're under Windows I recommend the "System"-encoding, except if you=
r=20
file was encoded differently. (KDiff3 doesn't yet detect the encoding=20
automatically, but that's planned for a future version.)
In KDiff3-0.9.89 the default-encoding would be the systems default (i.e.=20
"System" on Windows), but if you had 0.9.88 installed previously then the=20
setting might still be UTF-8.
Cheers,
Joachim
Am Montag, 1. Mai 2006 18:13 schrieb John W Greenley Jr:
> My source has a "=AC" (x'AC') within it.
> (If you can't see it here, it looks like a horizontal bar with a short
> vertical descender on the right side. Sometimes called a "Lazy J", often
> used as a NOT charactor on IBM EBCDIC systems.)
>
> Windows 2000 r5.00.2195 Service Pack 4
> KDiff3 0.9.89
>
> Comparing the following two line:
>
> #1
> % &EXEC-DLI-REL-OPR-5 =3D "NE=AC=3D"
> #2
> % &EXEC-DLI-REL-OPR-5 =3D "NE=3D"
> (The "=AC" is between the NE and the " in line #1)
>
> KDIFF3 reports that the "files have equal text but are not binary equal."=
=20
> The KDiff3 display omits the "=AC".
> Other editors and applications do show the "=AC".
>
> More important, in a 3way compare/merge, Kdiff 3 neither reports the
> presence of the "=AC" NOR saves it in the merged output.
>
> Am I missing a setting or option somewhere?
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> Kdiff3-user mailing list
> Kdi...@li...
> https://lists.sourceforge.net/lists/listinfo/kdiff3-user
|