|Re: [pdt-dev] PDT 2.0 and use of encodings for remote debug|
I am looking at the various areas where encoding applies and the current configurable options available in PDT 2.0
The output encoding looks like it only applies to output from the php script which will be displayed in the Debug and Browser output views.
The transfer encoding applies to the binary data that flows over the wire (so must be in sync with the encoding used by the debug engine when sending information such as stack frame names, variable names etc). It also looks like the transfer encoding is used to convert php string information to Java.lang.String for display in the variables display.
Is this correct ?
One of the issues I have is that in php strings (ignoring php6 at present) can contain binary or character data. The character data and the encoding that correctly represents that data is known to the php program and could very well be different to the transfer encoding.
A Common problem I see for both Zend and XDebug debug environments is a user may want to have a binary representation of a php string in the debugger or may want to display the string based on a user selected encoding.
Is anyone looking at this issue for PDT 2.0 ? I haven't had the opportunity to investigate it but it seems to me that the solution should be common for any installed debugger.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
pdt-dev mailing list