libxmlplusplus-general — Open discusions about libXML++

Re: [libxml++] Charset conversion error -- ignoring encoding declaration?

[Murray C. <mu...@mu...>]

On Thu, 2007-11-29 at 12:48 +0000, Hugo Mills wrote:
>    I've done a bit more poking, and it's rejecting the same character
> after running through xmllint 

But does xmllint complain about the document at all?

-- 
mu...@mu...
www.murrayc.com
www.openismus.com

Re: [libxml++] Charset conversion error -- ignoring encoding declaration?

[Murray C. <mu...@mu...>]

On Wed, 2007-11-28 at 19:42 +0000, Hugo Mills wrote:
> Hi,
> 
>    I'm trying to use the SAX parser from libxml++ to read a simple XML
> file generated from a third-party program. At the head of the file is
> an XML declaration specifying the charset encoding:
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> 
>   A short distance into the file is the following text:
> 
> <sub-title lang="en">Highlights of the final of the Grand Slam of Darts, played over the best of 35 legs. The winner will be crowned the inaugural champion and receive a cheque for &#xA3;80,000. [S]</sub-title>
> 
>    (Just in case that's got mangled in transit, that's the
> entity/character literal 0xa3, for the UK Pound symbol in ISO-8859-1).
> 
>    When I pass this to libxml++, I get a Glib::Error thrown,
> complaining about "Invalid byte sequence in conversion input". It
> seems that libxml++ is reading the &#A3; and converting it to a byte,
> then trying to interpret that as UTF-8, which it isn't. I've tried
> converting the input chunk before I pass it to the parser (using
> Glib::convert), but obviously that isn't working, as it's processing
> the entity as its component characters, rather than converting it to a
> byte sequence.

What does xmllint say?

>    How do I handle this input correctly with libxml++? Do I have to
> preprocess each chunk manually to convert the character entities
> before passing it to the parser, or is there some way of persuading
> the SaxParser to do it?
> 
>    Thanks,
>    Hugo.

-- 
mu...@mu...
www.murrayc.com
www.openismus.com

Re: [libxml++] Charset conversion error -- ignoring encoding declaration?

[Hugo M. <hug...@ca...>]

On Wed, Nov 28, 2007 at 07:42:38PM +0000, Hugo Mills wrote:
>    When I pass this to libxml++, I get a Glib::Error thrown,
> complaining about "Invalid byte sequence in conversion input". It
> seems that libxml++ is reading the &#A3; and converting it to a byte,
> then trying to interpret that as UTF-8, which it isn't. I've tried
> converting the input chunk before I pass it to the parser (using
> Glib::convert), but obviously that isn't working, as it's processing
> the entity as its component characters, rather than converting it to a
> byte sequence.
> 
>    How do I handle this input correctly with libxml++? Do I have to
> preprocess each chunk manually to convert the character entities
> before passing it to the parser, or is there some way of persuading
> the SaxParser to do it?

   As a follow-up, I have tried converting the character entities in
two different ways, both failing in the same manner as above:

1) Convert entity to bytes; use Glib::convert to go from ISO-8859-1 to
UTF8.

2) Convert entity to bytes; use Glib::convert to go from ISO-8859-1 to
UTF8; convert new bytes back to entities.

   Surely this can't be so difficult to use. The input text is
well-formed, and accurately reports its character set. What am I doing
wrong, that libxml++ fails to cope with it?

   Hugo, getting frustrated.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
         --- Is it true that "last known good" on Windows XP ---         
                            boots into CP/M?                             

[libxml++] Charset conversion error -- ignoring encoding declaration?

[Hugo M. <hug...@ca...>]

   Hi,

   I'm trying to use the SAX parser from libxml++ to read a simple XML
file generated from a third-party program. At the head of the file is
an XML declaration specifying the charset encoding:

<?xml version="1.0" encoding="ISO-8859-1"?>

  A short distance into the file is the following text:

<sub-title lang="en">Highlights of the final of the Grand Slam of Darts, played over the best of 35 legs. The winner will be crowned the inaugural champion and receive a cheque for &#xA3;80,000. [S]</sub-title>

   (Just in case that's got mangled in transit, that's the
entity/character literal 0xa3, for the UK Pound symbol in ISO-8859-1).

   When I pass this to libxml++, I get a Glib::Error thrown,
complaining about "Invalid byte sequence in conversion input". It
seems that libxml++ is reading the &#A3; and converting it to a byte,
then trying to interpret that as UTF-8, which it isn't. I've tried
converting the input chunk before I pass it to the parser (using
Glib::convert), but obviously that isn't working, as it's processing
the entity as its component characters, rather than converting it to a
byte sequence.

   How do I handle this input correctly with libxml++? Do I have to
preprocess each chunk manually to convert the character entities
before passing it to the parser, or is there some way of persuading
the SaxParser to do it?

   Thanks,
   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
    --- "What are we going to do tonight?" "The same thing we do ---     
            every night, Pinky.  Try to take over the world!"            

[libxml++] Navigating through the XML document

[Pedro S. <pas...@gm...>]

Hi,

I'm using libxml++ to access  files. I want my program to execute two tasks:

1) The program must in a cycle, load files and search for an attribute 
in a certain node. If the attribute contain the desired value, it must 
show the name of the file.
I want to understand how can I do this, without memory leeches.

2) I don't want to read the file sequentially. That is, when load the 
file, I want to read directly the specified node.
In the examples in manual  of libxml++ ,  I only see examples of  
sequential access methods. Can anyone help me in performing the desired 
actions? If I'm wrong, can anyone point me out the solution?

Thanks in advance
    Pedro Sousa

Re: [libxml++] Problem catching parser exceptions on Win32

[Tony C. <to...@co...>]

Tony Cowderoy wrote:
> I think I've (2.20.0), built it with msys/mingw and it seems to work OK.
> 
That should have read:

I think I've fixed it myself.  I've downloaded the latest libxml++ 
source (2.20.0), built it with msys/mingw and it seems to work OK.

Tony Cowderoy

Re: [libxml++] Problem catching parser exceptions on Win32

[Tony C. <to...@co...>]

Tony Cowderoy wrote:
> I have a problem catching parser exceptions on Win32 
> (XP/msys/mingw/gcc).  This is causing me difficuties with error handling 
> in libglademm and also when using libxml++ directly.  I've reproduced 
> the problem in a minimal example.

I think I've (2.20.0), built it with msys/mingw and it seems to work OK.

Tony Cowderoy

[libxml++] Problem catching parser exceptions on Win32

[Tony C. <to...@co...>]

I have a problem catching parser exceptions on Win32 
(XP/msys/mingw/gcc).  This is causing me difficuties with error handling 
in libglademm and also when using libxml++ directly.  I've reproduced 
the problem in a minimal example.

The following code catches an exception OK when built and run on Debian 
etch, but fails to do so when built and run on XP SP2.  Does anyone have 
any idea why or what I can do to fix it?

Here's the code:

include <iostream>
#include <libxml++/libxml++.h>

int main (int argc, char *argv[])
{
    xmlpp::DomParser parser;
     try {
       parser.parse_memory("xxxxxxxxx<root_node/>");
     }
     catch (...) {
         std::cerr << "Caught an exception from the parser." << std::endl;
     }
}

On Debian etch, the output is:

> Entity: line 1: parser error : Start tag expected, '<' not found
> xxxxxxxxx<root_node/>
> ^
> Caught an exception from the parser.

On Win XP/msys, the output is:

> This application has requested the Runtime to terminate it in an unusual way.
> Please contact the application's support team for more information.
> Entity: line 1: parser error : Start tag expected, '<' not found
> xxxxxxxxx<root_node/>
> ^

Note that the exception hasn't been caught this time.

The Win 32 environment is:
Windows XP SP2
MSYS 1.0.11
MinGW 5.1.3
gcc 3.4.5
Gtk 2.10.11-1 (from gladewin32.sourceforge.net)
gtkmm 2.10.11-1 (from ftp.gnome.org)

The Debian build environment uses gcc 4.1.2 .

The build command line on Debian etch was:

> gcc xmlpp_test01.cc -o xmlpp_test01 `pkg-config libxml++-2.6 --cflags --libs`

Replacing gcc with g++ works OK as well.

On Win XP/msys it was:

> g++ xmlpp_test01.cc -o xmlpp_test01 `pkg-config libxml++-2.6 --cflags --libs`

Running it as gcc instead causes problems.

Any help will be much appreciated.

Tony Cowderoy

[libxml++] Adding child with certain order

[Arthur M. <art...@gm...>]

SGkuCgpJwrRtIHByb2Nlc3NpbmcgYSB4bWwgZmlsZSBpbiB3aGljaCBjaGlsZHJlbiBzaG91bGQg
YmUgYWRkZWQgaW4gY2VydGFpbgpvcmRlci4KCkZvciBleGFtcGxlOgoKVGhlc2Ugc2hvdWxkIG5v
dCBiZSB2YWxpZDoKPHJvb3Q+CiAgICA8Ym9vaz4KICAgICAgICA8Y2hhcHRlcj48L2NoYXB0ZXI+
CiAgICAgICAgPGNoYXB0ZXI+PC9jaGFwdGVyPgogICAgICAgIDxwcmVmYWNlPjwvcHJlZmFjZT4K
ICAgIDwvYm9vaz4KPC9yb290PgoKYXMgPHByZWZhY2U+IHNob3VsZCBiZSB0aGUgZmlyc3QgY2hp
bGQgb2YgPGJvb2s+LiBUaGUgZmFjdCBpcyBJIGdldCB0aGlzIHhtbApmaWxlIGFscmVhZHkgd3Jp
dHRlbiBhbmQgb25seSB0aGUgPGNoYXB0ZXI+cyBub2RlcyBhcmUgdGhlcmUuIE9ubHkgZHVyaW5n
CnJ1bnRpbWUgSSBjYW4gZ2V0IGluZm9ybWF0aW9uIHJlbGF0aXZlIHRvIHByZWZhY2UsIHdoZW4g
SSBhZGQgaXQgd2l0aApib29rX25vZGUtPmFkZF9jaGlsZCgicHJlZmFjZSIpLCBtYWtpbmcgaXQg
ZXhpc3QgYXMgb24gdGhlIGV4YW1wbGUgYWJvdmUgKGFzCnRoZSBsYXN0IGNoaWxkKS4KCkhvdyBj
b3VsZCBJIG1hbmFnZSB0byBpbnNlcnQgPHByZWZhY2U+IGJlZm9yZSA8Y2hhcHRlcj5zPyBJcyB0
aGVyZSBhIHNwZWNpYWwKbWV0aG9kIGZvciBpbnNlcnRpbmcgYSBjaGlsZCBhdCBhIGNlcnRhaW4g
cG9zaXRpb24gaW5zaWRlIGl0cyByb290IG5vZGUKdHJlZT8KClRoYW5rcyBpbiBhZHZhbmNlLiBJ
IHJlYWxseSB1cmdlIGZvciBhbiBlZmZlY3RpdmUgc29sdXRpb24uCgpSZWdhcmRzLApBcnRodXIK
ClBTLjogdGhlIG5vZGUgbmFtZXMgaGVyZSBhcmUgZmljdGl0aW91cyBmb3Igc2ltcGxpZnlpbmcg
cHVycG9zZXMuCg==

[libxml++] create_root_node and memory leak

[Fabian J. <fab...@gm...>]

Hi,

I'm using libxml++ 2.18.1 and I have some memory leak. Maybe is there a
mistake...

I have a pointer to a xmlpp::Document which has a root and some children.
I have to reset it and so I do MyDoc.create_root_node("MyNewRoot");
This make memory leak. I think it loose last root node.

To correct this I delete and renew my document before creating my new root.

Can I do it better?
Is it normal create_root_node loose the last root node?

[libxml++] libxml++ in CGI scipt breaks Apache connection

[Andrej v. d. Z. <ma...@ya...>]

Hi,

I am sorry if this already has been asked...

I am trying to use libxml++ to parse XML-requests in a
CGI script. The problem is that somehow the connection
is broken in the xmlpp::Node::find(xpath) method and
then I get a ".Premature end of script headers:
mbrace.cgi" message in my Apache log. 

Does the library raise any SIGPIPE signal? Is this a
known issue? More important, what is the best thing to
solve this issue? Blocking all signals in the
main-thread didn't work out for me. 

Thanks,
Andrej


      ___________________________________________________________ 
Want ideas for reducing your carbon footprint? Visit Yahoo! For Good  http://uk.promotions.yahoo.com/forgood/environment.html

[libxml++] Writing to file

[Arthur M. <art...@gm...>]

SGkgdGhlcmUuCgpJwrRtIHBhcnNpbmcgYSBYTUwgZmlsZSB3aXRoIERPTSBQYXJzZXIgYW5kIEnC
tGxsIG5lZWQgdG8gY2hhbmdlIG5vZGVzCm5hbWVzIGFuZCBhdHRyaWJ1dGVzLiBBcyBET00gUGFy
c2VyIHJlYWRzIHRoZSBmaWxlIGludG8gbWVtb3J5LCB0aGUKb25seSB0aW1lIHRoaXMgY2hhbmdl
cyB3aWxsIHRha2UgZWZmZWN0IGlzIHdoZW4gSSB1c2UgRG9jdW1lbnTCtHMKd3JpdGVfdG9fZmls
ZSBvciB3cml0ZV90b19maWxlX2Zvcm1hdHRlZD8KCklmIHNvLCB3aGVuIHJlLXJlYWQgYSBub2Rl
IHRoYXQgaGFkIGJlZW4gY2hhbmdlZCBJwrRsbCBnZXQgdGhlIHVwZGF0ZWQKdmFsdWUgb3IgbmFt
ZSwgcmlnaHQ/CgpJwrRtIHN0aWxsIHVuZGVyc3RhbmRpbmcgdGhlIHN0cnVjdHVyZSBvZiBsaWJ4
bWwrKyBhbmQgaG93IGl0IHdvcmtzLgoKVGhhbmtzIGluIGFkdmFuY2UuCkFydGh1cgo=

[libxml++] Problem while using Libxml

[Radheshyam M. <rdm...@re...>]

Hi,=0A     I have a problem while using libxml.I download libxml .It requir=
e some other library glib and glibmm .From where ,i can download these libr=
ary.While using it gives error "Cannot open include file: 'glib/gmacros.h':=
 "Please suggest me.=0A=0AThanks and Regard,=0ARadheshyam Mishra=0A

[libxml++] Method to get text children with content

[Arthur M. <art...@gm...>]

Hi there.

Just as a suggestion, do you think it would be useful for libxml++ to
have a method of tthe class Node to get children that are NOT  ( (text
AND white space) OR comment ) ? This should be useful for getting
children that have content.

I have to do this testing almost everywhere I need to get children.

Would like to hear your opinion.

Regards,
Arthur

Re: [libxml++] Cryptography for reading data

[Murray C. <mu...@mu...>]

On Sun, 2007-09-23 at 00:05 -0300, Arthur Maciel wrote:
> Hi there.
> 
> Really don´t know if it is off-topic, but I would like to know if
> Glibmm provides any tool to cryptograph a file and to decryptograph
> it.
> 
> I´m reading XML files with libxml++ and would like to give only to my
> program the ability to understand the XML file (and of course to the
> program that generates it), so the data, if intercepted, cannot be
> understood.

No, there's nothing in libxml++, glibmm, or gtkmm for this.

Whatever technique you use, you can just give the unecrypted string to
libxml++ and encrypt the string that libxml++ gives you. 

-- 
mu...@mu...
www.murrayc.com
www.openismus.com

[libxml++] Cryptography for reading data

[Arthur M. <art...@gm...>]

SGkgdGhlcmUuCgpSZWFsbHkgZG9uwrR0IGtub3cgaWYgaXQgaXMgb2ZmLXRvcGljLCBidXQgSSB3
b3VsZCBsaWtlIHRvIGtub3cgaWYKR2xpYm1tIHByb3ZpZGVzIGFueSB0b29sIHRvIGNyeXB0b2dy
YXBoIGEgZmlsZSBhbmQgdG8gZGVjcnlwdG9ncmFwaAppdC4KCknCtG0gcmVhZGluZyBYTUwgZmls
ZXMgd2l0aCBsaWJ4bWwrKyBhbmQgd291bGQgbGlrZSB0byBnaXZlIG9ubHkgdG8gbXkKcHJvZ3Jh
bSB0aGUgYWJpbGl0eSB0byB1bmRlcnN0YW5kIHRoZSBYTUwgZmlsZSAoYW5kIG9mIGNvdXJzZSB0
byB0aGUKcHJvZ3JhbSB0aGF0IGdlbmVyYXRlcyBpdCksIHNvIHRoZSBkYXRhLCBpZiBpbnRlcmNl
cHRlZCwgY2Fubm90IGJlCnVuZGVyc3Rvb2QuCgpUaGFua3MgaW4gYWR2YW5jZS4KQXJ0aHVyIE1h
Y2llbAo=

[libxml++] Getting content of a "element"(?) node

[Arthur M. <art...@gm...>]

SGkgdGhlcmUuCgpJwrR2ZSBiZWVuIHN1aW5nIGxpYnhtbCsrIGFuZCBJIGhhdmUgdGhlIGZvbGxv
d2luZyBxdWVzdGlvbjoKQXQgdGhlIHczc2Nob29scy5vcmcgKGh0dHA6Ly93d3cudzNzY2hvb2xz
LmNvbS94cGF0aC94cGF0aF9ub2Rlcy5hc3ApCnRoZXJlIGlzIGEgZGVmaW5pdGlvbiBvZiBub2Rl
IHR5cGVzLCBhcyBmb2xsb3dpbmc6CgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLVN0YXJ0IG9m
IHNpdGUgZXh0cmFjdCAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPD94bWwgdmVyc2lv
bj0iMS4wIiBlbmNvZGluZz0iSVNPLTg4NTktMSI/Pgo8Ym9va3N0b3JlPgo8Ym9vaz4KICA8dGl0
bGUgbGFuZz0iZW4iPkhhcnJ5IFBvdHRlcjwvdGl0bGU+CiAgPGF1dGhvcj5KIEsuIFJvd2xpbmc8
L2F1dGhvcj4KICA8eWVhcj4yMDA1PC95ZWFyPgogIDxwcmljZT4yOS45OTwvcHJpY2U+CjwvYm9v
az4KPC9ib29rc3RvcmU+JwoKRXhhbXBsZSBvZiBub2RlcyBpbiB0aGUgWE1MIGRvY3VtZW50IGFi
b3ZlOgo8Ym9va3N0b3JlPiAgKGRvY3VtZW50IG5vZGUpCjxhdXRob3I+SiBLLiBSb3dsaW5nPC9h
dXRob3I+ICAoZWxlbWVudCBub2RlKQpsYW5nPSJlbiIgIChhdHRyaWJ1dGUgbm9kZSkKLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tRW5kIG9mIHNpdGUgZXh0cmFjdCAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQoKCkluIGxpYnhtbCsrIHdoYXQgdHlwZSBpcyB0aGUgPGF1dGhvcj4g
bm9kZT8gSG93IGNvdWxkIEkgcmV0cmlldmUgaXRzCmNvbnRlbnQsIGFzIGVsZW1lbnRzIG5vZGVz
IGluIGxpYnhtbCsrIGRvZXMgbm90IGhhdmUgdGhlCidnZXRfY29udGVudCgpJyBtZXRob2Q/CgpJ
biBhIHNpbWlsYXIgY2FzZSwgScK0dmUgdHJpZWQgZXh0cmFjdGluZyB0aGUgaW5mb3JtYXRpb24g
dXNpbmcKVGV4dE5vZGUsIENvbnRlbnROb2RlIGFuZCBFbGVtZW50Tm9kZSwgd2l0aG91dCBzdWNj
ZXNzLgoKVGhhbmtzLApBcnRodXIK

Re: [libxml++] filename encoding

[Murray C. <mu...@mu...>]

On Mon, 2007-09-10 at 15:25 +0200, Philipp Klaus Krause wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Throughout gtkmm they use std::string for filenames, while using
> Glib::ustring for all other strings.
> Why does libxml++ use Glib::ustring for filenames (as argument to
> write_to_file, etc)?

Yes, it probably should use std::string:

/** Write the document to a file.
 * @param filename
 * @param encoding If not provided, UTF-8 is used
 */
void write_to_file(const Glib::ustring& filename, 
  const Glib::ustring& encoding = Glib::ustring());

But I don't think we can change that now. I will add a comment for the
future, in case we can ever break the ABI.

-- 
mu...@mu...
www.murrayc.com
www.openismus.com

[libxml++] filename encoding

[Philipp K. K. <pk...@sp...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Throughout gtkmm they use std::string for filenames, while using
Glib::ustring for all other strings.
Why does libxml++ use Glib::ustring for filenames (as argument to
write_to_file, etc)?

Philipp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG5UXUbtUV+xsoLpoRAgUGAJ9/ypd3BrB2JI99xfEqE1vIBRQ0BQCgjDYJ
pQHVnF4KwFZBqzN9kOyXflM=
=4IU3
-----END PGP SIGNATURE-----

[libxml++] Creating xml files

[Arthur M. <art...@gm...>]

Hi there.

I'm new to XML and would like to know if libxmlpp just parses XML or it does
also have any facility to write XML files.

Thanks.
Arthur

[libxml++] Compiling @64bits on Solaris 10

[ale <il...@fa...>]

Hi guys!
I'm attempting to compile libxml++ on this system:
 
SunOS aldebaran 5.10 Generic_125100-10 sun4u sparc SUNW,Ultra-Enterprise
 
with SunStudio 12. No problem compiling at 32 bits. I'm in troubles with 64
bits compilation. I started the configure tool with this switch:
 
 
./configure CXXFLAGS=-m64 LDFLAGS=-m64
 
 
but when I run make I always have the following error:
 
 
Making all in libxml++
Making all in parsers
Making all in exceptions
Making all in nodes
Making all in io
/bin/bash ../libtool --tag=CXX --mode=link CC   -m64  -m64 -o
libxml++-1.0.la -rpath /usr/local/lib -version-info 1:4:0 attribute.lo
dtd.lo document.lo noncopyable.lo  keepblanks.lo     parsers/libparsers.la
exceptions/libexceptions.la  nodes/libnodes.la  io/libio.la  -lxml2
-lpthread -lz -lm -lsocket -lnsl
CC -G -nolib -hlibxml++-1.0.so.1 -o .libs/libxml++-1.0.so.1.0.4
.libs/attribute.o .libs/dtd.o .libs/document.o .libs/noncopyable.o
.libs/keepblanks.o -Qoption ld -z -Qoption ld
allextract,parsers/.libs/libparsers.a,exceptions/.libs/libexceptions.a,nodes
/.libs/libnodes.a,io/.libs/libio.a -Qoption ld -z -Qoption ld defaultextract
-lxml2 -lpthread -lz -lm -lsocket -lnsl
ld: warning: file parsers/.libs/libparsers.a(parser.o): wrong ELF class:
ELFCLASS64
ld: warning: file exceptions/.libs/libexceptions.a(exception.o): wrong ELF
class: ELFCLASS64
ld: warning: file nodes/.libs/libnodes.a(cdatanode.o): wrong ELF class:
ELFCLASS64
ld: warning: file io/.libs/libio.a(outputbuffer.o): wrong ELF class:
ELFCLASS64
ld: fatal: file .libs/attribute.o: wrong ELF class: ELFCLASS64
ld: fatal: File processing errors. No output written to
.libs/libxml++-1.0.so.1.0.4
*** Error code 1
make: Fatal error: Command failed for target `libxml++-1.0.la'
Current working directory /export/home/jack/libxml++-1.0.5/libxml++
...
 
 
Can you please help me compiling @ 64 bit this library?
 
Thanks in advance!!!
 
Bye
Alessandro

Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++

[Trappel M. <mar...@ks...>]

> -----Original Message-----
> From: lib...@li...=20
> [mailto:lib...@li...]=20
> On Behalf Of Lo=EFc Joly
> Sent: Tuesday, August 28, 2007 6:14 PM
> To: lib...@li...
> Subject: Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++
>=20
> > De la part de Tom Browder
>=20
> > A couple of years ago I participated in a thread here discussing=20
> > decoupling libxml++'s dependency on the whole of Glib and friends.
> > Among other things discussed was possible substitutes for ustring.
> >=20
> > Now I've come back to ask if there has been any thought to=20
> proposing=20
> > that ustring be made a member of the Boost library (for possible=20
> > future incorporation into the C++ standard library).
>=20
> UTF8 string are certainly considered for the C++ standard.=20
> They would probably not look like Glib::ustring, however, but=20
> like an instanciation of basic_string with a specific=20
> char_trait. Here are last versions of the standard evolution=20
> papers about UTF8 support in the standard:
>=20
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2295.
html (UTF8 litteral) http://www.open-> =
std.org/jtc1/sc22/wg21/docs/papers/2007/n2149.html (UTF8=20
> char)=20
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2238.
html (UTF8 in the SL)
>=20
> --
> Lo=EFc
>=20

Pfff ... Too me it seems it specifically hasn't been addressed:

[quote =
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2238.html]
(...) items are conspicuously missing from this paper: UTF-8 support, =
(...)
(...) One way to provide UTF-8 support would be a new string class whose =
interface is very different from basic_string, (...)
(...) Some form of UTF-8 support is important because there's an awful =
lot of real-world code that uses UTF-8 even internally, and programmers =
certainly need UTF-8 to interface with third-party libraries like =
libxml2. (...)
[/quote]


best regards / mit freundlichen Gr=FC=DFen,
Martin Trappel
=20

Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++

[<Loi...@re...>]

> De la part de Tom Browder

> A couple of years ago I participated in a thread here discussing=20
> decoupling libxml++'s dependency on the whole of Glib and friends.
> Among other things discussed was possible substitutes for ustring.
>=20
> Now I've come back to ask if there has been any thought to proposing=20
> that ustring be made a member of the Boost library (for possible=20
> future incorporation into the C++ standard library).

UTF8 string are certainly considered for the C++ standard. They would =
probably not look like Glib::ustring, however, but like an instanciation =
of basic_string with a specific char_trait. Here are last versions of =
the standard evolution papers about UTF8 support in the standard:

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2295.html (UTF8 =
litteral) =
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2149.html (UTF8 =
char) http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2238.html =
(UTF8 in the SL)

--
Lo=EFc

Re: [libxml++] Glib::ustring, lBoost Lib, and libstdc++

[Trappel M. <mar...@ks...>]

Seems a great idea to me ... I probably could start using libxml++ then =
:-)

Though that will probably for the boost / glib people to decide?

best regards / mit freundlichen Gr=FC=DFen,
Martin Trappel
=20

> -----Original Message-----
> From: lib...@li...=20
> [mailto:lib...@li...]=20
> On Behalf Of Tom Browder
> Sent: Tuesday, August 28, 2007 1:45 AM
> To: lib...@li...
> Subject: [libxml++] Glib::ustring, lBoost Lib, and libstdc++
>=20
> A couple of years ago I participated in a thread here=20
> discussing decoupling libxml++'s dependency on the whole of=20
> Glib and friends.
> Among other things discussed was possible substitutes for ustring.
>=20
> Now I've come back to ask if there has been any thought to=20
> proposing that ustring be made a member of the Boost library=20
> (for possible future incorporation into the C++ standard library).
>=20
> I've looked around a fair amount and it seems to me that=20
> ustring is a strong candidate for that honor.  I've searched=20
> the archives here and have seen no such discussion, so=20
> perhaps there may be interest.
>=20
> Comments?
>=20
> Thanks.
>=20
> -Tom
>=20
> Tom Browder
> Niceville, Florida
> USA
>=20
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and=20
> a browser.
> Download your FREE copy of Splunk now >> =20
> http://get.splunk.com/ _______________________________________________
> Libxmlplusplus-general mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general
>=20

[libxml++] Glib::ustring, lBoost Lib, and libstdc++

[Tom B. <tom...@gm...>]

A couple of years ago I participated in a thread here discussing
decoupling libxml++'s dependency on the whole of Glib and friends.
Among other things discussed was possible substitutes for ustring.

Now I've come back to ask if there has been any thought to proposing
that ustring be made a member of the Boost library (for possible
future incorporation into the C++ standard library).

I've looked around a fair amount and it seems to me that ustring is a
strong candidate for that honor.  I've searched the archives here and
have seen no such discussion, so perhaps there may be interest.

Comments?

Thanks.

-Tom

Tom Browder
Niceville, Florida
USA