From noreply at sourceforge.net Thu Apr 18 01:24:33 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 17 Apr 2013 16:24:33 -0700 Subject: [Expat-bugs] [ expat-Bugs-3611241 ] Turning off utf16 support Message-ID: <3Zrffq6VngzS2n@mail.python.org> Bugs item #3611241, was opened at 2013-04-17 16:24 Message generated for change (Tracker Item Submitted) made by csiki You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611241&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: www.libexpat.org Group: Feature Request Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andr?s Csikv?ri (csiki) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Turning off utf16 support Initial Comment: It would be very nice if we could able to turn off the utf16 support for an even smaller code size in a future release. Like XML_MIN_SIZE macro, we could define an XML_NO_UTF16 macro. Thank you, Andr?s ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611241&group_id=10127 From noreply at sourceforge.net Sat Apr 20 17:46:22 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 20 Apr 2013 08:46:22 -0700 Subject: [Expat-bugs] [ expat-Bugs-3611466 ] Can't install lib64expat1-dev Message-ID: <3ZtJLm40CwzSt3@mail.python.org> Bugs item #3611466, was opened at 2013-04-20 08:46 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611466&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build control Group: Test Required Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Greg Stein (gstein) Summary: Can't install lib64expat1-dev Initial Comment: wani at tester:~$ sudo apt-get install lib64expat1-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: lib64expat1-dev:i386 : Depends: lib64expat1:i386 (= 2.1.0-1ubuntu1) but it is not going to be installed Depends: gcc-multilib:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. wani at tester:~$ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611466&group_id=10127 From noreply at sourceforge.net Mon Apr 22 15:13:56 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 22 Apr 2013 06:13:56 -0700 Subject: [Expat-bugs] [ expat-Bugs-3611241 ] Turning off utf16 support Message-ID: <3ZvSsy4fJ1zSvY@mail.python.org> Bugs item #3611241, was opened at 2013-04-17 16:24 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611241&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None Group: Feature Request Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andr?s Csikv?ri (csiki) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Turning off utf16 support Initial Comment: It would be very nice if we could able to turn off the utf16 support for an even smaller code size in a future release. Like XML_MIN_SIZE macro, we could define an XML_NO_UTF16 macro. Thank you, Andr?s ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2013-04-22 06:13 Message: Are you referring to UTF-16 input, or output? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611241&group_id=10127 From noreply at sourceforge.net Wed Apr 24 21:18:07 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 24 Apr 2013 12:18:07 -0700 Subject: [Expat-bugs] [ expat-Bugs-3611241 ] Turning off utf16 support Message-ID: <3ZwrsF6w2Hz7Lkw@mail.python.org> Bugs item #3611241, was opened at 2013-04-17 16:24 Message generated for change (Comment added) made by csiki You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611241&group_id=10127 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Feature Request Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andr?s Csikv?ri (csiki) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Turning off utf16 support Initial Comment: It would be very nice if we could able to turn off the utf16 support for an even smaller code size in a future release. Like XML_MIN_SIZE macro, we could define an XML_NO_UTF16 macro. Thank you, Andr?s ---------------------------------------------------------------------- >Comment By: Andr?s Csikv?ri (csiki) Date: 2013-04-24 12:18 Message: Both. Output: because of wchar_t size problems, its hard to use, and not practical at all: the real "character" length still can be fewer than the number of short ints, so the programmer does not win anything, if he want to handle everything correctly. Input: even if it's part of the standard, does not seems to be widely used today (I don't think I would be able to find an utf16 xml on the web...) The whole utf16 standard seems to me a dead end. ---------------------------------------------------------------------- Comment By: Fred L. Drake, Jr. (fdrake) Date: 2013-04-22 06:13 Message: Are you referring to UTF-16 input, or output? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=3611241&group_id=10127 From 12msccsaali at seecs.edu.pk Mon Apr 15 06:46:47 2013 From: 12msccsaali at seecs.edu.pk (Amir Ali) Date: Mon, 15 Apr 2013 04:46:47 -0000 Subject: [Expat-bugs] Undefined Reference Errors in ExpatXMLParser.cc file Message-ID: I am using OMNET++ 4.1, when I build my project iCanCloud then there are 16 errors occurred during building project and all are related to expat_parse. Can you suggest me what is the actual problem ? . I shall be very thankful to you for this act of kindness. I got following errors... " Description Resource Path Location Type undefined reference to `XML_GetErrorCode' ExpatXMLParser.cc /iCanCloud/src/Util/expatmm-1.0.2/src line 173 C/C++ Problem undefined reference to `XML_Parse' ExpatXMLParser.cc /iCanCloud/src/Util/expatmm-1.0.2/src line 169 C/C++ Problem undefined reference to `XML_Parse' ExpatXMLParser.cc /iCanCloud/src/Util/expatmm-1.0.2/src line 185 C/C++ Problem undefined reference to `XML_ParserCreate' ExpatXMLParser.cc /iCanCloud/src/Util/expatmm-1.0.2/src line 63 C/C++ Problem ................................. " Regards, AMIR -------------- next part -------------- An HTML attachment was scrubbed... URL: