<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>69322</bug_id>
          
          <creation_ts>2004-10-28 14:28 0000</creation_ts>
          <short_desc>python ebuild does not support wide char type functions</short_desc>
          <delta_ts>2006-09-02 05:03:17 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Core system</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          <bug_file_loc>http://www.python.org</bug_file_loc>
          
          <keywords>Inclusion</keywords>
          <priority>P1</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>caglar@pardus.org.tr</reporter>
          <assigned_to>python@gentoo.org</assigned_to>
          <cc>baris@uludag.org.tr</cc>

      

      
          <long_desc isprivate="0">
            <who>caglar@pardus.org.tr</who>
            <bug_when>2004-10-28 14:28:56 0000</bug_when>
            <thetext>Python [ 2.3.x series ] can handle wide chars, but current ebuilds not use this functions properly. For example in tr_TR.UTF-8 locale, upper case of &quot;i&quot; is differ than &quot;I&quot; ( correct one is I WITH THE DOT ABOVE ), and lower case of &quot;I&quot; is differ than &quot;i&quot; ( correct one is LATIN SMALL LETTER DOTLESS I ) but if wide char support is not enabled then python converts them into &quot;I&quot; and &quot;i&quot; respectively, which is wrong.

Maybe a local USE flag can be implemented and used in ebuild. ( Patch is written by Baris Metin &lt;baris@uludag.org.tr&gt; )</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>caglar@pardus.org.tr</who>
            <bug_when>2004-10-28 14:29:54 0000</bug_when>
            <thetext>Created an attachment (id=42802)
python-2.3.4-wctype.patch

written by Baris Metin (baris@uludag.org.tr)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2004-10-29 02:09:49 0000</bug_when>
            <thetext>i&apos;d support adding it as a default option and not underneath a useflag. we&apos;ll consider this for python-2.4</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>lanius@gentoo.org</who>
            <bug_when>2005-04-24 16:14:06 0000</bug_when>
            <thetext>what&apos;s the status of this?
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2005-04-26 05:13:15 0000</bug_when>
            <thetext>well, upon further investigation, there were soem comments about wctype causing problems for certain locales, and a proposal to remove that switch for later versions of python.

so i&apos;m not so sure about adding this switch in now.

https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1076790&amp;group_id=5470&amp;atid=105470
http://mail.python.org/pipermail/python-dev/2004-December/050193.html</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>caglar@pardus.org.tr</who>
            <bug_when>2005-04-26 05:48:05 0000</bug_when>
            <thetext>Because of this problem, i suggested to implement a use flag, so decision may made by user( all Turkish spoken users need this to correct case operations ). I think &quot;unicode&quot; flag suitable for this situation like this;

if use unicode; then
	myconf=&quot;${myconf} --with-wctype-functions&quot;
fi

what u think?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2005-04-26 06:05:22 0000</bug_when>
            <thetext>unicode isn&apos;t a suitable flag in this case, if it is only for the turkish locale. the problems that they describe seem to be quite serious (toupper() and tolower() giving the wrong output), but i&apos;m not sure whether it applies to the turkish locale. 

i&apos;m not quite sure what the status of linguas support is, but maybe using that to enable it would be better. the unicode is used for many other languages like chinese and japanese that don&apos;t require wctype support for normal operations.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>caglar@pardus.org.tr</who>
            <bug_when>2005-04-26 06:34:44 0000</bug_when>
            <thetext>After talked with kloeri in irc, i just send an email to python-dev to get status of wctype support in Python. As soon as they reply, ill also update here...</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2006-09-02 05:03:17 0000</bug_when>
            <thetext>Reference: http://mail.python.org/pipermail/python-dev/2005-April/052968.html

There was never a suitable conclusion to this. One possible solution would
probably be only enabling this for the turkish locale, but I really don&apos;t
want to do that.

REOPEN if a suitable solution can be found.

</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>42802</attachid>
            <date>2004-10-28 14:29 0000</date>
            <desc>python-2.3.4-wctype.patch</desc>
            <filename>python-2.3.4-wctype.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIHB5dGhvbi0yLjMuNC5lYnVpbGQub3JpZwkyMDA0LTEwLTI5IDAwOjEzOjE5LjgzNzE5MzA0
MCArMDMwMAorKysgcHl0aG9uLTIuMy40LmVidWlsZAkyMDA0LTEwLTI5IDAwOjIyOjEzLjczNTAy
ODIzMiArMDMwMApAQCAtMTEyLDYgKzExMiwxMSBAQAogCQkmJiBteWNvbmY9IiR7bXljb25mfSAt
LWVuYWJsZS11bmljb2RlPXVjczIiIFwKIAkJfHwgbXljb25mPSIke215Y29uZn0gLS1lbmFibGUt
dW5pY29kZT11Y3M0IgogCisJIyB1c2UgLS13aXRoLXdjdHlwZS1mdW5jdGlvbnMgZm9yIHRyX1RS
Wy5VVEYtOF0KKwlpZiB1c2Ugd2NoYXI7IHRoZW4KKwkJbXljb25mPSIke215Y29uZn0gLS13aXRo
LXdjdHlwZS1mdW5jdGlvbnMiCisJZmkKKwogCXNyY19jb25maWd1cmUKIAogCWVjb25mIC0td2l0
aC1mcGVjdGwgXAo=
</data>        

          </attachment>
    </bug>

</bugzilla>