[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Quick annotate diff uses wrong encoding, normal annotate view returns ERROR

From: Jens Seidel <jensseidel_at_users.sourceforge.net>
Date: 2007-03-15 15:21:56 CET

On Thu, Mar 15, 2007 at 09:00:32AM -0400, Mark Phippard wrote:
> On 3/15/07, Jens Seidel <jensseidel@users.sf.net> wrote:
> >I managed to fix my previous problems with subclipse 1.2.0 somehow and
> >found now a few problems in the annotate functionality.
> >
> >First of all the quick diff assumes the log message to be encoded in
> >latin1 instead of UTF-8 and displays "für" instead of "fr".
> >
> >I also noticed that the normal annotate operation does not work for
> >all files. For some it just opens a text editor containing "ERROR" and
> >adds the attached text to the log. It works for other files work as
> >expected.
> >
> >I'm using SVNKit, OpenSuse 10.1, Sun java 1.5.0_06, eclipse 3.3M5eh.
> I cannot really comment on the log issue (as I do not know). OK, one
> comment. I doubt we are making any assumptions in the code, are we sure
> that the quick diff tool tips can display UTF-8?

At least tooltips are able to display 8 bit characters as "für" shows.
I do not know what message encoding it assumes. If it's indeed latin1 it
whould be bad, since not every text could be displayed this way.
My system encoding is UTF-8, don't know where the wrong assumption of
latin1 (or pure ASCII?) comes from.
> As for not supporting all files, this is true. CVS has the same
> limitation. There are things (again that I do not know) that the editor has
> to support for the quick diff annotate to work. That is why the default
> preference for CVS and SVN is to prompt to pick which type of annotation to
> use. The old annotate method should still work for all files.

You misunderstood me. The old annotate method fails on some files, the
new one (quick view) works (as far as I tested) on all files!
> Again, I did not write this code, so if you know of ways that the CVS
> plug-in handles this differently, then let us know. For example, perhaps it
> is possible to figure out in advance if the editor supports the feature. I
> do not think you can, but maybe.

You are not a developer? OK, nevertheless I hope that someone confirms
my error or asks for other information so that either a bug report can be
opened or even better the error is simply fixed.

I try to avoid filling new bugs on the fly because my knowledge of Java
and eclipse is very very limited. Give me a proper C++ program and I can
do much more ...
(PS: Filling bugs for eclipse whould be a never ending story, each day I
recognize at least 10 problems, ranging from trivial stuff such as
"activated entry in a combo box is invisible because of wrong color
settings" to hard crashs (didn't happened the last day, but I still
expect one :-) I try to report most of it but it's real hard work and I
still need to be productive ...)


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Mar 15 15:21:01 2007

This is an archived mail posted to the Subclipse Users mailing list.