Can't compare two XML files. "Unknown encoding" error
is thrown. Necessary files are attached.
BTW, why isn't it possible to use "Edit with unpacker"
option from editor in "Manual Unpacking" mode to
quickly select necessary filter?
1st file to compare
winmerge 188.8.131.52 config
unable to select XML mode from editor
2nd error window
1st error window
Logged In: YES
It must have been tedious for you to upload them all
separately, and it's likewide tedious for us to download
them all individually; in the future, I recommend using
7-zip, or some such tool.
The "Edit with Unpacker" menu item is for use from directory
view; it doesn't work from edit view (as you observed).
Your bug sounds like
BUG [ 1326628 ] Compare XML files with iso-8859-2 encoding
which has now been fixed in cvs.
I'm testing with your files now.
Ok, the cvs has my patch, so it knows about ISO encodings,
but not Microsoft proprietary encodings, but it passes them
through, so with cvs version, you still get the message box,
but the unpacking succeeds. This change was made on
2005-11-22, so it should be available in the latest
2005-11-23 WinMerge experimental release 184.108.40.206 (cvs)
Anatoly Techntonik, you forgot to post your version info
(which is requested on the New Bug page, because it is a
plague of our lives that bug submitters keep omitting this
most crucial info) -- could you please test with WinMerge
220.127.116.11 experimental version?
Logged In: YES
elsapo, as of
File Added 157730: config.txt 2005-11-27 21:01
you may find this info below
config.txt winmerge 18.104.22.168 config Download
Tested once more with 22.214.171.124 - the same thing - "unknown
encoding" and "file not unpacked" message boxes are still shown.
I cannot reproduce the reported error, neither with cvs
trunk (WinMerge.exe, 8-bit, debug), nor with the 126.96.36.199
(re: version info - I apologize, I was wrong, you had
included the entire config file)
Are you using Russian Windows, but you've set your Regional
preferences to United States, and locale to English?
I believe I've diagnosed all open issues here, as follows.
The full fix for this really needs both
PATCH: [ 1335128 ] Ignore uninstalled codepages
which I just applied to cvs trunk today, in order to avoid
user winding up with blank editor window, which is a
terrible outcome, and also
windows codepages support
which I added to DisplayXmlFiles 2005-12-01 (and forgot to
make a patch for), in cvs trunk.
So, this is fixed in cvs trunk, but not in branch, and fixed
version is not yet available in an experimental release.
Also, the fix to DisplayXmlFiles was done on 2005-11-22,
which fixes the problem with unpacking failing, but the
binary dll (in Plugins/dlls) was not updated until
2005-11-27, so it missed the 188.8.131.52 experimental release.
Great! Put a notice here when the new version will be
available, so I can test it too.
(as for windows - I'm using english w2k with russian system
locale and english (U.S) locale set for current user)
Logged In: YES
I hope I have time to make next experimental release next
Perry, is it possible to merge your fixes to 2.4 branch too?
Seems more and more people are really starting to use that
xml plugin so it would be nice to fix these bugs in branch
(for next stable release) too.
re: backport fixes to 2.4
Yes, it's possible, but I think it would be more convenient
to first apply
PATCH [ 1371384 ] Move Expat maps into WinMerge src
to the cvs trunk, and then backport the result to 2.4 --
because that moves all the expat map files, so it would be
easier to put them into final locations and then backport them?
Independently of that, I'll make a 2.4 version of the patch
(1335128/Ignore uninstalled codepages) that I aplied today,
to avoid blank editor screen, and post it on that patch.
Sounds nice. Unfortunate reality is that 2.5/2.6 stable
release cannot happen before summer - lots of things to do
still. But I can make new 2.4.x releases when needed. So
without backporting these fixes most users have to wait for
an year to get them..