utf 8 - Java XMLReader not clearing multi-byte UTF-8 encoded attributes -

-

i've got strange situation sax contenthandler being handed bad attributes xmlreader. document being parsed utf-8 multi-byte characters inside xml attributes. appears happen these attributes being accumulated each time handler called. rather being passed in succession, concatenated onto previous node's value.

here example demonstrates using public data (wikipedia).

public class mycontenthandler extends org.xml.sax.helpers.defaulthandler {      public static void main(string[] args) {         try {             org.xml.sax.xmlreader reader = org.xml.sax.helpers.xmlreaderfactory.createxmlreader();             reader.setcontenthandler(new mycontenthandler());             reader.parse("http://en.wikipedia.org/w/api.php?format=xml&action=query&list=allpages&apfilterredir=redirects&apdir=descending");          } catch (exception ex) {             ex.printstacktrace();         }     }      public void startelement(string uri, string localname, string qname, org.xml.sax.attributes attributes) {         if ("p".equals(qname)) {             string title = attributes.getvalue("title");             system.out.println(title);         }     } }

update: complete example produces (apologies cantonese speakers vulgar output):

𩧢 𩧢𨳒 𩧢𨳒🛅 𩧢𨳒🛅🛄 𩧢𨳒🛅🛄🛃 𩧢𨳒🛅🛄🛃🛂 𩧢𨳒🛅🛄🛃🛂🛁 𩧢𨳒🛅🛄🛃🛂🛁🛀 𩧢𨳒🛅🛄🛃🛂🛁🛀🚿 𩧢𨳒🛅🛄🛃🛂🛁🛀🚿🚾

does have clue happening , how fix it? comes in document doesn't match happening debug through snippet.

seems bug in jre included version of xerces (com.sun.org.apache.xerces.internal.parsers.saxparser). below notes.

the version bundled jre 1.6.0_24, v2.4.0, v2.5.0, v2.6.0 does do accumulation of attributes.

xerces-j v1.4.4 does not appear have bug.

xerces2-j v2.6.1, v2.6.2, v2.9.0, 2.11.0 does not appear have bug.

you can tell versions tested bisecting version history. appears fixed between v2.6.0 , v2.6.1. i'm kind of surprised jre hasn't been updated fixed in main xerces 7 years ago!


Comments

Post a Comment

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

-
what’s difference between $_server['path_info'] , $_server['orig_path_info'] ? how use them? when run print_r($_server) , path_info , orig_path_info not present in array. why not? how can enable them? i have read php manual on them, still don’t understand them. the path_info variable present if invoke php script this: http://www.example.com/phpinfo.php/hello_there it's /hello_there part after .php script. if don't invoke url that, there won't $_server["path_info"] environment variable. the porig_ prefix uncommon. path_info standard cgi-environment variable, , should never prefixed. did read that? (there issues around php3/php4 if invoked php interpreter via cgi-bin/ - hardly has such setups today.) for reference: http://www.ietf.org/rfc/rfc3875
Read more

fortran - Function return type mismatch -

-
i'm attempting recode old c++ program in fortran make use of lapack (i'm aware c++ have lapack++, i'm having lot of trouble installing it, gave up). i didn't have problems compilation, when had variables declared real . when started coding section of program required lapack, found parameters passed dsyev need double precision . tried change double precision (including changing hard coded numbers double precision counterparts, i.e. 0.0 -> 0.0d0) when try compile, following error of functions , subroutines i've written: error: return type mismatch of function <function> @ (1) (real(4)/real(8)) i'm not sure coming from, in program has been changed double precision. for example, i've declared following: double precision :: alpha(3),d(3),zeta1,zeta2 double precision :: a1(3),a2(3),d1(3),d2(3) double precision :: pi pi = 3.14159265359d0 alpha = (/0.109818d0, 0.405771d0, 2.22766d0/) d = (/0.444635d0, 0.535328d0, 0.154329d0 /) 10 i=1,3 ...
Read more

queue - mq_receive: message too long -

-
i implementing communication between 2 processes using queue. problem when call function mq_receive, error: message long. i have done following: struct mq_attr attr; long size = attr.mq_msgsize; .... // initializing queue "/gateway" int rc = mq_receive(gateway, buffer, size, &prio); if print size value, size=1, while when print same size program (got same mechanism), not long integer ( -1217186280 )... how can solve error?....so while size = 1, believe it's right "message long" why 1? p.s. have tried put : int rc = mq_receive(gateway, buffer, sizeof(buffer), &prio); but no result. it seems need read docs more carefully. when call mq_receive should pass size of destination buffer. this size must greater mq_msgsize attribute of queue . in addition, seems have error in queue attributes initialisation makes proper mq_receive call impossible. here standard message queue session: fill mq_attr struct ( doc ): struct mq_a...
Read more