A
andrew.may
Guest
Currently the scratchpad encodes its files in the host JVM's default text file encoding & not the workspaces one. This is particularly nasty because the scratchpad view does seem to render in the workspace's default. e.g. If JVM default is cp1252, but workspace default is UTF8, you can enter a UTF8 character into scratchpad source, but will get codepage problems when you try to run or save the scratchpad source (because the source is saved as cp1252 first).
Continue reading...
Continue reading...