After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 215415 - Virtual Folders Editor: display of non-ascii symbols is broken
Virtual Folders Editor: display of non-ascii symbols is broken
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other other
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-11-15 03:59 UTC by Dmitry G. Mastrukov
Modified: 2013-09-10 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch (677 bytes, patch)
2001-11-15 13:20 UTC, Zbigniew Chyla
none Details | Review

Description Dmitry G. Mastrukov 2001-11-15 03:59:55 UTC
Description of Problem:
In Virtual Folders Editor in the list of folders all non-ascii symbols are
displayed as utf8 garbage. In Edit (Create) folder window it's OK and in
the folders tree it's OK too.
Comment 1 Zbigniew Chyla 2001-11-15 13:20:37 UTC
Created attachment 40670 [details] [review]
Patch
Comment 2 Zbigniew Chyla 2001-11-15 14:01:39 UTC
Why not 1.0? We already have trivial patch for this bug. Are you going
to release 1.0 in the next 24 hours?
Comment 3 Vlad 2001-11-15 14:22:50 UTC
Yes, why not 1.0? I confirm that the patch is correct, and moreover
it's trivial. Why for not include it for 1.0?
 The bug affects all non-ascii symbols - i.e. words with letters with umlauts
will be displayed in funky and unreadable way.
Comment 4 Dan Winship 2001-11-15 17:24:41 UTC
Unless there is some horrible (reliably crashing for lots of people,
losing data, etc) bug in RC2, RC2 will become 1.0.

If we hold up 1.0 until the stream of simple bugfixes for small
bugs stops, we'll never release it. And we're *NOT* going to
release 1.0 with patches that haven't been tested as part of a
release candidate, no matter how simple they look. (Although I
confess, I can't imagine how this patch would hurt either.)

Besides, there are already worse i18n problems that aren't going
to be fixed in time for 1.0 anyway, right?
Comment 5 Vlad 2001-11-16 08:32:51 UTC
No, I don't know about any i18n-related bugs beside this and #15379
(that is BY ORDERS MORE IMPORTANT), but both are very trivial.
 Why are you that principal? If you confirm that this is innocent patch,
why not commit it right now? You behave like religious people :)
Comment 6 trow 2001-11-16 15:05:59 UTC
Amen!
Comment 7 Not Zed 2001-11-27 21:49:51 UTC
patch applied.  although the patch was wrong somehow (the changelog
bit), use cvs diff -u in future
Comment 8 Zbigniew Chyla 2001-11-27 22:08:05 UTC
What's wrong with the patch? I always use "diff -up" (+ editing by hand)
Maybe you mean "-0,0" part? It allows you to add new ChangeLog entry
always at the top of the file.