TAP parsing problem with SAVOT

[Pierre Fernique]

Dear SAVOT developers,

It seems that some DACHS TAP VOTable outputs are using a VOTable 
serialization not (yet) supported by SAVOT 4. It is clearly related to 
the BASE64 encoding (with UTF-16 strings) that DACHS used by default. 
Parsing bug ? or just a feature not yet implemented ? Concretely, a 
large fraction of TAP servers (50%?) are not accessible by SAVOT due to 
this problem.

Also, do you plan to support BINARY2 in a close future ? I imagine that 
DACHS could evolve to BINARY2 in a next release...

Cheers
Pierre

---

Here an example to reproduce the problem

http://voparis-tap-planeto.obspm.fr/__system__/tap/run/tap/sync?REQUEST=doQuery&LANG=ADQL&QUERY=SELECT+*+FROM+TAP_SCHEMA.columns+where+table_name+=+'tap_schema.columns'+

java.lang.ArrayIndexOutOfBoundsException: 26
     at 
cds.savot.model.interpreter.UnicodeCharInterpreter.decodePrimary(UnicodeCharInterpreter.java:43)
     at 
cds.savot.model.interpreter.CharInterpreter.decodePrimary(CharInterpreter.java:1)
     at 
cds.savot.model.interpreter.BinaryFieldInterpreter.decode(BinaryFieldInterpreter.java:132)
     at cds.savot.binary.DataBinaryReader.next(DataBinaryReader.java:379)
     at cds.aladin.TapManager.binaryColumnReader(TapManager.java:885)
     at cds.aladin.TapManager.populateColumns(TapManager.java:778)
     at cds.aladin.TapManager$3.run(TapManager.java:463)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)