[wp-trac] [WordPress Trac] #9417: IPTC IIM IRB character encoding (UTF-8) misinterpreted as ISO-8859-1

[WordPress Trac]

#9417: IPTC IIM IRB character encoding (UTF-8) misinterpreted as ISO-8859-1
--------------------------------------------+-----------------------------
 Reporter:  kallewangstedt                  |       Owner:  westi
     Type:  defect (bug)                    |      Status:  reviewing
 Priority:  normal                          |   Milestone:  Future Release
Component:  Charset                         |     Version:  2.7.1
 Severity:  major                           |  Resolution:
 Keywords:  needs-unit-tests needs-refresh  |
--------------------------------------------+-----------------------------

Comment (by hakre):

 from php.ini-development (as of PHP 5.3.5), see the EXIF section:

 > [exif]
 > ; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as
 JIS.
 > ; With mbstring support this will automatically be converted into the
 encoding
 > ; given by corresponding encode setting. When empty
 mbstring.internal_encoding
 > ; is used. For the decode settings you can distinguish between motorola
 and
 > ; intel byte order. A decode setting cannot be empty.
 > ; http://php.net/exif.encode-unicode
 > ;exif.encode_unicode = ISO-8859-15
 >
 > ; http://php.net/exif.decode-unicode-motorola
 > ;exif.decode_unicode_motorola = UCS-2BE
 >
 > ; http://php.net/exif.decode-unicode-intel
 > ;exif.decode_unicode_intel    = UCS-2LE
 >
 > ; http://php.net/exif.encode-jis
 > ;exif.encode_jis =
 >
 > ; http://php.net/exif.decode-jis-motorola
 > ;exif.decode_jis_motorola = JIS
 >
 > ; http://php.net/exif.decode-jis-intel
 > ;exif.decode_jis_intel    = JIS

 I just stumbeled over that information, it might be that this might be
 related to a configuration issue as well.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9417#comment:38>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software