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 712484 - Bind IptcData::detectCharset
Bind IptcData::detectCharset
Status: RESOLVED OBSOLETE
Product: gexiv2
Classification: Other
Component: implementation
unspecified
Other All
: Low normal
: ---
Assigned To: Gexiv2 Maintainers
Gexiv2 Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-08 12:46 UTC by Jim Nelson
Modified: 2018-05-22 12:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Charles Lindsay 2013-11-16 14:44:24 UTC 


---- Reported by jim@yorba.org 2010-12-07 16:46:00 -0800 ----

Original Redmine bug id: 2928
Original URL: http://redmine.yorba.org/issues/2928
Searchable id: yorba-bug-2928
Original author: Jim Nelson
Original description:

The IPTC interface offers a handy detectCharset() method to determine which
encoding should be used for all strings.



---- Additional Comments From valencia-maint@gnome.bugs 2013-01-02 14:28:00 -0800 ----

### History

####

#1

Updated by Jim Nelson 11 months ago

  * **Category** set to _implementation_



--- Bug imported by chaz@yorba.org 2013-11-16 14:45 UTC  ---

This bug was previously known as _bug_ 2928 at http://redmine.yorba.org/show_bug.cgi?id=2928

Unknown version " in product gexiv2. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product gexiv2. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution
Comment 1 GNOME Infrastructure Team 2018-05-22 12:32:53 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gexiv2/issues/12.