I reproduced the bug in the situation when a string variable in the debugged
application contains special characters like tabulators or new-lines. These
special characters are displayed by debugger as squares.

(I was not able to reproduce the situation when the string variable would
contain "/ta" or "\ta" as stated in the bug description. These strings were
displayed correctly by both JPDA and jdk1.1 debuggers.)

Tabulators and new-lines are correctly retrived from the debugged application.
Then they are displayed as squares on three places:

1) in the name of the watch node
--------------------------------
This is caused by javax.swing.tree.DefaultTreeCellRenderer.paint(Graphics)
method called by the method
org.openide.explorer.view.NodeRenderer.paint(Graphics).

2) in the property "value" of the watch node
--------------------------------------------
This is caused by java.awt.Graphics.drawString(...) method called by the method
org.openide.explorer.propertysheet.SheetButton.paint(Graphics).

3) in the tooltip in the editor window
--------------------------------------
This is caused by JLabel displaying the tooltip. This JLabel is filled with the
string in org.netbeans.editor.ext.ToolTipSupport.setToolTipText(String).

All these three problems are caused by JDK classes that are not able to show the
special characters. Forte gives them in all tree cases correct string and they
show tabulators and new-lines as squares.

One possible work-around would be to replace tabulators by \t and new-lines by
\n. However, it can't be done in the debugger because the multiline editor of
the property sheet value would then show the string as one line as well. And I
don't want to do it on the mentioned three places, because they are very
frequently used and the change could affect some other parts of the IDE.

It isn't problem replace tabulators and new lines character of watches values by
symbol '\n' and '\t' only for it. It is better. Property editor then has one
line for these strings or it  can be writen special property editor for these
strings too.

Resolved for 3.3.x or earlier, no new info since then -> closing.