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 57691 - check error conditions in backend read/write/seek
check error conditions in backend read/write/seek
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: win32
1.3.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-win32 maintainers
Depends on:
Blocks:
 
 
Reported: 2001-07-17 21:57 UTC by Ron Steinke
Modified: 2013-11-24 01:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ron Steinke 2001-07-17 21:57:45 UTC 
Someone who understands the win32 backend needs to check that
the GIOChannelError error messages which replaced the old
GIOError error messages make sense.
Comment 1 Owen Taylor 2002-03-07 19:27:04 UTC 
Moving open 2.0.0 Win32 bugs to 2.0.1 milestone.
Comment 2 Owen Taylor 2002-03-25 22:24:33 UTC 
Moving 2.0.1 Win32 bugs to 2.0.2 milestone.
Comment 3 Owen Taylor 2002-12-16 20:12:07 UTC 
Would cause string changes, so best not done at this point.
(The error messages really could use improvement though)
Comment 4 Owen Taylor 2003-01-28 20:58:45 UTC 
Could be done for 2.2.x once the GNOME-2.2 string freeze
is over, but probably simplest to just do on HEAD.
Comment 5 Tor Lillqvist 2004-01-23 00:31:50 UTC 
I have forgotten what error messages (or status enum codes?) exactly 
this bug refers to. Ron, could you refresh my memory...?
Comment 6 Owen Taylor 2004-03-14 15:26:21 UTC 
Search for g_set_error() in giowin32.c; I think that's what
this bug refers to.

It turns out that the error strings in giowin32.c aren't currently 
marked for translation, but they actually should be for
consistency with GError usage in the rest of GLib.

(So, this shouldn't probably be changed before 2.4.1, which
is going to be a only-bugs update of 2.4.0 but since we don't have 
a 2.4.2 milestone, I'm putting it on 2.4.1 for now.)
Comment 7 Matthias Clasen 2013-11-24 01:33:55 UTC 
I don't think we will do anything here, after all these years.