Community
Participate
Working Groups
For any text file, the colouring and formatting in Eclipse looks great. It would be really useful if the colouring and formatting could be captured and exported to an HTML file. Obviously this is only going to work for text-based resources (rather than any GUI based ones) but the editor could easily spew out a table with a single cell-per-line, and also put the fontify-colourings in that are used to generate the comments etc. in the editor-of-your-choice. For example, having a Java file: import java.util.*; /** * No comment */ public class Thing { could be generated as: <TABLE> <TR><TD><SPAN class="keyword">import</SPAN> <SPAN class="class">java.util.*</SPAN>;</TD></TR> <TR><TD><SPAN class="comment">/**</SPAN></TD></TR> <TR><TD><SPAN class="comment"> *</SPAN></TD></TR> <TR><TD><SPAN class="comment"> *</SPAN></TD></TR> <TR><TD><SPAN class="keyword">public class</SPAN> <SPAN class="class">Thing,</SPAN></TR></TR> </TABLE> where the definitions could be done in an attached/generated/in-line stylesheet. Of course, it doesn't even have to be that flexible; you could just read off the colours from the JFace colourings and use that with a <FONT> tag instead. It would also help in writing nicely coloured tutorials ;-)
Sounds like a perfect opportunity for a contribution.
Here's a workaround (that doesn't currently work because of bug 64498)... Before code folding was added, it used to be that you could select all, copy, and paste into MS Word or something, and the syntax coloring was maintained. This won't work in eclipse 3.0, but if you are running a much older version of eclipse, this will still work. From MS Word, you can save as HTML or whatever you like.
It still does work: simply disable folding before copying
*** Bug 93065 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.