buglibiconv - Bugs: bug #37504, libiconv-1.14 can't convert from...

 
 

bug #37504: libiconv-1.14 can't convert from 'C' to 'UTF-8'

Submitted by:  Alan Hourihane <alanh>
Submitted on:  Thu 04 Oct 2012 01:26:18 PM UTC  
 
Category: OtherSeverity: 3 - Normal
Item Group: NoneStatus: Not a Bug
Privacy: PublicAssigned to: Bruno Haible <haible>
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Thu 21 Feb 2013 10:53:03 AM UTC, comment #6:

Hi Bruno,

I'm not sure how to fix, but if you can guide me here then I can make appropriate changes.

Thanks.

Alan Hourihane <alanh>
Tue 09 Oct 2012 02:45:00 PM UTC, comment #5:

Bruno - any comments on this one ? Thanks.

Alan Hourihane <alanh>
Sat 06 Oct 2012 12:40:44 PM UTC, comment #4:

Doing this on linux, and the problem doesn't reproduce, as we're not using libiconv there, and using glibc's internals.

Are we sure this isn't a libiconv bug ?

Alan Hourihane <alanh>
Sat 06 Oct 2012 12:32:14 PM UTC, comment #3:

Mmm, it comes down to just this....

bash# export LC_CTYPE=C
bash# pkg-config --atleast-pkgconfig-version 0.9.0
Conversion from character set 'C' to 'UTF-8' is not supported

Looks like glib uses libcharset. I've seen mention that using LC_CTYPE=C is valid. On this webpage...

http://ereimer.net/programs/charsets-cp1252-utf8.htm

Maybe the bug is in libcharset ?

Alan Hourihane <alanh>
Sat 06 Oct 2012 08:13:51 AM UTC, comment #2:

Well, pkg-config 0.27.1 uses glib, and so it must be glib's fault.

Alan Hourihane <alanh>
Sat 06 Oct 2012 12:25:27 AM UTC, comment #1:

> I'm not sure whether the configure script is incorrect,
> or whether libiconv should be fixed to deal with 'C'.


'C' is not a valid encoding name. Moreover the 'C' locale uses
different encoding on different systems: Some use US-ASCII
(such as glibc systems), some use UTF-8 (such as Mac OS X),
and both are POSIX compliant.

Most probably some software tries to extract the locale encoding
of a locale by looking at the locale name, not by invoking
locale_charset() or nl_langinfo(CODESET), and infers a locale
encoding of "C". This logic is wrong and needs to be fixed.

Bruno Haible <haible>
Project AdministratorIn charge of this item.
Thu 04 Oct 2012 01:26:18 PM UTC, original submission:

This is a generic problem, really as 'C' is less than the minimum characters iconv checks for in aliases.h.

The problem stems from a few configure scripts use this in them...

# NLS nuisances
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE

Then later when running pkg-config-0.27.1 which is built with libiconv, this happens....

checking pkg-config is at least version 0.9.0... Conversion from character set 'C' to 'UTF-8' is not supported
no

I'm not sure whether the configure script is incorrect, or whether libiconv should be fixed to deal with 'C'.

Alan Hourihane <alanh>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by haible (Posted a comment)
  • -unavailable- added by alanh (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 24 Nov 2016 12:38:49 AM UTChaibleCategoryNone=>Other
    Sat 06 Oct 2012 12:25:27 AM UTChaibleStatusNone=>Not a Bug
      Assigned toNone=>haible
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1