[gtkmm] Gtkmm-forge digest, Vol 1 #698 - 2 msgs

[gtkmm-forge-request lists sourceforge net]

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-admin lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 143447] New:  - glibmm has gtkmm's .spec file. (bugzilla-daemon bugzilla gnome org)
   2. [Bug 142138]  - Gtk::FileChooser::get_filename() should return std::string (bugzilla-daemon bugzilla gnome org)

--__--__--

Message: 1
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Mon, 31 May 2004 10:23:05 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 143447] New:  - glibmm has gtkmm's .spec file.

http://bugzilla.gnome.org/show_bug.cgi?id=143447
gtkmm | build | Ver: 2.4

           Summary: glibmm has gtkmm's .spec file.
           Product: gtkmm
           Version: 2.4
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: build
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: exor iclub nsu ru


I've tried to build Fedora core 1 rpm of glibmm and after I've put .spec and
rpmbuild -ba glibmm.spec, I've found that it requires gtkmm sources.

# sudo rpmbuild --target=athlon -ba glibmm.spec
Building target platforms: athlon
Building for target athlon
error: File /usr/src/redhat/SOURCES/gtkmm-2.4.1.tar.gz: No such file or directory

It seems like glibmm distribution is provided with wrong glibmm.spec.in.

PS: Hope this would be helpfull.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


--__--__--

Message: 2
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Mon, 31 May 2004 19:21:11 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 142138]  - Gtk::FileChooser::get_filename() should return std::string

http://bugzilla.gnome.org/show_bug.cgi?id=142138
gtkmm | general | Ver: 2.4





------- Additional Comments From daniel elstner gmx net  2004-05-31 19:21 -------
No, doing that would break ABI.  The ABI includes the behavior of the library
functions too, not just the ability to link with any library of the same ABI
version.

Also, applying Glib::filename_to_utf8() and Glib::filename_from_utf8() *does*
work regardless of the fact that the return type should be std::string for
clarity.  A Glib::ustring can contain invalid UTF-8 (or else validate() would be
useless) -- you just aren't allowed to use any methods apart from validate(),
is_ascii(), bytes(), empty(), raw(), operator std::string(), c_str(), data() and
the copy constructor.

Note that there is a reason why the Gtk::FileChooser interface operates directly
in the filesystem encoding:  Many users still use some legacy character set for
filenames but aren't aware of the G_FILENAME_ENCODING environment variable. 
Worse yet, they might be using UTF-8 encoded filenames on their system partition
but don't have the utf8 mount option specified in /etc/fstab for floppy and
cdrom drives (even I didn't use that flag until very recently -- simply because
I wasn't aware of it).  Thus, the app must be able to cope with invalid byte
sequences in filenames.  Those bytes of course have to be escaped in order to
display the filename, but that shouldn't stop the app from working.

Last but not least I don't think gtkmm should change what is cleary a design
decision in GTK+ (apart from language-specific considerations of course).

What we need is a prominent NOTE in the documentation of each and every
Gtk::FileChooser function that takes or returns filenames (it appears that all
of them are affected).  This note should explain the fact that the gtkmm API is
broken and mistakingly uses Glib::ustring where it shouldn't.  It should also
mention that you have to call Glib::filename_to_utf8() before displaying the
filename, and that Glib::filename_from_utf8() has to be used before a filename
obtained from Gtk::Entry or the like is passed to Gtk::FileChooser.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



--__--__--

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest